- From: Ashok Malhotra <ashok.malhotra@oracle.com>
- Date: Thu, 14 Sep 2006 11:17:59 -0700
- To: "Daniel Roth" <Daniel.Roth@microsoft.com>, "Frederick Hirsch" <frederick.hirsch@nokia.com>
- CC: "Sverdlov, Yakov" <Yakov.Sverdlov@ca.com>, "public-ws-policy@w3.org" <public-ws-policy@w3.org>
You need to open the Word document in OpenOffice and then export as PDF. I can do that if you want me to. All the best, Ashok > -----Original Message----- > From: public-ws-policy-request@w3.org > [mailto:public-ws-policy-request@w3.org] On Behalf Of Daniel Roth > Sent: Thursday, September 14, 2006 6:52 AM > To: Frederick Hirsch > Cc: Sverdlov, Yakov; public-ws-policy@w3.org > Subject: RE: NEW ISSUE: Clarify the policy model for Web Services > > > I actually don't have a way to generate a PDF. All I did was > dump the text into word and then use the Compare > functionality. Does someone out there have a Word -> PDF converter? > > Daniel Roth > > -----Original Message----- > From: Frederick Hirsch [mailto:frederick.hirsch@nokia.com] > Sent: Wednesday, September 13, 2006 12:05 PM > To: Daniel Roth > Cc: Frederick Hirsch; Sverdlov, Yakov; public-ws-policy@w3.org > Subject: Re: NEW ISSUE: Clarify the policy model for Web Services > > Daniel > > Can you please send a PDF, I appear to be unable to open this file. > > Thanks > > regards, Frederick > > Frederick Hirsch > Nokia > > > On Sep 13, 2006, at 11:43 AM, ext Daniel Roth wrote: > > > To help people process this proposal, I created the > attached diff in > > Word so you can see what is changing. > > > > > > > > Yakov, please make sure that the diff looks right. > > > > > > > > Thanks. > > > > > > > > Daniel Roth > > > > > > > > From: public-ws-policy-request@w3.org [mailto:public-ws-policy- > > request@w3.org] On Behalf Of Sverdlov, Yakov > > Sent: Wednesday, September 13, 2006 7:27 AM > > To: public-ws-policy@w3.org > > Subject: Re: NEW ISSUE: Clarify the policy model for Web Services > > > > > > > > Hi, > > > > > > > > Here's the draft proposal for section 3.4. As you can see, > I tried to > > minimize the changes. > > > > > > > > Regards, > > > > > > > > Yakov Sverdlov > > > > CA > > > > > > > > 3.4 Policies of Entities in a Web Services-based System > > > > Applied in the Web services-based system, policy is used to convey > > conditions on an interaction between entities (requester > application, > > provider service, Web infrastructure component, etc). > > Any entity in a Web services-based system may expose a policy to > > convey conditions under which it functions. Satisfying > assertions in > > the policy usually results in behavior that reflects these > conditions. > > For example, if two entities - requester and provider - > expose their > > policies, a requester might use the policy of the provider > to decide > > whether or not to use the service. A requester may choose any > > alternative since each is a valid configuration for > interaction with > > the service, but a requester MUST choose only a single > alternative for > > an interaction with a service since each represents an alternative > > configuration. > > > > A policy assertion is supported by an entity in the web services- > > based system if and only if the entity satisfies the > requirement (or > > accommodates the capability) corresponding to the > assertion. A policy > > alternative is supported by an entity if and only if the entity > > supports all the assertions in the alternative. And, a policy is > > supported by an entity if and only if the entity supports > at least one > > of the alternatives in the policy. Note that although policy > > alternatives are meant to be mutually exclusive, it cannot > be decided > > in general whether or not more than one alternative can be > supported > > at the same time. > > > > Note that an entity may be able to support a policy even if > the entity > > does not understand the type of each assertion in the vocabulary of > > the policy; the entity only has to understand the type of each > > assertion in the vocabulary of a policy alternative the entity > > supports. This characteristic is crucial to versioning and > incremental > > deployment of new assertions because this allows a > provider's policy > > to include new assertions in new alternatives while > allowing entities > > to continue to use old alternatives in a backward-compatible manner. > > > > > > > > <3672_proposal_dif.xml> > > > >
Received on Thursday, 14 September 2006 18:19:17 UTC