RE: [xacml] [CR] AttributeSelectorIndirect

[Polar Humenn <polar@syr.edu>]

On Fri, 6 Sep 2002, Daniel Engovatov wrote:

> >Unfortunately, the first argument, by the schema, says that it must be the
> >Selector or Designator. The explicit value to match against is the second
> >element in the schema. To reverse them, which I wouldn't mind, we would
> >need a SCHEMA change, and I would have to change the definition of the
> >match functions.
>
>
> I would not mind it either.  Other wise we either should use only the
> sequence type functions (at-least-one-member-of, set-equals), of member-of,
> with one argument specified as <attributevalue> element. *-equal would be
> illegal.

It doesn't work that way.

> Otherwise we need to allow arguments to be *-first-and-only, or *-sequence
> functions,
> and in this case why not to use the same semantics as for <condition>
> element altogether.

The target is suppose to be simple for indexing. That is why the explicit
value was listed as the matching argument and not some general expression.

-Polar


> daniel;
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>