W3C home > Mailing lists > Public > public-ws-policy@w3.org > August 2006

Issue 3620 is out of scope

From: Paul Cotton <Paul.Cotton@microsoft.com>
Date: Wed, 30 Aug 2006 10:45:43 -0700
To: "public-ws-policy@w3.org" <public-ws-policy@w3.org>
Message-ID: <4D66CCFC0B64BA4BBD79D55F6EBC22570ED21BBB4F@NA-EXMSG-C103.redmond.corp.microsoft.com>
Policy Attachment to WS-Addr EndpointReferences

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3620



I believe this issue is out of scope for the current version of WS-Policy.



The charter [1] clearly states:



"The Web Services Policy Working Group is also chartered to standardize mechanisms for associating policy expressions with Web Service constructs. These mechanisms consist of items 5-9 below."



and this explicit list does not include the additional work of attaching policies to EPRs:
5.      A model for attaching policies to WSDL 1.1 and WSDL 2.0 constructs. The model defines:
a.      A partitioning of WSDL constructs into message, operation, endpoint, and service policy subjects.
b.      The semantics of attaching a policy to each policy subject.
c.      How to combine policies attached to more than one WSDL component within a single policy subject.
6.      An XML representation of policy expressions attached to WSDL 1.1 and WSDL 2.0 constructs and annotating those policy expressions as required extensions using the WSDL-defined extensibility flag @wsdl:required.
7.      A model for attaching policies to UDDI v2 and UDDI v3 entities. The model defines:
a.      A partitioning of UDDI constructs into service provider, service, and endpoint policy subjects.
b.      The semantics of attaching a policy to each policy subject.
c.      How to combine policies attached to more than one UDDI entity within a policy subject.
8.      A set of tModels for referencing and registering policy expressions in UDDI v2 and UDDI v3.
9.      A general-purpose mechanism for external policy attachment.

In addition the charter clearly states:

"The following is intended to more tightly constrain the in-scope features, to prevent feature bloat and assure timely delivery. If some function, mechanism or feature is not mentioned here, and it is not mentioned in the Scope of Work section either, then it will be deemed to be out of scope."

I believe this is a feature request that we should consider for V.Next (e.g. futureConsideration [1]) in order to assure timely delivery of the first WS-Policy Recommendation.

/paulc

[1] http://www.w3.org/2006/04/ws-policy-charter.html

[2]  http://www.w3.org/Bugs/Public/describekeywords.cgi



Paul Cotton, Microsoft Canada

17 Eleanor Drive, Ottawa, Ontario K2E 6A3

Tel: (613) 225-5445 Fax: (425) 936-7329

mailto:Paul.Cotton@microsoft.com
Received on Wednesday, 30 August 2006 17:45:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:40 GMT