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

Issue 388 Proposed Resolution

From: Marc Hadley <marc.hadley@sun.com>
Date: Mon, 28 Oct 2002 22:01:26 -0500
To: xml-dist-app@w3.org
Message-Id: <B6E5AB45-EAEA-11D6-BBD0-0003937568DC@sun.com>

On last weeks telcon I took an action to propose a resolution for issue 
388:

"4. Section 6: We suggest to explicitly reference the equivalence rules
used for the URIs when the message parts are identified. (We believe
editors meant the URI equivalence rules specified in the URI spec 
[RFC2396]).
The fact that XML namespace spec uses different equivalence rules for
namespace URIs then the original URI spec causes a confusion among
developers on which rules to use in each case of the URIs use."

Section 6 of SOAP 1.2 Part 1 discusses uses of URIs in SOAP including 
determination of a base URI for relative URIs and URI equivalence 
rules. I propose adding a reference to this section to the AF document 
to resolve this issue without duplicating text between Part 1 and the 
AF specification.

<current>
*     A mechanism by which each part is identified using one (or more) 
URI(s). The URI scheme used MAY but need not be the same for all parts. 
The URI scheme used for multiple identifiers of a single part MAY but 
need not be the same. If a SOAP binding allows the use of relative 
URIs, then the binding MUST specify how the base URI is established.
       Note: the ability to identify a single part with multiple URIs is 
provided because, in general, the Web architecture allows such multiple 
names for a single resource. It is anticipated that most bindings will 
name each part with a single URI, and through the use of base URIs, 
provide for absolute and/or relative URI references to that URI.
</current>

<proposed>
*     A mechanism by which each part is identified using one (or more) 
URI(s), see (ref to SOAP Part 1, 6. Use of URIs in SOAP). The URI 
scheme used MAY but need not be the same for all parts. The URI scheme 
used for multiple identifiers of a single part MAY but need not be the 
same.
       Note: the ability to identify a single part with multiple URIs is 
provided because, in general, the Web architecture allows such multiple 
names for a single resource. It is anticipated that most bindings will 
name each part with a single URI, and through the use of base URIs, 
provide for absolute and/or relative URI references to that URI.
</proposed>

Thoughts, comments ?

Marc.

--
Marc Hadley <marc.hadley@sun.com>
XML Technology Center, Sun Microsystems.
Received on Monday, 28 October 2002 22:01:23 GMT

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