RE: Is schemaLocation Required When Importing Inline Schemas?

> provided that an appropriate value is specified for their 
> schemaLocation attribute information items, such as a fragment identifier 
 
"fragment identifier" got in via LC41 [1]. Are there any reasons why WSDL
2.0 has to say that an appropriate value for schemaLocation is required to
refer to other embedded schemas? AFAIK, WG decided not to say anything about
composition of XML Schema for embedded schema elements.
 
[1] http://www.w3.org/2002/ws/desc/4/lc-issues/#LC41
<http://www.w3.org/2002/ws/desc/4/lc-issues/#LC41> 
 
Regards,
Asir S Vedamuthu
asirv at webmethods dot com
 <http://www.webmethods.com/> http://www.webmethods.com/

 
 -----Original Message-----
From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
Behalf Of Arthur Ryman
Sent: Wednesday, March 30, 2005 6:18 AM
To: www-ws-desc@w3.org
Subject: Is schemaLocation Required When Importing Inline Schemas?



The spec currently says that when you refer to inline schemas within the
same document you need to provide a schemaLocation attribute with a suitable
fragid in the xs:import statement: 

Inside an embedded XML schema, the xs:import and xs:include element
information items MAY be used to refer to other XML schemas embedded in the
same WSDL description, provided that an appropriate value is specified for
their schemaLocation attribute information items, such as a fragment
identifier (see [
<file:///d:/workspaces/Corona%20V6.0/W3C/wsdl20/wsdl20.html#XMLSchemaP1> XML
Schema: Structures] 4.3.1). The semantics of such element information items
are governed solely by the XML Schema specification [
<file:///d:/workspaces/Corona%20V6.0/W3C/wsdl20/wsdl20.html#XMLSchemaP1> XML
Schema: Structures]. 

I thought we said the fragid was unnecessary since the WSDL processor knows
where to find the schemas. 

On the other hand, there was a very long thread [1] about how to refer to an
inline schema from another WSDL document. The thread ended inconclusively
with an action item [2] that doesn't seem to exist. The conclusion seems to
have been that you didn't need the schemaLocation, but the behavioir was
dependent on the processor. 

Can we please tighten this up? I just created some Primer text that may not
be correct. 

I propose that we require a WSDL processor to know how to locate any inline
schemas it encouters while processing a document so that the schemaLocations
are not required. 

"If schemaLocation is not present then a WSDL processor MUST attempt to
locate the schema among the inline schemas it has encountered while
processing the WSDL document." 

[1] http://lists.w3.org/Archives/Public/www-ws-desc/2003Nov/0109.html 
[2] http://lists.w3.org/Archives/Public/www-ws-desc/2003Nov/0156.html 

Arthur Ryman,
Rational Desktop Tools Development

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
intranet: http://labweb.torolab.ibm.com/DRY6/