METS is used by Variations-Web to drive the web player by creating the container structure and associating it with the audio streams as well as including some metadata and access control information (METSRights).
VideoMD (METS Extension)
VideoMD is a technical metadata extension for METS that describes a digital video object.
PREMIS (METS Extension)
Preservation technical metadata extension for METS
ProvenanceMD (METS Extension)
Digital provenance and source metadata extensions for METS to capture metadata about "physical preparation of source materials" and "how a specific file was made".
METSRights (METS Extension)
Rights metadata extension for METS that is currently used by Variations-Web. METSRights can include copyright status, copyright owner, and access control information (in the form of permissions to be perform specified actions by individuals or groups).
A broad set of standards for descriptive and structural metadata for audio, video, images, and more. This is used by Matterhorn for their video segmentation metadata. MPEG-7 supports hierarchical, continuous or non-continuous segments in its structural metadata. It also supports spacial-temporal segments to capture key parts of frames over time geared towards searching.
Is this set of standards protected by patents that require us to negotiate licenses? Does MPEG-7 have much traction in the digital library world? How much of this large set of standards would we use? How much MPEG-7 work has already been done that we could leverage?
Used by Variations-Web to display basic bibliographic information.
PBCore is based on Dublin Core and adds additional elements specific to the use case of audiovisual content. PBCore also allows for inclusion of technical metadata for each flavor without having to duplicate descriptive or rights metadata.
See wiki page on the subject: Subtitles
Not exactly a format, but more an api/protocol for obtaining different representations of resources. This might be useful to use on the web services backend or for metadata we share.
Like unAPI, this is not a format, but an api/protocol for embedding/allowing easy embedding of a resource using only the URL of its owning page. This might be useful for allowing embedding of our content or for pulling in embeddable content. I could see this as a Fedora disseminator if it doesn't already exist.