- From: Doug Schepers <schepers@w3.org>
- Date: Fri, 15 Oct 2010 17:06:11 -0400
- To: 이현재 <hj08.lee@lge.com>
- CC: 'Kazuyuki Ashimura' <ashimura@w3.org>, 'Giuseppe Pascale' <giuseppep@opera.com>, public-web-and-tv@w3.org
Hi, HJ- Please let me clarify: DOM3 Events would not define or even suggest any arrangement of keys on the remote; DOM3 Events would not require any set of keys to be present or supported on a remote. What DOM3 Events would define is a set of possible common key values associated with the remote control of media devices; if these keys are present on the remote, and the remote is being used to control a user agent (browser) that supports DOM3 Events, then the value that the browser script would expose to the content developer when the user presses one of these defined keys should be the value from the list of predefined keys. That makes it easier for content authors to create Web content that works across devices. Please note that this does not limit or constrain other software on the same system (including the device OS) from using a different value for that same key. For example, HbbTV defines the key values 'play', 'pause', and 'stop' (mapped to the virtual keys VK_PLAY and VK_PAUSE or VK_PLAY_PAUSE, and VK_STOP, as appropriate to the remote device drivers), while DOM3 Events would define the key values 'MediaPlayPause', 'MediaPlay', 'MediaPause', and 'MediaStop'; on a device supporting both HbbTV and a Web browser, for OS-level methods the virtual-key values would be used, for HbbTV applications the HbbTV values would be used, and for Web content the browser would expose these with the DOM3 Events names; same key, same event, different strings. So, for TV vendors, you would not have to change anything about the keys you choose to support on your remote, but for those keys which have equivalent values in the DOM3 Events spec, that is the name that should be supported by browsers on your device when using Web content. I hope that clarifies the matter and eases your concerns. Please let me know if you have other thoughts on the matter. I would especially appreciate pointers to lists of keys you think should be supported. Regards- -Doug Schepers W3C Team Contact, SVG and WebApps WGs 이현재 wrote (on 10/15/10 11:23 AM): > Dear all, > > I'm obliged to say something from TV makers voice. Remote key > arrangement is kind of TV unique features/identities from other > devices and even among TV makers. As new technology introduced to TV > world, the most necessary key is added to a certain position with a > big discretion. As a TV expert, I can say very confidently that > adding single button is very huge decision for product concept. > Unlike IT devices having various derivatives, TV is inclined to keep > its own identity relatively longer time. > > We could recommend some essential keys of web tech, however web tech > is changing very quickly. The inertia attribute of TV remote must be > respected. > > I suggested this mailing list to priortize adaptive streaming for > VOD, javascript API for TV interaction, HTML profiling for TV some > time ago. But I discontinued for quick IG startup. With this regards, > I agree with Kaz that just leave current IG charter as it is. > > Best regards, HJ > > -----Original Message----- From: Sent: 없음 To: Kazuyuki Ashimura Cc: > Giuseppe Pascale; public-web-and-tv@w3.org Subject: Re: [tech] > Standardize Buttons For TV-Web Remotes? > > On Fri, Oct 15, 2010 at 1:16 PM, Kazuyuki Ashimura<ashimura@w3.org> > wrote: > >> 2. There are various existing DTV standards which handle TV remote >> events (not only OIPF/HbbTV but also DVB, ATSC, ARIB (BML), ABNT, >> etc.). > > This may be of interest, as it's somewhat broader in scope than TV > remote events in particular. > > I've been speaking recently with the chair of the DVB SI working > group, which has the ultimate responsibility for (amongst other > things) the dvb: URI scheme. I got in touch in relation to > draft-mcroberts-dvb-uri, which is a small step in an attempt to > bring the Internet and Broadcast communities a little closer together > in this area. > > It's been expressed to me that there is a positive attitude towards > collaborating with the W3C and the IETF (as appropriate) and they > would help to fulfil a "bridging role" between the communities. I > can pass on contact details if appropriate? (AIUI also, DVB has some > responsibilities conferred upon it by other broadcast systems to > avoid duplicating efforts in some areas). > > All the best, > > Mo. >
Received on Friday, 15 October 2010 21:06:17 UTC