| From | Sent On | Attachments |
|---|---|---|
| Seth Proctor | Mar 23, 2004 11:09 am | |
| Rich Salz | Mar 23, 2004 11:23 am | |
| Daniel Engovatov | Mar 23, 2004 11:24 am | |
| Seth Proctor | Mar 23, 2004 12:05 pm | |
| Seth Proctor | Mar 23, 2004 12:08 pm | |
| Daniel Engovatov | Mar 23, 2004 12:10 pm | |
| Satoshi Hada | Mar 23, 2004 11:27 pm | |
| Polar Humenn | Mar 25, 2004 5:28 am | |
| Daniel Engovatov | Mar 25, 2004 9:47 am | |
| Tim Moses | Mar 25, 2004 10:51 am | |
| Daniel Engovatov | Mar 25, 2004 10:55 am | |
| Tim Moses | Mar 25, 2004 11:12 am | |
| Seth Proctor | Mar 26, 2004 9:12 am | |
| Seth Proctor | Mar 26, 2004 9:48 am |
| Subject: | RE: [xacml] legal values for Strings | |
|---|---|---|
| From: | Tim Moses (tim....@entrust.com) | |
| Date: | Mar 25, 2004 11:12:15 am | |
| List: | org.oasis-open.lists.xacml | |
Daniel - No we don't. You'd have to define an extension function. Shouldn't be a problem. Should it? All the best. Tim.
-----Original Message----- From: Daniel Engovatov [mailto:deng...@bea.com] Sent: Thursday, March 25, 2004 2:11 PM To: Tim Moses; Seth Proctor Cc: xac...@lists.oasis-open.org Subject: RE: [xacml] legal values for Strings
Do we have any functions that accept this datatype? What would we do with it?
-----Original Message----- From: Tim Moses [mailto:tim....@entrust.com] Sent: Thursday, March 25, 2004 11:07 AM To: 'Seth Proctor'; Daniel Engovatov Cc: 'xac...@lists.oasis-open.org' Subject: RE: [xacml] legal values for Strings
Seth et al - Probably a silly question. But, why wouldn't we solve this problem like this ... ?
<AttributeAssignment DataType="urn:oasis:xacml:2.0:policy:schema:wd:08#AttributeSelector" AttributeId="..." <AttributeSelector ... </AttributeAssignment>
All the best. Tim.
-----Original Message----- From: Seth Proctor [mailto:Seth...@Sun.COM] Sent: Tuesday, March 23, 2004 3:24 PM To: Daniel Engovatov Cc: xac...@lists.oasis-open.org 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 < 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_workgro up.p hp.





