W3C home > Mailing lists > Public > xml-dist-app@w3.org > February 2002

ETF: Proposed Resolution for Issue 184

From: Asir S Vedamuthu <asirv@webmethods.com>
Date: Thu, 21 Feb 2002 12:19:18 -0500
Message-ID: <021f01c1bafb$e6bb3270$4813030a@webmethods.com>
To: "xml-dist-app" <xml-dist-app@w3.org>
Issue 184 [1]

SOAP Encoding schema [2] declares several elements whose type is a complex
type derived from XML legacy types:

(a) <xs:element name="NMTOKEN" type="tns:NMTOKEN" />
(b) <xs:element name="NMTOKENS" type="tns:NMTOKENS" />
(c) <xs:element name="ID" type="tns:ID" />
(d) <xs:element name="IDREF" type="tns:IDREF" />
(e) <xs:element name="ENTITY" type="tns:ENTITY" />
(f) <xs:element name="IDREFS" type="tns:IDREFS" />
(g) <xs:element name="ENTITIES" type="tns:ENTITIES" />
(h) <xs:attribute name="NOTATION" type="tns:NOTATION" /> (an attribute decl)

Per XML 1.0, all these types are attribute types [2]. XML Schema specifies
that [3], for compatibility these types should be used only on attributes.
But, SOAP specs do not specify any such health warning.

Proposed Resolution

- REMOVE Notation attribute declaration item. 'Cos Notation built-in type
cannot be deployed without specifying an enumeration [5]

- Add a health warning,

"The use of elements declarations whose types are ID, IDREF, IDREFS, ENTITY,
ENTITIES, NMTOKEN and NMTOKENS is discouraged by the XML Schema
specification because it goes beyond XML 1.0. Nevertheless, for the sake of
completeness, the SOAP Encoding schema provides element declarations using
these types"

[1] http://www.w3.org/2000/xp/Group/xmlp-issues#x184
[2] http://www.w3.org/2001/12/soap-encoding
[3] http://www.w3.org/TR/REC-xml#sec-attribute-types
[4] http://www.w3.org/TR/xmlschema-2/#ID (and more)
[5] http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/datatypes#NOTATION


Asir S Vedamuthu

webMethods, Inc.
703-460-2513 or asirv@webmethods.com
Received on Thursday, 21 February 2002 12:21:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:18 UTC