[sunxacml-discuss] Re:AttributeSelector Ussage

[Muhammad M. A. <Muh...@ui...>]

Dear seth,
This email was that i posed on xacml user list , plz have a look




> Daniel - I think you missed Prakash's point. It's not that he wants=20
> AttributeSelector to return a generic DOM node, it's that he wants it =
to=20
> be able to use an arbitrary node as the root for some data, which may =
be a=20
> single value or may be mixed content. True, in the standard there are =
no=20
> datatypes that support this, but you can write a custom datatype (and=20
> custom functions) that do. When you do so, you can't select it with an =

> AttributeSelector since that mechanism is restricted to work only with =

> attributes/text/etc.

what about my presented solution, like what are your comments ?

<Apply FunctionId=3D"SECTINO: Extract-parameter-from-request">
        <AttributeValue  =3D"http://www.w3.org/2001/XMLSchema#string">
                =
/Request/Action/Attribute[@AttributeID=3D"p"]/AttributeValue/p/ID
        </AttributeValue>
</Apply>



in response the the request
<Request>
..
..
<Action>
<Attribute AttributeId=3D"urn:oasis:names:tc:xacml:1.0:attribute:p"
                DataType=3D"http://www.w3.org/2001/XMLSchema#String">
 <AttributeValue  DataType=3D"http://www.w3.org/2001/XMLSchema#String">
   &lt;p&gt;
    &lt;iD&gt;127Asbc &lt;/iD&gt;
    .
    &lt;/p&gt;
   </AttributeValue>
     </Attribute>
</Action>
.
.
</Request>

since it deals with not only single values, but mixed contents agreed??
what are the discrepencies in your opinion as you are the author of=20
sun-xacml implemenation, is this makes any conflict with your =
implemenations=20
functions by the way ???

regards
Muhammad.=20