OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [wsrp] [errata #30] Where does the xsi:type attribute go on extensions?



Comment: #30. 6/20/03 (Interoperability SC)
The conformance statement regarding the type specification for extensions is too vague for proper interoperability. Suggest explicitly requiring the extension element’s child to carry the xsi:type attribute. This makes the use of the xsi:type attribute consistent with its definition without requiring everyone to redefine the extension element as a choice of their set of extensions.

Document: Spec
Section: 5.5.1
Old Text: Each such extension MUST declare its type using the schema-defined “type” attribute
New Text: Each such extension element carries a single child element which MUST declare its type using the schema-defined “type” attribute

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]