Redundant constraint in Canonical N-Triples

In §4 of N-Triples, the additional constraints on Canonical 
N-Triples are listed.  They include:

* HEX MUST use only uppercase letters ([A-F]).
* Characters MUST NOT be represented by UCHAR.

The latter makes the former redundant.  HEX only appears in 
the UCHAR construct, and if it that MUST NOT be used, it's 
moot whether they're upper or lowercase.

I suggest removing the constraint about HEX being uppercase.

While I'm emailing about Canonical N-Triples, I find it 
surprising that it permits blank lines by virtue of (1)

   EOL  ::=  [#xD#xA]+

and (2) that the first triple is optional in

   nriplesDoc  ::=  triple? (EOL triple)* EOL?

I can understand that in full N-Triples, but as Canonical 
N-Triples removes almost every other piece of syntactic 
flexibility, it's surprising that this one remains.  Is this 
intentional?

This behaviour is not changed in Peter F. Patel-Schneider's 
errata of 29 June to clarify the whitespace handling of 
N-Triples.

Richard