[Bug 25421] Split the key/code value tables out of the primary DOM3 Events spec.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25421

--- Comment #2 from Gary Kacmarcik <garykac@google.com> ---
We are doing this because of the following reasons:

(1) We need a light-weight process for updating the 'key' and 'code' tables
that is separate from the main D3E spec so that we can easily add new values to
these tables without revising the entire D3E spec. We hope that we don't have
to update these tables often, but we recognize that mobile (e.g.) is an
interesting area that is changing relatively fast.

See the previous discussion relating to this:
http://lists.w3.org/Archives/Public/www-dom/2014JanMar/0135.html

(2) It is *easier* to find 'key' and 'code' values when they are in separate
documents because you can search the entire doc without worrying about
encountering values from the other table. This is an issue that has already
come up as people are using the ED because the tables are rather large --
searching is practically a requirement when looking for appropriate values and
it is easy to find yourself in the "wrong" section.

By having a separate spec that defines all the 'key' values, developers can
refer to this single doc without having to worry about being confused by the
'code' values. And vice versa for people looking up 'code' values.


And finally, your comment that it is "already hard enough to find the latest
version" is not a valid argument. Once the spec is finalized and released, the
latest version will be clear and obvious - just as it is for other W3C specs.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 23 April 2014 16:46:40 UTC