Closed Bug 272422 Opened 20 years ago Closed 8 years ago

Implement Unique Particle Attribution validation of complex types in XML Schemas

Categories

(Core Graveyard :: Web Services, defect)

Product:
Core Graveyard
Component:
Web Services
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: doronr, Assigned: doronr)

References

(
URL
)

Details

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
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.