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

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

From: Anthony Nadalin <drsecure@us.ibm.com>
Date: Tue, 1 Aug 2006 22:12:13 -0500
To: "Yalcinalp, Umit" <umit.yalcinalp@sap.com>
Cc: public-ws-policy@w3.org, public-ws-policy-request@w3.org
Message-ID: <OF352BC56B.2B22DEA5-ON862571BE.00115C7A-862571BE.00119939@us.ibm.com>

Seems that this is a mix between folks that will have to write a
implementation of a domain provider and folks that want to write domain
specific assertions (which seems to be the title). So I'm still not clear
on what audience you are targeting

Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122

             "Yalcinalp, Umit"                                             
             ap.com>                                                    To 
             Sent by:                  <public-ws-policy@w3.org>           
             public-ws-policy-                                          cc 
                                       Action Item                         
             08/01/2006 07:45          http://www.w3.org/2006/07/12-ws-pol 
             PM                        icy-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


--umit & maryann

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


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

(image/gif attachment: graycol.gif)

(image/gif attachment: pic26036.gif)

(image/gif attachment: ecblank.gif)

Received on Wednesday, 2 August 2006 03:12:56 UTC

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