This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Title: WS-Policy does not define its relationship to XML Base [1] Description: WS-Policy does not define its relationship to XML Base [1] Justification: The XML Base spec says: The deployment of XML Base is through normative reference by new specifications, for example XLink and the XML Infoset. Applications and specifications built upon these new technologies will natively support XML Base. The behavior of xml:base attributes in applications based on specifications that do not have direct or indirect normative reference to XML Base is undefined. Unspecifying the relationship to XML Base will likely lead to interoperability problems, since by definition, behavior is undefined. Proposal: TBD, but roughly treat along the lines of how SOAP1.2 has handled it [2] [1] http://www.w3.org/TR/2001/REC-xmlbase-20010627/ [2] http://www.w3.org/TR/soap12-part1/#useofuris
Resolved on Dec 13 based on proposal in: http://lists.w3.org/Archives/Public/public-ws-policy/2006Dec/0040.html The proposal was amended to include the following text: "This document does not define a base URI but relies on the mechanisms defined in XML Base [XML Base] and RFCs 3023 [RFC3023], 3986 [RFC 3986] and 3987 [RFC 3987] for establishing a base URI against which relative IRIs can be made absolute." See: http://www.w3.org/2006/12/13-ws-policy-irc#T17-45-16 /paulc