xacml — archive

RE: [xacml] Hierarhical resources.. part 0.1

From: Daniel Engovatov <[email protected]>
To: [email protected]
Date: Tue, 11 May 2004 20:02:00 -0000

 MHonArc v2.5.0b2 -->
















xacml message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: RE: [xacml] Hierarhical resources.. part 0.1




From: "Daniel Engovatov" <[email protected]>
To: <[email protected]>
Date: Tue, 11 May 2004 13:06:14 -0700








Dang, you may be right.   We bypassed this issue for constraints as we
had functions to make a bag of values.  As I was not working with
request schema I forgot about that.

But, couldn't you just specify multiple instances of the same attribute
in request context?  Attribute currently has exactly one attribute value
(which is a bad outage in my opinion - we need to be able to  bags) -
but is it prohibited to have multiple attribute with the same
attributeId?

In request:
<resource>
	<Attribute AttributeID = "foo" DataType = "string">
		<AttributeValue >bar</AttributeValue>
	</Attribute>
	<Attribute AttributeID = "foo" DataType = "string">
		<AttributeValue >spam</AttributeValue>
	</Attribute>
<resource>

Would not that define bag[string]   foo = ["bar", "spam"] ?


Of cause defining "bag" metadata along with datatype, and supplying
multiple
<AttributeValue>'s is much better.

Remind me - why do we not send bags in a request?