xacml — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
Re: [xacml] CR 144: function "present" needs to be fixed.
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.
- From: Simon Godik <[email protected]>
- To: XACML <[email protected]>
- Date: Thu, 24 Oct 2002 11:24:00 -0700
> 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
> 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>
<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
- Follow-Ups:
- Re: [xacml] CR 144: function "present" needs to be fixed.
- From: Polar Humenn <[email protected]>
- Re: [xacml] CR 144: function "present" needs to be fixed.
- References:
- Re: [xacml] CR 144: function "present" needs to be fixed.
- From: Polar Humenn <[email protected]>
- Re: [xacml] CR 144: function "present" needs to be fixed.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]