4288 2007-01-30 22:16:46 +0000 [Primer] Absence of Policy Assertions (editorial) 2007-03-13 22:51:39 +0000 1 1 1 Unclassified WS-Policy Primer FPWD PC Windows XP RESOLVED FIXED P2 normal --- 1 monica.martin fsasaki fabian.ritzmann public-ws-policy-qa oldest_to_newest 13847 0 monica.martin 2007-01-30 22:16:46 +0000 Target: Primer (http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-primer.html?content-type=text/html;%20charset=utf-8) 22 January 2007 Description and Justification: Currently, a statement exists in Section 2.10, Primer, about the absence of policy assertions only in the context of inline to a WSDL document while no mention is made earlier where it more appropriately applies such as in Section 2.6, Optional Policy Assertion. Suggest we promote similar statements to Section 2.6 where it applies rather than limit its relationship to policy expressions in a WSDL document as a parenthetical comment. In other groups, questions have arisen about this statement so promotion herein seems a logical approach. This suggestion was also part of Issue 3602 proposal as well [1] and may have been missed. Proposal: A. At the end of Section 2.6, include a brief statement where optional policy assertions are discussed. Change from: Contoso is able to meet their customer needs by adding optional support for the Optimized MIME Serialization. An optional policy assertion represents a behavior that may be engaged. Change to: Contoso is able to meet their customer needs by adding optional support for the Optimized MIME Serialization. An optional policy assertion represents a behavior that may be engaged. Where the behavior is not engaged, the absence of policy expressions does not indicate anything about the capabilities and requirements of a service. A policy aware client should not conclude anything (other than ‘no claims’) about the absence of policy expressions. B. Apply minor update to Section 2.10, Attaching Policy Expressions to WSDL. Change from: The absence of policy expressions in a WSDL document does not indicate anything about the capabilities and requirements of a service. The service may have capabilities and requirements that can be expressed as policy expressions, such as the use of addressing, security and optimization. Or, the service may not have such capabilities and requirements. A policy aware client should not conclude anything (other than ‘no claims’) about the absence of policy expressions. Change to: The absence of policy expressions, for example in a WSDL document, does not indicate anything about the capabilities and requirements of a service. The service may have capabilities and requirements that can be expressed as policy expressions, such as the use of addressing, security and optimization. Or, the service may not have such capabilities and requirements. [1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=3602, http://www.w3.org/Bugs/Public/show_bug.cgi?id=3602#c3 13914 1 monica.martin 2007-02-07 00:43:47 +0000 Updated proposal submitted at: http://lists.w3.org/Archives/Public/public-ws-policy/2007Feb/0014.html 14080 2 monica.martin 2007-02-23 19:00:05 +0000 Updated from on/off list comments on editorial changes. Update sent at: http://lists.w3.org/Archives/Public/public-ws-policy/2007Feb/0151.html 14399 3 monica.martin 2007-03-13 19:28:04 +0000 13 March 2007: Update includes Friendly Amendment from MaryAnn Hondo. See: http://lists.w3.org/Archives/Public/public-ws-policy/2007Mar/0084.html 14410 4 chrisfer 2007-03-13 22:51:39 +0000 [18:50] cferris: RESOLUTION: Issue 4288 closed with monica's proposal in http://lists.w3.org/Archives/Public/public-ws-policy/2007Mar/0084.html as amended by Maryann in http://lists.w3.org/Archives/Public/public-ws-policy/2007Mar/0047.html with acknowledgements around the table to all those that contributed to the iterations/discussions [18:50] dmoberg: cferris: typing in resolution [18:50] cferris: rrsagent, where am i? [18:50] RRSAgent: See http://www.w3.org/2007/03/13-ws-policy-irc#T22-51-09