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

RE: Action Item http://www.w3.org/2006/07/12-ws-policy-minutes.html#action01

From: Paul Cotton <Paul.Cotton@microsoft.com>
Date: Tue, 5 Sep 2006 18:10:41 -0700
To: "Yalcinalp, Umit" <umit.yalcinalp@sap.com>, Maryann Hondo <mhondo@us.ibm.com>
CC: "public-ws-policy@w3.org" <public-ws-policy@w3.org>
Message-ID: <4D66CCFC0B64BA4BBD79D55F6EBC22570ED21BBC00@NA-EXMSG-C103.redmond.corp.microsoft.com>
>We will prepare a detailed proposal as to which sections of the UWSP document may also be used within the context of our guideline as the next step.

I believe the WG is awaiting this additional work.  Is this going to be done in time for the F2F meeting?


Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (613) 225-5445 Fax: (425) 936-7329

From: public-ws-policy-request@w3.org [mailto:public-ws-policy-request@w3.org] On Behalf Of Yalcinalp, Umit
Sent: August 1, 2006 8:45 PM
To: public-ws-policy@w3.org
Subject: Action Item http://www.w3.org/2006/07/12-ws-policy-minutes.html#action01


Per our action item on [1], here is our outline for the Guidelines for WS-Policy Assertion Authors document.

We realize that there is some overlap with the submitted Understanding WS Policy document [2] content. Our intention is however to focus on guidelines for policy authors rather than detailed descriptions of the policy framework itself. We feel that the content should be tailored to guiding authors in making the best choices. You will find the outline illustrates this intent.

We will prepare a detailed proposal as to which sections of the UWSP document may also be used within the context of our guideline as the next step.


--umit & maryann

[1] http://www.w3.org/2006/07/12-ws-policy-minutes.html#action01

[2] http://lists.w3.org/Archives/Public/public-ws-policy/2006Jul/att-0001/understanding-ws-policy-07-06-2006.pdf

2.0 Roles and Responsibilities in Utilizing Policy Assertions
2.0.1Domain owners
2.0.2 Consumers
2.1 General Guidelines for Representation of Policy Expressions and Their Target Use
2.1.1 Compact vs Normal Policy Expressions
3. Guidelines for Modeling Assertions for Single Domains
3.1 Identifying a new Policy Domain
3.2 Framework considerations for Decomposing a new Policy Domain
3.2.1 Nested domains
3.2.2 Assertions with Parameters
3.2.3 Comparison
3.2.4 Self-Describing Messages
3.3. Considering Intersection and Merging
3.4.. Typing Assertions
3.4.1 Representing Capability vs. Constraints
3.4.2 Specifying and Naming Assertions
3.5. Subject Scoping Considerations [related to section 5]
3.5.1 Levels of Abstraction (i.e. portType vs endpoint)
3.6.1 Enabling Reuse using policy references
3.7. Lifecycle of Assertions
3.7.1 Factors in Extending Assertions
3.8 Evolution of Assertions (Versioning and Compatibility)
4. Inter-domain Policy and Composition Issues
5. Understanding Policy Attachment Mechanisms /Best Practices
5.1. Appropriate Attachment: Preserving Context-Free Policies
5.2. Appropriate Attachment: Identifying Assertion Subjects
5.2.1 Interaction between Subjects
5.3. Appropriate Attachment: Identifying Assertion Sources
5.4. Typing Attachment Mechanisms
6. Scenario and a worked example


Dr. Umit Yalcinalp
NetWeaver Industry Standards
Email: umit.yalcinalp@sap.com Tel: (650) 320-3095
SDN: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/u/36238
Received on Wednesday, 6 September 2006 01:10:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:33:14 UTC