OASIS Open Mailing List Archives  ·  All Lists  ·  xacml  ·  2004-03

xacml — archive

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]

RE: [xacml] legal values for Strings


 MHonArc v2.5.0b2 -->

















xacml message

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


Subject: RE: [xacml] legal values for Strings



On Tue, 2004-03-23 at 14:40, Daniel Engovatov wrote:
> None of the XACML standard data types had to be represented as complex
> content, so that would definitely be an extension.   It seems to me that
> your example is not valid (need to have all the proper &lt etc..) - is
> it?

Well, I'd like the example I gave to be invalid. This gets back to my
previous posting about AttributeAssignments. We have examples that look like:

  <AttributeAssignment DataType="...:string" AttributeId="..."
    <AttributeSelector ...
  </AttributeAssignment>

As I read that, we're looking at an AttributeValue (the assignment) of
type string that contains complex content. Thus, my concern.


seth



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



[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]