Re: schemaLocation background

Jonathan,

Thx. I'll write up the Primer section and add some test cases to the Test 
Suite.

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/



"Jonathan Marsh" <jmarsh@microsoft.com> 
Sent by: www-ws-desc-request@w3.org
02/16/2005 07:46 PM

To
Arthur Ryman/Toronto/IBM@IBMCA
cc
<www-ws-desc@w3.org>
Subject
schemaLocation background







As I recall it, there have been several items relating to embedded and
imported schemas and the use of schemaLocation.

I have an action to help dig up the schemaLocation scenarios.

1) Can you inline two schemas instead of one.  Answer: yes, even if they
have the same targetNamespace (but no duplicate definitions.) [1, 2]

2) Can you import one embedded schema into the other.  Answer: yes, this
should be expected to work.  A schemaLocation attribute with a fragment
ID can be added to make this explicit. [3, 4]

3) Can you see schema components in an imported WSDL.  Answer: no, this
is by design. [5]

4) I thought we also agreed that you can import a schema embedded in
another WSDL, and a schemaLocation attribute with a fragment ID would
likely be required by most processors in this case. (A schemaLocation
pointing to the WSDL file would not conform to the defn of
schemaLocation.)  I can't find documentation on this point though.

Hope this is what you were looking for...

[1] http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#lc60 
[2]
http://lists.w3.org/Archives/Public/www-ws-desc/2005Jan/att-0092/2005012
7-ws-desc-minutes.html#item07
[3] http://lists.w3.org/Archives/Public/www-ws-desc/2004Sep/0022.html
[4] http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html?view=wg#LC65
[5] http://lists.w3.org/Archives/Public/www-ws-desc/2003Nov/0130.html