- From: Frederick Hirsch <frederick.hirsch@nokia.com>
- Date: Mon, 21 Aug 2006 16:14:01 -0400
- To: ext Anthony Nadalin <drsecure@us.ibm.com>
- Cc: Frederick Hirsch <frederick.hirsch@nokia.com>, public-ws-policy@w3.org, public-ws-policy-request@w3.org
which is the assertion and which the parameter? <foo:Hello> <bar:GoodDay> regards, Frederick Frederick Hirsch Nokia On Aug 21, 2006, at 3:42 PM, ext Anthony Nadalin wrote: > You don't need to tell them apart as they are easy to distinguish > from one another, They are used for different purposes, the main > reason of nested policy is to be able to have intersection, suggest > that you give the intersection as the concrete example. > > 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/21/2006 02:35 PM > > <ecblank.gif> > > To > <ecblank.gif> > > Anthony Nadalin/Austin/IBM@IBMUS > <ecblank.gif> > > cc > <ecblank.gif> > > Frederick Hirsch <frederick.hirsch@nokia.com>, public-ws- > policy@w3.org, public-ws-policy-request@w3.org > <ecblank.gif> > > Subject > <ecblank.gif> > > Re: Proposed change to Framework 3.1 > <ecblank.gif> > <ecblank.gif> > > > This is what this sentence says, that you need to tell parameters and > assertions apart, exactly for that reason, and that how it is done is > by putting nested assertions within wsp elements as described in the > proposed text. > > regards, Frederick > > Frederick Hirsch > Nokia > > > On Aug 21, 2006, at 3:11 PM, ext Anthony Nadalin wrote: > > > >Use of a policy framework element to contain a nested assertion > > enables nested assertions to be distinguished from assertion > > parameters and processed appropriately > > > > The major difference between using assertion parameter and a nested > > assertion is the intersection ability, the above sentence does not > > make sense > > > > 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/21/2006 12:01 PM > > > > <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 change to Framework 3.1 > > <ecblank.gif> > > <ecblank.gif> > > > > I propose the following change to 3.1, "Policy Assertion" in the > > latest editor's draft of the policy framework [1]. The change is > > shown as a red-line to 3.1, in the attached PDF. > > > > This is proposed as a partial resolution to bug report 3549 [2] and > > as a replacement to previous proposals regarding text to clarify the > > framework with regards to this issue. > > > > I propose the issue with regards to the normalization procedure in > > 4.2 (as also noted in the bug report) should be made a separate > > issue. This normalization procedure does not appear to explicitly > > pass through parameters. > > > > 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] <http://www.w3.org/Bugs/Public/show_bug.cgi?id=3549> > > > > [attachment "policy-framework-3549-proposal.pdf" deleted by Anthony > > Nadalin/Austin/IBM] > > >
Received on Monday, 21 August 2006 20:16:13 UTC