> -----Original Message-----
> From: Anne Anderson [mailto:]
> Sent: Monday, Dec 19, 2005 2:25 PM
> To: Frank McCabe
> Cc:
> Subject: Re: [dipal-discuss] FAQ: what are the basic
> Assertion functions, and how are they provided?
>
> Hi Frank,
>
> These are good points. I think they touch partly on expressivity
> requirements for a policy Assertion language and partly on an
> appropriate division of functionality between the Assertions and the
> policy framework in which Assertions are used.
>
> For issuer information, I envision this expressed at the policy
> framework level (or even the policy metatdata level - the policy
> envelope), and not the Assertion level. An entire policy,
> including all
> its Assertions, would be issued by the one issuer identified at the
> policy or policy metadata level. Since we are discussing an Assertion
> language to be used within some externally-specified policy framework
> language, I did not include this functionality in the list of "basic
> functions" for an Assertion itself.
>
> For subject information, there are at least three approaches. 1) The
> identity of the subject is not always relevant for a web services
> policy, so I don't think all policies will include a "subject".
Hi Anne,
Could you elaborate on (1) a bit ? I am trying to imagine the situations
how a policy subject may not be relevant. I can imagine that a policy
may apply to several subjects #Subject >=1, but it is a bit hard for me
to imagine situations where the subject is never relevant (i.e. #Subject
= 0). I am not sure why a policy will exist if there is no policy
subject.
Or did you mean that a policy subject is beyond WSDL component model
attachment(if we were to take WS-Policy as an example...) ?
Thanks,
--umit
