RE: [xacml] legal values for Strings

I think that all these responses agree that we should
correct

the test cases for obligations as per Seth's comment:

http://lists.oasis-open.org/archives/xacml-comment/200403/msg00003.html

PS:

The attribute selector example was the reason why
I (wrongly?) thought that 

all the attribute assignments must be written like

 <AttributeAssignment

     AttributeId="..."

     DataType="http://www.w3.org/2001/XMLSchema#string">

     <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">assignment1</AttributeValue>

 </AttributeAssignment>

Satoshi Hada

IBM Tokyo Research Laboratory 

mailto:

"Daniel Engovatov"
<> 

2004/03/24 05:25

To

"Seth Proctor"
<>

cc

<>

Subject

RE: [xacml] legal values
for Strings

Yep.  That is most definitely a type error that
we should not make.

<AttributeSelector> is not of data type ":string" 

-----Original Message-----

From: Seth Proctor [mailto:] 

Sent: Tuesday, March 23, 2004 12:24 PM

To: Daniel Engovatov

Cc: 

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

To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/xacml/members/leave_workgroup.php.