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] | [Elist Home]

Subject: RE: [xacml] [Polar] PH09: New section 7.4.2 Attributes

I have suggested this many times - but we never got to discuss this.

My suggestion was to treat Designator used as an argument for a funciton
requiring single attribute as if it is implicitly wrapped in *-one-and-only
function application (will yield indeterminate if the bag is not of size


-----Original Message-----
From: Seth Proctor [mailto:seth.proctor@sun.com]
Sent: Monday, November 04, 2002 8:54 AM
To: xacml@lists.oasis-open.org
Subject: [xacml] [Polar] PH09: New section 7.4.2 Attributes

While working on our implementation, I noticed the problem of AD/AS types
always returning bags but almost all standard functions requiring single
types (and therefore rejecting bags as input). I suggested that one way to
solve this was to treat a bag with a single item the same as that single
on its own. Text was proposed for this change. There was no discussion on
list, but the updated change list from Thursday afternoon suggests that this
change suggestion was rejected, with no explination except "Use anyOf."

Since "Use anyOf" doesn't apply to my change request, and since there is no
other explination for why this was rejected or how I'm supposed to treat
this problem, I am asking my question again: how are functions that expect
single values supposed to deal with the bags that are required to be
from AD/AS types? I will once again suggest that text be added that makes
it clear that bags with one element are treated the same as just that one
element on its own. I will also point out that trying to solve this problem
by wrapping AD/AS types in functions that select single values from bags
result in much larger (and more copmlex) policies, and will increase
time dramatically, since all standard functions will require this wrapping.
Making the simple change I have suggested will prevent both of these


To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

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

Powered by eList eXpress LLC