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


Help: OASIS Mailing Lists Help | MarkMail Help

xacml-users message

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

Subject: Re: [xacml-users] AttributeSelector usage


Based on your suggestion - I could feed an Attribute with datatype 'X'
to my own function f1 using the AttributeDesignators; but I can't feed
a Node of type 'X' to my function f1 - using AttributeSelectors
because the spec seems to imply if the XPath expression points to an
element node the the string representation needs to be used (thus
going back to the fact that it needs to be atomic). I don't see why
they need to be atomic when I have my own custom function f1 that
understands nodes of type 'X'.

Is this truly a spec restriction (or a bug in the implementation I am using)? 


On Wed, 9 Mar 2005 22:47:18 -0800, Daniel Engovatov <dengovatov@bea.com> wrote:
> >The question is "why we need ResourceContent element at all i.e. If we
> can >carry attribute values inside the request like  given above."
> For simplicity and for historical purposes I guess.   There is no
> requirement that the request is instantiated as an XML document.
> ResourceContent part is something that you actually need to instantiate
> as an XML document and feed it into your path processor.
> D;

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