Skip to content

case sensitivity badly used #15

@domicoudin

Description

@domicoudin

When in a schema you define two elements with same name but not same case the last one is used in place of first one.
See attached exemple with elements a and A.
In xsddiagram, when showing content of element x we expect to see elements a and b.
Unfortunately we see elements A and b
Version of xsddiagram used is 1.1

capture

Content of my xsd:

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="x">
xs:complexType
xs:sequence
<xs:element ref="a"/>
<xs:element ref="b"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="a">
xs:complexType
xs:sequence
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="b">
xs:complexType
xs:sequence
<xs:element ref="A"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="A">
xs:complexType
xs:sequence
<xs:element ref="c"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="c">
xs:complexType
xs:sequence
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions