RE: XML Schema comment "T2" on WSDL 2.0

Actually, upon reflection, I inadvertently blurred our rules regarding the 
need for an import in each schema document.  Perhaps I should have 
suggested:

"Note that while the effect of import is pervasive within an XML schema, 
the same is not true of references from WSDL 2.0 constructs to schema 
components.  In schema, a QName that successfully resolves in one schema
document necessarily resolves when referenced elsewhere in the schema
(except that an import for the namespace as a whole is a precondition
in each document for attempting a reference.)

By contrast, in WSDL, only components defined and declared in the schema 
itself and components included by it via xs:include are available for 
direct 
reference from WSDL 2.0. Specifically components that the schema imports 
via xs:import are NOT available for such references;  they are, however, 
available for reference from within schemas that are contained within 
WSDL."

The above is more verbose, unfortunately, but perhaps it does a better job 
of covering the edge cases?

--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------








Noah Mendelsohn
06/02/2005 04:28 PM


        To:     "Jonathan Marsh" <jmarsh@microsoft.com>
        cc:     public-ws-desc-comments@w3.org, w3c-xml-schema-wg@w3.org, "Xan Gregg" 
<xan.gregg@jmp.com>
        Subject:        RE: XML Schema comment "T2" on WSDL 2.0


I've just been taking a look at this.  Overall, I'm very pleased to see 
the progress that's been made in responding to the Schema WG's concerns. 
Speaking for myself, as opposed to the WG, I do have a lingering concern 
with the statement that [1]:

"Note that only components defined and declared in the schema itself and 
components included by it via xs:include are available to WSDL 2.0. 
Specifically components that the schema imports via xs:import are NOT 
available to WSDL 2.0."

I presume that the above is true as far as it goes with respect to 
references from WSDL itself, but it cannot be true I think with respect to 

references from within the schemas used by WSDL.   The schema 
recommendation is (or should be) clear that with respect to references 
from within a schema or schema document, the effect of import and include 
are both pervasive.   So, if an inlined schema contains an xs:import, and 
if that import results in "components that the schema imports", then such 
components are necessarily available for references from schema 
constructs.  If, for example, the the type imp:t were imported, then the 
reference <xsd:element name="n" type="imp:t"/> would necessarily succeed. 
I wonder whether it would be clearer to say something along the lines of:

"Note that while the effect if import is pervasive within an XML schema, 
the same is not true of references from WSDL 2.0 constructs to schema 
components.  Only components defined and declared in the schema itself and 

components included by it via xs:include are available for direct 
reference from WSDL 2.0. Specifically components that the schema imports 
via xs:import are NOT available for such references;  they are, however, 
available for reference from within schemas that are contained within 
WSDL."

...or some such.

Noah

[1] http://www.w3.org/TR/2005/WD-wsdl20-20050510/#inlining-xsd



--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------








"Jonathan Marsh" <jmarsh@microsoft.com>
Sent by: w3c-xml-schema-wg-request@w3.org
05/13/2005 03:33 PM

 
        To:     "Xan Gregg" <xan.gregg@jmp.com>, 
<w3c-xml-schema-wg@w3.org>
        cc:     <public-ws-desc-comments@w3.org>, (bcc: Noah 
Mendelsohn/Cambridge/IBM)
        Subject:        RE: XML Schema comment "T2" on WSDL 2.0



Thank you for your comment - we tracked this as a Last Call comment LC91 
[1].  The Working Group agreed to incorporate the wording you suggest. You 

can view the resolution in context at [2] and [3].  If we don't hear 
otherwise within two weeks, we will assume this satisfies your concern.

[1] http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC91
[2] http://www.w3.org/TR/2005/WD-wsdl20-20050510/#import-xsd
[3] http://www.w3.org/TR/2005/WD-wsdl20-20050510/#inlining-xsd

> -----Original Message-----
> From: public-ws-desc-comments-request@w3.org [mailto:public-ws-desc-
> comments-request@w3.org] On Behalf Of Xan Gregg
> Sent: Friday, December 03, 2004 5:16 PM
> To: public-ws-desc-comments@w3.org
> Cc: w3c-xml-schema-wg@w3.org
> Subject: XML Schema comment "T2" on WSDL 2.0
> 
> 
> The following is a comment on the WSDL 2.0 last call [1] from the XML
> Schema WG.  We very much appologize about the lateness of this
> comment.
> 
> Xan Gregg, for the XML Schema WG
> [1] http://www.w3.org/TR/2004/WD-wsdl20-20040803
> 
> This is an editorial comment on the impact of xs:import in 3.1.1 and
> 3.1.2.
> 
> 3.1.1 contains:
> 
>      Note that only components defined in the schema itself
>      and components included by it via xs:include are available
>      to WSDL. Specifically, components that the schema imports
>      via xs:import are NOT available to WSDL.
> 
> We think this is correct, but not all of us were sure of the intent at
> first reading, so we suggest wording along the following lines, which
> reinforces the idea that it is a namespace that is imported, not a
> schema.
> 
> For 3.1.1 instead of the above two sentences:
> 
>     Note that only components in the imported namespace are
>     available for reference in the WSDL document.
> 
> For 3.1.2 instead of the similar two sentences, we suggest:
> 
>      Note that only components in the namespace corresponding
>      to the targetNamespace attribute of the embedded schema
>      element are available for reference in the WSDL document.
> 
> (The latter also emphasizes that the targetNamespace is a property of
> the schema element and not of the schema itself.)
>

Received on Thursday, 2 June 2005 20:37:42 UTC