Field names - Revision history

MrZeus at 23:34, 18 August 2015

2015-08-18T23:34:15Z

← Older revision		Revision as of 23:34, 18 August 2015
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.

			[[Category:Vorbis]]

Martin.leese: /* Analysis */ Typo

2011-01-15T16:04:12Z

Analysis: Typo

← Older revision		Revision as of 16:04, 15 January 2011
Line 14:		Line 14:
	* [http://www.mp3tag.de/en/ Mp3tag] tagging program ([http://forums.mp3tag.de/index.php?showtopic=9730 post in the Mp3tag Forum])		* [http://www.mp3tag.de/en/ Mp3tag] tagging program ([http://forums.mp3tag.de/index.php?showtopic=9730 post in the Mp3tag Forum])

	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 ==

Martin.leese: /* Analysis */ Clarity

2011-01-10T19:28:51Z

Analysis: Clarity

← Older revision		Revision as of 19:28, 10 January 2011
Line 14:		Line 14:
	* [http://www.mp3tag.de/en/ Mp3tag] tagging program ([http://forums.mp3tag.de/index.php?showtopic=9730 post in the Mp3tag Forum])		* [http://www.mp3tag.de/en/ Mp3tag] tagging program ([http://forums.mp3tag.de/index.php?showtopic=9730 post in the Mp3tag Forum])

	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 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).

	== Proposal ==		== Proposal ==

Martin.leese: Added link to

2009-07-29T12:11:42Z

Added link to <vorbis-dev>

← Older revision		Revision as of 12:11, 29 July 2009
Line 1:		Line 1:
	This page describes a proposed update to the minimal list of 15 standard field names in the [http://xiph.org/vorbis/doc/v-comment.html Vorbis I specification]. Please keep discussion confined to [[Talk:Field names\|the Discussion page]] (or, better, the <vorbis-dev> mailing list).		This page describes a proposed update to the minimal list of 15 standard field names in the [http://xiph.org/vorbis/doc/v-comment.html Vorbis I specification]. Please keep discussion confined to [[Talk:Field names\|the Discussion page]] (or, better, the [http://lists.xiph.org/mailman/listinfo/vorbis-dev <vorbis-dev>] mailing list).

	After the proposal has been discussed, and accepted or rejected, this page should be deleted.		After the proposal has been discussed, and accepted or rejected, this page should be deleted.
Line 14:		Line 14:
	* [http://www.mp3tag.de/en/ Mp3tag] tagging program ([http://forums.mp3tag.de/index.php?showtopic=9730 post in the Mp3tag Forum])		* [http://www.mp3tag.de/en/ Mp3tag] tagging program ([http://forums.mp3tag.de/index.php?showtopic=9730 post in the Mp3tag Forum])

	The analysis is presented as [http://lists.xiph.org/pipermail/vorbis-dev/attachments/20090716/e2db9203/attachment-0001.xls an Excel spreadsheet] (note that it contains two sheets).		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).

	== Proposal ==		== Proposal ==

Martin.leese: /* Analysis */ Verb tense

2009-07-25T04:38:36Z

Analysis: Verb tense

← Older revision		Revision as of 04:38, 25 July 2009
Line 14:		Line 14:
	* [http://www.mp3tag.de/en/ Mp3tag] tagging program ([http://forums.mp3tag.de/index.php?showtopic=9730 post in the Mp3tag Forum])		* [http://www.mp3tag.de/en/ Mp3tag] tagging program ([http://forums.mp3tag.de/index.php?showtopic=9730 post in the Mp3tag Forum])

	The analysis ~~has been~~ presented as [http://lists.xiph.org/pipermail/vorbis-dev/attachments/20090716/e2db9203/attachment-0001.xls an Excel spreadsheet] (note that it contains two sheets).		The analysis is presented as [http://lists.xiph.org/pipermail/vorbis-dev/attachments/20090716/e2db9203/attachment-0001.xls an Excel spreadsheet] (note that it contains two sheets).

	== Proposal ==		== Proposal ==

Martin.leese: /* Analysis */ Added link to Excel spreadsheet. (It needs to be uploaded to XiphWiki.)

2009-07-25T04:37:48Z

Analysis: Added link to Excel spreadsheet. (It needs to be uploaded to XiphWiki.)

← Older revision		Revision as of 04:37, 25 July 2009
Line 14:		Line 14:
	* [http://www.mp3tag.de/en/ Mp3tag] tagging program ([http://forums.mp3tag.de/index.php?showtopic=9730 post in the Mp3tag Forum])		* [http://www.mp3tag.de/en/ Mp3tag] tagging program ([http://forums.mp3tag.de/index.php?showtopic=9730 post in the Mp3tag Forum])

	The analysis has been presented as an Excel spreadsheet (note that it contains two sheets).		The analysis has been presented as [http://lists.xiph.org/pipermail/vorbis-dev/attachments/20090716/e2db9203/attachment-0001.xls an Excel spreadsheet] (note that it contains two sheets).

	== Proposal ==		== Proposal ==

Martin.leese: /* Proposal */ Added one more

2009-07-16T14:48:17Z

Proposal: Added one more

← Older revision		Revision as of 14:48, 16 July 2009
Line 21:		Line 21:

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

Martin.leese: Tidy

2009-07-15T18:40:42Z

Tidy

← Older revision		Revision as of 18:40, 15 July 2009
Line 1:		Line 1:
	This page describes a proposed update to the minimal list of standard field names in the [http://xiph.org/vorbis/doc/v-comment.html Vorbis I specification]. Please keep discussion confined to [[Talk:Field names\|the Discussion page]] (or, better, the <vorbis-dev> mailing list).		This page describes a proposed update to the minimal list of 15 standard field names in the [http://xiph.org/vorbis/doc/v-comment.html Vorbis I specification]. Please keep discussion confined to [[Talk:Field names\|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.		After the proposal has been discussed, and accepted or rejected, this page should be deleted.

Martin.leese: /* Proposal */ Tidy

2009-07-15T18:36:53Z

Proposal: Tidy

← Older revision		Revision as of 18:36, 15 July 2009
Line 31:		Line 31:
	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 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~~. ~~This~~ is not ~~proposed~~ only because storing barcodes is thought to be esoteric.		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 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>.

Martin.leese: /* Proposal */ Tidy

2009-07-15T18:31:33Z

Proposal: Tidy

← Older revision		Revision as of 18:31, 15 July 2009
Line 29:		Line 29:
	# <code>METADATA_BLOCK_PICTURE</code> – see [[VorbisComment]] page		# <code>METADATA_BLOCK_PICTURE</code> – 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>.