vcarddav | K. Li |
Internet-Draft | B. Leiba |
Intended status: Standards Track | Huawei Technologies |
Expires: May 26, 2012 | November 23, 2011 |
vCard Format Extensions : place of birth, place and date of death
draft-ietf-vcarddav-birth-death-extensions-02
Abstract
The base vCard 4.0 specification defines a large number of properties, including date of birth. This specification adds three new properties to vCard 4.0, for place of birth, place of death, and date 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 provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering 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 and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 26, 2012.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
Table of Contents
- 1. Introduction
- 1.1. Terminology Used in This Document
- 2. Identification Property Extensions
- 2.1. Property: BIRTHPLACE
- 2.2. Property: DEATHPLACE
- 2.3. Property: DEATHDATE
- 3. Security Considerations
- 4. IANA Considerations
- 5. Acknowledgements
- 6. References
- Authors' Addresses
1. Introduction
The base vCard 4.0 specification [RFC6350] defines a large number of properties, including date of birth. This specification adds three new properties to vCard 4.0, for place of birth, place of death, and date of death.
1.1. Terminology Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
Syntax specifications shown here use the augmented Backus-Naur Form (ABNF) as described in [RFC5234], and are specified as in the base vcard specification [RFC6350].
2. Identification Property Extensions
2.1. Property: BIRTHPLACE
- Namespace:
-
- Property name:
- BIRTHPLACE
- Purpose:
- To specify the place of birth of the object the vCard represents.
- Value type:
- A single text value (default) or a single URI value.
- Cardinality:
- *1
- Property parameters:
- VALUE, LANGUAGE
- Description:
-
- 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
- Examples:
-
BIRTHPLACE:Babies'R'Us Hospital
BIRTHPLACE;VALUE=uri:http://example.com/hospitals/babiesrus.vcf
BIRTHPLACE;VALUE=uri:geo:46.769307,-71.283079
2.2. Property: DEATHPLACE
- Namespace:
-
- Property name:
- DEATHPLACE
- Purpose:
- To specify the place of death of the object the vCard represents.
- Value type:
- A single text value (default) or a single URI value.
- Cardinality:
- *1
- Property parameters:
- VALUE, LANGUAGE
- Description:
-
- 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
- Examples:
-
DEATHPLACE:Aboard the Titanic\, near Newfoundland
DEATHPLACE;VALUE=uri:http://example.com/ships/titanic.vcf
DEATHPLACE;VALUE=uri:geo:41.731944,-49.945833
2.3. Property: DEATHDATE
- Namespace:
-
- Property name:
- DEATHDATE
- Purpose:
- To specify the date of death of the object the vCard represents.
- Value type:
- The default is a single date-and-or-time value. It can also be reset to a single text value.
- Cardinality:
- *1
- 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.
LANGUAGE can only be present when the value is text.
- Description:
- The presence of a DEATHDATE property indicates that the subject of the vCard is known to be dead. The absence of this property makes no statement one way or the other.
- 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
; calscale-param can only be present when DEATHDATE-value is
; date-and-or-time and actually contains a date or date-time.
- DEATHDATE-param-date =
- "VALUE=text" / language-param
- DEATHDATE-param =/
- altid-param / any-param
- Examples:
-
DEATHDATE:19960415
DEATHDATE:--0415
DEATHDATE;19531015T231000Z
DEATHDATE;VALUE=text:circa 1800
3. Security Considerations
This presents no security considerations beyond those in section 9 of the base vcard specification [RFC6350].
4. IANA Considerations
The IANA is requested to add the following entries to the vCard Properties registry, defined in [RFC6350] section 10.3.1.
+-----------+--------------+------------------------+ | Namespace | Property | Reference | +-----------+--------------+------------------------+ | | BIRTHPLACE | RFCXXXX, section 2.1 | | | DEATHPLACE | RFCXXXX, section 2.2 | | | DEATHDATE | RFCXXXX, section 2.3 | +-----------+--------------+------------------------+
5. Acknowledgements
The authors of this draft would like thank the authors of draft-ietf-vcarddav-vcardrev-13, because much of the text is copied from there.
6. References
[RFC2119] | Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. |
[RFC5234] | Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008. |
[RFC6350] | Perreault, S., "vCard Format Specification", RFC 6350, August 2011. |