W3C home > Mailing lists > Public > public-ws-policy@w3.org > January 2007

NEW ISSUE: Example 3.1 does not follow the algorithm/definition in merging policies

From: Yalcinalp, Umit <umit.yalcinalp@sap.com>
Date: Fri, 12 Jan 2007 15:52:09 -0800
Message-ID: <2BA6015847F82645A9BB31C7F9D641650324114A@uspale20.pal.sap.corp>
To: <public-ws-policy@w3.org>

Title: Example 3.1 does not follow the algorithm in merging policies

Description: The example 3.1 claims to be result of merging. The merge
is defined to be 

{
Definition: a merge consists of serializing each policy as a policy
expression, replacing their wsp:Policy element with a wsp:All element,
and placing each as children of a wrapper wsp:Policy element.] The
resulting policy expression is considered to represent the combined
policy of all of the attachments to that policy subject.
}

The resulting example does not contain any replacement of wsp:All
elements with a wsp:Policy element and does not follow the definition. 

Justification: The example is confusing and does not follow the
description of the merge. 

Proposal: Fix the example to reflect the merge algorithms intent by
introducing wsp:All as appropriate wrappers. 

This is also files as [Issue 4209]. 

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

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

Dr. Umit Yalcinalp
Research Scientist
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 Friday, 12 January 2007 23:51:12 GMT

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