% Title = "Matroska Tags" % abbrev = "Matroska" % category = "std" % docName = "draft-lhomme-cellar-tags-00" % ipr= "trust200902" % area = "art" % workgroup = "cellar" % keyword = [""] % % [[author]] % initials="S." % surname="Lhomme" % fullname="Steve Lhomme" % [author.address] % email="[email protected]" % % [[author]] % initials="M." % surname="Bunkus" % fullname="Moritz Bunkus" % [author.address] % email="[email protected]" % % [[author]] % initials="D." % surname="Rice" % fullname="Dave Rice" % [author.address] % email="[email protected]"
.# Abstract
This document defines the Matroska tags, namely the tag names and their respective semantic meaning.
{mainmatter}
Matroska aims to become THE standard of multimedia container formats. It can store timestamped multimedia data but also chapters and tags. The Tag Elements add important metadata to identify and classify the information found in a Matroska Segment. It can tag a whole Segment, separate Track Elements, individual Chapter Elements or Attachment Elements.
While the Matroska tagging framework allows anyone to create their own custom tags, it's important to have a common set of values for interoperability. This document intends to define a set of common tag names used in Matroska.
This document is a work-in-progress specification defining the Matroska file format as part of the IETF Cellar working group. It uses basic elements and concepts already defined in the Matroska specifications defined by this workgroup.
Tag values can be either strings or binary blobs. This document inherits security considerations from the EBML and Matroska documents.
To be determined.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.