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: The framework specification should also enable the usage of xml:id Description: The WS-Policy Framework specification uses wsu:id element to designate identification for elements[WS-Policy]. W3C also published xml:id document that allows the same use [XMLID] that is a recommendation. Currently, the WS-Policy specification does not use the xml:id mechanism for uniquely identifying XML elements and relies on the WSS definition of id mechanism. Justification: The purpose of the xml:id specification is to have unique element identifiers to be recognized by all conformant XML processors. Currently, WS-Policy relies on WS-Security specification for generating URI references instead and requires the framework providers to recognize this alternate mechanism for processing references. As xml:id will be adopted, the support of xml:id in all XML processors may require WS-Policy to also allow utilization of xml:id. Further, the specification does not clarify whether the xml:id is permissable as an identification mechanism for a WS-Policy expression. Target: Section 4.2 of the WS-Policy, Appendix A. Proposal: Allow xml:id as a permissible mechanism for identifying policy expressions in addition to wsu:Id 1. Replace {/wsp:Policy/@wsu:Id The identity of the policy expression as an ID within the enclosing XML document. If omitted, there is no implied value. To refer to this policy expression, a URI-reference MAY be formed using this value per Section 4.2 of WS-Security [WS-Security 2004].} With /wsp:Policy/{@wsu:Id | @xml:id} The identity of the policy expression as an ID within the enclosing XML document. If omitted, there is no implied value. To refer to this policy expression, a URI-reference MAY be formed using this value per Section 4.2 of WS-Security [WS-Security 2004] when @wsu:Id is used. 2. Repeat last example in Section 4.2 using xml:id in addition to wsu:id (last paragraph of Section 4.2) to illustrate the form. This is purely editorial. 3. Add normative reference to xml:id [XMLID] in A.1. Personal Note: I have chosen to retain the reference on wsu:Id given the expected schedule of the publication rather than removing it due to existing support on this attribute in the existing implementations. We could also add a note in the framework/primer when it is not desirable to use xml:id but rely on wsu:id if the wg feels that is necessary. References: [XMLID] http://www.w3.org/TR/xml-id/ [WS-Policy] http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;%20charset=utf-8
The original email thread can be found in here. http://lists.w3.org/Archives/Public/public-ws-policy/2006Jul/0099.html
This issue is resolved by accepting the proposal with two amendements: -- No new example will be added in Section 4.2 http://lists.w3.org/Archives/Public/public-ws-policy/2006Aug/0099.html -- A new paragraph & reference will be added to section 4.2 "The use of xml:id attribute in conjunction with Canonical XML 1.0 is inappropriate as described in Appendix C of xml:id Version 1.0 [XMLID] and thus this combination must be avoided (see [C14NNOTE]). For example, a policy expression identified using xml:id attribute should not be signed using XML Digital Signature when Canonical XML 1.0 is being used as the canonicalization method." Where, C14NNOTE is a non-normative reference to [2]. http://www.w3.org/2006/04/c14n-note/c14n-note.html#S3 This is per email http://lists.w3.org/Archives/Public/public-ws-policy/2006Aug/0074.html
The resolution is achieved during the conference call in [ConfCall]. [Confcall] http://www.w3.org/2006/08/16-ws-policy-minutes.html