[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
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.moses@entrust.com] Sent: Thursday, March 25, 2004 11:07 AM To: 'Seth Proctor'; Daniel Engovatov Cc: 'xacml@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.Proctor@Sun.COM] Sent: Tuesday, March 23, 2004 3:24 PM To: Daniel Engovatov Cc: xacml@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.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]