idnits 2.17.1 draft-ietf-cellar-tags-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (27 October 2019) is 1615 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 cellar S. Lhomme 3 Internet-Draft 4 Intended status: Informational M. Bunkus 5 Expires: 29 April 2020 6 D. Rice 7 27 October 2019 9 Matroska Tags 10 draft-ietf-cellar-tags-03 12 Abstract 14 This document defines the Matroska tags, namely the tag names and 15 their respective semantic meaning. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at https://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on 29 April 2020. 34 Copyright Notice 36 Copyright (c) 2019 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 41 license-info) in effect on the date of publication of this document. 42 Please review these documents carefully, as they describe your rights 43 and restrictions with respect to this document. Code Components 44 extracted from this document must include Simplified BSD License text 45 as described in Section 4.e of the Trust Legal Provisions and are 46 provided without warranty as described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 2. Status of this document . . . . . . . . . . . . . . . . . . . 3 52 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 53 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 54 5. Notations and Conventions . . . . . . . . . . . . . . . . . . 3 55 6. Tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 6.1. Why official tags matter . . . . . . . . . . . . . . . . 4 57 6.2. Tag translations . . . . . . . . . . . . . . . . . . . . 4 58 6.3. Tag Formatting . . . . . . . . . . . . . . . . . . . . . 5 59 6.4. Target types . . . . . . . . . . . . . . . . . . . . . . 5 60 6.5. Official tags . . . . . . . . . . . . . . . . . . . . . . 7 61 6.6. Nesting Information . . . . . . . . . . . . . . . . . . . 7 62 6.7. Organization Information . . . . . . . . . . . . . . . . 9 63 6.8. Titles . . . . . . . . . . . . . . . . . . . . . . . . . 9 64 6.9. Nested Information . . . . . . . . . . . . . . . . . . . 9 65 6.10. Entities . . . . . . . . . . . . . . . . . . . . . . . . 10 66 6.11. Search and Classification . . . . . . . . . . . . . . . . 14 67 6.12. Temporal Information . . . . . . . . . . . . . . . . . . 15 68 6.13. Spacial Information . . . . . . . . . . . . . . . . . . . 16 69 6.14. Personal . . . . . . . . . . . . . . . . . . . . . . . . 17 70 6.15. Technical Information . . . . . . . . . . . . . . . . . . 18 71 6.16. Identifiers . . . . . . . . . . . . . . . . . . . . . . . 19 72 6.17. Commercial . . . . . . . . . . . . . . . . . . . . . . . 20 73 6.18. Legal . . . . . . . . . . . . . . . . . . . . . . . . . . 21 74 6.19. Notes . . . . . . . . . . . . . . . . . . . . . . . . . . 21 75 7. Normative References . . . . . . . . . . . . . . . . . . . . 21 76 8. Informative References . . . . . . . . . . . . . . . . . . . 22 77 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 79 1. Introduction 81 Matroska aims to become THE standard of multimedia container formats. 82 It can store timestamped multimedia data but also chapters and tags. 83 The "Tag Elements" add important metadata to identify and classify 84 the information found in a "Matroska Segment". It can tag a whole 85 "Segment", separate "Track Elements", individual "Chapter Elements" 86 or "Attachment Elements". 88 While the Matroska tagging framework allows anyone to create their 89 own custom tags, it's important to have a common set of values for 90 interoperability. This document intends to define a set of common 91 tag names used in Matroska. 93 2. Status of this document 95 This document is a work-in-progress specification defining the 96 Matroska file format as part of the IETF Cellar working group 97 (https://datatracker.ietf.org/wg/cellar/charter/). It uses basic 98 elements and concepts already defined in the Matroska specifications 99 defined by this workgroup. 101 3. Security Considerations 103 "Tag" values can be either strings or binary blobs. This document 104 inherits security considerations from the EBML and Matroska 105 documents. 107 4. IANA Considerations 109 To be determined. 111 5. Notations and Conventions 113 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 114 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 115 "OPTIONAL" in this document are to be interpreted as described in BCP 116 14 [RFC2119] [RFC8174] when, and only when, they appear in all 117 capitals, as shown here. 119 6. Tagging 121 When a Tag is nested within another Tag, the nested Tag becomes an 122 attribute of the base tag. For instance, if you wanted to store the 123 dates that a singer used certain addresses for, that singer being the 124 lead singer for a track that included multiple bands simultaneously, 125 then your tag tree would look something like this: 127 * Targets 129 - TrackUID 131 * BAND 133 - LEADPERFORMER 135 - ADDRESS 137 o DATE 139 o DATEEND 141 - ADDRESS 143 o DATE 145 In this way, it becomes possible to store any Tag as attributes of 146 another tag. 148 Multiple items SHOULD never be stored as a list in a single 149 TagString. If there is more than one tag of a certain type to be 150 stored, then more than one SimpleTag SHOULD be used. 152 For authoring Tags outside of EBML, the following XML syntax is 153 proposed (http://www.matroska.org/files/tags/matroskatags.dtd) used 154 in mkvmerge (http://www.bunkus.org/videotools/mkvtoolnix/doc/ 155 mkvmerge.html#mkvmerge.tags). Binary data SHOULD be stored using 156 BASE64 encoding if it is being stored at authoring time. 158 6.1. Why official tags matter 160 There is a debate between people who think all tags SHOULD be free 161 and those who think all tags SHOULD be strict. If you look at this 162 page you will realize we are in between. 164 Advanced-users application might let you put any tag in your file. 165 But for the rest of the applications, they usually give you a basic 166 list of tags you can use. Both have their needs. But it's usually a 167 bad idea to use custom/exotic tags because you will probably be the 168 only person to use this information even though everyone else could 169 benefit from it. So hopefully when someone wants to put information 170 in one's file, they will find an official one that fit them and 171 hopefully use it ! If it's not in the list, this person can contact 172 us any time for addition of such a missing tag. But it doesn't mean 173 it will be accepted... Matroska files are not meant the become a 174 whole database of people who made costumes for a film. A website 175 would be better for that... It's hard to define what SHOULD be in and 176 what doesn't make sense in a file. So we'll treat each request 177 carefully. 179 We also need an official list simply for developers to be able to 180 display relevant information in their own design (if they choose to 181 support a list of meta-information they SHOULD know which tag has the 182 wanted meaning so that other apps could understand the same meaning). 184 6.2. Tag translations 186 To be able to save tags from other systems to Matroska we need to 187 translate them to our system. There is a translation table on our 188 site (othertagsystems/comparetable.html). 190 6.3. Tag Formatting 192 * The TagName SHOULD always be written in all capital letters and 193 contain no space. 195 * The fields with dates SHOULD have the following format: YYYY-MM-DD 196 hh:mm:ss.mss YYYY = Year, MM = Month, DD = Days, HH = Hours, mm = 197 Minutes, ss = Seconds, mss = Milliseconds. To store less 198 accuracy, you remove items starting from the right. To store only 199 the year, you would use, "2004". To store a specific day such as 200 May 1st, 2003, you would use "2003-05-01". 202 * Fields that require a Float SHOULD use the "." mark instead of the 203 "," mark. To display it differently for another local, 204 applications SHOULD support auto replacement on display. Also, a 205 thousandths separator SHOULD NOT be used. 207 * For currency amounts, there SHOULD only be a numeric value in the 208 Tag. Only numbers, no letters or symbols other than ".". For 209 instance, you would store "15.59" instead of "$15.59USD". 211 6.4. Target types 213 The TargetType element allows tagging of different parts that are 214 inside or outside a given file. For example in an audio file with 215 one song you could have information about the album it comes from and 216 even the CD set even if it's not found in the file. 218 For application to know what kind of information (like TITLE) relates 219 to a certain level (CD title or track title), we also need a set of 220 official TargetType names. For now audio and video will have 221 different values & names. That also means the same tag name can have 222 different meanings depending on where it is (otherwise we would end 223 up with 15 TITLE_ tags). 225 +-----------------+------------+------------+-----------------------+ 226 | TargetTypeValue | Audio | Video | Comment | 227 | | strings | strings | | 228 +=================+============+============+=======================+ 229 | 70 | COLLECTION | COLLECTION | the high | 230 | | | | hierarchy | 231 | | | | consisting of | 232 | | | | many different | 233 | | | | lower items | 234 +-----------------+------------+------------+-----------------------+ 235 | 60 | EDITION / | SEASON / | a list of lower | 236 | | ISSUE / | SEQUEL / | levels grouped | 237 | | VOLUME / | VOLUME | together | 238 | | OPUS | | | 239 +-----------------+------------+------------+-----------------------+ 240 | 50 | ALBUM / | MOVIE / | the most common | 241 | | OPERA / | EPISODE / | grouping level | 242 | | CONCERT | CONCERT | of music and | 243 | | | | video (equals | 244 | | | | to an episode | 245 | | | | for TV series) | 246 +-----------------+------------+------------+-----------------------+ 247 | 40 | PART / | PART / | when an album | 248 | | SESSION | SESSION | or episode has | 249 | | | | different | 250 | | | | logical parts | 251 +-----------------+------------+------------+-----------------------+ 252 | 30 | TRACK / | CHAPTER | the common | 253 | | SONG | | parts of an | 254 | | | | album or a | 255 | | | | movie | 256 +-----------------+------------+------------+-----------------------+ 257 | 20 | SUBTRACK / | SCENE | corresponds to | 258 | | PART / | | parts of a | 259 | | MOVEMENT | | track for audio | 260 | | | | (like a | 261 | | | | movement) | 262 +-----------------+------------+------------+-----------------------+ 263 | 10 | - | SHOT | the lowest | 264 | | | | hierarchy found | 265 | | | | in music or | 266 | | | | movies | 267 +-----------------+------------+------------+-----------------------+ 269 Table 1 271 An upper level value tag applies to the lower level. That means if a 272 CD has the same artist for all tracks, you just need to set the 273 ARTIST tag at level 50 (ALBUM) and not to each TRACK (but you can). 274 That also means that if some parts of the CD have no known ARTIST the 275 value MUST be set to nothing (a void string ""). 277 When a level doesn't exist it MUST NOT be specified in the files, so 278 that the TOTAL_PARTS and PART_NUMBER elements match the same levels. 280 Here is an example of how these "organizational" tags work: If you 281 set 10 TOTAL_PARTS to the ALBUM level (40) it means the album 282 contains 10 lower parts. The lower part in question is the first 283 lower level that is specified in the file. So if it's TRACK (30) 284 then that means it contains 10 tracks. If it's MOVEMENT (20) that 285 means it's 10 movements, etc. 287 6.5. Official tags 289 The following is a complete list of the supported Matroska Tags. 290 While it is possible to use Tag names that are not listed below, this 291 is not recommended as compatibility will be compromised. If you find 292 that there is a Tag missing that you would like to use, then please 293 contact the Matroska team for its inclusion in the specifications 294 before the format reaches 1.0. 296 6.6. Nesting Information 298 Nesting Information tags are intended to contain other tags. 300 +----------+-------+-------------------------------------------+ 301 | Tag Name | Type | Description | 302 +==========+=======+===========================================+ 303 | ORIGINAL | - | A special tag that is meant to have other | 304 | | | tags inside (using nested tags) to | 305 | | | describe the original work of art that | 306 | | | this item is based on. All tags in this | 307 | | | list can be used "under" the ORIGINAL tag | 308 | | | like LYRICIST, PERFORMER, etc. | 309 +----------+-------+-------------------------------------------+ 310 | SAMPLE | - | A tag that contains other tags to | 311 | | | describe a sample used in the targeted | 312 | | | item taken from another work of art. All | 313 | | | tags in this list can be used "under" the | 314 | | | SAMPLE tag like TITLE, ARTIST, | 315 | | | DATE_RELEASED, etc. | 316 +----------+-------+-------------------------------------------+ 317 | COUNTRY | UTF-8 | The name of the country (biblio ISO-639-2 | 318 | | | (https://www.loc.gov/standards/iso639- | 319 | | | 2/php/English_list.php)) that is meant to | 320 | | | have other tags inside (using nested | 321 | | | tags) to country specific information | 322 | | | about the item. All tags in this list | 323 | | | can be used "under" the COUNTRY_SPECIFIC | 324 | | | tag like LABEL, PUBLISH_RATING, etc. | 325 +----------+-------+-------------------------------------------+ 327 Table 2 329 6.7. Organization Information 331 +-------------+-------+--------------------------------------------+ 332 | Tag Name | Type | Description | 333 +=============+=======+============================================+ 334 | TOTAL_PARTS | UTF-8 | Total number of parts defined at the first | 335 | | | lower level. (e.g. if TargetType is ALBUM, | 336 | | | the total number of tracks of an audio CD) | 337 +-------------+-------+--------------------------------------------+ 338 | PART_NUMBER | UTF-8 | Number of the current part of the current | 339 | | | level. (e.g. if TargetType is TRACK, the | 340 | | | track number of an audio CD) | 341 +-------------+-------+--------------------------------------------+ 342 | PART_OFFSET | UTF-8 | A number to add to PART_NUMBER when the | 343 | | | parts at that level don't start at 1. | 344 | | | (e.g. if TargetType is TRACK, the track | 345 | | | number of the second audio CD) | 346 +-------------+-------+--------------------------------------------+ 348 Table 3 350 6.8. Titles 352 +----------+-------+------------------------------------------------+ 353 | Tag Name | Type | Description | 354 +==========+=======+================================================+ 355 | TITLE | UTF-8 | The title of this item. For example, | 356 | | | for music you might label this "Canon | 357 | | | in D", or for video's audio track you | 358 | | | might use "English 5.1" This is akin | 359 | | | to the TIT2 tag in ID3. | 360 +----------+-------+------------------------------------------------+ 361 | SUBTITLE | UTF-8 | Sub Title of the entity. | 362 +----------+-------+------------------------------------------------+ 364 Table 4 366 6.9. Nested Information 368 Nested Information includes tags contained in other tags. 370 +-------------+-------+---------------------------------------------+ 371 | Tag Name | Type | Description | 372 +=============+=======+=============================================+ 373 | URL | UTF-8 | URL corresponding to the tag it's | 374 | | | included in. | 375 +-------------+-------+---------------------------------------------+ 376 | SORT_WITH | UTF-8 | A child element to indicate what | 377 | | | alternative value the parent tag | 378 | | | can have to be sorted, for example | 379 | | | "Pet Shop Boys" instead of "The Pet | 380 | | | Shop Boys". Or "Marley Bob" and | 381 | | | "Marley Ziggy" (no comma needed). | 382 +-------------+-------+---------------------------------------------+ 383 | INSTRUMENTS | UTF-8 | The instruments that are being | 384 | | | used/played, separated by a comma. | 385 | | | It SHOULD be a child of the | 386 | | | following tags: ARTIST, | 387 | | | LEAD_PERFORMER or ACCOMPANIMENT. | 388 +-------------+-------+---------------------------------------------+ 389 | EMAIL | UTF-8 | Email corresponding to the tag it's | 390 | | | included in. | 391 +-------------+-------+---------------------------------------------+ 392 | ADDRESS | UTF-8 | The physical address of the entity. | 393 | | | The address SHOULD include a | 394 | | | country code. It can be useful for | 395 | | | a recording label. | 396 +-------------+-------+---------------------------------------------+ 397 | FAX | UTF-8 | The fax number corresponding to the | 398 | | | tag it's included in. It can be | 399 | | | useful for a recording label. | 400 +-------------+-------+---------------------------------------------+ 401 | PHONE | UTF-8 | The phone number corresponding to | 402 | | | the tag it's included in. It can | 403 | | | be useful for a recording label. | 404 +-------------+-------+---------------------------------------------+ 406 Table 5 408 6.10. Entities 410 +-------------------------+-------+-------------------------------+ 411 | Tag Name | Type | Description | 412 +=========================+=======+===============================+ 413 | ARTIST | UTF-8 | A person or band/collective | 414 | | | generally considered | 415 | | | responsible for the work. | 416 | | | This is akin to the TPE1 tag | 417 | | | in ID3 (http://id3.org/ | 418 | | | id3v2.3.0#TPE1). | 419 +-------------------------+-------+-------------------------------+ 420 | LEAD_PERFORMER | UTF-8 | Lead Performer/Soloist(s). | 421 | | | This can sometimes be the | 422 | | | same as ARTIST. | 423 +-------------------------+-------+-------------------------------+ 424 | ACCOMPANIMENT | UTF-8 | Band/orchestra/accompaniment/ | 425 | | | musician. This is akin to | 426 | | | the TPE2 tag in ID3 | 427 | | | (http://id3.org/ | 428 | | | id3v2.3.0#TPE2). | 429 +-------------------------+-------+-------------------------------+ 430 | COMPOSER | UTF-8 | The name of the composer of | 431 | | | this item. This is akin to | 432 | | | the TCOM tag in ID3 | 433 | | | (http://id3.org/ | 434 | | | id3v2.3.0#TCOM). | 435 +-------------------------+-------+-------------------------------+ 436 | ARRANGER | UTF-8 | The person who arranged the | 437 | | | piece, e.g., Ravel. | 438 +-------------------------+-------+-------------------------------+ 439 | LYRICS | UTF-8 | The lyrics corresponding to a | 440 | | | song (in case audio | 441 | | | synchronization is not known | 442 | | | or as a doublon to a subtitle | 443 | | | track). Editing this value | 444 | | | when subtitles are found | 445 | | | SHOULD also result in editing | 446 | | | the subtitle track for more | 447 | | | consistency. | 448 +-------------------------+-------+-------------------------------+ 449 | LYRICIST | UTF-8 | The person who wrote the | 450 | | | lyrics for a musical item. | 451 | | | This is akin to the TEXT | 452 | | | (http://id3.org/ | 453 | | | id3v2.3.0#TEXT) tag in ID3. | 454 +-------------------------+-------+-------------------------------+ 455 | CONDUCTOR | UTF-8 | Conductor/performer | 456 | | | refinement. This is akin to | 457 | | | the TPE3 (http://id3.org/ | 458 | | | id3v2.3.0#TPE3). | 459 +-------------------------+-------+-------------------------------+ 460 | DIRECTOR | UTF-8 | This is akin to the [IART tag | 461 | | | in RIFF][RIFF.tags]. | 462 +-------------------------+-------+-------------------------------+ 463 | ASSISTANT_DIRECTOR | UTF-8 | The name of the assistant | 464 | | | director. | 465 +-------------------------+-------+-------------------------------+ 466 | DIRECTOR_OF_PHOTOGRAPHY | UTF-8 | The name of the director of | 467 | | | photography, also known as | 468 | | | cinematographer. This is | 469 | | | akin to the ICNM tag in | 470 | | | Extended RIFF. | 471 +-------------------------+-------+-------------------------------+ 472 | SOUND_ENGINEER | UTF-8 | The name of the sound | 473 | | | engineer or sound recordist. | 474 +-------------------------+-------+-------------------------------+ 475 | ART_DIRECTOR | UTF-8 | The person who oversees the | 476 | | | artists and craftspeople who | 477 | | | build the sets. | 478 +-------------------------+-------+-------------------------------+ 479 | PRODUCTION_DESIGNER | UTF-8 | Artist responsible for | 480 | | | designing the overall visual | 481 | | | appearance of a movie. | 482 +-------------------------+-------+-------------------------------+ 483 | CHOREGRAPHER | UTF-8 | The name of the choregrapher | 484 +-------------------------+-------+-------------------------------+ 485 | COSTUME_DESIGNER | UTF-8 | The name of the costume | 486 | | | designer | 487 +-------------------------+-------+-------------------------------+ 488 | ACTOR | UTF-8 | An actor or actress playing a | 489 | | | role in this movie. This is | 490 | | | the person's real name, not | 491 | | | the character's name the | 492 | | | person is playing. | 493 +-------------------------+-------+-------------------------------+ 494 | CHARACTER | UTF-8 | The name of the character an | 495 | | | actor or actress plays in | 496 | | | this movie. This SHOULD be a | 497 | | | sub-tag of an "ACTOR" tag in | 498 | | | order not to cause | 499 | | | ambiguities. | 500 +-------------------------+-------+-------------------------------+ 501 | WRITTEN_BY | UTF-8 | The author of the story or | 502 | | | script (used for movies and | 503 | | | TV shows). | 504 +-------------------------+-------+-------------------------------+ 505 | SCREENPLAY_BY | UTF-8 | The author of the screenplay | 506 | | | or scenario (used for movies | 507 | | | and TV shows). | 508 +-------------------------+-------+-------------------------------+ 509 | EDITED_BY | UTF-8 | This is akin to the IEDT tag | 510 | | | in Extended RIFF. | 511 +-------------------------+-------+-------------------------------+ 512 | PRODUCER | UTF-8 | Produced by. This is akin to | 513 | | | the IPRO tag in Extended | 514 | | | RIFF. | 515 +-------------------------+-------+-------------------------------+ 516 | COPRODUCER | UTF-8 | The name of a co-producer. | 517 +-------------------------+-------+-------------------------------+ 518 | EXECUTIVE_PRODUCER | UTF-8 | The name of an executive | 519 | | | producer. | 520 +-------------------------+-------+-------------------------------+ 521 | DISTRIBUTED_BY | UTF-8 | This is akin to the IDST tag | 522 | | | in Extended RIFF. | 523 +-------------------------+-------+-------------------------------+ 524 | MASTERED_BY | UTF-8 | The engineer who mastered the | 525 | | | content for a physical medium | 526 | | | or for digital distribution. | 527 +-------------------------+-------+-------------------------------+ 528 | ENCODED_BY | UTF-8 | This is akin to the TENC tag | 529 | | | (http://id3.org/ | 530 | | | id3v2.3.0#TENC) in ID3. | 531 +-------------------------+-------+-------------------------------+ 532 | MIXED_BY | UTF-8 | DJ mix by the artist | 533 | | | specified | 534 +-------------------------+-------+-------------------------------+ 535 | REMIXED_BY | UTF-8 | Interpreted, remixed, or | 536 | | | otherwise modified by. This | 537 | | | is akin to the TPE4 tag in | 538 | | | ID3 (http://id3.org/ | 539 | | | id3v2.3.0#TPE4). | 540 +-------------------------+-------+-------------------------------+ 541 | PRODUCTION_STUDIO | UTF-8 | This is akin to the ISTD tag | 542 | | | in Extended RIFF. | 543 +-------------------------+-------+-------------------------------+ 544 | THANKS_TO | UTF-8 | A very general tag for | 545 | | | everyone else that wants to | 546 | | | be listed. | 547 +-------------------------+-------+-------------------------------+ 548 | PUBLISHER | UTF-8 | This is akin to the TPUB tag | 549 | | | in ID3 (http://id3.org/ | 550 | | | id3v2.3.0#TPUB). | 551 +-------------------------+-------+-------------------------------+ 552 | LABEL | UTF-8 | The record label or imprint | 553 | | | on the disc. | 554 +-------------------------+-------+-------------------------------+ 556 Table 6 558 6.11. Search and Classification 560 +---------------------+--------+-----------------------------------+ 561 | Tag Name | Type | Description | 562 +=====================+========+===================================+ 563 | GENRE | UTF-8 | The main genre (classical, | 564 | | | ambient-house, synthpop, sci-fi, | 565 | | | drama, etc). The format follows | 566 | | | the infamous TCON tag in ID3. | 567 +---------------------+--------+-----------------------------------+ 568 | MOOD | UTF-8 | Intended to reflect the mood of | 569 | | | the item with a few keywords, | 570 | | | e.g. "Romantic", "Sad" or | 571 | | | "Uplifting". The format follows | 572 | | | that of the TMOO tag in ID3. | 573 +---------------------+--------+-----------------------------------+ 574 | ORIGINAL_MEDIA_TYPE | UTF-8 | Describes the original type of | 575 | | | the media, such as, "DVD", "CD", | 576 | | | "computer image," "drawing," | 577 | | | "lithograph," and so forth. This | 578 | | | is akin to the TMED tag in ID3 | 579 | | | (http://id3.org/id3v2.3.0#TMED). | 580 +---------------------+--------+-----------------------------------+ 581 | CONTENT_TYPE | UTF-8 | The type of the item. e.g. | 582 | | | Documentary, Feature Film, | 583 | | | Cartoon, Music Video, Music, | 584 | | | Sound FX, ... | 585 +---------------------+--------+-----------------------------------+ 586 | SUBJECT | UTF-8 | Describes the topic of the file, | 587 | | | such as "Aerial view of Seattle." | 588 +---------------------+--------+-----------------------------------+ 589 | DESCRIPTION | UTF-8 | A short description of the | 590 | | | content, such as "Two birds | 591 | | | flying." | 592 +---------------------+--------+-----------------------------------+ 593 | KEYWORDS | UTF-8 | Keywords to the item separated by | 594 | | | a comma, used for searching. | 595 +---------------------+--------+-----------------------------------+ 596 | SUMMARY | UTF-8 | A plot outline or a summary of | 597 | | | the story. | 598 +---------------------+--------+-----------------------------------+ 599 | SYNOPSIS | UTF-8 | A description of the story line | 600 | | | of the item. | 601 +---------------------+--------+-----------------------------------+ 602 | INITIAL_KEY | UTF-8 | The initial key that a musical | 603 | | | track starts in. The format is | 604 | | | identical to ID3. | 605 +---------------------+--------+-----------------------------------+ 606 | PERIOD | UTF-8 | Describes the period that the | 607 | | | piece is from or about. For | 608 | | | example, "Renaissance". | 609 +---------------------+--------+-----------------------------------+ 610 | LAW_RATING | UTF-8 | Depending on the "COUNTRY" it's | 611 | | | the format of the rating of a | 612 | | | movie (P, R, X in the USA, an age | 613 | | | in other countries or a URI | 614 | | | defining a logo). | 615 +---------------------+--------+-----------------------------------+ 616 | ICRA | binary | The ICRA (http://www.icra.org/) | 617 | | | content rating for parental | 618 | | | control. (Previously RSACi) | 619 +---------------------+--------+-----------------------------------+ 621 Table 7 623 6.12. Temporal Information 625 +----------------+-------+---------------------------------------+ 626 | Tag Name | Type | Description | 627 +================+=======+=======================================+ 628 | DATE_RELEASED | UTF-8 | The time that the item was originally | 629 | | | released. This is akin to the TDRL | 630 | | | tag in ID3. | 631 +----------------+-------+---------------------------------------+ 632 | DATE_RECORDED | UTF-8 | The time that the recording began. | 633 | | | This is akin to the TDRC tag in ID3. | 634 +----------------+-------+---------------------------------------+ 635 | DATE_ENCODED | UTF-8 | The time that the encoding of this | 636 | | | item was completed began. This is | 637 | | | akin to the TDEN tag in ID3. | 638 +----------------+-------+---------------------------------------+ 639 | DATE_TAGGED | UTF-8 | The time that the tags were done for | 640 | | | this item. This is akin to the TDTG | 641 | | | tag in ID3. | 642 +----------------+-------+---------------------------------------+ 643 | DATE_DIGITIZED | UTF-8 | The time that the item was | 644 | | | transferred to a digital medium. | 645 | | | This is akin to the IDIT tag in RIFF. | 646 +----------------+-------+---------------------------------------+ 647 | DATE_WRITTEN | UTF-8 | The time that the writing of the | 648 | | | music/script began. | 649 +----------------+-------+---------------------------------------+ 650 | DATE_PURCHASED | UTF-8 | Information on when the file was | 651 | | | purchased (see also purchase tags | 652 | | | (#commercial)). | 653 +----------------+-------+---------------------------------------+ 654 Table 8 656 6.13. Spacial Information 658 +----------------------+-------+-----------------------------------+ 659 | Tag Name | Type | Description | 660 +======================+=======+===================================+ 661 | RECORDING_LOCATION | UTF-8 | The location where the item was | 662 | | | recorded. The countries | 663 | | | corresponding to the string, same | 664 | | | 2 octets as in Internet domains | 665 | | | (https://www.iana.org/whois), or | 666 | | | possibly ISO-3166 | 667 | | | (https://www.iso.org/iso-3166- | 668 | | | country-codes.html). This code | 669 | | | is followed by a comma, then more | 670 | | | detailed information such as | 671 | | | state/province, another comma, | 672 | | | and then city. For example, "US, | 673 | | | Texas, Austin". This will allow | 674 | | | for easy sorting. It is okay to | 675 | | | only store the country, or the | 676 | | | country and the state/province. | 677 | | | More detailed information can be | 678 | | | added after the city through the | 679 | | | use of additional commas. In | 680 | | | cases where the province/state is | 681 | | | unknown, but you want to store | 682 | | | the city, simply leave a space | 683 | | | between the two commas. For | 684 | | | example, "US, , Austin". | 685 +----------------------+-------+-----------------------------------+ 686 | COMPOSITION_LOCATION | UTF-8 | Location that the item was | 687 | | | originally designed/written. The | 688 | | | countries corresponding to the | 689 | | | string, same 2 octets as in | 690 | | | Internet domains | 691 | | | (https://www.iana.org/whois), or | 692 | | | possibly ISO-3166 | 693 | | | (https://www.iso.org/iso-3166- | 694 | | | country-codes.html). This code | 695 | | | is followed by a comma, then more | 696 | | | detailed information such as | 697 | | | state/province, another comma, | 698 | | | and then city. For example, "US, | 699 | | | Texas, Austin". This will allow | 700 | | | for easy sorting. It is okay to | 701 | | | only store the country, or the | 702 | | | country and the state/province. | 703 | | | More detailed information can be | 704 | | | added after the city through the | 705 | | | use of additional commas. In | 706 | | | cases where the province/state is | 707 | | | unknown, but you want to store | 708 | | | the city, simply leave a space | 709 | | | between the two commas. For | 710 | | | example, "US, , Austin". | 711 +----------------------+-------+-----------------------------------+ 712 | COMPOSER_NATIONALITY | UTF-8 | Nationality of the main composer | 713 | | | of the item, mostly for classical | 714 | | | music. The countries | 715 | | | corresponding to the string, same | 716 | | | 2 octets as in Internet domains | 717 | | | (https://www.iana.org/whois), or | 718 | | | possibly ISO-3166 | 719 | | | (https://www.iso.org/iso-3166- | 720 | | | country-codes.html). | 721 +----------------------+-------+-----------------------------------+ 723 Table 9 725 6.14. Personal 727 +--------------+-------+----------------------------------------+ 728 | Tag Name | Type | Description | 729 +==============+=======+========================================+ 730 | COMMENT | UTF-8 | Any comment related to the content. | 731 +--------------+-------+----------------------------------------+ 732 | PLAY_COUNTER | UTF-8 | The number of time the item has been | 733 | | | played. | 734 +--------------+-------+----------------------------------------+ 735 | RATING | UTF-8 | A numeric value defining how much a | 736 | | | person likes the song/movie. The | 737 | | | number is between 0 and 5 with decimal | 738 | | | values possible (e.g. 2.7), 5(.0) | 739 | | | being the highest possible rating. | 740 | | | Other rating systems with different | 741 | | | ranges will have to be scaled. | 742 +--------------+-------+----------------------------------------+ 744 Table 10 746 6.15. Technical Information 748 +------------------+--------+-------------------------------------+ 749 | Tag Name | Type | Description | 750 +==================+========+=====================================+ 751 | ENCODER | UTF-8 | The software or hardware used to | 752 | | | encode this item. ("LAME" or | 753 | | | "XviD") | 754 +------------------+--------+-------------------------------------+ 755 | ENCODER_SETTINGS | UTF-8 | A list of the settings used for | 756 | | | encoding this item. No specific | 757 | | | format. | 758 +------------------+--------+-------------------------------------+ 759 | BPS | UTF-8 | The average bits per second of the | 760 | | | specified item. This is only the | 761 | | | data in the Blocks, and excludes | 762 | | | headers and any container overhead. | 763 +------------------+--------+-------------------------------------+ 764 | FPS | UTF-8 | The average frames per second of | 765 | | | the specified item. This is | 766 | | | typically the average number of | 767 | | | Blocks per second. In the event | 768 | | | that lacing is used, each laced | 769 | | | chunk is to be counted as a | 770 | | | separate frame. | 771 +------------------+--------+-------------------------------------+ 772 | BPM | UTF-8 | Average number of beats per minute | 773 | | | in the complete target (e.g. a | 774 | | | chapter). Usually a decimal | 775 | | | number. | 776 +------------------+--------+-------------------------------------+ 777 | MEASURE | UTF-8 | In music, a measure is a unit of | 778 | | | time in Western music like "4/4". | 779 | | | It represents a regular grouping of | 780 | | | beats, a meter, as indicated in | 781 | | | musical notation by the time | 782 | | | signature.. The majority of the | 783 | | | contemporary rock and pop music you | 784 | | | hear on the radio these days is | 785 | | | written in the 4/4 time signature. | 786 +------------------+--------+-------------------------------------+ 787 | TUNING | UTF-8 | It is saved as a frequency in hertz | 788 | | | to allow near-perfect tuning of | 789 | | | instruments to the same tone as the | 790 | | | musical piece (e.g. "441.34" in | 791 | | | Hertz). The default value is 440.0 | 792 | | | Hz. | 793 +------------------+--------+-------------------------------------+ 794 | REPLAYGAIN_GAIN | binary | The gain to apply to reach 89dB SPL | 795 | | | on playback. This is based on the | 796 | | | Replay Gain standard | 797 | | | (http://www.replaygain.org/). Note | 798 | | | that ReplayGain information can be | 799 | | | found at all TargetType levels | 800 | | | (track, album, etc). | 801 +------------------+--------+-------------------------------------+ 802 | REPLAYGAIN_PEAK | binary | The maximum absolute peak value of | 803 | | | the item. This is based on the | 804 | | | Replay Gain standard | 805 | | | (http://www.replaygain.org/). | 806 +------------------+--------+-------------------------------------+ 808 Table 11 810 6.16. Identifiers 812 +----------------+-------+------------------------------------------+ 813 | Tag Name | Type | Description | 814 +================+=======+==========================================+ 815 | ISRC | UTF-8 |The International Standard Recording Code | 816 | | | (http://www.ifpi.org/isrc/ | 817 | | |isrc_handbook.html#Heading198), excluding | 818 | | | the "ISRC" prefix and including hyphens. | 819 +----------------+-------+------------------------------------------+ 820 | MCDI |binary | This is a binary dump of the TOC of the | 821 | | |CDROM that this item was taken from. This| 822 | | |holds the same information as the MCDI in | 823 | | | ID3. | 824 +----------------+-------+------------------------------------------+ 825 | ISBN | UTF-8 | International Standard Book Number | 826 | | | (https://www.isbn-international.org/) | 827 +----------------+-------+------------------------------------------+ 828 | BARCODE | UTF-8 | EAN-13 | 829 | | | (https://www.gs1.org/standards/barcodes/ | 830 | | | ean-upc) (European Article Numbering) or | 831 | | | UPC-A (http://www.uc-council.org/) | 832 | | | (Universal Product Code) bar code | 833 | | | identifier | 834 +----------------+-------+------------------------------------------+ 835 | CATALOG_NUMBER | UTF-8 | A label-specific string used to identify | 836 | | | the release (TIC 01 for example). | 837 +----------------+-------+------------------------------------------+ 838 | LABEL_CODE | UTF-8 | A 4-digit or 5-digit number to identify | 839 | | | the record label, typically printed as | 840 | | | (LC) xxxx or (LC) 0xxxx on CDs medias or | 841 | | | covers (only the number is stored). | 842 +----------------+-------+------------------------------------------+ 843 | LCCN | UTF-8 | Library of Congress Control Number | 844 | | | (https://www.loc.gov/marc/lccn.html) | 845 +----------------+-------+------------------------------------------+ 846 | IMDB | UTF-8 | Internet Movie Database (IMDb) | 847 | | | (https://www.imdb.com/) identifier. 'tt' | 848 | | |followed by at least 7 digits for Movies, | 849 | | | TV Shows and Episodes. | 850 +----------------+-------+------------------------------------------+ 851 | TMDB | UTF-8 | The Movie Database (TMDb) | 852 | | |(https://www.themoviedb.org/) identifier. | 853 | | |The variable length digits string MUST be | 854 | | | prefixed with either "movie/" or "tv/". | 855 +----------------+-------+------------------------------------------+ 856 | TVDB | UTF-8 | The TV Database (TheTVDB) | 857 | | | (https://www.thetvdb.com/) identifier. | 858 | | | Variable length all-digits string | 859 | | | identifying a TV Show. | 860 +----------------+-------+------------------------------------------+ 862 Table 12 864 6.17. Commercial 866 +-------------------+-------+------------------------------------+ 867 | Tag Name | Type | Description | 868 +===================+=======+====================================+ 869 | PURCHASE_ITEM | UTF-8 | URL to purchase this file. This | 870 | | | is akin to the WPAY tag in ID3. | 871 +-------------------+-------+------------------------------------+ 872 | PURCHASE_INFO | UTF-8 | Information on where to purchase | 873 | | | this album. This is akin to the | 874 | | | WCOM tag in ID3. | 875 +-------------------+-------+------------------------------------+ 876 | PURCHASE_OWNER | UTF-8 | Information on the person who | 877 | | | purchased the file. This is akin | 878 | | | to the TOWN tag in ID3 | 879 | | | (http://id3.org/id3v2.3.0#TOWN). | 880 +-------------------+-------+------------------------------------+ 881 | PURCHASE_PRICE | UTF-8 | The amount paid for entity. There | 882 | | | SHOULD only be a numeric value in | 883 | | | here. Only numbers, no letters or | 884 | | | symbols other than ".". For | 885 | | | instance, you would store "15.59" | 886 | | | instead of "$15.59USD". | 887 +-------------------+-------+------------------------------------+ 888 | PURCHASE_CURRENCY | UTF-8 | The currency type used to pay for | 889 | | | the entity. Use ISO-4217 | 890 | | | (https://www.xe.com/iso4217.php) | 891 | | | for the 3 letter currency code. | 892 +-------------------+-------+------------------------------------+ 894 Table 13 896 6.18. Legal 898 +----------------------+-------+---------------------------------+ 899 | Tag Name | Type | Description | 900 +======================+=======+=================================+ 901 | COPYRIGHT | UTF-8 | The copyright information as | 902 | | | per the copyright holder. This | 903 | | | is akin to the TCOP tag in ID3. | 904 +----------------------+-------+---------------------------------+ 905 | PRODUCTION_COPYRIGHT | UTF-8 | The copyright information as | 906 | | | per the production copyright | 907 | | | holder. This is akin to the | 908 | | | TPRO tag in ID3. | 909 +----------------------+-------+---------------------------------+ 910 | LICENSE | UTF-8 | The license applied to the | 911 | | | content (like Creative Commons | 912 | | | variants). | 913 +----------------------+-------+---------------------------------+ 914 | TERMS_OF_USE | UTF-8 | The terms of use for this item. | 915 | | | This is akin to the USER tag in | 916 | | | ID3. | 917 +----------------------+-------+---------------------------------+ 919 Table 14 921 6.19. Notes 923 * In the Target list, a logical OR is applied on all tracks, a 924 logical OR is applied on all chapters. Then a logical AND is 925 applied between the Tracks list and the Chapters list to know if 926 an element belongs to this Target. 928 7. Normative References 930 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 931 Requirement Levels", BCP 14, RFC 2119, 932 DOI 10.17487/RFC2119, March 1997, 933 . 935 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 936 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 937 May 2017, . 939 8. Informative References 941 [RIFF.tags] 942 Exiftool, "RIFF Tags", October 2019, 943 . 946 Authors' Addresses 948 Steve Lhomme 950 Email: slhomme@matroska.org 952 Moritz Bunkus 954 Email: moritz@bunkus.org 956 Dave Rice 958 Email: dave@dericed.com