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

[Issue] XML Legacy Types in SOAP Encoding Schema

From: Asir S Vedamuthu <asirv@webmethods.com>
Date: Tue, 12 Feb 2002 11:07:12 -0500
Message-ID: <01e901c1b3df$554a82f0$4813030a@webmethods.com>
To: "'Xml-Dist-App@W3. Org'" <xml-dist-app@w3.org>
Cc: "Jacek Kopecky" <jacek@systinet.com>, "Marc Hadley" <marc.hadley@sun.com>, "Henrik Frystyk Nielsen" <henrikn@microsoft.com>
Issue

SOAP Encoding schema [1] 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 Resolutions

[Resolution 1] Remove these element declarations and related complex types
from the SOAP Encoding schema. 'Cos, I do not see any uses cases for
representing any part of the SOAP Data Model using these element decls or
complex types.

OR

[Resolution 2] Include the health warning in XML Schema by reference

My preference is [Resolution 1]

[1] http://www.w3.org/2001/12/soap-encoding
[2] http://www.w3.org/TR/REC-xml#sec-attribute-types
[3] http://www.w3.org/TR/xmlschema-2/#ID (and more)

Regards,

Asir S Vedamuthu

webMethods, Inc.
703-460-2513 or asirv@webmethods.com
http://www.webmethods.com/
Received on Tuesday, 12 February 2002 11:01:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:06 GMT