- From: David Orchard <david.orchard@bea.com>
- Date: Fri, 05 Oct 2001 17:16:42 -0700
- To: xml-dist-app@w3.org
- Message-Id: <5.1.0.14.0.20011005165735.00b097a0@sj-mail-01.beasys.com>
I took Noah's excellent wording[1] and semantically NOTed it. My attempt follows. Please note that this wording defines that relative URI's ARE interpreted according to xml:base, therefore implementations must support xml:base. It seems to me that an application that doesn't support xml:base but supports relative URIs is an undefined state. BASE URI's and Relative URI Resolution -------------------------------------- "This version of the SOAP specification supports the W3C XML Base Recommendation. The xml:base attribute MAY appear on the SOAP-ENV:Envelope, SOAP-ENV:Body, SOAP-ENV:Header, or SOAP-ENV:Fault elements. The XML Base specification provides a standard Base URI for the contents of the SOAP-ENV:Body or other header entries. Specifications for particular applications of SOAP, as well as specifications for transport bindings, header entries and/or body entries MAY define the interpretation of relative URI's within such body or entries additionally. In the absence of such additional specifications, the resolution of relative URI's appearing within the contents of a body or other header entry is defined by XML Base. Relative URI's MAY be used as values for attributes or elements (such as SOAP-ENV:Actor, SOAP-ENV:EncodingStyle) defined by this specification; if such values are used, their resolution to absolute URI's is defined according to the XML Base Recommendation. Namespace declarations for the namespaces used in this specification (such as http://www.w3.org/2001/06/soap-envelope) MUST be provided as absolute URI's. Element or attribute names qualified with relative URI namespaces are not recognized as matching the absolute names mandated by this specification." Cheers, Dave Orchard [1] http://lists.w3.org/Archives/Public/xml-dist-app/2001Aug/0268.html
Received on Friday, 5 October 2001 20:21:57 UTC