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 Clarify text surrounding PolicyReference and for usage of wsp:Name attribute Description See Justification and Proposal Justification The usage of wsu:Id is addressed in the Primer. However, more description is needed for the use of the Name attribute, particularly to accommodate when wsdl:import applies. wsdl:import is used frequently in real WSDL documents and should be covered when the Name attribute is discussed. Secondarily the explanations of PolicyReference should be collected in one section. Target Primer Note: At some point, if Section 5.9.1 or the Guidelines is extended, the Guidelines may be affected. Proposal 1.a Move the entire block text in Section 3.2 to Section 2.8: "Just as other service metadata languages, Web Services Policy does not mandate any specific policy retrieval mechanism....If the referenced policy expression is in the same XML document as the reference, then the policy expression should be identified using the wsu:Id (XML ID) attribute and referenced using an IRI reference to this XML ID value." 1.b Add a reference to the end of section 3.2: "See section 2.8 for more details how to reference policy expressions." 2.a Section 3.2: "If the referenced policy expression is in the same XML document as the reference, then the policy expression should be identified using the wsu:Id (XML ID) attribute and referenced using an IRI reference to this XML ID value." Add: "If the referenced policy expression is in another XML document as the reference, the wsp:Name attribute is used to identify the policy expression. WSDL 1.1 and 2.0 allow to import a WSDL document into another WSDL document with the wsdl:import statement. While the importing and imported WSDL documents may be regarded as one logical WSDL document altogether, they constitute separate XML documents. Therefore, the rules for policy references between separate XML documents apply if policies are referenced across documents that use wsdl:import." 2.b Change from: "Use the referenced IRI and retrieve an existing policy expression from the containing XML document: a policy element with an XML ID." Change from: "Use the referenced IRI and retrieve an existing policy expression from the containing XML document: a policy element identified with an XML ID or Name attribute." ======= If needed, reference: WSDL v1.1 specification, Section 2.1.1 and 2.1.2.
Updated proposal: Title Clarify text surrounding PolicyReference and cover wsdl:import use Description See Justification and Proposal Justification The description of retrieving policy references seems mislocated in section 3.2 (normalization). wsdl:import is used frequently in real WSDL documents and should be covered when policy references are discussed. Target Primer Note: At some point, if section 5.1 of the Guidelines is extended, the Guidelines may be affected. Proposal 1.a) Create a new section after section 3.5. Name the new section "3.6 Policy Retrieval". Move the entire block of text in Section 3.2 to the newly created section 3.6: "Just as other service metadata languages, Web Services Policy does not mandate any specific policy retrieval mechanism ... If the referenced policy expression is in the same XML document as the reference, then the policy expression should be identified using the wsu:Id (XML ID) attribute and referenced using an IRI reference to this XML ID value." 1.b) Add a reference to the end of section 3.2: "See section 3.6 for more details how to retrieve referenced policy expressions." 2. Add to the end of the newly created section 3.6: WSDL 1.1 [WSDL 1.1] section 2.1 and WSDL 2.0 [WSDL 2.0 Core Language] chapter 4 allow to import or include WSDL documents into another WSDL document with the wsdl11:import, wsdl20:import, and wsdl20:include statements. The importing and imported WSDL documents constitute separate XML documents each. If e.g. the importing WSDL document references a policy in the imported WSDL document, the rules for policy references between separate XML documents apply as described in section 2.8.
RESOLUTION: Resolved 6 December 2006 as proposed and amended. a. Proposal: http://lists.w3.org/Archives/Public/public-ws-policy/2006Dec/0012.html b. Amendment: http://www.w3.org/2005/06/tracker/wspolicyeds/actions/94 (per comments and response in http://lists.w3.org/Archives/Public/public-ws-policy/2006Dec/0016.html) Add a pointer to the 4.3.4 PolicyReference that points forward to the newly proposed text in the Primer. Editor's discretion as to adding reference to Guidelines document, Section 3.6.