[Bug 4890] 4.3.2 Filter Expressions - Normalization for standalone PrimaryExpr needed?

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4890


jmdyck@ibiblio.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         OS/Version|Windows XP                  |All
           Platform|PC                          |All
         Resolution|                            |INVALID




------- Comment #1 from jmdyck@ibiblio.org  2007-07-29 22:35 -------
> Presumably the intent is to normalize the standalone case w/ no special
> treatment (unlike 4.2.1)?  Something like:
> 
> [PrimaryExpr]Expr
> =
> PrimaryExpr

Asserting that normalization has no effect on PrimaryExprs would be incorrect.
(Most kinds of PrimaryExpr, apart from Literals and VerRefs, can be expected to
change under normalization.)

You'll often find that non-terminal N does not have an explicit normalization
rule [N]_Expr == ...  (The main exception to this is cases where normalization
has no effect.) Instead, normalization is defined on various more specific
forms derived from N; collectively, they define the normalization of N.

I'm marking this issue as resolved INVALID, because that's the closest
alternative to "reasonable question, but not a bug in the spec". If you agree
with this resolution, please CLOSE the issue.

Received on Sunday, 29 July 2007 22:35:07 UTC