[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [xacml] Multi-valued attributes in Request. Forwarded from SethProctor.
I agree too. Multi-value attributes make the semantics of attribute comparison more difficult. Konstantin bill parducci wrote: > i agree. > > b > > Polar Humenn wrote: > >> 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 > > > > ---------------------------------------------------------------- > To subscribe or unsubscribe from this elist use the subscription > manager: <http://lists.oasis-open.org/ob/adm.pl> > -- ___________________________________________________________ Konstantin Beznosov Security Architect Quadrasis -- We Unify Security http://www.quadrasis.com Hitachi Computer Products (America), Inc. konstantin.beznosov@quadrasis.com http://www.beznosov.net/konstantin 1601 Trapelo Road Phone: 781 768 5840 Waltham, MA 02451 Fax: 781 890 4998 ___________________________________________________________
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC