draft-ietf-cellar-tags-00.txt   draft-ietf-cellar-tags-01.txt 
cellar S. Lhomme cellar S. Lhomme
Internet-Draft Internet-Draft
Intended status: Standards Track M. Bunkus Intended status: Standards Track M. Bunkus
Expires: January 18, 2019 Expires: July 13, 2019
D. Rice D. Rice
July 17, 2018 January 9, 2019
Matroska Tags Matroska Tags
draft-ietf-cellar-tags-00 draft-ietf-cellar-tags-01
Abstract Abstract
This document defines the Matroska tags, namely the tag names and This document defines the Matroska tags, namely the tag names and
their respective semantic meaning. their respective semantic meaning.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 33 skipping to change at page 1, line 33
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 18, 2019. This Internet-Draft will expire on July 13, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 4, line 20 skipping to change at page 4, line 20
stored, then more than one SimpleTag SHOULD be used. stored, then more than one SimpleTag SHOULD be used.
For authoring Tags outside of EBML, the following XML syntax is For authoring Tags outside of EBML, the following XML syntax is
proposed [3] used in mkvmerge [4]. Binary data SHOULD be stored proposed [3] used in mkvmerge [4]. Binary data SHOULD be stored
using BASE64 encoding if it is being stored at authoring time. using BASE64 encoding if it is being stored at authoring time.
6.1. Why official tags matter 6.1. Why official tags matter
There is a debate between people who think all tags SHOULD be free There is a debate between people who think all tags SHOULD be free
and those who think all tags SHOULD be strict. If you look at this and those who think all tags SHOULD be strict. If you look at this
page you will realise we are in between. page you will realize we are in between.
Advanced-users application might let you put any tag in your file. Advanced-users application might let you put any tag in your file.
But for the rest of the applications, they usually give you a basic But for the rest of the applications, they usually give you a basic
list of tags you can use. Both have their needs. But it's usually a list of tags you can use. Both have their needs. But it's usually a
bad idea to use custom/exotic tags because you will probably be the bad idea to use custom/exotic tags because you will probably be the
only person to use this information even though everyone else could only person to use this information even though everyone else could
benefit from it. So hopefully when someone wants to put information benefit from it. So hopefully when someone wants to put information
in one's file, they will find an official one that fit them and in one's file, they will find an official one that fit them and
hopefully use it ! If it's not in the list, this person can contact hopefully use it ! If it's not in the list, this person can contact
us any time for addition of such a missing tag. But it doesn't mean us any time for addition of such a missing tag. But it doesn't mean
skipping to change at page 19, line 32 skipping to change at page 19, line 32
[7] http://id3.org/id3v2.3.0#TPE1 [7] http://id3.org/id3v2.3.0#TPE1
[8] http://id3.org/id3v2.3.0#TPE2 [8] http://id3.org/id3v2.3.0#TPE2
[9] http://id3.org/id3v2.3.0#TCOM [9] http://id3.org/id3v2.3.0#TCOM
[10] http://id3.org/id3v2.3.0#TEXT [10] http://id3.org/id3v2.3.0#TEXT
[11] http://id3.org/id3v2.3.0#TPE3 [11] http://id3.org/id3v2.3.0#TPE3
[12] http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/RIFF.html [12] https://sno.phy.queensu.ca/~phil/exiftool/TagNames/RIFF.html
[13] http://id3.org/id3v2.3.0#TENC [13] http://id3.org/id3v2.3.0#TENC
[14] http://id3.org/id3v2.3.0#TPE4 [14] http://id3.org/id3v2.3.0#TPE4
[15] http://id3.org/id3v2.3.0#TPUB [15] http://id3.org/id3v2.3.0#TPUB
[16] http://id3.org/id3v2.3.0#TMED [16] http://id3.org/id3v2.3.0#TMED
[17] http://www.icra.org/ [17] http://www.icra.org/
[18] http://www.iana.org/cctld/cctld-whois.htm [18] https://www.iana.org/whois
[19] http://www.iso.org/iso/country_codes [19] https://www.iso.org/iso-3166-country-codes.html
[20] http://www.iana.org/cctld/cctld-whois.htm [20] https://www.iana.org/whois
[21] http://www.iso.org/iso/country_codes [21] https://www.iso.org/iso-3166-country-codes.html
[22] http://www.iana.org/cctld/cctld-whois.htm [22] https://www.iana.org/whois
[23] http://www.iso.org/iso/country_codes [23] https://www.iso.org/iso-3166-country-codes.html
[24] http://www.replaygain.org/ [24] http://www.replaygain.org/
[25] http://www.replaygain.org/ [25] http://www.replaygain.org/
[26] http://www.ifpi.org/isrc/isrc_handbook.html#Heading198 [26] http://www.ifpi.org/isrc/isrc_handbook.html#Heading198
[27] http://www.isbn-international.org/ [27] http://www.isbn-international.org/
[28] http://www.ean-int.org/ [28] http://www.ean-int.org/
[29] http://www.uc-council.org/ [29] http://www.uc-council.org/
[30] http://www.loc.gov/marc/lccn.html [30] https://www.loc.gov/marc/lccn.html
[31] http://id3.org/id3v2.3.0#TOWN [31] http://id3.org/id3v2.3.0#TOWN
[32] http://www.xe.com/iso4217.htm [32] http://www.xe.com/iso4217.htm
Authors' Addresses Authors' Addresses
Steve Lhomme Steve Lhomme
Email: slhomme@matroska.org Email: slhomme@matroska.org
 End of changes. 14 change blocks. 
14 lines changed or deleted 14 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/