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

Ambiguous Content Models

• To: "'xml-dev@l...'" <xml-dev@l...>
• Subject: Ambiguous Content Models
• From: Max Chappell <max@m...>
• Date: Fri, 03 Oct 2003 11:42:33 +0100
• Organization: Maxxml Limited
• Reply-to: max@m...
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)

Hi,

Our users want a virtually wide open content model. However, there are 
the occasional exceptions..
Here is an example:

<xs:sequence minOccurs="1">
    <xs:sequence maxOccurs="unbounded">
        <xs:group ref="tns:GenericElements" minOccurs="0"/>
        <xs:element name="Person" type="tns:Person" minOccurs="0"/>
        <xs:element name="Location" type="tns:Loc" minOccurs="0"/>
    </xs:sequence>
    <xs:element name="Person" type="tns:Person"/>
    <xs:sequence maxOccurs="unbounded">
        <xs:group ref="tns:GenericElements" minOccurs="0"/>
        <xs:element name="Person" type="tns:Person" minOccurs="0"/>
        <xs:element name="Location" type="tns:Loc" minOccurs="0"/>
    </xs:sequence>
</xs:sequence>

In short, they want any element of the three elements in any order, as 
many or as few times as they want. However, they also want at least one 
person element to be present every time.
I think that the above is absolutely valid. However, the IBM Schema 
Quality Checker grumbles about amiguous content models with this.
I am on a new machine, so as yet have not been able to validate samples 
against this model using xerces etc.

Does anybody have any comments on the validity of the above? 

thanks

Max

• Follow-Ups:
  • Re: Ambiguous Content Models
    • From: David Carlisle <davidc@n...>
  • Re: Ambiguous Content Models
    • From: Eric van der Vlist <vdv@d...>

• Prev by Date: Re: Position Papers Available for W3C Workshop on Binary Interchange of XML Information Item Sets
• Next by Date: Re: Ambiguous Content Models
• Previous by thread: Fwd: [e-lang] Protocol implementation errors
• Next by thread: Re: Ambiguous Content Models
• Index(es):
  • Date
  • Thread