How to Treat Built-In Schema Types

I have an action [1] to propose how to handle built-in schema types. Part 
2 of the XSD spec defines a lot of simple types. Property component may 
reference Type Definition components. Our spec currently demands that any 
referenced type definition be imported. 

I suggest that it would be a minor simplification to regard the XSD 
built-in types as well-known, and to not require them to be explicitly 
imported.

Currently section 3.1 of Part says:

A WSDL 2.0 description MUST NOT refer to XML Schema components in a given 
namespace unless an xs:import or xs:schema statement for that namespace is 
present. That is, using the xs:import or xs:schema constructs is a 
necessary condition for making XML Schema components available to a WSDL 
2.0 description. 

I suggest the following text:

A WSDL 2.0 description MUST NOT refer to XML Schema components in a given 
namespace unless an xs:import or xs:schema statement for that namespace is 
present or the namespace is the XML Schema namespace which contains 
built-in types as defined in XML Schema Part 2: Datatypes Second Edition. 
That is, using the xs:import or xs:schema constructs is a necessary 
condition for making XML Schema components, other than the built-in 
components, available to a WSDL 2.0 description. 

[1] 
http://lists.w3.org/Archives/Public/www-ws-desc/2005Sep/att-0067/20050926-ws-desc-minutes.html#action01

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca

Received on Monday, 17 October 2005 22:56:09 UTC