TOC 
vcarddavK. Li
Internet-DraftB. Leiba
Intended status: Standards TrackHuawei Technologies
Expires: July 10, 2011January 6, 2011


vCard Format Extensions : date of death; places of birth and death
draft-li-vcarddav-vcard-id-property-extensions-01

Abstract

This document defines an extension to the vCard data format for representing and exchanging information about the date of death, the place of birth, and the place of death of the object the vCard represents.

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 July 10, 2011.

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: DEATHDAY
    2.2.  Property: BIRTHPLACE
    2.3.  Property: DEATHPLACE
3.  Security Considerations
4.  IANA Considerations
5.  Acknowledgements
6.  Normative References
§  Authors' Addresses




 TOC 

1.  Introduction

This specification adds three new properties to vCard 4.0, to specify the date of death, the place of birth, and the place of death of the object the vCard represents.



 TOC 

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] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.).

Syntax specifications shown here use the augmented Backus-Naur Form (ABNF) as described in [RFC5234] (Crocker, D. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF,” January 2008.), and are specified as in the base vcard specification [I‑D.ietf‑vcarddav‑vcardrev] (Perreault, S. and P. Resnick, “vCard Format Specification,” December 2010.).



 TOC 

2.  Identification Property Extensions



 TOC 

2.1.  Property: DEATHDAY

Namespace:

Property name:
DEATHDAY
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 b present when the value is text.

Description:

Format definition:
DEATHDAY-param =
DEATHDAY-param-date / DEATHDAY-param-text
DEATHDAY-value =
date-and-or-time / text
; Value and parameter MUST match.
DEATHDAY-param-date =
"VALUE=date-and-or-time"
DEATHDAY-param-text =
"VALUE=text" / language-param
DEATHDAY-param =/
altid-param / calscale-param / any-param ; calscale-param can only be present when DEATHDAY-value is
; date-and-or-time and actually contains a date or date-time.


Examples:
DEATHDAY:19960415
DEATHDAY:--0415
DEATHDAY;19531015T231000Z
DEATHDAY;VALUE=text:circa 1800



 TOC 

2.2.  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 and 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



 TOC 

2.3.  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 and 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:41.731944,-49.945833



 TOC 

3.  Security Considerations

This presents no security considerations beyond those in section 9 of the base vcard specification [I‑D.ietf‑vcarddav‑vcardrev] (Perreault, S. and P. Resnick, “vCard Format Specification,” December 2010.).



 TOC 

4.  IANA Considerations

The IANA is requested to add the following entries to the vCard Properties registry, defined in [I‑D.ietf‑vcarddav‑vcardrev] (Perreault, S. and P. Resnick, “vCard Format Specification,” December 2010.) section 10.3.1.

      +-----------+--------------+---------+------------------------+
      | Namespace | Property     | Status  | Reference              |
      +-----------+--------------+---------+------------------------+
      |           | DEATHDAY     | Current | RFCXXXX, section 2.1   |
      |           | BIRTHPLACE   | Current | RFCXXXX, section 2.2   |
      |           | DEATHPLACE   | Current | RFCXXXX, section 2.3   |
      +-----------+--------------+---------+------------------------+


 TOC 

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. Also thanks Simon for the review and suggestion.



 TOC 

6. Normative References

[I-D.ietf-vcarddav-vcardrev] Perreault, S. and P. Resnick, “vCard Format Specification,” draft-ietf-vcarddav-vcardrev-15 (work in progress), December 2010 (TXT).
[RFC2119] Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” BCP 14, RFC 2119, March 1997 (TXT, HTML, XML).
[RFC5234] Crocker, D. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF,” STD 68, RFC 5234, January 2008 (TXT).


 TOC 

Authors' Addresses

  Kepeng Li
  Huawei Technologies
  Huawei Base, Bantian, Longgang District
  Shenzhen, Guangdong 518129
  P. R. China
Phone:  +86-755-28974289
Email:  likepeng@huawei.com
  
  Barry Leiba
  Huawei Technologies
Phone:  +1 646 827 0648
Email:  barryleiba@computer.org
URI:  http://internetmessagingtechnology.org/