RE: Media timed events use cases and gap analysis

Chris, all,

Note that the HbbTV spec does mandate the use of DataCue in some cases - see section 9.3.2 of the HbbTV 2.0 (or later) spec.

They do include some restrictions in order to address the issues that are discussed in your document, but I don't think it resolves all of the identified issues.

Steve.

> -----Original Message-----
> From: Chris Needham [mailto:chris.needham@bbc.co.uk]
> Sent: 16 February 2018 12:20
> To: public-web-and-tv@w3.org
> Subject: Media timed events use cases and gap analysis
> 
> Dear all,
> 
> Following the discussion on media timed events during the last M&E IG call
> [1], I have started a document to gather use cases and requirements [2].
> 
> This is just an initial draft so far, intended to provide input to the work on any
> spec changes needed.
> 
> The document needs your input, so that it reflects the IG's requirements.
> One particular area that needs attention is improved use case descriptions,
> particularly from the point of view of end users or content authors, as some
> of what's currently written is technology rather than use-case driven.
> 
> Please submit feedback via the GitHub issue tracker (pull requests are very
> welcome), or via this mailing list if you prefer.
> 
> Kind regards,
> 
> Chris (Co-chair, Media & Entertainment Interest Group)
> 
> [1] https://www.w3.org/2018/02/01-me-minutes.html
> [2] https://github.com/w3c/media-and-entertainment/blob/master/media-
> timed-events/use-cases-and-gap-analysis.md
> 
> 
> -----------------------------
> http://www.bbc.co.uk
> This e-mail (and any attachments) is confidential and may contain personal
> views which are not the views of the BBC unless specifically stated.
> If you have received it in
> error, please delete it from your system.
> Do not use, copy or disclose the
> information in any way nor act in reliance on it and notify the sender
> immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.
> -----------------------------
>

Received on Monday, 19 February 2018 11:28:37 UTC