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

[GGIE] Future web standards question

From: Deen, Glenn (NBCUniversal) <glenn.deen@nbcuni.com>
Date: Wed, 9 Mar 2016 18:30:23 +0000
To: "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
Message-ID: <D305ABBF.94D09%glenn.deen@nbcuni.com>
Iím looking for input from the GGIE participants, and anyone else who wants to chime In,  from a GGIE perspective on Mark Watsonís request for comment on future web standards for the entertainment industry.

The two initial things that came to my mind, based on what weíve worked on in GGIE are:

1.   New user identity standards beyond the simplistic   USER@EXAMPLE.COM email based, or  NAME that only works in the context of a service  (e.g. a Facebook account name).        These new identity standards would support privacy protection features such as pseudonyms and the ability to abandon an identity which has had Itís anonymity veil broken, but without loosing all the assets tied to the that identity.     GGIE has been working on both use cases ) for this, and a requirements document. ((https://www.w3.org/2011/webtv/wiki/GGIE_TF/UseCases/Identit<https://www.w3.org/2011/webtv/wiki/GGIE_TF/UseCases/Identity>   , https://github.com/w3c/tv-ggie/blob/master/GGIE.Identity.UC.Requirements.md)

2.  A standard API that would permit web applications to identify content.    This API would permit the application to query and obtain a URI that includes at least an identifier that uniquely identifies the content.   This could be an AD-ID or EIDR for professional content, or some other id for content from other sources.      The API would present a standard way to ask the question, and behind the scenes could employ extraction from any of  metadata, fingerprinting, or watermarking as the means to identify the content and find the associated identifier.        GGIE has a series of use cases that depend on an applications ability to know what the content is. (https://www.w3.org/2011/webtv/wiki/GGIE_TF/UseCases/Content_Identification and https://www.w3.org/2011/webtv/wiki/GGIE_TF/UseCases/Streaming)


I know there are a number of non-Web Standards that have been discussed in the GGIE scope, including content addressing in caches, but Mark specificially asked for Web Standards, so we should focus in that context I thing.

Are there other Web Standards that we should include in responding to Mark?

regards
Glenn Deen (Chair GGIE taskforce)
Received on Wednesday, 9 March 2016 18:30:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 9 March 2016 18:30:59 UTC