Re: [xacml] Multi-valued attributes in Request. Forwarded from SethProctor.

[Polar Humenn <polar@syr.edu>]

We have multiple <AttributeValue> in attributes?
You mean in the Request Context?

That really shouldn't be.

Being that the request context is a "notational"  structure, there really
insn't any need for "economy", such as it is with XML, on these things.
Also, since the <Attribute> has the DataType attribute, and has the
<AttributeValue> element which must conform to the DataType, I really see
no reason to have such things. Why complicate matters?

The request context is "notational" and using the language of XML schema
should just say that each attribute shall have an attribute id, a
datatype, and a value for that datatype, and may have and issuer and issue
instant.

I suggest we clear this up by changing the schema to make the attribute
value occurance to minOccurs=1 maxOccurs=1.

Cheers,
-Polar


On Tue, 22 Oct 2002, Anne Anderson - Sun Microsystems wrote:

> I'm looking for a clarification on the use of multiple AttribueValue entries
> in an Attribute type in the Request. If I have an Attribute with multiple
> AttributeValue entries, am I supposed to treat each of these as being
> (effectively) separate Attributes with the same values for their meta-data?
> This seems like the logical approach, but nothing in the spec defines the
> right behavior. Following from this, is it an error if the Subject Category
> (for instance) Attribute has multiple AttributeValue entries, since the spec
> says that there must be one and only one value for this attribute?
>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>