[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Problem designing complexType accepting a specified element and allowing

• To: "'xml-dev@l...'" <xml-dev@l...>
• Subject: Problem designing complexType accepting a specified element and allowing any others.
• From: Hess Yvan <yvan.hess@i...>
• Date: Thu, 11 Mar 2004 20:50:23 +0100

I want to design a complexType named "metadata" that forces the presence of
an "identifier" element and allows any others elements not predefined.
Moreover the "identifier" and the others elements can appear in any order
into the "metadata" element. Here are examples of valid xml instances:

<metadata xmlns="http://www.imtf.com/test">
  <identifier>urn:hsc:1234</identifier>
  <name>Hess Yvan</name>
</metadata>

<metadata xmlns="http://www.imtf.com/test">
  <subject>This is the subject</subject>
  <identifier>urn:hsc:1234</identifier>
  <title>This is the title</title>
</metadata>

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>


I get the following error with Xerces validation and a similar one with XSV
(it seems I violate the "Unique Particle Attribution"). 

[Error] choice.xsd:4:23: cos-nonambig: "http://www.imtf.com/test":identifier
and
 WC[##any] (or elements from their substitution group) violate "Unique
Particle
Attribution". During validation against this schema, ambiguity would be
created
for those two particles.
choice.xml: 571 ms (3 elems, 1 attrs, 0 spaces, 30 chars)

If I change my xml schema using sequence instead of choice as follow:

<xs:element name="metadata">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="identifier" type="xs:string"/>
      <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>

it works but in this case the "identifier" element must be at the FIRST
position and I don't want that !!! 

Please can you help me to solve this problem. I have no idea how to solve it
!!!

Regards. Yvan Hess

--------------------------------------------------------
XML file:

<?xml version="1.0" encoding="UTF-8"?>
<metadata xmlns="http://www.imtf.com/test"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.imtf.com/test choice.xsd">
   <identifier>urn:hsc:1234</identifier>
   <name>Hess Yvan</name>
</metadata>

--------------------------------------------------------
XML schema file:

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="http://www.imtf.com/test"
xmlns="http://www.imtf.com/test" xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified" attributeFormDefault="unqualified">
   <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>
</xs:schema>

• Follow-Ups:
  • Re: Problem designing complexType accepting a specified element and allowing any others.
    • From: "Chiusano Joseph" <chiusano_joseph@b...>
  • Re: Problem designing complexType accepting a specifiedelement and a llowing any others.
    • From: Mike Fitzgerald <mikefz@w...>

• Prev by Date: Re: C14n namespaces
• Next by Date: Re: W3C suckered by Microsoft?
• Previous by thread: C14n namespaces
• Next by thread: Re: Problem designing complexType accepting a specifiedelement and a llowing any others.
• Index(es):
  • Date
  • Thread