vcard-errata - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:34:48Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:34, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~ vCard errata ~~</entry-title>~~		{{DISPLAYTITLE: vCard errata }}

	In the development of [[hcard\|hCard]] and proxies like X2V, we have discovered various details of [[RFC2426]] vCard that appear to be mistakes. Thus we are documenting them here as we find them, organized by [[RFC2426]] section number.		In the development of [[hcard\|hCard]] and proxies like X2V, we have discovered various details of [[RFC2426]] vCard that appear to be mistakes. Thus we are documenting them here as we find them, organized by [[RFC2426]] section number.

Tantek: vcard4

2010-11-29T21:21:31Z

vcard4

← Older revision		Revision as of 21:21, 29 November 2010
Line 74:		Line 74:
	# delete the above quoted bullet item from section 5.		# delete the above quoted bullet item from section 5.
	# make the change to section 2.2 as noted above.		# make the change to section 2.2 as noted above.

			== external resources ==
			* [http://www.imc.org/imc-vcard/ vCard mailing list] - a place to raise these issues, and where similar issues can be found.

	== See Also ==		== See Also ==
	* [[vcard-suggestions]]		* [[vcard-suggestions]]
	* [[vcard-implementations]]		* [[vcard-implementations]]
			* [[vCard4]]
	* [[hcard\|hCard]]		* [[hcard\|hCard]]
	* [http://www.imc.org/imc-vcard/ vCard mailing list] - a place to raise these issues, and where similar issues can be found.

Tantek: entry-title

2010-11-29T21:19:12Z

entry-title

← Older revision		Revision as of 21:19, 29 November 2010
Line 1:		Line 1:
	<h1> vCard errata </h1>		<entry-title> vCard errata </entry-title>

	In the development of [[hcard\|hCard]] and proxies like X2V, we have discovered various details of [[RFC2426]] vCard that appear to be mistakes. Thus we are documenting them here as we find them, organized by [[RFC2426]] section number.		In the development of [[hcard\|hCard]] and proxies like X2V, we have discovered various details of [[RFC2426]] vCard that appear to be mistakes. Thus we are documenting them here as we find them, organized by [[RFC2426]] section number.

Brian: Reverted edits by ZelmoNdomo (Talk) to last version by PeterSheerin

2009-01-03T19:38:04Z

Reverted edits by ZelmoNdomo (Talk) to last version by PeterSheerin

← Older revision		Revision as of 19:38, 3 January 2009
Line 1:		Line 1:
	~~alchip~~
	<h1> vCard errata </h1>		<h1> vCard errata </h1>

	In the development of [[hcard\|hCard]] and proxies like X2V, we have discovered various details of [[RFC2426]] vCard that appear to be mistakes. Thus we are documenting them here as we find them, organized by [[RFC2426]] section number.		In the development of [[hcard\|hCard]] and proxies like X2V, we have discovered various details of [[RFC2426]] vCard that appear to be mistakes. Thus we are documenting them here as we find them, organized by [[RFC2426]] section number.

	; Editor: Tantek ~~Ãelik~~		; Editor: Tantek Çelik

	== Errata ==		== Errata ==
Line 10:		Line 9:
	=== 2.2 Predefined Type Parameter Usage ===		=== 2.2 Predefined Type Parameter Usage ===

	# 2005-11-24 by [http://tantek.com/ Tantek ~~Ãelik~~]		# 2005-11-24 by [http://tantek.com/ Tantek Çelik]

	Just after this block:		Just after this block:
Line 34:		Line 33:
	=== 3.6.7 UID Type Definition ===		=== 3.6.7 UID Type Definition ===

	# 2007-09-08 by [http://tantek.com/ Tantek ~~Ãelik~~] based on [http://microformats.org/wiki?title=uid&diff=21212&oldid=21211 issue raised by Andy Mabbett 11:10, 7 Sep 2007].		# 2007-09-08 by [http://tantek.com/ Tantek Çelik] based on [http://microformats.org/wiki?title=uid&diff=21212&oldid=21211 issue raised by Andy Mabbett 11:10, 7 Sep 2007].

	[[RFC2426]] says [note inserted text for clarification].		[[RFC2426]] says [note inserted text for clarification].
Line 57:		Line 56:
	=== 5. Differences From vCard v2.1 ===		=== 5. Differences From vCard v2.1 ===

	# 2005-11-24 by [http://tantek.com/ Tantek ~~Ãelik~~]		# 2005-11-24 by [http://tantek.com/ Tantek Çelik]

	[[RFC2426]] says:		[[RFC2426]] says:

ZelmoNdomo: aceldro

2009-01-03T17:14:45Z

aceldro

← Older revision		Revision as of 17:14, 3 January 2009
Line 1:		Line 1:
			alchip
	<h1> vCard errata </h1>		<h1> vCard errata </h1>

	In the development of [[hcard\|hCard]] and proxies like X2V, we have discovered various details of [[RFC2426]] vCard that appear to be mistakes. Thus we are documenting them here as we find them, organized by [[RFC2426]] section number.		In the development of [[hcard\|hCard]] and proxies like X2V, we have discovered various details of [[RFC2426]] vCard that appear to be mistakes. Thus we are documenting them here as we find them, organized by [[RFC2426]] section number.

	; Editor: Tantek ~~Çelik~~		; Editor: Tantek Ãelik

	== Errata ==		== Errata ==
Line 9:		Line 10:
	=== 2.2 Predefined Type Parameter Usage ===		=== 2.2 Predefined Type Parameter Usage ===

	# 2005-11-24 by [http://tantek.com/ Tantek ~~Çelik~~]		# 2005-11-24 by [http://tantek.com/ Tantek Ãelik]

	Just after this block:		Just after this block:
Line 33:		Line 34:
	=== 3.6.7 UID Type Definition ===		=== 3.6.7 UID Type Definition ===

	# 2007-09-08 by [http://tantek.com/ Tantek ~~Çelik~~] based on [http://microformats.org/wiki?title=uid&diff=21212&oldid=21211 issue raised by Andy Mabbett 11:10, 7 Sep 2007].		# 2007-09-08 by [http://tantek.com/ Tantek Ãelik] based on [http://microformats.org/wiki?title=uid&diff=21212&oldid=21211 issue raised by Andy Mabbett 11:10, 7 Sep 2007].

	[[RFC2426]] says [note inserted text for clarification].		[[RFC2426]] says [note inserted text for clarification].
Line 56:		Line 57:
	=== 5. Differences From vCard v2.1 ===		=== 5. Differences From vCard v2.1 ===

	# 2005-11-24 by [http://tantek.com/ Tantek ~~Çelik~~]		# 2005-11-24 by [http://tantek.com/ Tantek Ãelik]

	[[RFC2426]] says:		[[RFC2426]] says:

PeterSheerin: /* 3.6.7 UID Type Definition */ UUID

2008-01-15T00:22:53Z

3.6.7 UID Type Definition: UUID

← Older revision		Revision as of 00:22, 15 January 2008
Line 50:		Line 50:
	of the identifier. The value can be a non-standard format.		of the identifier. The value can be a non-standard format.
	</nowiki></pre>		</nowiki></pre>

			# 2008-01-14 by [http://PetesGuide.com/ Peter Sheerin]
			I too have failed to find any reference to "registered itentifier format", and believe that sentence was intended to indicate that any IANA (MIME type) type of identifier, whereas most of the types referenced in the RFC are confined to one branch (image for photo and logo, audio for sound, etc.). However, I can find no obvious IANA MIME type appropriate for a UID. There is an RFC for a UUID, however. RFC 4122 describes the procedure for generating a globally unique 128-bit UID, using time, MAC address, and a few other things. Perhaps vCard should reference this?

	=== 5. Differences From vCard v2.1 ===		=== 5. Differences From vCard v2.1 ===

Tantek at 01:25, 9 September 2007

2007-09-09T01:25:22Z

← Older revision		Revision as of 01:25, 9 September 2007
Line 44:		Line 44:
	</nowiki></pre>		</nowiki></pre>

	Note that a search of the IANA website as of 11:10, 7 Sep 2007 finds no occurrences of "identifier format", therefore there is no way to comply with the "should" sentence in the above-quoted portion of section 3.6.7. Since the statement is only a "should", thus content {{may}} ignore it, and there is no way to comply with the "should", it the simplest errata is to drop the impossible "should" statement, and remove the word "also" from the following sentence, as follows:		Note that a search of the IANA website as of 11:10, 7 Sep 2007 finds no occurrences of "identifier format", therefore there is no way to comply with the "should" sentence in the above-quoted portion of section 3.6.7. Since the statement is only a "should", thus content {{may}} ignore it, and there is no way to comply with the "should", the simplest errata is to drop the impossible "should" statement, and remove the word "also" from the following sentence, as follows:

	<pre><nowiki>		<pre><nowiki>

Tantek at 01:22, 9 September 2007

2007-09-09T01:22:44Z

← Older revision		Revision as of 01:22, 9 September 2007
Line 1:		Line 1:
	<h1> vCard errata </h1>		<h1> vCard errata </h1>

	In the development of [[hcard\|hCard]] and proxies like X2V, we have discovered various details of ~~RFC 2426~~ vCard that appear to be mistakes. Thus we are documenting them here as we find them, organized by ~~RFC 2426~~ section number.		In the development of [[hcard\|hCard]] and proxies like X2V, we have discovered various details of [[RFC2426]] vCard that appear to be mistakes. Thus we are documenting them here as we find them, organized by [[RFC2426]] section number.

	; Editor: Tantek Çelik		; Editor: Tantek Çelik

Tantek: 3.6.7 UID Type Definition - no IANA registered identifier formats found

2007-09-09T00:52:37Z

3.6.7 UID Type Definition - no IANA registered identifier formats found

← Older revision		Revision as of 00:52, 9 September 2007
Line 3:		Line 3:
	In the development of [[hcard\|hCard]] and proxies like X2V, we have discovered various details of RFC 2426 vCard that appear to be mistakes. Thus we are documenting them here as we find them, organized by RFC 2426 section number.		In the development of [[hcard\|hCard]] and proxies like X2V, we have discovered various details of RFC 2426 vCard that appear to be mistakes. Thus we are documenting them here as we find them, organized by RFC 2426 section number.

	; ~~Author(s)~~: Tantek Çelik		; Editor: Tantek Çelik

	== Errata ==		== Errata ==
Line 9:		Line 9:
	=== 2.2 Predefined Type Parameter Usage ===		=== 2.2 Predefined Type Parameter Usage ===

	# 2005-11-24 by [http://tantek.com~~/log~~/ Tantek Çelik]		# 2005-11-24 by [http://tantek.com/ Tantek Çelik]

	Just after this block:		Just after this block:
Line 30:		Line 30:
	</nowiki></pre>		</nowiki></pre>


			=== 3.6.7 UID Type Definition ===

			# 2007-09-08 by [http://tantek.com/ Tantek Çelik] based on [http://microformats.org/wiki?title=uid&diff=21212&oldid=21211 issue raised by Andy Mabbett 11:10, 7 Sep 2007].

			[[RFC2426]] says [note inserted text for clarification].

			<pre><nowiki>
			The [UID] type can include the type parameter "TYPE" to specify the format
			of the identifier. The TYPE parameter value should be an IANA
			registered identifier format. The value can also be a non-standard
			format.
			</nowiki></pre>

			Note that a search of the IANA website as of 11:10, 7 Sep 2007 finds no occurrences of "identifier format", therefore there is no way to comply with the "should" sentence in the above-quoted portion of section 3.6.7. Since the statement is only a "should", thus content {{may}} ignore it, and there is no way to comply with the "should", it the simplest errata is to drop the impossible "should" statement, and remove the word "also" from the following sentence, as follows:

			<pre><nowiki>
			The [UID] type can include the type parameter "TYPE" to specify the format
			of the identifier. The value can be a non-standard format.
			</nowiki></pre>

	=== 5. Differences From vCard v2.1 ===		=== 5. Differences From vCard v2.1 ===

	# 2005-11-24 by [http://tantek.com~~/log~~/ Tantek Çelik]		# 2005-11-24 by [http://tantek.com/ Tantek Çelik]

	~~RFC 2426~~ says:		[[RFC2426]] says:

	<pre><nowiki>		<pre><nowiki>
Line 43:		Line 63:
	</nowiki></pre>		</nowiki></pre>

	We believe this to have been a mistake, note in particular that section 1. of ~~RFC 2426~~ explicitly states that the CHARSET parameter is one of the "Predefined MIME Directory parameters" that is "used". We believe that statement in section 1. of ~~RFC 2426~~ to be '''correct'''.		We believe this to have been a mistake, note in particular that section 1. of [[RFC2426]] explicitly states that the CHARSET parameter is one of the "Predefined MIME Directory parameters" that is "used". We believe that statement in section 1. of [[RFC2426]] to be '''correct'''.

	The most obvious proof of why this is needed is when a vCard .vcf file is stored on and retrieved from a local file-system, you obviously cannot depend on the Content-Type MIME (or HTTP) header field, nor can you assume that the operating system will keep character set metadata about the file in some other location.		The most obvious proof of why this is needed is when a vCard .vcf file is stored on and retrieved from a local file-system, you obviously cannot depend on the Content-Type MIME (or HTTP) header field, nor can you assume that the operating system will keep character set metadata about the file in some other location.

Tantek: add vcard-implementations link

2007-08-03T18:43:05Z

add vcard-implementations link

← Older revision		Revision as of 18:43, 3 August 2007
Line 53:		Line 53:

	== See Also ==		== See Also ==

	* [[vcard-suggestions]]		* [[vcard-suggestions]]
			* [[vcard-implementations]]
	* [[hcard\|hCard]]		* [[hcard\|hCard]]
	* [http://www.imc.org/imc-vcard/ vCard mailing list] - a place to raise these issues, and where similar issues can be found.		* [http://www.imc.org/imc-vcard/ vCard mailing list] - a place to raise these issues, and where similar issues can be found.