draft-ietf-vcarddav-birth-death-extensions-02.txt   rfc6474.txt 
vcarddav K. Li Internet Engineering Task Force (IETF) K. Li
Internet-Draft B. Leiba Request for Comments: 6474 B. Leiba
Intended status: Standards Track Huawei Technologies Category: Standards Track Huawei Technologies
Expires: May 26, 2012 November 23, 2011 ISSN: 2070-1721 December 2011
vCard Format Extensions : place of birth, place and date of death vCard Format Extensions: Place of Birth, Place and Date of Death
draft-ietf-vcarddav-birth-death-extensions-02
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: place of birth, place of death, and date
date of death. of death.
Note
Discussion and suggestions for improvement are requested, and should
be sent to vcarddav@ietf.org.
Status of this Memo
This Internet-Draft is submitted in full conformance with the Status of This Memo
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on May 26, 2012. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6474.
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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
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 ....................................................2
1.1. Terminology Used in This Document . . . . . . . . . . . . . 3 1.1. Terminology Used in This Document ..........................2
2. Identification Property Extensions . . . . . . . . . . . . . . 3 2. Identification Property Extensions ..............................2
2.1. Property: BIRTHPLACE . . . . . . . . . . . . . . . . . . . 3 2.1. Property: BIRTHPLACE .......................................2
2.2. Property: DEATHPLACE . . . . . . . . . . . . . . . . . . . 4 2.2. Property: DEATHPLACE .......................................3
2.3. Property: DEATHDATE . . . . . . . . . . . . . . . . . . . . 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 ................................................5
6. Normative References . . . . . . . . . . . . . . . . . . . . . 6 6. Normative References ............................................5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
The base vCard 4.0 specification [RFC6350] defines a large number of The base vCard 4.0 specification [RFC6350] 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: place of birth, place of death, and date
date of death. of death.
1.1. Terminology Used in This Document 1.1. Terminology Used in This Document
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 [RFC6350]. vCard specification [RFC6350].
2. Identification Property Extensions 2. Identification Property Extensions
2.1. Property: BIRTHPLACE 2.1. Property: BIRTHPLACE
Namespace: Namespace:
Property name: BIRTHPLACE 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:
BIRTHPLACE-param = "VALUE=" ("text" / "uri")
BIRTHPLACE-value = text / uri
; Value type and VALUE parameter MUST match.
BIRTHPLACE-param =/ altid-param / language-param / any-param BIRTHPLACE-param = "VALUE=" ("text" / "uri")
BIRTHPLACE-value = text / uri
; Value type and VALUE parameter MUST match.
BIRTHPLACE-param =/ altid-param / language-param / any-param
Examples: Examples:
BIRTHPLACE:Babies'R'Us Hospital
BIRTHPLACE;VALUE=uri:http://example.com/hospitals/babiesrus.vcf BIRTHPLACE:Babies'R'Us Hospital
BIRTHPLACE;VALUE=uri:geo:46.769307,-71.283079 BIRTHPLACE;VALUE=uri:http://example.com/hospitals/babiesrus.vcf
BIRTHPLACE;VALUE=uri:geo:46.769307,-71.283079
2.2. Property: DEATHPLACE 2.2. Property: DEATHPLACE
Namespace: Namespace:
Property name: DEATHPLACE 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:
DEATHPLACE-param = "VALUE=" ("text" / "uri")
DEATHPLACE-value = text / uri
; Value type and VALUE parameter MUST match.
DEATHPLACE-param =/ altid-param / language-param / any-param DEATHPLACE-param = "VALUE=" ("text" / "uri")
DEATHPLACE-value = text / uri
; Value type and VALUE parameter MUST match.
DEATHPLACE-param =/ altid-param / language-param / any-param
Examples: Examples:
DEATHPLACE:Aboard the Titanic\, near Newfoundland
DEATHPLACE;VALUE=uri:http://example.com/ships/titanic.vcf DEATHPLACE:Aboard the Titanic\, near Newfoundland
DEATHPLACE;VALUE=uri:geo:41.731944,-49.945833 DEATHPLACE;VALUE=uri:http://example.com/ships/titanic.vcf
DEATHPLACE;VALUE=uri:geo:41.731944,-49.945833
2.3. Property: DEATHDATE 2.3. Property: DEATHDATE
Namespace: Namespace:
Property name: DEATHDATE 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
date-and-or-time value and actually contains a date or date-time. CALSCALE can only be present when the value is a
LANGUAGE can only be present when the value is text. date-and-or-time value and actually contains a date or date-time.
LANGUAGE can only be present when the value is text.
Description: The presence of a DEATHDATE property indicates that the Description: The presence of a DEATHDATE property indicates that the
subject of the vCard is known to be dead. The absence of this subject of the vCard is known to be dead. The absence
property makes no statement one way or the other. of this property makes no statement one way or the
other.
Format definition: Format definition:
DEATHDATE-param = DEATHDATE-param-date / DEATHDATE-param-text
DEATHDATE-value = date-and-or-time / text
; Value type and VALUE parameter MUST match.
DEATHDATE-param-date = "VALUE=date-and-or-time" / calscale-param DEATHDATE-param = DEATHDATE-param-date / DEATHDATE-param-text
; calscale-param can only be present when DEATHDATE-value is DEATHDATE-value = date-and-or-time / text
; date-and-or-time and actually contains a date or date-time. ; Value type and VALUE parameter MUST match.
DEATHDATE-param-date = "VALUE=text" / language-param DEATHDATE-param-date = "VALUE=date-and-or-time" / calscale-param
; calscale-param can only be present when DEATHDATE-value is
; date-and-or-time and actually contains a date or date-time.
DEATHDATE-param =/ altid-param / any-param DEATHDATE-param-date = "VALUE=text" / language-param
DEATHDATE-param =/ altid-param / any-param
Examples: Examples:
DEATHDATE:19960415
DEATHDATE:--0415 DEATHDATE:19960415
DEATHDATE;19531015T231000Z DEATHDATE:--0415
DEATHDATE;VALUE=text:circa 1800 DEATHDATE;19531015T231000Z
DEATHDATE;VALUE=text:circa 1800
3. Security Considerations 3. Security Considerations
This presents no security considerations beyond those in section 9 of The properties defined in this document present no security
the base vcard specification [RFC6350]. considerations beyond those in Section 9 of the base vCard
specification [RFC6350].
4. IANA Considerations 4. IANA Considerations
The IANA is requested to add the following entries to the vCard IANA has added the following entries to the vCard Properties
Properties registry, defined in [RFC6350] section 10.3.1. registry, defined in Section 10.3.1 of [RFC6350].
+-----------+--------------+------------------------+ +-----------+--------------+------------------------+
| Namespace | Property | Reference | | Namespace | Property | Reference |
+-----------+--------------+------------------------+ +-----------+--------------+------------------------+
| | BIRTHPLACE | RFCXXXX, section 2.1 | | | BIRTHPLACE | [RFC6474], Section 2.1 |
| | DEATHPLACE | RFCXXXX, section 2.2 | | | DEATHPLACE | [RFC6474], Section 2.2 |
| | DEATHDATE | RFCXXXX, section 2.3 | | | DEATHDATE | [RFC6474], Section 2.3 |
+-----------+--------------+------------------------+ +-----------+--------------+------------------------+
5. Acknowledgements 5. Acknowledgements
The authors of this draft would like thank the authors of The authors of this document would like to thank Simon Perreault and
draft-ietf-vcarddav-vcardrev-13, because much of the text is copied Pete Resnick, the authors of a draft version of RFC 6350 whence the
from there. properties defined herein originated.
6. Normative References 6. Normative References
[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., Ed., and P. Overell, "Augmented BNF for
Specifications: ABNF", STD 68, RFC 5234, January 2008. Syntax Specifications: ABNF", STD 68, RFC 5234,
January 2008.
[RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350,
August 2011. August 2011.
Authors' Addresses Authors' Addresses
Kepeng Li Kepeng Li
Huawei Technologies Huawei Technologies
Huawei Base, Bantian, Longgang District Huawei Base, Bantian, Longgang District
Shenzhen, Guangdong 518129 Shenzhen, Guangdong 518129
P. R. China P.R. China
Phone: +86-755-28974289 Phone: +86-755-28974289
Email: likepeng@huawei.com EMail: likepeng@huawei.com
Barry Leiba Barry Leiba
Huawei Technologies Huawei Technologies
Phone: +1 646 827 0648 Phone: +1 646 827 0648
Email: barryleiba@computer.org EMail: barryleiba@computer.org
URI: http://internetmessagingtechnology.org/ URI: http://internetmessagingtechnology.org/
 End of changes. 36 change blocks. 
91 lines changed or deleted 90 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/