Re: [Xmldb-org-xupdate] Re: Xupdate XSD
Brought to you by:
reinhapa
From: Kasimier B. <kbu...@4c...> - 2005-08-19 14:07:42
|
Hi, On Fri, 2005-08-19 at 14:48 +0100, Isidro Vila Verde wrote: > Hi Kasimier, > > It seems that Libmxl2 don't have full support for XML Schema, but I change > the XSD a little bit to workaround with this Libxml2 limitation. This is not a limitation of Libxml2, but simply ruled out by the schema for schemas. Check out http://www.w3.org/TR/xmlschema-1/#normative-schemaSchema where we have <xs:complexType name="namedGroup"> which reflects the model group definition and contains <xs:complexType name="simpleExplicitGroup"> which prohibits occurences <xs:attribute name="minOccurs" use="prohibited"/> <xs:attribute name="maxOccurs" use="prohibited"/> The reason for ruling them out is that only the occurences of the model group definition _reference_ are used. More technically speaking, the particle which will correspond to the model group definition reference will point to the model group child of a model group definition. Actually the following construct: <group name="foo"> <choice ...> </choice> </group> does not produce any particles (particles hold the occurence information) at the component level. So there is just no component to store any occurence information for the above mentioned <choice>. If schema processors don't bark, then they probably don't catch this constraint and leave you unaware that your occurences were just skipped. By the way, what schema processor did you use ? Regards, Kasimier |