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

Re: Proposed resolutions to issues 3549 and 3548

From: Frederick Hirsch <frederick.hirsch@nokia.com>
Date: Thu, 10 Aug 2006 14:30:08 -0400
Message-Id: <3B581E3E-D972-4932-AA40-C3ADCB8A5CF6@nokia.com>
Cc: Hirsch Frederick <frederick.hirsch@nokia.com>, public-ws-policy@w3.org
To: ext Anthony Nadalin <drsecure@us.ibm.com>

Tony

Any assertion that may have nested assertions MUST have a wsp:Policy  
child element.

Currently, the latest framework document [1] says [2], "if the schema  
outline for an
assertion type requires a nested policy expression but the assertion
does not further qualify one or more aspects of the behavior indicated
by the assertion type (i.e., no assertions are needed in the nested
policy expression), the assertion MUST include an empty <wsp:Policy/>
Element Information Item in its [children] property."

I think this needs clarification earlier in the document.

Reasons I noted are in the issue descriptions, related to  
distinguishing parameters from assertions without relying on  
namespace (due to unanticipated domains) and for normalization/ 
matching issues, as well as needed clarity.

regards, Frederick

Frederick Hirsch
Nokia

[1] <http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy- 
framework.html?content-type=text/html;%20charset=utf-8>

[2] "Note" under /Assertion/wsp:Policy in Section 4.3.2


On Aug 9, 2006, at 10:12 PM, ext Anthony Nadalin wrote:

> Since nesting is optional and depends on the assertion why would a  
> policy author have to include a empty wsp:Policy element ? I also  
> don't consider an empty wsp:Policy element the same as not having a  
> wsp:Policy element.
>
> Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
> <graycol.gif>
> Frederick Hirsch <frederick.hirsch@nokia.com>
>
>
> Frederick Hirsch <frederick.hirsch@nokia.com>
> Sent by: public-ws-policy-request@w3.org
> 08/09/2006 11:32 AM
>
> <ecblank.gif>
>
> To
> <ecblank.gif>
>
> public-ws-policy@w3.org
> <ecblank.gif>
>
> cc
> <ecblank.gif>
>
> Hirsch Frederick <frederick.hirsch@nokia.com>
> <ecblank.gif>
>
> Subject
> <ecblank.gif>
>
> Proposed resolutions to issues 3549 and 3548
> <ecblank.gif>
> <ecblank.gif>
>
>
> Issue 3549
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=3549>
>
> "Require assertions to be distinguished from parameter elements"
>
> Proposed Resolution:
>
> Proposed change to Framework section 3.1
> <http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-
> framework.html>
>
>
> After:
>
> "Domain authors MAY define that an assertion contains a policy
> expression as one of its [children]. Policy expression nesting is
> used by domain authors to further qualify one or more specific
> aspects of the original assertion. For example, security policy
> domain authors may define an assertion describing a set of security
> algorithms to qualify the specific behavior of a security binding
> assertion."
>
> Add additional sentences:
> Any assertion that may contain a policy expression as a child must
> always have a child wsp:Policy element that either contains that
> policy expression, or is empty if the child policy expression is
> optional and not needed."
>
> Related issues:
>
> Issue 3548 is related to 3549, close with no action once 3549 is
> resolved.
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=3548>
>
> regards, Frederick
>
> Frederick Hirsch
> Nokia
>
>
>
>
Received on Thursday, 10 August 2006 18:32:02 UTC

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