MHonArc v2.5.2 -->
xacml message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: Re: [xacml] CR 144: function "present" needs to be fixed.
> So, I think a better approach would be to add
the following elementsto the
> schema with the semantics I proposed in the
previous iterations.
>
> These elements woud be element instances
of the <AttributeDesignatorType>:
>
>
ActionAttributeIsPresent
ActionAttributeMustBePresent
>
ResourceAttributeIsPresent
ResourceAttributeMustBePresent
> EnvironmentAttributeIsPresent
EnvironmentAttributeMustBePresent
>
> These elements would be
element instances of the
> <SubjectAttributeDesignatorType>:
>
> SubjectAttributeIsPresent
SubjectAttributeMustBePresent
>
> These elements would be element
instances of the
> <SubjectAttributeDesignatorWhereType>:
>
> These elements can be element instances of the
<AttributeSelectorType>:
>
>
AttributeIsPresent
AttributeMustBePresent
I think that <AttributeDesignator> and
<AttributeSelector> elements with mustBePresent attribute will
cover
all cases:
<xs:complexType
name="AttributeDesignatorType">
<xs:attribute
name="AttributeId" type="xs:anyURI" use="required"/>
<xs:attribute name="DataType"
type="xs:QName" use="required"/>
<xs:attribute
name="MustBePresent" type="xs:boolean" use="required"/>
<-- new attribute
<xs:attribute name="Issuer"
type="xs:anyURI" use="optional"/>
</xs:complexType>
<xs:complexType
name="AttributeSelectorType">
<xs:attribute
name="RequestContextPath" type="xs:string" use="required"/>
<xs:attribute name="DataType"
type="xs:QName" use="required"/>
<xs:attribute
name="MustBePresent" type="xs:boolean" use="required"/> <-- new
attribute
</xs:complexType>
Simon
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC