Re: [tech] Standardize Buttons For TV-Web Remotes?

Hi Giuseppe and all,

Giuseppe, as I privately sent to you 12 hours ago, I really would
suggest we ask all the TV experts subscribing this list whether we
want to include this in the scope of the IG or not *before* starting
actual technical discussion on this list itself.

I think so, because:

1. The scope of the expected TV IG (and the possible WG) is being
    discussed on this list so that we can finalize the draft charter.

2. There are various existing DTV standards which handle TV remote
    events (not only OIPF/HbbTV but also DVB, ATSC, ARIB (BML), ABNT,

And I think we should add this to the draft charter [a] if and only if
there is consensus on this list.  I mean unless consensus we should
not add it to the charter or discuss it on this list.  We should be
able to hold discussion on concrete technical topics including the
relationship between necessary TV control APIs/events and existing

Opinion from other (candidate) co-Chairs?


I personally don't believe we have to add anything to the draft
charter about this, because both the Web Applications WG and other
standardization bodies are already included in the list at
"3. Dependencies and Liaisons" in the draft charter and we surely will
work with the groups and talk about possible collaboration once the TV
IG is launched.



On 10/15/2010 07:16 PM, Giuseppe Pascale wrote:
> Hi Doug,
> thanks for proposing this topic.
> I think this is exactly the kind of topics we want to discuss in this IG
> and I hope all people on this ML can contribute with their view (mine is
> few lines below)
> I marked the thread with [tech] in order not to confuse it with other
> discussions like the one about the charter draft.
> I would also invite people to open other technical discussion and mark
> them with [tech], since regardless from the charter approval every
> discussion is welcome in order to improve the synergy among different
> PoVs and industry areas active in this IG.
> Going back to the original topic, here my answer:
> I think the issue you raised is a valid one and there was some work done
> in the groups I've been working with, in particular OIPF[1] and HbbTV[2]
> (partially inherited from another spec)
> The relevant documents you should check are:
> HbbTV:
> In particular you can check
> 7.2.5 The Keyset class
> 9.1 Minimum DAE capability requirements (text at the end of the section)
> Annex B sect. B.3 "Changes to Section 5.4" contains some text about key
> events (not strictly relevant to your question but may be of interest)
> in Hbbtv
> sect. 5.2 "User input"
> sect. 10.2.2 "User input"
> annex A.2.6 XHTML Profile may also be of interest for you
> I understand that diving into these specs may not be easy so I can
> provide some help/clarification if needed.
> Let us know what do you think and if there is some overlap between what
> have been done in these groups and what your WG is planning to do.
> cheers
> /g
> [1]
> [2]
> On Fri, 08 Oct 2010 18:59:37 +0200, Doug Schepers <> wrote:
>> 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]
>> [2]
>> Thanks-
>> -Doug Schepers
>> W3C Team Contact, SVG and WebApps WGs

Kazuyuki Ashimura / W3C Multimodal & Voice Activity Lead
voice: +81.466.49.1170 / fax: +81.466.49.1171

Received on Friday, 15 October 2010 12:17:41 UTC