The analysis is presented as an [http://lists.xiph.org/pipermail/vorbis-dev/attachments/20090716/e2db9203/attachment-0001.xls Excel spreadsheet] (note that it contains two sheets, the first of which is more interesting).

+

The analysis is presented as an [http://lists.xiph.org/pipermail/vorbis-dev/attachments/20090716/e2db9203/attachment-0001.xls Excel spreadsheet] (note that it contains two sheets, the first of which is the more interesting).

== Proposal ==

== Proposal ==

Line 35:

Line 35:

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.

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.

SOURCEMEDIA – recommended because two different field names have been proposed

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.