W3C home > Mailing lists > Public > public-web-and-tv@w3.org > March 2016

RE: Entertainment industry requirements for Web Standards

From: HU, BIN <bh526r@att.com>
Date: Thu, 10 Mar 2016 04:52:36 +0000
To: "Alexandra.Mikityuk@telekom.de" <Alexandra.Mikityuk@telekom.de>, "watsonm@netflix.com" <watsonm@netflix.com>, "louay.bassbouss@fokus.fraunhofer.de" <louay.bassbouss@fokus.fraunhofer.de>, "ingar.arntzen@gmail.com" <ingar.arntzen@gmail.com>
CC: "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>, "public-webtiming@w3.org" <public-webtiming@w3.org>
Message-ID: <179FD336116F754C876A9347238FE29A251FA9F5@CAFRFD1MSGUSRIA.ITServices.sbc.com>
Hi Mark and all,

Here are some information regarding TV Control API:

TV Control API:

-          A CG was initiated based on gap analysis from the Media APIs TF of the Web and TV  IG.

-          TV Control API CG homepage for mission and goal: https://www.w3.org/community/tvapi/


-          The Phase 1 Use Case Page: https://www.w3.org/community/tvapi/wiki/Main_Page/Technical_Use_Cases


-          The Phase 1 Technical Requirement Page: https://www.w3.org/community/tvapi/wiki/Main_Page/Technical_Requirement


-          TV Control API Technical Report to manage native TV modules   based on existing related API definitions: Webinos, Mozilla, HbbTV,  OIPF, etc.

-          TV Control API v.1.0 (CG Report): https://www.w3.org/2015/tvapi/


-          Now we are launching a WG and the draft WG Charter is under the AC review. https://lists.w3.org/Archives/Member/w3c-ac-members/2016JanMar/0024.html


-          On the other hand, the CG continues its incubator work for v2.0   spec and has started the Phase 2 work based on the new use cases  including non-TV channels, serurity and privacy, in-car radio and  interactive application signaling.

-          The  Phase 2 work: https://www.w3.org/community/tvapi/wiki/Main_Page/Phase2_Technical_Use_Cases


-          New WG may have a f2f at TPAC 2016.

Thanks
Bin

From: Alexandra.Mikityuk@telekom.de [mailto:Alexandra.Mikityuk@telekom.de]
Sent: Wednesday, March 09, 2016 6:37 AM
To: watsonm@netflix.com; louay.bassbouss@fokus.fraunhofer.de; ingar.arntzen@gmail.com
Cc: public-web-and-tv@w3.org; public-webtiming@w3.org
Subject: RE: Entertainment industry requirements for Web Standards

Hi all,

Thank you Louay for  referencing the Cloud Browser TF [1].

@Mark: As millions of devices like legacy STBs and minimum horse power HDML dongles struggle with execution of rich UIs, we kicked off the Cloud Browser TF. This TF puts together different Use Cases [2] to enable the communication between the Cloud Browser and the client over a standard browser API.

[1]: https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF

[2]: https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases


Mit freundlichen Grüßen / Viele Grüße / Best Regards
Alexandra Mikityuk


DEUTSCHE TELEKOM AG
T-Labs (Research & Innovation)
Alexandra Mikityuk
Winterfeldtstr. 21, 10781 Berlin
+4930835358151 (Tel.)
+4930835358408 (Fax)
E-Mail: alexandra.mikityuk@telekom.de<mailto:alexandra.mikityuk@telekom.de>
www.telekom.com<http://www.telekom.com/>
Erleben, was verbindet.

Die gesetzlichen Pflichtangaben finden Sie unter: www.telekom.com/pflichtangaben<http://www.telekom.com/pflichtangaben>

Grosse Veränderungen fangen klein an – Ressourcen schonen und nicht jede E-Mail drucken.


From: Bassbouss, Louay [mailto:louay.bassbouss@fokus.fraunhofer.de]
Sent: Mittwoch, 9. März 2016 11:00
To: Ingar Mæhlum Arntzen
Cc: Mark Watson; public-web-and-tv IG; public-webtiming@w3.org<mailto:public-webtiming@w3.org>
Subject: Re: Entertainment industry requirements for Web Standards

Hi Mark, Ingar,

Thx Ingar for your use cases. The Presentation API [1] can be also relevant for most of these use cases: Netflix Web App running in Browser on mobile discovers TV, launches Netflix App on TV and then uses Multi-device Timing API for synchronisation.
Another work which could be relevant for you is the Cloud Browser Task Force [2] (Web&TV TF) launched after last TPAC.

[1]: https://www.w3.org/TR/presentation-api/

[2]: https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF


Best regards,
Louay
On 09 Mar 2016, at 09:08, Ingar Mæhlum Arntzen <ingar.arntzen@gmail.com<mailto:ingar.arntzen@gmail.com>> wrote:

Hi Mark

Thanks for your interest in WebTVIG activities :)

I’d like to suggest that the entertainment industry should consider requirements relating to multi-device timing.

I’ll give you a few use-case examples.

1) Watching a Netflix episode on the big screen, with the audio provided by earbuds connected to the smartphone in your pocket.

Why would anyone want that? Lots of reasons really. Maybe you need to be silent to not disturb the rest of your family, yet you really want to use that big screen. Maybe you need to wander around a bit while watching. Or, it could be accessibility. Grandmother might want to have some extra volume without bothering the rest too much. Or, you could be doing the dishes in the far end of the room. Maybe you’d want to have the french version while your kids get the dubbed audio track. Or, it might be more technical - synchronizing audio tracks delivered separate from the video would allow users of many languages to use the same video resources, making for less versions of a video file (with multi-audio tracks) and higher flexibility for users (choose your local audio language even while abroad).

When presented with this scenario, people tend to think about intranet solutions like Chromecast or SONOS or similar. However, there is a much easier way of doing this, and that’s simply to do online sync. I.e., the Netflix Webpage on the big screen would be synced with the Netflix Webpage on your smartphone. You load the page and it’s synced. That’s it.
This is what the multi-device timing CG is all about. We are advocating the importance of support for distributed timing and control in the Web, and we are working on the standards/bug reports that are needed for this. As this is currently not a primary concern for browser vendors it would be extra nice to have someone from the entertainment industry actively pushing for this. And, by the way, the above scenario is not something that might become possible some time in the future. The Web is quite ready for this already, it only takes some minor adjustments to ensure universal support.

Going back to the use cases. The fun really starts when you already have multi-device timing, and you start to think about what you can do with it.

2) The Netflix Webpage always gives you the remote controls to whatever you are watching, independent of which device is doing the playback and from which device playback was started. The remote control also gives you the ability to launch a synchronized secondary Webpage that is made specifically for the program. It could be the other camera angle, the parallel story, the context-sensitive infocards, or the time sensitive like button. Of course, it could also be timed ads.

3) Your partner is travelling, yet even if he/she is someplace in a hotel and you are at home, the two of you can still watch a few episodes together. If you pause the show, his/hers will pause as well. Laughing at the same time makes it feel like you are together.

Though these may appear as different use cases, they all depend on multi-device timing.

The Multi-device Timing Community Group would welcome your interest and participation.

Multi-device Timing Community Group www.w3.org/community/webtiming/<https://www.w3.org/community/webtiming/>
Timing Object Draft Spec webtiming.github.io/timingobject/<http://webtiming.github.io/timingobject/>
Timingsrc: Implementation of multi-device timing webtiming.github.io/timingsrc/<http://webtiming.github.io/timingsrc/>

Best regards,

Ingar Arntzen, Chair Multi-device Timing CG


2016-03-08 20:14 GMT+01:00 Mark Watson <watsonm@netflix.com<mailto:watsonm@netflix.com>>:
All,

I was asked to present to the W3C Advisory Committee in a couple of weeks about what requirements we (Netflix) and the entertainment industry generally have for future web standards.

I confess to not having followed this group closely for a while and I would be happy to receive input from any of you on the areas you think require most attention in W3C.

...Mark


Received on Thursday, 10 March 2016 04:53:36 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 10 March 2016 04:53:37 UTC