Re: Wiki update

From: Giuseppe Pascale <giuseppep@opera.com<mailto:giuseppep@opera.com>>
Date: Friday, November 22, 2013 1:17 AM
To: Bob Lund <b.lund@cablelabs.com<mailto:b.lund@cablelabs.com>>
Cc: "public-inbandtracks@w3.org<mailto:public-inbandtracks@w3.org>" <public-inbandtracks@w3.org<mailto:public-inbandtracks@w3.org>>
Subject: Re: Wiki update

few generic comments on the wiki

* the overview section doesn't mention DASH that is mentioned throughout the wiki
http://www.w3.org/community/inbandtracks/wiki/Main_Page#Overview


* latest draft of HTML include the data track interface.

I assume you mean the DataCue http://www.w3.org/html/wg/drafts/html/master/text-level-semantics.html#datacue

This is not mentioned in the requirements section
http://www.w3.org/community/inbandtracks/wiki/Main_Page#Requirements

This would be referenced in the implementation section  as the means to create a Cue for metadata in-band tracks.




On Thu, Nov 21, 2013 at 9:41 PM, Bob Lund <B.Lund@cablelabs.com<mailto:B.Lund@cablelabs.com>> wrote:
Hi All,

About a week ago I outlined two implementation approaches on the Wiki [1] for exposing track metadata to Web applications. One uses a dedicated text track and the other proposes a new attribute for each video, audio and text track.

Today I updated [1] to highlight (I hope) the aspects of the implementation that are independent of the media resource format and those that are media resource format dependent. I then proposed how the media resource format specific parts would look for MPEG-2 TS.


the name may not be the most important thing at this point, but wouldn't that be more a "trackType" or simply "type" rather than a "trackMetadata"?

I don't have a preference for the name. What I'd like to hear back from the group are thoughts/preference about using a per track attribute for metadata or to use a dedicated metadata track. My preference would be a per track attribute. I think this results in a cleaner, simpler interface for Web apps.

Also, if people think there is a need for a track "type" regardless of the type of track, I guess that means  inBandMetadataTrackDispatchType is not needed anymore? (since each track will have a type, not only Metadata text tracks?)

Yes, adding an attribute for per track metadata for all video, audio and text tracks subsumes the role of the inBand…Type. You'll note, though, that in the Wiki I also propose that the MIME type of the media resource containing tracks be encoded in all track IDs. I think this is needed so that script knows how to parse the track metadata in the attribute.



/g

What is everyone's thoughts on the two approaches?

Thanks,
Bob

[1] http://www.w3.org/community/inbandtracks/wiki/Main_Page#Implementation_Approaches