This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
E.1.3 Attribute filtering Notation "Value filter @QName => ()" "Value filter @QName => SimpleValue" But SimpleValue derives (), so in a judgment where the RHS value is (), it could be an instance of either form. And they appear to mean slightly different things. "Value filter @QName => () or SimpleValue" This seems fairly ad hoc. Instead of: Value1 filter @xsi:nil => () or false why not use existing notation and say: Value1 filter @xsi:nil => SimpleValue SimpleValue in { (), false } Sem / rule (1|2) / premise 1 "dynEnv |- Value1 of attribute:: => Value2" What kind of judgment is this? Maybe you mean: dynEnv |- axis attribute:: of Value1 => Value2 (leftover from last year, comment #236) Sem / rule (1|2) / premise 2 "dynEnv |- Value2 of attribute, QName => ..." Again, what kind of judgment is it? I don't even have a guess. (leftover from last year, comment #237)
Applied the following fixes: (1) distinguished when the attribute content is empty: Value filter @QName => () from then the attribute is absent: Value filter @QName => absent (2) As suggested, used the standard notation when multiple values are possible for a judgment, as in: Value1 filter @xsi:nil => SimpleValue SimpleValue in { (), false } (3) Fixed the definition for the filter judgment to use the axis and nodetest judgment properly. - Jerome