[
Lists Home |
Date Index |
Thread Index
]
Title: RE: [xml-dev] Problem designing complexType accepting a specified element and a llowing any others.
Yvan,
One solution in XML Schema would be to specify that the <xs:any> elements are in a different namespace using namespace="##other". This would mean that any additional elements you want to include must be from a different namespace and would avoid confusing the parser. It would mean that additional XML structures would need a namespace prefix.
Hope this helps if you want to maintain Schemas.
Jon
-----Original Message-----
From: Hess Yvan [mailto:yvan.hess@imtf.ch]
Sent: 11 March 2004 21:43
To: 'jcowan@reutershealth.com '
Cc: 'xml-dev@lists.xml.org '
Subject: RE: [xml-dev] Problem designing complexType accepting a specified element and a llowing any others.
John,
Thanks for your answer. Do you mean that there is NO solution to solve my problem using XML schema ? Are you sure about that because it will have a big impact on the project I am working on...
Yvan
-----Original Message-----
From: jcowan@reutershealth.com
To: Hess Yvan
Cc: xml-dev@lists.xml.org
Sent: 11.03.04 21:54
Subject: Re: [xml-dev] Problem designing complexType accepting a specified element and a llowing any others.
Hess Yvan scripsit:
> I implemented the following xml schema complexType but it doesn't
work:
>
> <xs:element name="metadata">
> <xs:complexType>
> <xs:choice minOccurs="0" maxOccurs="unbounded">
> <xs:element name="identifier" type="xs:string"/>
> <xs:any processContents="lax" minOccurs="0"
maxOccurs="unbounded"/>
> </xs:choice>
> </xs:complexType>
> </xs:element>
First of all, you are specifying a choice between an identifier element and any number of arbitrary elements, but the choice is itself repeated any number of times. So <ident/><ident/><ident/> will match. But even if you get past that problem, when an "identifier" element is seen, the schema validator can't tell if it matches the explicit xs:element declaration or the xs:any declaration. This is what the UPA rule means: an element has to match exactly one of the cases in a choice, and if it matches more than one, the schema is incorrect.
<propaganda>The RELAX NG schema language doesn't have this problem, and will handle this pattern correctly:
metadata = "element" identifier {xsd:string}
& element * - identifier {attribute * {text}*, ANY*}*
ANY = element * {attribute * {text}*, ANY*}
Here we clearly specify that "metadata" means an identifier element interleaved with any number of elements other than identifier elements (with the latter allowed to contain any attributes and any child elements). The effect of interleaving is that the identifier element may appear before, after, or mixed in with the other elements. </propaganda>
--
You are a child of the universe no less John Cowan
than the trees and all other acyclic http://www.reutershealth.com graphs; you have a right to be here. http://www.ccil.org/~cowan
--DeXiderata by Sean McGrath jcowan@reutershealth.com
-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription
manager: <http://www.oasis-open.org/mlmanage/index.php>
************************************************************************
DISCLAIMER
The information contained in this e-mail is confidential and is intended
for the recipient only.
If you have received it in error, please notify us immediately by reply
e-mail and then delete it from your system. Please do not copy it or
use it for any other purposes, or disclose the content of the e-mail
to any other person or store or copy the information in any medium.
The views contained in this e-mail are those of the author and not
necessarily those of Admenta UK Group.
************************************************************************
| 