W3C home > Mailing lists > Public > public-web-and-tv@w3.org > July 2015

[GGIE] Minutes for July 1st meeting

From: Daniel Davis <ddavis@w3.org>
Date: Mon, 06 Jul 2015 17:44:45 +0900
Message-ID: <559A3FFD.6020109@w3.org>
To: "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
Hello all,

Here are the minutes from the GGIE call on July 1st:
http://www.w3.org/2015/07/01-webtv-minutes.html

and pasted in full below. Thanks to Bill for scribing again.

Please note the next call will be on Wednesday July 15th from 11:00 am
Eastern Time (US). See here for the Webex call details:
https://www.w3.org/2011/webtv/wiki/Main_Page#Teleconferences_.2F_Meetings

With regards,
Daniel

==========

                      Web and TV IG: GGIE meeting

01 Jul 2015

   See also: [2]IRC log

      [2] http://www.w3.org/2015/07/01-webtv-irc

Attendees

   Present
          Glenn Deen, Bill Rose, Nilo Mitra, Dale Rochon, Andrew
          Zamler-Carhart, Paul, Higgs, Leslie Daigle, Kaz
          Ashimura, Yosuke Funahashi, Daniel Davis

   Regrets

   Chair
          Glenn

   Scribe
          Bill

Contents

     * [3]High Level GGIE Review
          + [4]Glass-to-Glass Overview
          + [5]Capture Use Case
     * [6]Next meeting
     * [7]IETF meetings in Prague
     __________________________________________________________

High Level GGIE Review

Glass-to-Glass Overview

   1. Glenn walked through a Glass to Glass Overview slide. A
   preliminary Draft with the slides shown on the call is
   available on the members only site at
   [8]https://lists.w3.org/Archives/Member/member-web-and-tv/2015J
   ul/att-0002/GGIE-High_Level_Picture_-_pre-updates_version.pptx

      [8]
https://lists.w3.org/Archives/Member/member-web-and-tv/2015Jul/att-0002/GGIE-High_Level_Picture_-_pre-updates_version.pptx

   <glennd> Main components are the Smart edge (Creation), the
   Core, Smart Edge (Glass of viewing)

   <glennd> Smart Creation edge includes capture (camera, etc.);
   Storage, Editing/composition

   <glennd> Core includes Discovery (Web, EPG, Search);
   Distribution (Web, Cloud); Cache (CDN, etc.)

   <glennd> Smart Edge (Viewing): View (PC, mobile, etc.); Edge
   Cache (in-home – device, disk)

   <glennd> Enabler: Content ID – Standardize content Identifiers
   – Standardized Content URI

   <glennd> Issues to be covered within GGIE: Content ID;
   Metadata; Scalability; User ID; Privacy

   <bill> Any comments?

   <glennd> If a neighborhood cache or an enterprise cache, etc.,
   (an edge cache that is not part of the end user’s equipment) is
   considered part of the core cache, the end-user’s cache, or
   something else?

   <glennd> Not sure where this should reside in the GGIE view.

   <leslie> This is an important point – includes enterprise
   cache, ISO edge, etc.

   <glennd> I suggest moving it into the Smart Edge/viewing as a
   separate bubble – managed edge cache?

   <digitaldale> Need to add relationships to the 3 building
   blocks

   <nilo> The core has ingestion as a function which is not shown.
   Neither is the composition of the linear stream e.g. ad
   insertion. This can take place in both the core and at the
   viewing edge cache

   <digitaldale> It depends on where composition takes place - at
   viewing edge or creation side.

   <glennd> It appears we need to capture one or more new UCs

   <digitaldale> Ads may be stitched at multiple points. Depends
   on incentives e.g. the user may not want to provide storage
   space for ads that will be inserted.

   <azamlerc_> We need to ID the content and ID the ads. Problem –
   if someone steals content, the ad may still be inserted in
   which case the wrong people may get paid since the “owner” is
   unclear.

   <glennd> AdID exists.

   <digitaldale> What about TV Anytime? Is this still ongoing?

   <Paul_Higgs> Yes. The work is still ongoing. More popular in
   Europe. Unclear in US, Asia. Jean Pierre may have information
   on this.

   <glennd> need to add Creation UCs for adding ads to content: *
   Assemble/managed at core – e.g. YouTube, Hulu; *
   Assembled/insertion done locally even if it is managed at the
   edge

   Action Item: Nilo, Dale to look into creating new UCs capturing
   the basic core elements of this discussion

Capture Use Case

   3. Discussion on Capture UC-5: 3rd party composite asset – Bill
   Rose
   [9]https://www.w3.org/2011/webtv/wiki/GGIE_TF/UseCases/Content_
   Capture#Capture_UC-5_Distributing_3rd_Party_Composite_Asset_Usi
   ng_Composite_Manifest

      [9]
https://www.w3.org/2011/webtv/wiki/GGIE_TF/UseCases/Content_Capture#Capture_UC-5_Distributing_3rd_Party_Composite_Asset_Using_Composite_Manifest

   <glennd> Capture UC-4 was the precursor to UC-5. A compositor
   creates a new asset from multiple linear assets from other
   sources.

   <bill> The change from Capture UC-4 is that the compositor does
   not actually assemble a final asset and distribute it. Instead
   he assembles and distributes a manifest that contains the links
   to various assets that comprise the final asset. The manifest
   also identifies the fragments to be used from each link and any
   needed timing information so an end device can assemble the
   final asset. It may also include new audio assets, ad insertion
   points/links, etc.

   <digitaldale> this was used in NASCAR’s In-Car. The user
   selects a feed from the race car of their choice. Ads were
   inserted which can be common to all viewers or user-dependent.

   <glennd> We may want to differentiate between live content and
   recorded content. The needs may be different. For truly live
   content there may not be an ID assigned yet. The ID may not be
   assigned until the recording window is closed. Also can’t
   pre-cache live content. Might be related to ingest of live
   versus pre-recorded content.

   Action Item – Bill Rose to add note to UC-5 that live content
   may not have an ID or be able to be cached.

   <leslie> There is a difference between live ephemeral versus
   live persistent/stored content.

   Action Item: Bill Rose to add this to note in Creation UC-5.

   Discussion on whether UC-5 is a creation or distribution UC.

   <Paul_Higgs> The asset created in UC-5 is a Play List asset. It
   is a creation UC.

   <leslie> It's both.

   Action Item – Bill Rose to add a note to UC-5 that when we
   discuss the UCs we ensure there is a discussion on Content UC-5
   within the Distribution UC discussions.

Next meeting

   Next call: July 15th at 11:00 AM ET.

IETF meetings in Prague

   <glennd> If anyone will be at the IETF meetings in Prague the
   week of July 19 please contact me.

Summary of Action Items

     * Nilo, Dale to look into creating new UCs capturing the
       basic core elements of the discussion on ad insertion (see
       above)
     * Bill Rose to add note to UC-5 that live content may not
       have an ID or be able to be cached.
     * Bill Rose to add note to Creation UC-5 on the difference
       between live ephemeral versus live persistent content in
       Creation UC-5.
     * Bill Rose to add a note to UC-5 that when we discuss the
       UCs we ensure there is a discussion on Content UC-5 within
       the Distribution UC discussions.

   [End of minutes]
     __________________________________________________________
Received on Monday, 6 July 2015 08:45:19 UTC

This archive was generated by hypermail 2.3.1 : Monday, 6 July 2015 08:45:20 UTC