[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: NDR Review - Section 7.7
Greetings, I know we are not currently going to reconsider decisions already made; however, we do have to change the explanatory text around the xsd:choice rule (Section 7.7 - GXS9). It currently reads: ================================================== The xsd:choice compositor allows for any element declared inside it to occur in the instance document, but only one. As with the xsd:all compositor, this feature is inconsistent with business transaction exchanges and is not allowed in UBL. ================================================== I don't think this is true. As I had mentioned on yesterday's call, because an xsd:choice element can be contained within an xsd:sequence, it leads to no more uncertainty/variability in an instance than a "minOccurs='0'" does; therefore, I don't believe it is "inconsistent with business transaction exchanges". Comments? Thank You, Mike Grimley
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]