< draft-li-vcarddav-vcard-id-property-extensions-02.txt		draft-li-vcarddav-vcard-id-property-extensions-03.txt >
	vcarddav K. Li		vcarddav K. Li
	Internet-Draft B. Leiba		Internet-Draft B. Leiba
	Intended status: Standards Track Huawei Technologies		Intended status: Standards Track Huawei Technologies
	Expires: December 24, 2011 June 22, 2011		Expires: January 6, 2012 July 5, 2011
	vCard Format Extensions : place of birth, place and date of death		vCard Format Extensions : place of birth, place and date of death
	draft-li-vcarddav-vcard-id-property-extensions-02		draft-li-vcarddav-vcard-id-property-extensions-03
	Abstract		Abstract
	The base vCard 4.0 specification defines a large number of		The base vCard 4.0 specification defines a large number of
	properties, including date of birth. This specification adds three		properties, including date of birth. This specification adds three
	new properties to vCard 4.0, for place of birth, place of death, and		new properties to vCard 4.0, for place of birth, place of death, and
	date of death.		date of death.
	Note		Note
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on December 24, 2011.		This Internet-Draft will expire on January 6, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 IETF Trust and the persons identified as the		Copyright (c) 2011 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 2, line 14 ¶		skipping to change at page 2, line 14 ¶
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Terminology Used in This Document . . . . . . . . . . . . . 3		1.1. Terminology Used in This Document . . . . . . . . . . . . . 3
	2. Identification Property Extensions . . . . . . . . . . . . . . 3		2. Identification Property Extensions . . . . . . . . . . . . . . 3
	2.1. Property: BIRTH . . . . . . . . . . . . . . . . . . . . . . 3		2.1. Property: BIRTHPLACE . . . . . . . . . . . . . . . . . . . 3
	2.2. Property: DEATH . . . . . . . . . . . . . . . . . . . . . . 4		2.2. Property: DEATHPLACE . . . . . . . . . . . . . . . . . . . 4
	2.3. Property: DDAY . . . . . . . . . . . . . . . . . . . . . . 4		2.3. Property: DEATHDATE . . . . . . . . . . . . . . . . . . . . 4
	3. Security Considerations . . . . . . . . . . . . . . . . . . . . 5		3. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
	5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6		5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
	6. Normative References . . . . . . . . . . . . . . . . . . . . . 6		6. Normative References . . . . . . . . . . . . . . . . . . . . . 6
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
	1. Introduction		1. Introduction
	The base vCard 4.0 specification [I-D.ietf-vcarddav-vcardrev] defines		The base vCard 4.0 specification [I-D.ietf-vcarddav-vcardrev] defines
	a large number of properties, including date of birth. This		a large number of properties, including date of birth. This
	skipping to change at page 3, line 24 ¶		skipping to change at page 3, line 24 ¶
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119].		document are to be interpreted as described in [RFC2119].
	Syntax specifications shown here use the augmented Backus-Naur Form		Syntax specifications shown here use the augmented Backus-Naur Form
	(ABNF) as described in [RFC5234], and are specified as in the base		(ABNF) as described in [RFC5234], and are specified as in the base
	vcard specification [I-D.ietf-vcarddav-vcardrev].		vcard specification [I-D.ietf-vcarddav-vcardrev].
	2. Identification Property Extensions		2. Identification Property Extensions
	2.1. Property: BIRTH		2.1. Property: BIRTHPLACE
	Namespace:		Namespace:
	Property name: BIRTH		Property name: BIRTHPLACE
	Purpose: To specify the place of birth of the object the vCard		Purpose: To specify the place of birth of the object the vCard
	represents.		represents.
	Value type: A single text value (default) or a single URI value.		Value type: A single text value (default) or a single URI value.
	Cardinality: *1		Cardinality: *1
	Property parameters: VALUE, LANGUAGE		Property parameters: VALUE, LANGUAGE
	Description:		Description:
	Format definition:		Format definition:
	BIRTH-param = "VALUE=" / ("text" / "uri")		BIRTHPLACE-param = "VALUE=" / ("text" / "uri")
	BIRTH-value = text / uri		BIRTHPLACE-value = text / uri
	; Value and parameter MUST match.		; Value and parameter MUST match.
	BIRTH-param =/ altid-param / language-param / any-param		BIRTHPLACE-param =/ altid-param / language-param / any-param
	Examples:		Examples:
	BIRTH:Babies'R'Us Hospital		BIRTHPLACE:Babies'R'Us Hospital
	BIRTH;VALUE=uri:http://example.com/hospitals/babiesrus.vcf		BIRTHPLACE;VALUE=uri:http://example.com/hospitals/babiesrus.vcf
	BIRTH;VALUE=uri:geo:46.769307,-71.283079		BIRTHPLACE;VALUE=uri:geo:46.769307,-71.283079
	2.2. Property: DEATH		2.2. Property: DEATHPLACE
	Namespace:		Namespace:
	Property name: DEATH		Property name: DEATHPLACE
	Purpose: To specify the place of death of the object the vCard		Purpose: To specify the place of death of the object the vCard
	represents.		represents.
	Value type: A single text value (default) or a single URI value.		Value type: A single text value (default) or a single URI value.
	Cardinality: *1		Cardinality: *1
	Property parameters: VALUE, LANGUAGE		Property parameters: VALUE, LANGUAGE
	Description:		Description:
	Format definition:		Format definition:
	DEATH-param = "VALUE=" / ("text" / "uri")		DEATHPLACE-param = "VALUE=" / ("text" / "uri")
	DEATH-value = text / uri		DEATHPLACE-value = text / uri
	; Value and parameter MUST match.		; Value and parameter MUST match.
	DEATH-param =/ altid-param / language-param / any-param		DEATHPLACE-param =/ altid-param / language-param / any-param
	Examples:		Examples:
	DEATH:Aboard the Titanic\, near Newfoundland		DEATHPLACE:Aboard the Titanic\, near Newfoundland
	DEATH;VALUE=uri:http://example.com/ships/titanic.vcf		DEATHPLACE;VALUE=uri:http://example.com/ships/titanic.vcf
	DEATH;VALUE=uri:41.731944,-49.945833		DEATHPLACE;VALUE=uri:41.731944,-49.945833
	2.3. Property: DDAY		2.3. Property: DEATHDATE
	Namespace:		Namespace:
	Property name: DDAY		Property name: DEATHDATE
	Purpose: To specify the date of death of the object the vCard		Purpose: To specify the date of death of the object the vCard
	represents.		represents.
	Value type: The default is a single date-and-or-time value. It can		Value type: The default is a single date-and-or-time value. It can
	also be reset to a single text value.		also be reset to a single text value.
	Cardinality: *1		Cardinality: *1
	Property parameters: VALUE, CALSCALE, LANGUAGE		Property parameters: VALUE, CALSCALE, LANGUAGE
	CALSCALE can only be present when the value is a		CALSCALE can only be present when the value is a
	date-and-or-time value and actually contains a date or date-time.		date-and-or-time value and actually contains a date or date-time.
	LANGUAGE can only be present when the value is text.		LANGUAGE can only be present when the value is text.
	Description:		Description:
	Format definition:		Format definition:
	DDAY-param = DDAY-param-date / DDAY-param-text		DEATHDATE-param = DEATHDATE-param-date / DEATHDATE-param-text
	DDAY-value = date-and-or-time / text		DEATHDATE-value = date-and-or-time / text
	; Value and parameter MUST match.		; Value and parameter MUST match.
	DDAY-param-date = "VALUE=date-and-or-time"		DEATHDATE-param-date = "VALUE=date-and-or-time"
	DDAY-param-text = "VALUE=text" / language-param		DEATHDATE-param-text = "VALUE=text" / language-param
	DDAY-param =/ altid-param / calscale-param / any-param		DEATHDATE-param =/ altid-param / calscale-param / any-param
	; calscale-param can only be present when DDAY-value is		; calscale-param can only be present when DEATHDATE-value is
	; date-and-or-time and actually contains a date or date-time.		; date-and-or-time and actually contains a date or date-time.
	Examples:		Examples:
	DDAY:19960415		DEATHDATE:19960415
	DDAY:--0415		DEATHDATE:--0415
	DDAY;19531015T231000Z		DEATHDATE;19531015T231000Z
	DDAY;VALUE=text:circa 1800		DEATHDATE;VALUE=text:circa 1800
	3. Security Considerations		3. Security Considerations
	This presents no security considerations beyond those in section 9 of		This presents no security considerations beyond those in section 9 of
	the base vcard specification [I-D.ietf-vcarddav-vcardrev].		the base vcard specification [I-D.ietf-vcarddav-vcardrev].
	4. IANA Considerations		4. IANA Considerations
	The IANA is requested to add the following entries to the vCard		The IANA is requested to add the following entries to the vCard
	Properties registry, defined in [I-D.ietf-vcarddav-vcardrev] section		Properties registry, defined in [I-D.ietf-vcarddav-vcardrev] section
	10.3.1.		10.3.1.
	+-----------+--------------+---------+------------------------+		+-----------+--------------+---------+------------------------+
	| Namespace | Property | Status | Reference |		| Namespace | Property | Status | Reference |
	+-----------+--------------+---------+------------------------+		+-----------+--------------+---------+------------------------+
	| | BIRTH | Current | RFCXXXX, section 2.1 |		| | BIRTHPLACE | Current | RFCXXXX, section 2.1 |
	| | DEATH | Current | RFCXXXX, section 2.2 |		| | DEATHPLACE | Current | RFCXXXX, section 2.2 |
	| | DDAY | Current | RFCXXXX, section 2.3 |		| | DEATHDATE | Current | RFCXXXX, section 2.3 |
	+-----------+--------------+---------+------------------------+		+-----------+--------------+---------+------------------------+
	5. Acknowledgements		5. Acknowledgements
	The author of this draft would like thank the authors of		The author of this draft would like thank the authors of
	draft-ietf-vcarddav-vcardrev-13, because much of the text is copied		draft-ietf-vcarddav-vcardrev-13, because much of the text is copied
	from there.		from there.
	6. Normative References		6. Normative References
	[I-D.ietf-vcarddav-vcardrev]		[I-D.ietf-vcarddav-vcardrev]
	Perreault, S. and P. Resnick, "vCard Format		Perreault, S., "vCard Format Specification",
	Specification", draft-ietf-vcarddav-vcardrev-15 (work in		draft-ietf-vcarddav-vcardrev-22 (work in progress),
	progress), December 2010.		May 2011.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax		[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
	Specifications: ABNF", STD 68, RFC 5234, January 2008.		Specifications: ABNF", STD 68, RFC 5234, January 2008.
	Authors' Addresses		Authors' Addresses
	Kepeng Li		Kepeng Li
End of changes. 22 change blocks.
	40 lines changed or deleted		40 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/