Re: Standardize Buttons For TV-Web Remotes?

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> 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> 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>> 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>] 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>
>>>        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
>>>
>>>
>>>
>