Field names: Difference between revisions

From XiphWiki
Jump to navigation Jump to search
m (Tidy)
(→‎Proposal: Added one more)
Line 21: Line 21:


# <code>COMPOSER</code>
# <code>COMPOSER</code>
# <code>TRACKTOTAL</code> &ndash; compliments the existing <code>TRACKNUMBER</code>
# <code>TRACKTOTAL</code> &ndash; complements the existing <code>TRACKNUMBER</code>
# <code>DISCNUMBER</code> &ndash; used if part of a multi-disc album
# <code>DISCNUMBER</code> &ndash; used if part of a multi-disc album
# <code>DISCTOTAL</code> &ndash; total number of discs in a multi-disc album
# <code>DISCTOTAL</code> &ndash; total number of discs in a multi-disc album
# <code>SOURCEMEDIA</code> &ndash; recommended because two different field names have been proposed
# <code>ENCODED-BY</code> &ndash; see [[VorbisComment]] page
# <code>ENCODED-BY</code> &ndash; see [[VorbisComment]] page
# <code>ENCODER</code> &ndash; see [[VorbisComment]] page
# <code>ENCODER</code> &ndash; see [[VorbisComment]] page
# <code>METADATA_BLOCK_PICTURE</code> &ndash; see [[VorbisComment]] page
# <code>METADATA_BLOCK_PICTURE</code> &ndash; see [[VorbisComment]] page
# <code>SOURCEMEDIA</code> &ndash; recommended because two different field names have been proposed
# <code>PRODUCTNUMBER</code> &ndash; recommended because two different field names have been proposed


The field name <code>SOURCEMEDIA</code> could be dropped if Xiph does '''not''' wish to prescribe field names. (The alternative which has been proposed to store this information is <code>SOURCE MEDIUM</code>.)
The field names <code>SOURCEMEDIA</code> and <code>PRODUCTNUMBER</code> could be dropped if Xiph does '''not''' wish to prescribe field names. (The alternatives which have also been proposed to store the same information are <code>SOURCE MEDIUM</code> and <code>EAN/UPN</code>, respectively.)
 
There are also two proposals for a field name to store barcodes, <code>PRODUCTNUMBER</code> and <code>EAN/UPN</code>. If Xiph ''does'' wish to prescribe field names then <code>PRODUCTNUMBER</code> could be included. It is not included only because storing barcodes is thought to be esoteric.


The triple <code>RIGHTS</code>, <code>RIGHTS-DATE</code>, <code>RIGHTS-URI</code> has not been included because this is structured metadata. VorbisComments are inherently unstructured and this should be respected.
The field name <code>REMIXER</code> has '''not''' been included as its use is covered by the existing <code>VERSION</code>.


The field name <code>REMIXER</code> is '''not''' proposed as its use is covered by the existing <code>VERSION</code>.
The triple <code>RIGHTS</code>, <code>RIGHTS-DATE</code>, <code>RIGHTS-URI</code>, proposed on the [[VorbisComment]] page, has '''not''' been included because this is structured metadata. VorbisComments are inherently unstructured and this should be respected.

Revision as of 07:48, 16 July 2009

This page describes a proposed update to the minimal list of 15 standard field names in the Vorbis I specification. Please keep discussion confined to the Discussion page (or, better, the <vorbis-dev> mailing list).

After the proposal has been discussed, and accepted or rejected, this page should be deleted.

Analysis

To determine what field names are being used in the wild, the following resources were analysed:

The analysis has been presented as an Excel spreadsheet (note that it contains two sheets).

Proposal

The following modest list of additions to the minimal list in the specification is proposed:

  1. COMPOSER
  2. TRACKTOTAL – complements the existing TRACKNUMBER
  3. DISCNUMBER – used if part of a multi-disc album
  4. DISCTOTAL – total number of discs in a multi-disc album
  5. ENCODED-BY – see VorbisComment page
  6. ENCODER – see VorbisComment page
  7. METADATA_BLOCK_PICTURE – see VorbisComment page
  8. SOURCEMEDIA – recommended because two different field names have been proposed
  9. PRODUCTNUMBER – recommended because two different field names have been proposed

The field names SOURCEMEDIA and PRODUCTNUMBER could be dropped if Xiph does not wish to prescribe field names. (The alternatives which have also been proposed to store the same information are SOURCE MEDIUM and EAN/UPN, respectively.)

The field name REMIXER has not been included as its use is covered by the existing VERSION.

The triple RIGHTS, RIGHTS-DATE, RIGHTS-URI, proposed on the VorbisComment page, has not been included because this is structured metadata. VorbisComments are inherently unstructured and this should be respected.