Re: APPEL and the dataschema element

> > But this seems to cause a serious problem for the APPEL matching algorithm
> >
> > Here is an example of what I mean:
> >
> > RULESET
> > ========
> >  <DATA-GROUP base="mycustomschema.xml" appel:connective="or">
> >         <DATA category="online"/>
> >       </DATA-GROUP>
> >
> > EVIDENCE
> > ========
> > <DATA-GROUP base="" appel:connective="or">

Oops? There can't be an appel:connective in the *evidence*!

base="" would mean the local document, the policy, f.e.
I guess, you just mean <DATA-GROUP>?

> >         <DATA ref="#user.home.online.email"/>
> >         <DATA ref="#user.home.online.uri"/>
> >         <DATA ref="#user.business.online.email"/>
> >         <DATA ref="#user.business.online.uri"/>
> >         <DATA ref="#dynamic.cookies" category="online"/>
> >         <DATA ref="#dynamic.miscdata" category="online"/>
> >       </DATA-GROUP>
> >
> >
> > Although the ruleset and the evidence may be referring to the same
> external
> > schema, the matching algorithm ( APPEL 5.5.2 ) will fail on the
> <DATA-GROUP>
> > element.

That's right. So the matching semantics of the <DATA-GROUP> and the
<DATA> element will be changed slightly in the upcoming spec:
Each DATA ref attribute needs to be expanded to a full URI with respect to
the DATA-GROUP base attribute, if any. The DATA-GROUP ref attribute
will not be matched directly any longer.

Nikolaj