OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xacml-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [xacml-dev] Why are PolicySetIdReference and PolicyIdReference distinct elements?


Hi Danny,

They don't have the same scope. Policy and PolicySets could conceivably have different identifier spaces since there is nothing in the spec which explicitly requires that identifiers must be unique across Policies and PolicySets. Therefore the reference must indicate whether it is for resolving a policy set or a policy.

Best regards,
Erik

On 2011-12-16 20:10, Danny Thorpe wrote:

I was digging through some old code recently and was reminded of a little puzzle I came across some time ago:

 

Why does XACML have different elements for PolicySetIdReference and PolicyIdReference?  They have the same data, same ancestor, and live in the same scope. The only difference is in what lives at the other end of the reference.

 

Are they separate elements to appease a schema requirement?

 

It just seems odd that to identify a policy you have to carry around its unique ID *and* its type. If the ID is truly unique, isn’t the type redundant? 

 

-Danny




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]