vcard-suggestions - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:34:49Z

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

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

	As a result of experience using [[hcard\|hCard]] to markup people, organizations, and contact information in general on [[hcard-examples-in-wild\|real world websites]], we have discovered a few aspects of {{RFC2426}} vCard that could be improved. Thus we are documenting suggestions for improving vCard here as we find them, organized by {{RFC2426}} properties, with a "new" section for new properties.		As a result of experience using [[hcard\|hCard]] to markup people, organizations, and contact information in general on [[hcard-examples-in-wild\|real world websites]], we have discovered a few aspects of {{RFC2426}} vCard that could be improved. Thus we are documenting suggestions for improving vCard here as we find them, organized by {{RFC2426}} properties, with a "new" section for new properties.

Tantek: vcard4

2010-11-29T21:22:21Z

vcard4

← Older revision		Revision as of 21:22, 29 November 2010
Line 201:		Line 201:

	However, see [[events/2007-09-18-calconnect-vcard-workshop]] for an event with vCard modification on the agenda. There may be some IETF work on vCard in the future.		However, see [[events/2007-09-18-calconnect-vcard-workshop]] for an event with vCard modification on the agenda. There may be some IETF work on vCard in the future.

			== 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-errata\|vCard errata]]		* [[vcard-errata\|vCard errata]]
	* [[vcard-implementations]]		* [[vcard-implementations]]
			* [[vCard4]]
	* [[hcard\|hCard]]		* [[hcard\|hCard]]
	* [[hcard-brainstorming#Post_vCard_additions]]		* [[hcard-brainstorming#Post_vCard_additions]]
	* [http://www.imc.org/imc-vcard/ vCard mailing list] - a place to raise these issues, and where similar issues can be found.
	* [[events/2007-09-18-calconnect-vcard-workshop]]		* [[events/2007-09-18-calconnect-vcard-workshop]]
	* <span id="3.3.3_Suggestion_for_Types_Definition"3>A [[hcard-issues#tel-type-lang\|comment on the language of TEL types]], moved because it was not vCard specific</span><!--span preserves former ID-->		* <span id="3.3.3_Suggestion_for_Types_Definition"3>A [[hcard-issues#tel-type-lang\|comment on the language of TEL types]], moved because it was not vCard specific</span><!--span preserves former ID-->

Tantek: entry-title, autotoc, BDAY heading

2009-09-01T17:38:40Z

entry-title, autotoc, BDAY heading

← Older revision		Revision as of 17:38, 1 September 2009
Line 1:		Line 1:
	<h1> vCard suggestions </h1>		<entry-title> vCard suggestions </entry-title>
	~~{{TOC-right}}~~
	As a result of experience using [[hcard\|hCard]] to markup people, organizations, and contact information in general on [[hcard-examples-in-wild\|real world websites]], we have discovered a few aspects of {{RFC2426}} vCard that could be improved. Thus we are documenting suggestions for improving vCard here as we find them, organized by {{RFC2426}} properties, with a "new" section for new properties.		As a result of experience using [[hcard\|hCard]] to markup people, organizations, and contact information in general on [[hcard-examples-in-wild\|real world websites]], we have discovered a few aspects of {{RFC2426}} vCard that could be improved. Thus we are documenting suggestions for improving vCard here as we find them, organized by {{RFC2426}} properties, with a "new" section for new properties.

Line 6:		Line 6:
	Suggestions for improvement could include new features and other such more major changes to the specification, organized under headings that reflect RFC 2426 vCard section numbers and heading. For documentation of errors, corrections, errata for vCard, please see [[vcard-errata]].		Suggestions for improvement could include new features and other such more major changes to the specification, organized under headings that reflect RFC 2426 vCard section numbers and heading. For documentation of errors, corrections, errata for vCard, please see [[vcard-errata]].

	=== BDAY ~~Type Definition~~ ===		=== BDAY ===
	:'''See: {{RFC2426}} section 3.1.5		:'''See: {{RFC2426}} section 3.1.5
	The definition for BDAY says: <blockquote><p>Type value: The default is a single date value. It can also be reset to a single date-time value.</p></blockquote>		The definition for BDAY says: <blockquote><p>Type value: The default is a single date value. It can also be reset to a single date-time value.</p></blockquote>

Tantek: /* Suggestions for Existing Properties */ BDAY should permit year only, or month and date only

2009-09-01T17:27:42Z

Suggestions for Existing Properties: BDAY should permit year only, or month and date only

@@ Line 5: / Line 5: @@
 == Suggestions for Existing Properties ==
 Suggestions for improvement could include new features and other such more major changes to the specification, organized under headings that reflect RFC 2426 vCard section numbers and heading. For documentation of errors, corrections, errata for vCard, please see [[vcard-errata]].
 === <span id="3.3.1_TEL_Type_Definition">TEL Type Definition</span> === <!--span preserves former ID-->

Singpolyma: /* Suggestions for New Properties */ X-JABBER

2009-06-21T01:04:08Z

Suggestions for New Properties: X-JABBER

← Older revision		Revision as of 01:04, 21 June 2009
Line 142:		Line 142:
	===DCreated===		===DCreated===
	The date and time that this vcard was created. If possible this should be mandatory even if left blank to encourage usage. This will allow tools to remove older vcard entries with old contact details for the same person.		The date and time that this vcard was created. If possible this should be mandatory even if left blank to encourage usage. This will allow tools to remove older vcard entries with old contact details for the same person.

			=== X-JABBER ===

			From http://en.wikipedia.org/wiki/VCard#vCard_extensions

	== Suggestions for handling encodings ==		== Suggestions for handling encodings ==

Tantek: rejected "Original source of information" - vCard already has URL and SOURCE which is sufficient for this.

2009-05-20T19:29:34Z

rejected "Original source of information" - vCard already has URL and SOURCE which is sufficient for this.

← Older revision		Revision as of 19:29, 20 May 2009
Line 125:		Line 125:

	:Per [[User:FajRo\|FajRo]]		:Per [[User:FajRo\|FajRo]]

	~~===Original source of information===~~
	* An URL to a website/contact page with hCard
	* A lot of business directories contains outdated contact information

	~~:Per [[User:Emerikusz\|Emerikusz]]~~

	===Preferred method of contact===		===Preferred method of contact===
Line 158:		Line 152:
	The date and time that this vCard was last modified. Allows synchronization tools to detect only those vCard in a collection which have changed since the last synchronization or backup.		The date and time that this vCard was last modified. Allows synchronization tools to detect only those vCard in a collection which have changed since the last synchronization or backup.
	* '''vCard already has a <code>REV</code> ("revised") property. Use it.'''		* '''vCard already has a <code>REV</code> ("revised") property. Use it.'''

			===Original source of information===
			A URL to a website/contact page with hCard (because a lot of business directories contains outdated contact information) - per [[User:Emerikusz\|Emerikusz]]
			* '''vCard already has a <code>URL</code> property. In addition, the SOURCE property in vCard can be used for this specific purpose (where did the vCard come from), and in fact, [[X2V]] already supports this in its vCard output!'''

	==Suggestions made elsewhere==		==Suggestions made elsewhere==

Emerikusz: /* Suggestions for New Properties */

2009-05-20T13:40:41Z

Suggestions for New Properties

← Older revision		Revision as of 13:40, 20 May 2009
Line 125:		Line 125:

	:Per [[User:FajRo\|FajRo]]		:Per [[User:FajRo\|FajRo]]

			===Original source of information===
			* An URL to a website/contact page with hCard
			* A lot of business directories contains outdated contact information

			:Per [[User:Emerikusz\|Emerikusz]]

	===Preferred method of contact===		===Preferred method of contact===

Tantek: /* Suggestions made elsewhere */ note new contact-formats page

2009-05-08T20:57:34Z

Suggestions made elsewhere: note new contact-formats page

← Older revision		Revision as of 20:57, 8 May 2009
Line 154:		Line 154:

	==Suggestions made elsewhere==		==Suggestions made elsewhere==
			See [[contact-formats]] for other contact formats.

			The following should be incorporated into the [[contact-formats]] page.
	* [http://openid.net/specs/openid-attribute-exchange-1_0.html OpenID page on Attribute Exchange] and [[attribute-exchange]].		* [http://openid.net/specs/openid-attribute-exchange-1_0.html OpenID page on Attribute Exchange] and [[attribute-exchange]].
	** Warning: many Attribute Exchange properties unnecessarily reinvent vCard properties.		** Warning: many Attribute Exchange properties unnecessarily reinvent vCard properties.

Brian: Reverted edits by ZelcoOuvil (Talk) to last version by Tantek

2008-12-20T22:21:36Z

Reverted edits by ZelcoOuvil (Talk) to last version by Tantek

← Older revision		Revision as of 22:21, 20 December 2008
Line 1:		Line 1:
	~~eltlac4tlila~~
	<h1> vCard suggestions </h1>		<h1> vCard suggestions </h1>
	{{TOC-right}}		{{TOC-right}}

ZelcoOuvil: zelvaro

2008-12-20T04:38:41Z

zelvaro

← Older revision		Revision as of 04:38, 20 December 2008
Line 1:		Line 1:
			eltlac4tlila
	<h1> vCard suggestions </h1>		<h1> vCard suggestions </h1>
	{{TOC-right}}		{{TOC-right}}