- From: ashok malhotra <ashok.malhotra@oracle.com>
- Date: Wed, 10 Oct 2007 13:58:43 -0700
- To: David Orchard <dorchard@bea.com>
- CC: public-ws-policy@w3.org
Hi Dave: I used the fact that WS-SecurityPolicy discusses order to motivate the need for order in at least some policies. I also quoted from the note from Tony Rogers. Subsequently, there was a note from Bob Natale who agrees that order is important but does not like the solution I suggested. What needs to be made clear is that order is not important in all policies, but there are situations where it is important and for these situations we need a solution. Ashok David Orchard wrote: >>-----Original Message----- >>From: public-ws-policy-request@w3.org >>[mailto:public-ws-policy-request@w3.org] On Behalf Of ashok malhotra >>Sent: Wednesday, October 10, 2007 9:56 AM >>To: public-ws-policy@w3.org >>Subject: Ordering of Assertions: Comment on WS-Policy Primer LCWD >> >> ><snip/> > > >>In many cases the >>order in which assertions are processed may not matter, but >>where it does matter do we need to specify a special >>assertion for every pair of assertions that need to be >>ordered? Clearly, this is not feasible as the Policy >>processing engine will need to be undated whenever a new >>ordering assertion is added. So, what we need is a >>general-purpose ordering assertion. >> >> > >Your note jumps from assumption to conclusion to design with great >speed, indeed from assumption to conclusion within 3 sentences. Those 3 >fleety sentences do not answer my previous emails central question of >"when does order matter?". In case my question was missed, perhaps >because of burdensom length of my previous message, I'll ask again more >succinctly: > >When does order matter? > >Until the use case is agreed by the WG, design discussions are very >premature IMHO. > >Cheers, >Dave > > > > -- All the best, Ashok
Received on Wednesday, 10 October 2007 21:01:25 UTC