Media Annotations Working Group – overview

Joakim Söderberg / Felix SasakiContribution to

"Accessibility of Media Elements in HTML 5 Workshop"

November 1st 2009

Purpose

Facilitate metadata integration for media objects in the Web, such as video, audio and images

Main means Ontology for Media Resources 1.0 API for Media Resources 1.0

MAWG Vision

User sees an API, simple

handling only texts and URI

An Ontology relates the

different metadata formats

(this is hidden to the user)

Mapping is provided by MAWG

Some formats in sight

Formats:

XMP

DublinCore

ID3 (metadata in audio)

EXIF (metadata in images)

Media RSS

IPTC (news)

MPEG7

TV-Anytime

FRBR (multilevel description)

Youtube Data API Protocol

Other: SMPTE, LOM, METS, Cablelabs ADI 2.0, MIX, VRA etc.

Definition of metadata properties for multimedia objects:

Ontology for Media Resource 1.0

Example properties ma:contributor ma:language ma:compression ...

From http://www.w3.org/TR/mediaont-10/

Relating properties to existing formats

ma:contributor

media:credit@role

in YouTube Data API Protocol

dc:creator

in XMP

exactrelated to

Relating properties to existing formats

ma:contributor

related to

media:credit@role

in YouTube Data API Protocol

dc:creator

in XMP

exact

semantic mappings: exact, related to, more specific, more general (motivated by SKOS)

Relating properties to existing formats

ma:contributor

related to

media:credit@role

in YouTube Data API Protocol

dc:creator

in XMP

exact

semantic mappings: exact, related to, more specific, more general

syntactic mappings, e.g.

"Unicode string" in XMP

API for Media Resource 1.0

Implementing the mappings from the ontology Proving access methods Example for ma:contributor property

interface Contributors: Unstructured {

attribute DOMString id;

attribute DOMString role;

};

From http://www.w3.org/TR/mediaont-api-1.0/#contributors

Challenges

General Reading "easy part" ... but how to (or if to) write

"ma:" properties into media files Getting verification of mappings (needs to be based

on actual usage, not on the specifications)

Specific to Accessibility (How) does the media annotations approach

(ontology and API) fit to Accessibility needs? Are there Accessibility-related properties to be

related into "ma:"?

Resources

Working Group Homepage http://www.w3.org/2008/WebVideo/Annotations/

Use Cases and Requirements for Ontology and API for Media Object 1.0 http://www.w3.org/TR/media-annot-reqs

Ontology for Media Resources 1.0 http://www.w3.org/TR/mediaont-10/

API for Media Resources 1.0 http://www.w3.org/TR/mediaont-api-1.0/

Thank you for your attention!