Field names: Difference between revisions

From XiphWiki
Jump to navigation Jump to search
(→‎Proposal: Added stuff)
m (→‎Proposal: Tidy)
Line 29: Line 29:
# <code>METADATA_BLOCK_PICTURE</code> &ndash; see [[VorbisComment]] page
# <code>METADATA_BLOCK_PICTURE</code> &ndash; see [[VorbisComment]] page


The field name <code>SOURCEMEDIA</code> could be dropped if Xiph does '''not''' wish to prescribe field names. (The alternative proposed for this information is <code>SOURCE MEDIUM</code>.)
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>.)


There are also two proposals for a field name to store the barcode, <code>PRODUCTNUMBER</code> and <code>EAN/UPN</code>. If Xiph ''does'' wish to prescribe field names, then <code>PRODUCTNUMBER</code> could be added.
There are also two proposals for a field name to store the barcode, <code>PRODUCTNUMBER</code> and <code>EAN/UPN</code>. If Xiph ''does'' wish to prescribe field names, then <code>PRODUCTNUMBER</code> could be added. This is not proposed 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 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> is '''not''' proposed 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>.

Revision as of 11:31, 15 July 2009

This page describes a proposed update to the minimal list of 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 – compliments 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. SOURCEMEDIA – recommended because two different field names have been proposed
  6. ENCODED-BY – see VorbisComment page
  7. ENCODER – see VorbisComment page
  8. METADATA_BLOCK_PICTURE – see VorbisComment page

The field name SOURCEMEDIA could be dropped if Xiph does not wish to prescribe field names. (The alternative which has been proposed to store this information is SOURCE MEDIUM.)

There are also two proposals for a field name to store the barcode, PRODUCTNUMBER and EAN/UPN. If Xiph does wish to prescribe field names, then PRODUCTNUMBER could be added. This is not proposed only because storing barcodes is thought to be esoteric.

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

The field name REMIXER is not proposed as its use is covered by the existing VERSION.