RE: [Xmldb-org-xupdate] Re: Xupdate XSD
Brought to you by:
reinhapa
From: Isidro V. V. <jv...@gm...> - 2005-08-19 15:01:00
|
Well, In the same document, but in section where the choice is defined (http://www.w3.org/TR/xmlschema-1/#element-choice) say that: <choice id = ID maxOccurs = (nonNegativeInteger | unbounded) : 1 minOccurs = nonNegativeInteger : 1 {any attributes with non-schema namespace . . .}> Content: (annotation?, (element | group | choice | sequence | any)*) </choice> And in http://xmlsoft.org/index.html we have this warning: "A partial implementation of XML Schemas Part 1: Structure is being worked on but it would be far too early to make any conformance statement about it at the moment". But I must admit I don't check the Schema of Schemas. Thank you for your alert. Isidro > -----Mensagem original----- > De: Kasimier Buchcik [mailto:kbu...@4c...] > Enviada: sexta-feira, 19 de Agosto de 2005 15:03 > Para: ML-xmldb-xupdate > Cc: Isidro Vila Verde > Assunto: Re: [Xmldb-org-xupdate] Re: Xupdate XSD > > 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 > > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.338 / Virus Database: 267.10.12/77 - Release Date: 18-08-2005 > -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.338 / Virus Database: 267.10.12/77 - Release Date: 18-08-2005 |