Re: Multimedia Metadata

There are 4 kinds now, but that's all the kinds that are defined.  What
kind did you have in mind?

http://wiki.webmproject.org/webm-metadata/temporal-metadata/webvtt-in-webm


On Mon, Mar 3, 2014 at 10:39 AM, Brendan Long <B.Long@cablelabs.com> wrote:

>  You can determine the type of video track with the "kind" attribute:
>
>
> http://www.w3.org/html/wg/drafts/html/CR/embedded-content-0.html#dom-videotrack-kind
>
> It sounds like you might want to propose some additional ones?
>
> For Matroska/WebM getting the kind is kind of complicated right now. For
> WebVTT, you can get it from the codec ("D_WEBVTT/*kind*"), but I don't
> think there's any way to have a kind for other types of content right now.
> If you can convince the WebM maintainers to add one it would be nice though.
>
>
> On Wed, 2014-02-19 at 23:16 +0000, Adam Sobieski wrote:
>
> Media Resource In-band Tracks Community Group,
>
>
>
>  Greetings.  Which group(s) is exploring metadata standards and API for
> multimedia metadata such as XMP, MPEG7 and Matroska metadata?
>
>
>
>  A scenario is that of presentations and classroom lectures where videos
> might have three video tracks: (1) video of presenter, (2) video of a
> presentation surface, (3) video with cinematography between presenter and
> presentation surface.  HTML5 supports synchronizing multiple media
> elements, such as video tracks (1) and (2) (*http://www.w3.org/TR/html5/embedded-content-0.html#synchronising-multiple-media-elements
> <http://www.w3.org/TR/html5/embedded-content-0.html#synchronising-multiple-media-elements>*).
> A fourth track, however, could be (4) side-by-side of tracks (1) and (2).
> Some of the combinations of presenters and presentation surfaces, as
> aforementioned, are referred to as *enhanced video*.
>
>
>
>  Presentation scenarios are numerous, including digital education,
> and multimedia metadata can facilitate new web-based scenarios and
> features.  Describing multimedia tracks with metadata enhances the
> portability of the multimedia files, e.g. features from XMP, MPEG
> and Matroska.  Web browsers and multimedia software could provide enhanced
> viewing experiences and features based upon multimedia metadata.
>
>
>
>  Extensible semantic metadata ontology, vocabularies, and JavaScript
> API could facilitate the portability of multi-track, featureful, multimedia
> objects.
>
>
>
>
>
>
>
>  Kind regards,
>
>
>
>  Adam Sobieski
>
>
>
>
>
>
>
>
>
>
>