- From: Bob Lund <B.Lund@CableLabs.com>
- Date: Thu, 9 Jan 2014 20:05:59 +0000
- To: Brendan Long <B.Long@cablelabs.com>, "public-inbandtracks@w3.org" <public-inbandtracks@w3.org>
Received on Thursday, 9 January 2014 20:06:22 UTC
From: Brendan Long <B.Long@cablelabs.com<mailto:B.Long@cablelabs.com>> Date: Thursday, January 9, 2014 at 12:53 PM To: "public-inbandtracks@w3.org<mailto:public-inbandtracks@w3.org>" <public-inbandtracks@w3.org<mailto:public-inbandtracks@w3.org>> Subject: Re: Wiki update Resent-From: <public-inbandtracks@w3.org<mailto:public-inbandtracks@w3.org>> Resent-Date: Thursday, January 9, 2014 at 12:53 PM On Thu, 2014-01-09 at 16:45 +0000, Bob Lund wrote: 1. 2. A third implementation alternative is proposed – just use the existing inbandTrackMetadataDispatchType for exposing track metadata. This would really simplify the need for a companion spec to HTML5. This, of course, limits the availability of track metadata to TextTracks kind==‘metatdata’. However, its not clear why a Web app would need track metadata for tracks rendered by the UA. This seems like a good approach, but I'd rather add a "metadata" attribute to all tracks, instead of reusing the inbandTrackMetadataDispatchType. That way we can make metadata available on all tracks, and putting metadata in an attribute named "...DispatchType" would be confusing. This is the second alternative - ‘trackMetatdata’ , in the wiki.
Received on Thursday, 9 January 2014 20:06:22 UTC