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

Action164

From: Yalcinalp, Umit <umit.yalcinalp@sap.com>
Date: Tue, 19 Dec 2006 18:06:13 -0800
Message-ID: <2BA6015847F82645A9BB31C7F9D6416502F441D8@uspale20.pal.sap.corp>
To: <public-ws-policy@w3.org>
I have taken an action item [Action 164] to reword the following text as
part of [Issue 3979]. This is to capture the results of the discussion
as part of the Guidelines Document from the Meeting Minutes. This
completes my action item. 

The offending text: (particularly the term "naming convention"). The
paragraph is repeated to give context.  Note that this section no longer
corresponds to Section 5.9.1. but Section 5.1. I have reworded the
sentence to remove "naming convention" and added text capturing the
discussion. 

Have a look. 

--umit


Old text:

{The Web Services Policy Primer <>  illustrates how providers can
utilize the identification mechanism defined in the Policy specification
to expose a complex policy expression as a reusable building block for
other policy expressions by reference. Domain assertion authors,
especially those defining complex assertions that include nesting or
complex types should consider specifying or recommending naming
conventions in order to promote reuse. Reuse through referencing allows
a policy expression to be utilized not only within another expression
but also allows specification of additional policy subjects and their
association to common policy expressions that are identified. It also
promotes manageability of the expressions as they are uniquely
identified. }
Replace by: 
{The Web Services Policy Primer <>  illustrates how providers can
utilize the identification mechanism defined in the Policy specification
to expose a complex policy expression as a reusable building block for
other policy expressions by reference. Domain assertion authors,
especially those defining complex assertions using nesting or
parameterized assertions, may consider using identification mechanisms
when the nested or parameterized content could be utilized in different
contexts and/or serve as a template for later reuse. Reuse through
referencing allows a policy expression to be utilized not only within
another expression but also allows specification of additional policy
subjects and their association to common policy expressions that are
identified. It also promotes manageability of the expressions as they
are uniquely identified. When assertions contain parametrized
expressions and reuse is desired, care must be given to ensure that the
parameterized content is statically available. As an example, in Web
Services Policy Primer Section 4.2, the sp:issued Token assertion
utilizes the sp:RequestSecurityTokenTemplate parameter that contains
necessary information to request a security token. The contents of the
parameter are static and allows reuse in different security scenerios. 
}


[Issue 3979] http://www.w3.org/Bugs/Public/show_bug.cgi?id=3979

[Action 164]
http://www.w3.org/2006/12/06-ws-policy-minutes.html#action06


----------------------

Dr. Umit Yalcinalp
Architect
NetWeaver Industry Standards
SAP Labs, LLC
Email: umit.yalcinalp@sap.com Tel: (650) 320-3095 
SDN: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/u/36238
--------
"Nearly all men can stand adversity, but if you want to test a man's
character, give him power." Abraham Lincoln. 
Received on Wednesday, 20 December 2006 02:05:57 GMT

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