NEW ISSUE: Nested normative statements in 7.4.2

[Bryan Aupperle <aupperle@us.ibm.com>]

Target: Core Spec CD03-WD3

Description: Section 7.4.2 contains
this text:

If a ComplexType has content with two elements that have the same local name and the same targetNamespace, whether through declaration, extension, substitution, groups, or other means, the duplication MUST BE handled as follows [COR07040201]:

·        The ComplexType becomes a sequenced type, as if sdox:sequence="true" was declared.

·        A single property is used for all the elements with the same local name and the same targetNamespace. If the content model allows more than 1 instance of the element, then isMany=true. If, however, the elements are mutually exclusive (for example, they are single valued and on two sides of a xsd:choice group), then isMany=false.

·        If schema extension is used, the base type MAY be modified with sdox:sequence="true". Elements with name conflicts introduced in extensions require that the property in the extended base type MUST BE made many=true. [COR07040202]

This makes it look like COR07040202 is nested within COR07040201 which is not permissible  It also appears to mix MAY and MUST statements which is not desirable.

Proposal:  The formatting needs to be revised and the statements need to be separated.

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect
WW Center of Excellence for Enterprise Systems & Banking Center of Excellence Application Integration Architect

Research Triangle Park,  NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com