[encoding] Consider making the DOM name the canonical name (#32)

It's pretty sad that this specification chose to invent a new case (the lower case) for canonical names when a historical casing (the IANA case implemented by WebKit/Blink and, except for gbk, by Gecko) already existed.

Imagine that you are writing a library for this stuff. You can't compute the DOM name from the name in this specification without hard-coding knowledge of the DOM names. However, you could compute the name in this specification by ASCII-lower-casing the DOM name.

Is there a good reason not to:

1. Change the _names_ in this specification to the _Compatibility names_ from the DOM spec.
2. Get rid of the special mapping in the DOM spec.
3. Define that `.encoding` of `TextEncoder` and `TextDecoder` returns _name_ (i.e. now the mixed-case IANA/DOM name) ASCII-lowercased.

?

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/32