xacml — archive

[System]

Not sure what exactly is being broken - the evaluation performed is exactly the same - the only difference is the "automatic" type convertion function application for this very narrow and well defined case. Matching (member-of "blah" <designator>) and (string-equal "blah" <implicit string-one-and-only<designator> >) is the same - you can compile and make sure the type safety is satisfied just as well. It is only a syntax issue to allow easier use of designators/selector in target without opening up the syntax to a full blown <apply> tree. If you have your context precompiled and verified you index the target in just the same way - you just write it down in a little bit diferent manner. . But I do agree that everything complicated sould go into condition - but we already have our target structure. Daniel;