Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#6 inconsistency between <atom id=""> and <peak atomRefs="">

open
nobody
None
5
2007-07-17
2007-07-17
Egon Willighagen
No

I think there is an inconsistency between the <atom id=""> and <peak
atomRefs=""/> attributes.

The first is defined as type idType (<xsd:pattern value="[A-Za-z][A-Za-z0-9\.
\-_]*"/>) while the second is defined as type atomIDType (<xsd:patterI think there is an inconsistency between the <atom id=""> and <peak
atomRefs=""/> attributes.

The first is defined as type idType (<xsd:pattern value="[A-Za-z][A-Za-z0-9\.
\-_]*"/>) while the second is defined as type atomIDType (<xsd:pattern
value="[A-Za-z_][A-Za-z0-9_\-]*(:[A-Za-z0-9_\-]+)?"/>).

While the first allows me to use the '.', the second does not, and visa versa,
the second allows me to use the ':', which is not allowed by the first type.

The ':' might be for namespacing, but the '.' is a problem in either case.

This applies to the beta1 of CML Schema 2.5 in SVN.n
value="[A-Za-z_][A-Za-z0-9_\-]*(:[A-Za-z0-9_\-]+)?"/>).

While the first allows me to use the '.', the second does not, and visa versa,
the second allows me to use the ':', which is not allowed by the first type.

The ':' might be for namespacing, but the '.' is a problem in either case.

This applies to the beta1 of CML Schema 2.5 in SVN.

Discussion