W3C home > Mailing lists > Public > xml-dist-app@w3.org > December 2001

RE: Proposed text for XML Base support in SOAP 1.2

From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
Date: Wed, 5 Dec 2001 09:11:45 -0800
Message-ID: <79107D208BA38C45A4E45F62673A434D05A840B1@red-msg-07.redmond.corp.microsoft.com>
To: "Marc Hadley" <marc.hadley@sun.com>
Cc: <xml-dist-app@w3.org>

I think your amended text is fine but I think we should keep the text
talking about protocol bindings - see below.

Henrik Frystyk Nielsen

>I propose that we amend the text of this section to read:
>--- cut here ---
>6 Use of URIs in SOAP
>SOAP uses URIs for some identifiers including, but not limited to, 
>values of the encodingStyle (see 4.1.1 SOAP encodingStyle 
>Attribute) and 
>actor (see 4.2.2 SOAP actor Attribute) attribute information items. To 
>SOAP, a URI is simply a formatted string that identifies a web 
>via its name, location, or via any other characteristics.
>Although this section only applies to URIs directly used by 
>items defined by this specification, it is RECOMMENDED but NOT 
>that application-defined data carried within a SOAP envelope use the 
>same mechanisms and guidelines defined here for handling URIs.
>URIs used as values in information items identified by the 
>"http://www.w3.org/2001/09/soap-envelope" and 
>"http://www.w3.org/2001/09/soap-encoding" XML namespaces can be either 
>relative or absolute. In addition, URIs used as values of the local, 
>unqualified href attribute information item can be relative or 
>SOAP does not define a base URI but relies on the mechanisms 
>defined in 
>XML Base[x] and RFC 2396[y] for establishing a base URI against which 
>relative URIs can be made absolute.

The underlying protocol binding MAY define a base URI which can act as
the base URI for the SOAP envelope (see section X.X and the HTTP binding
in section X.X).

>SOAP does not define any equivalence rules for URIs in general 
>as these 
>are defined by the individual URI schemes and by RFC 2396. However, 
>because of inconsistencies with respect to URI equivalence 
>rules in many 
>current URI parsers, it is RECOMMENDED that SOAP senders do 
>NOT rely on 
>any special equivalence rules in SOAP receivers in order to determine 
>equivalence between URI values used in a SOAP message.
>The use of IP addresses in URIs SHOULD be avoided whenever 
>possible (see 
>RFC 1900). However, when used, the literal format for IPv6 
>addresses in 
>URI's as described by RFC 2732 SHOULD be supported.
>SOAP does not place any a priori limit on the length of a URI. 
>Any SOAP 
>node MUST be able to handle the length of any URI that it 
>publishes and 
>both SOAP senders and SOAP receivers SHOULD be able to deal 
>with URIs of 
>at least 8k in length.
Received on Wednesday, 5 December 2001 12:12:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:17 UTC