[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xacml-users] AttributeSelector usage
Dear seth, > Daniel - I think you missed Prakash's point. It's not that he wants > AttributeSelector to return a generic DOM node, it's that he wants it to > be able to use an arbitrary node as the root for some data, which may be a > single value or may be mixed content. True, in the standard there are no > datatypes that support this, but you can write a custom datatype (and > 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="SECTINO: Extract-parameter-from-request"> <AttributeValue ="http://www.w3.org/2001/XMLSchema#string"> /Request/Action/Attribute[@AttributeID="p"]/AttributeValue/p/ID </AttributeValue> </Apply> in response the the request <Request> .. .. <Action> <Attribute AttributeId="urn:oasis:names:tc:xacml:1.0:attribute:p" DataType="http://www.w3.org/2001/XMLSchema#String"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#String"> <p> <iD>127Asbc </iD> . </p> </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 sun-xacml implemenation, is this makes any conflict with your implemenations functions by the way ??? regards Muhammad.