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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xacml message

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


Subject: Re: [xacml] condition reference text (item 7)


Hi Tim,
My thinking was that we can place variable definition close to the rule. I'm
also ok to group all definitions together.
(as you propose)

Simon

----- Original Message -----
From: "Tim Moses" <tim.moses@entrust.com>
To: "'Simon Godik'" <simon.godik@overxeer.com>; <xacml@lists.oasis-open.org>
Sent: Tuesday, March 16, 2004 11:45 AM
Subject: RE: [xacml] condition reference text (item 7)


> Simon - Here is your definition of PolicyType ...
>
> <xs:complexType name="PolicyType">
>  <xs:sequence>
>   <xs:element ref="xacml:Description" minOccurs="0"/>
>   <xs:element ref="xacml:PolicyDefaults" minOccurs="0"/>
>   <xs:element ref="xacml:Target"/>
>   <xs:choice minOccurs="0" maxOccurs="unbounded">
>    <xs:element ref="xacml:VariableDefinition"/>
>    <xs:element ref="xacml:Rule"/>
>   </xs:choice>
>   <xs:element ref="xacml:Obligations" minOccurs="0"/>
>  </xs:sequence>
>  <xs:attribute name="PolicyId" type="xs:anyURI" use="required"/>
>  <xs:attribute name="RuleCombiningAlgId" type="xs:anyURI" use="required"/>
> </xs:complexType>
>
> I had been assuming it would be more like this ...
>
> <xs:complexType name="PolicyType">
>  <xs:sequence>
>   <xs:element ref="xacml:Description" minOccurs="0"/>
>   <xs:element ref="xacml:PolicyDefaults" minOccurs="0"/>
>   <xs:element ref="xacml:Target"/>
>   <xs:element ref="xacml:VariableDefinition" minOccurs="0"
> maxOccurs="unbounded"/>
>   <xs:element ref="xacml:Rule" minOccurs="0" maxOccurs="unbounded"/>
>   <xs:element ref="xacml:Obligations" minOccurs="0"/>
>  </xs:sequence>
>  <xs:attribute name="PolicyId" type="xs:anyURI" use="required"/>
>  <xs:attribute name="RuleCombiningAlgId" type="xs:anyURI" use="required"/>
> </xs:complexType>
>
> The only significance (I think) is that your definition allows
> VariableDefinition elements to be intermixed with Rule elements, whereas
the
> alternative causes all VariableDefinition elements to occur "up front".
> i.e. there can be no forward references.
>
> What do you think?  Is the alternative preferable?  All the best.  Tim.
>
> -----Original Message-----
> From: Simon Godik [mailto:simon.godik@overxeer.com]
> Sent: Wednesday, March 10, 2004 11:10 PM
> To: xacml@lists.oasis-open.org
> Subject: [xacml] condition reference text (item 7)
>
>
> Hi Tim,
> Here is condition reference text and schema. Text is adopted (with some
> additions) from Polar's email
>
> Simon
>




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