Implement Unique Particle Attribution validation of complex types in XML Schemas

RESOLVED INVALID

Status

Core Graveyard
Web Services
RESOLVED INVALID
14 years ago
9 months ago

People

(Reporter: Doron Rosenberg (IBM), Assigned: Doron Rosenberg (IBM))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Assignee)

Description

14 years ago
http://www.w3.org/TR/xmlschema-1/#cos-nonambig

Under certain conditions, XML schema complex types cannot be validated against
because it is impossible to determine when a particle sequence ends, such as the
example below:

  <xs:element name="book">
    <xs:complexType>
      <xs:sequence minOccurs="0" maxOccurs="unbounded">
        <xs:element minOccurs="1" maxOccurs="2" name="title" type="xs:string"/>
        <xs:element name="title" type="xs:string"/>
        <xs:element name="author" minOccurs="0" type="xs:string"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>

The correct behavior is probably during loading of schemas to check for this and
throw an exception.
QA Contact: doronr → web-services
(Assignee)

Updated

2 years ago
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INVALID

Updated

9 months ago
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.