RE: Proposed resolutions to issues 3549 and 3548

Tony: I think you are making a semantic distinction between an absent nested policy and an empty nested policy. Could you elaborate a bit on what that distinction may be? 
All the best, Ashok 
From: public-ws-policy-request@w3.org [mailto:public-ws-policy-request@w3.org] On Behalf Of Anthony Nadalin Sent: Wednesday, August 09, 2006 7:13 PM To: Frederick Hirsch Cc: Hirsch Frederick; public-ws-policy@w3.org; public-ws-policy-request@w3.org Subject: Re: Proposed resolutions to issues 3549 and 3548
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 " src="cid:420574615@10082006-2118" width=16 border=0Frederick 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
To  public-ws-policy@w3.org  cc  Hirsch Frederick <frederick.hirsch@nokia.com>  Subject  Proposed resolutions to issues 3549 and 3548  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 15:54:19 UTC