Re: Standardize Buttons For TV-Web Remotes?

Thanks Doug. Couple of comments:

   - under Character Key Values appears VK_PROGRAM_{UP,DOWN} which don't
   have character values;
   - under Duplicate Key Values, what were the criteria for inclusion here?
   was it: value is duplicate if it is already present in DOM-3 Events or if it
   is a duplicate in these (TV) tables?

G.

On Tue, May 17, 2011 at 4:58 AM, Doug Schepers <schepers@w3.org> wrote:

> Hi, folks-
>
> Sorry, it took me longer than I thought... I'm at a F2F meeting, which is
> distracting. :)
>
> I've now added around 70 new equivalent key values to the list [1], and
> changed the names of several others to be more broadly applicable.  I have
> changed names for several of the VK_* values, to be more clear in a general
> context, which I hope is acceptable.
>
> Attached is my breakdown of the table that Glenn provided, explaining my
> process.
>
> [1]
> http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#key-values-list
>
>
> Regards-
> -Doug Schepers
> W3C Team Contact, SVG, WebApps, and Web Events WGs
>
>
> Doug Schepers wrote (on 5/13/11 9:27 PM):
>
>  Hi, Glenn, Giuseppe-
>>
>> I'm in the process of doing exactly that... splitting Glenn's table out
>> into different types of keys, and marking up the candidates for
>> inclusion for DOM3 Events Key Values set. As Glen and I discussed
>> before, some of these are duplicates of existing key values, for
>> example, and others are for specific characters, which aren't necessary
>> with DOM3 Events' KeyboardEvent model, which simply uses Unicode for
>> such characters. I already did this process for an earlier version of
>> this table, and I'm documenting my process this time, to make it clear
>> which I'm adding and why I'm leaving off the others.
>>
>> So far, I've found approximately 70 new values that are unique to media
>> remotes (or similar devices), and I have already added most of these to
>> the spec. Please see the first rough draft in the DOM3 Events Editor's
>> Draft, all marked "Media", starting with the 'VolumeDown' key [1].
>>
>> I should be done by tomorrow, and I'll reply on this thread.
>>
>> [1]
>>
>> http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#key-VolumeDown
>>
>>
>> Regards-
>> -Doug Schepers
>> W3C Team Contact, SVG, WebApps, and Web Events WGs
>>
>> Glenn Adams wrote (on 5/13/11 11:53 AM):
>>
>>> My intention in creating this table was merely to enumerate and describe
>>> the current set of VKs being used in various TV related specifications.
>>> As you notice, I also attempted to identify some equivalence classes.
>>>
>>> What I did not do was to cull this table for the purpose of proposing a
>>> specific set of key identifiers. I'm not sure I am in a position to
>>> formulate a specific proposal for specific identifiers. I would prefer
>>> the editor(s) of DOM-3 Events to take this material as input, and to
>>> make appropriate decisions about what to support. I am available for
>>> consultation in such a process.
>>>
>>> Regards,
>>> Glenn
>>>
>>> On Fri, May 13, 2011 at 8:21 AM, Giuseppe Pascale <giuseppep@opera.com
>>> <mailto:giuseppep@opera.com>> wrote:
>>>
>>> Hi Glenn,
>>> thanks for sharing this.
>>>
>>> One general comment: as expected there are same overlaps between
>>> different specs (i.e. different variable / same key).
>>>
>>> My understanding from your proposal is that the DOM spec will
>>> "mandate" one and keep the other as legacy (but deprecated). Is that
>>> correct?
>>> One example could be VK_GREEN that is equivalent to VK_COLORED_KEY_1.
>>>
>>> If this is the case, wouldn't be better to split the table in 2 so
>>> that is clear which one are the variables to use (for content
>>> developers) and which one are the legacy variables to support (for
>>> UA developers)?
>>>
>>> cheers,
>>> /g
>>>
>>>
>>> On Thu, 12 May 2011 20:36:01 +0200, Glenn Adams <glenn@skynav.com
>>> <mailto:glenn@skynav.com>> wrote:
>>>
>>> Apparently I neglected to send out the promised update to the VK
>>> keys for
>>> TV, including MHEG-5 and EBIF data. Since DOM-3 Events is moving
>>> close
>>> towards LC [1], please consider this updated table as input for
>>> expanding
>>> Section 6.2.7 Key Values Set.
>>>
>>> I did not have an opportunity to verify DVB-HTML requirements.
>>> At this
>>> point, I presume that DVB-HTML usage is equal to or a subset of
>>> OCAP VKs.
>>>
>>> Note that I (personally) created the "Description" text for this
>>> table, so
>>> please consider this text to be a member contribution for direct
>>> use in the
>>> spec.
>>>
>>> Regards,
>>> Glenn Adams (for Samsung)
>>>
>>> [1]
>>> http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html
>>>
>>> On Thu, Oct 28, 2010 at 11:18 PM, Glenn Adams <glenn@skynav.com
>>> <mailto:glenn@skynav.com>> wrote:
>>>
>>> You're welcome. I am preparing an update that will add
>>> columns for MHEG-5,
>>> EBIF, and DVB-HTML as well. I hope to send this update out
>>> by early to mid
>>> next week.
>>>
>>> Regards,
>>> Glenn
>>>
>>>
>>> On Fri, Oct 29, 2010 at 11:54 AM, Doug Schepers
>>> <schepers@w3.org <mailto:schepers@w3.org>> wrote:
>>>
>>> Hi, Glenn, Mark, and Bob-
>>>
>>> Thank you very much, this is great information to have
>>> compiled and
>>> available; you really went above and beyond, here. I
>>> will try to integrate
>>> this feedback in an upcoming draft of DOM3 Events, and I
>>> will run it by this
>>> list for another round of feedback.
>>>
>>> Thanks!
>>> -Doug
>>>
>>> Glenn Adams wrote (on 10/21/10 10:56 PM):
>>>
>>> with attachment
>>>
>>> On Fri, Oct 22, 2010 at 10:55 AM, Glenn Adams
>>> <glenn@skynav.com <mailto:glenn@skynav.com>
>>> <mailto:glenn@skynav.com <mailto:glenn@skynav.com>>>
>>> wrote:
>>>
>>> Hi Doug,
>>>
>>> In regard to your request for input on key events
>>> (both remote
>>> control and keyboard) for television, and in
>>> consultation with Mark
>>> Vickers (Comcast) and Bob Lund (Cable
>>> Laboratories), we have
>>> prepared a table of "Virtual Key Identifiers for
>>> Television Input"
>>> based on three industry standards:
>>>
>>> * OCAP, Open Cable Application Platform
>>> (a.k.a. /tru2way/)
>>> * CEA-2014, Web-based Protocol and Framework
>>> for Remote User
>>> Interface on UPnPTM Networks and the
>>> Internet (Web4CE)
>>> * ATSC A/100-2, DTV Application Software
>>> Environment Level 1
>>> (DASE-1) Part 2: Declarative Applications
>>> and Environment
>>>
>>> The attached table includes the full set of
>>> virtual key identifiers
>>> defined for use with these standards. In
>>> addition, certain of these
>>> identifiers are designated as being included in
>>> the minimum support
>>> provided by a device that implements one of these
>>> cited standards.
>>>
>>> If there are any follow-up questions, please let
>>> me know.
>>>
>>> Regards,
>>> Glenn Adams
>>>
>>> -----Original Message-----
>>> From: public-web-and-tv-request@w3.org
>>> <mailto:public-web-and-tv-request@w3.org>
>>> <mailto:public-web-and-tv-request@w3.org
>>> <mailto:public-web-and-tv-request@w3.org>> [mailto:
>>> public-web-and-tv-request@w3.org
>>> <mailto:public-web-and-tv-request@w3.org>
>>> <mailto:public-web-and-tv-request@w3.org
>>> <mailto:public-web-and-tv-request@w3.org>>] On
>>> Behalf Of Doug
>>> Schepers
>>> Sent: Friday, October 08, 2010 11:00 AM
>>> To: public-web-and-tv@w3.org
>>> <mailto:public-web-and-tv@w3.org>
>>> <mailto:public-web-and-tv@w3.org
>>> <mailto:public-web-and-tv@w3.org>>
>>> Subject: Standardize Buttons For TV-Web Remotes?
>>>
>>> Hi, Folks-
>>>
>>> I'm the editor of DOM3 Events, which (among
>>> other things) is
>>> finally
>>> standardizing keyboard events. The spec
>>> contains a list of
>>> common keys
>>> [2], but focuses mainly on traditional
>>> desktop keyboards, and to a
>>> lesser extent, on mobiles. There are a few
>>> keys for media
>>> controls, but
>>> mainly in the context of "fancy" computer
>>> keyboards.
>>>
>>> It occurred to me that a more forward-looking
>>> spec would also
>>> include
>>> common buttons from media remote controls,
>>> such as would be
>>> useful for
>>> browser-TV-remote hybrid keyboards, like the
>>> ones from Logitech,
>>> Sony,
>>> etc., for GoogleTV, AppleTV, and other
>>> systems (I know there are
>>> many
>>> other projects, these are just the ones that
>>> popped into my head
>>> from
>>> reading tech blogs; no disrespect intended to
>>> other vendors).
>>>
>>> Including remote-control-type buttons would
>>> be good for content
>>> authors
>>> who want to program Web content inclusive of
>>> those devices.
>>> I've got a
>>> few keys/buttons in mind (ChannelUp,
>>> ChannelDown, FastForward,
>>> Reverse,
>>> Red, Green, Blue, Yellow, and so forth), but
>>> it would be good to
>>> have a
>>> more comprehensive list of possibilities,
>>> along with their
>>> relative
>>> importance and commonness.
>>>
>>> If anyone has any concrete suggestions about
>>> this, or could you
>>> put me
>>> in touch with people or companies who do, I
>>> would greatly
>>> appreciate any
>>> help.
>>>
>>>
>>> (To put DOM3 Events in context for those who
>>> don't know the
>>> technical
>>> background, the DOM is the primary way that
>>> script interacts
>>> with Web
>>> documents, by reading, writing, and changing
>>> elements,
>>> attributes, and
>>> text through the in-memory model of the
>>> document structure and the
>>> associated APIs; DOM events are the way that
>>> user interaction is
>>> managed
>>> within that, e.g. 'click' events, 'keydown'
>>> events, etc.)
>>>
>>> [1] http://www.w3.org/TR/DOM-Level-3-Events/
>>> [2]
>>> http://www.w3.org/TR/DOM-Level-3-Events/#key-values
>>>
>>> Thanks-
>>> -Doug Schepers
>>> W3C Team Contact, SVG and WebApps WGs
>>>
>>> --
>>> Giuseppe Pascale
>>> TV & Connected Devices
>>> Opera Software - Sweden
>>>
>>>
>>>
>>
>>
>
>