W3C home > Mailing lists > Public > public-tvapi@w3.org > March 2015

RE: tvapi-ACTION-27: Work on triggered interactive overlay requirements

From: HU, BIN <bh526r@att.com>
Date: Mon, 16 Mar 2015 14:01:40 +0000
To: Sean Lin <selin@mozilla.com>
CC: TV Control API Community Group <public-tvapi@w3.org>
Message-ID: <179FD336116F754C876A9347238FE29A02850573@CAFRFD1MSGUSRIA.ITServices.sbc.com>
Great, Sean, and thanks for working hard on this.

Bin

From: Sean Lin [mailto:selin@mozilla.com]
Sent: Monday, March 16, 2015 2:04 AM
To: HU, BIN
Cc: TV Control API Community Group
Subject: Re: tvapi-ACTION-27: Work on triggered interactive overlay requirements

Hi Bin,

Thanks for your help. Then DataCue (TextTrackCue) appears a promising direction. And I'm planning to follow the pattern of VTTCue [1] to have a similar one for TV triggers to realize the requirements.

Best regards,
Sean

[1] http://dev.w3.org/html5/webvtt/#the-vttcue-interface


On Mon, Mar 16, 2015 at 6:41 AM, HU, BIN <bh526r@att.com<mailto:bh526r@att.com>> wrote:
Sean,

Thank you for looking into this and working on it.

Yes, as a requirement [1], the start time and end time or duration are needed to be supported in the trigger so that START_OVERLAY and DISMISS_OVERLAY events can be dispatched. More particularly, [trigger.types] includes [trigger.types.time] [1]. And other types of triggers are required too.

Let me summarize the basic scenario of Triggered Interactive Overlay in order to look into what is the appropriate solution to support it. Some more detailed can be found in attached email thread we discussed last year.


1.       In-band triggering scenario:

a.       “Trigger” needs to be encoded into video assets’ metadata so that a DataCue element can be created within UA, which contains all of those information for dispatching a trigger event.

b.      To-Do in our spec:

                                                               i.      Content-type of data in DataCue that is specific to trigger

                                                             ii.      Data structure of the data in DataCue that is specific to trigger

1.       Mandatory elements for a trigger

2.       Optional elements for a trigger

2.       Out-band triggering scenario

a.       “Trigger” (and related information) is pre-provisioned in platform.

                                                               i.      The condition of triggering an event may be subject to content

b.      Based on pre-provisioned event, and current content, events are triggered.

c.       The same To-Do: content-type and data elements.

Please also see attached email thread that we discussed on June 8 2014 about this scenario.

Let me know if there are more questions, and I am very happy to discuss it.

Thank you
Bin

[1] https://www.w3.org/community/tvapi/wiki/Main_Page/Technical_Requirement#Triggered_Interactive_Overlay_Requirements


From: Sean Lin [mailto:selin@mozilla.com<mailto:selin@mozilla.com>]
Sent: Friday, March 13, 2015 1:53 AM
To: TV Control API Community Group
Subject: Re: tvapi-ACTION-27: Work on triggered interactive overlay requirements

Hi all,

I'm currently working on this item but have a question. Can we assume the trigger contains start time and end time, no matter it's from in-band or out-band signaling? If so, it appears DataCue element [1] in HTML 5.1 could be utilized to realize these requirements (or at least for some in-band scenarios).

Thoughts?!

Thanks and best regards,
Sean

[1] http://www.w3.org/html/wg/drafts/html/master/semantics.html#datacue



On Tue, Feb 17, 2015 at 10:57 PM, TV Control API Community Group Issue Tracker <sysbot+tracker@w3.org<mailto:sysbot+tracker@w3.org>> wrote:
tvapi-ACTION-27: Work on triggered interactive overlay requirements

http://www.w3.org/community/tvapi/track/actions/27


Assigned to: Bin Hu









--
Sean Lin
Mozilla Taiwan
selin@mozilla.com<mailto:selin@mozilla.com>




--
Sean Lin
Mozilla Taiwan
selin@mozilla.com<mailto:selin@mozilla.com>

Received on Monday, 16 March 2015 14:02:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:45:13 UTC