Good day,
java dom.Counter -v -s -f -n bindatalog.ruleml (or sax.Counter) produces the
following error for me:
[Error] atom_module.xsd:62:31: An internal error occurred while formatting
the following message:
mg-props-correct.2: Circular definitions detected for group ''{0}''.
Recursively following the {term} values of the particles leads to a particle
whose {term} is the group itself.
[Error] atom_module.xsd:62:31: src-redefine.6.2.1: No group in the redefined
schema has a name matching 'atom.extend'.
bindatalog.ruleml: 1492;40;0 ms (51 elems, 8 attrs, 0 spaces, 494 chars)
What's going on is that a content model originally defined as
<xs:group name="atom.extend">
<xs:sequence>
<xs:choice minOccurs="1" maxOccurs="unbounded">
<xs:element ref="ind"/>
<xs:element ref="var"/>
</xs:choice>
</xs:sequence>
</xs:group>
in http://www.ruleml.org/0.86/xsd/modules/atom_module.xsd is being redefined
to
<xs:redefine schemaLocation="datalog.xsd">
<xs:group name="atom.extend">
<xs:sequence>
<xs:choice minOccurs="2" maxOccurs="2">
<xs:element ref="ind"/>
<xs:element ref="var"/>
</xs:choice>
</xs:sequence>
</xs:group>
</xs:redefine>
in http://www.ruleml.org/0.86/xsd/bindatalog.xsd. (Note that bindatalog.xsd
actually redefines datalog.xsd which in turn includes atom_module.xsd.) As
far as I can tell, this is a valid restriction because the occurrence range
is being restricted from 1 or more to exactly 2 (i.e. binary, hence
bindatalog). The schemas validate okay with XSV 2.7-1, MSXML 4.0 and Saxon
8.0.
I'm using Xerces 2.6.2. Any help would be appreciated.
David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
