OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xacml-dev message

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


Subject: Re: [xacml-dev] attrubuteselector usage - how to get element nodesincluding their decendants with the attributeselector


Jan,

I believe we discussed this in the XACML TC, and the intent was
that you could use the identity of the element you want
(e.g. gml:Polygon) as the DataType.  As Seth says, you would have
to write code to handle these, as they are not standard XACML
DataTypes.  You would also have to write your own functions for
dealing with them.

Anne

On 16 November, Seth Proctor writes: Re: [xacml-dev] attrubuteselector usage - how to get element nodes including their decendants with the attributeselector
 > From: Seth Proctor <Seth.Proctor@Sun.COM>
 > To: Jan bei GMX <herrmann_jan@gmx.de>
 > Cc: xacml-dev@lists.oasis-open.org
 > Subject: Re: [xacml-dev] attrubuteselector usage - how to get element nodes
 > 	including their decendants with the attributeselector
 > Date: Tue, 16 Nov 2004 13:23:37 -0500
 > 
 > 
 > Hi Jan.
 > 
 > On Tue, 2004-11-16 at 10:38, Jan bei GMX wrote:
 > > I put the xml document which I want to protect in the resourceContent
 > > element of the xacml request context.
 > > [...]
 > > Now I'm trying to select a part of the resourceContent with the help of
 > > the attributeselecor.
 > > 
 > > <AttributeSelector RequestContextPath="//context:ResourceContent/gml:Polygon" DataType="urn:oasis:names:tc:xacml:1.0:data-type:string"/>
 > > 
 > > What I'd like to get back is a string which is equal to this one:
 > > [...XML content...]
 > > Unfortunately I can only access the text nodes. Does anybody now how I
 > > can get the desired string by using the attrubuteselector or is it
 > > simply not posssible?
 > 
 > What you want is not possible using an attribute selector. Check out
 > section 5.42 of the 2.0 specification. It says that a selector may only
 > resolve an attribute, text, comment, or processing intstruction node,
 > and then is supposed to take the string value and create an attribute
 > value from that. Yes, this is pretty limiting. It would be nice to get
 > back a node that you could operate on, or at least an Element that you
 > could work with, but that's not supported. You'll need to write a custom
 > function that lets you select an Element and handle all the
 > sub-elements. Sorry.
 > 
 > 
 > seth
 > 
 > 
 > ps  Looking at my code now, I think I may actually be too lenient here,
 > since I let you work on the text of top-level Elements too. Hrm..
 > 

-- 
Anne H. Anderson             Email: Anne.Anderson@Sun.COM
Sun Microsystems Laboratories
1 Network Drive,UBUR02-311     Tel: 781/442-0928
Burlington, MA 01803-0902 USA  Fax: 781/442-1692



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