TOC 
vcarddavK. Li
Internet-DraftB. Leiba
Intended status: Standards TrackHuawei Technologies
Expires: July 3, 2011December 30, 2010


vCard Format Extensions : DDAY, BIRTH, and DEATH
draft-li-vcarddav-vcard-id-property-extensions-00

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 3, 2011.

Copyright Notice

Copyright (c) 2010 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
2.  Terminology Used in This Document
3.  Identification Property Extensions
    3.1.  Property: DDAY
    3.2.  Property: BIRTH
    3.3.  Property: DEATH
4.  Security Considerations
5.  IANA Considerations
    5.1.  Registration of 'DDAY' property
    5.2.  Registration of 'BIRTH' property
    5.3.  Registration of 'DEATH' property
6.  Acknowledgements
7.  Normative References
§  Authors' Addresses




 TOC 

1.  Introduction

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



 TOC 

2.  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 

3.  Identification Property Extensions



 TOC 

3.1.  Property: DDAY

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
ABNF:
DDAY-param =
DDAY-param-date / DDAY-param-text
DDAY-value =
date-and-or-time / text
; Value and parameter MUST match.
DDAY-param-date =
"VALUE=date-and-or-time"
DDAY-param-text =
"VALUE=text" / language-param
DDAY-param =/
altid-param / calscale-param / any-param ; calscale-param can only be present when DDAY-value is
; date-and-or-time and actually contains a date or date-time.


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



 TOC 

3.2.  Property: BIRTH

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
ABNF:
BIRTH-param =
"VALUE=" / ("text" / "uri")
BIRTH-value =
text / uri
; Value and parameter MUST match.
BIRTH-param =/
altid-param / language-param / any-param


Examples:
BIRTH:Babies'R'Us Hospital
BIRTH;VALUE=uri:http://example.com/hospitals/babiesrus.vcf
BIRTH;VALUE=uri:geo:46.769307,-71.283079



 TOC 

3.3.  Property: DEATH

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
ABNF:
DEATH-param =
"VALUE=" / ("text" / "uri")
DEATH-value =
text / uri
; Value and parameter MUST match.
DEATH-param =/
altid-param / language-param / any-param


Examples:
DEATH:Aboard the Titanic\, near Newfoundland
DEATH;VALUE=uri:http://example.com/ships/titanic.vcf
DEATH;VALUE=uri:41.731944,-49.945833



 TOC 

4.  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 

5.  IANA Considerations

Registrations are requested for the three properties (DDAY, BIRTH, DEATH), according to the instructions in section 10.2.3 of the base vcard specification [I‑D.ietf‑vcarddav‑vcardrev] (Perreault, S. and P. Resnick, “vCard Format Specification,” December 2010.).



 TOC 

5.1.  Registration of 'DDAY' property

Namespace:

Property name:
DDAY
Purpose:
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:
DDAY-param =
DDAY-param-date / DDAY-param-text
DDAY-value =
date-and-or-time / text
; Value and parameter MUST match.
DDAY-param-date =
"VALUE=date-and-or-time"
DDAY-param-text =
"VALUE=text" / language-param
DDAY-param =/
altid-param / calscale-param / any-param ; calscale-param can only be present when DDAY-value is
; date-and-or-time and actually contains a date or date-time.


Example(s):
DDAY:19960415
DDAY:--0415
DDAY;19531015T231000Z
DDAY;VALUE=text:circa 1800



 TOC 

5.2.  Registration of 'BIRTH' property

Namespace:

Property name:
BIRTH
Purpose:
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:
BIRTH-param =
"VALUE=" / ("text" / "uri")
BIRTH-value =
text / uri
; Value and parameter MUST match.
BIRTH-param =/
altid-param / language-param / any-param


Example(s):
BIRTH:Babies'R'Us Hospital
BIRTH;VALUE=uri:http://example.com/hospitals/babiesrus.vcf
BIRTH;VALUE=uri:geo:46.769307,-71.283079



 TOC 

5.3.  Registration of 'DEATH' property

Namespace:

Property name:
DEATH
Purpose:
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:
DEATH-param =
"VALUE=" / ("text" / "uri")
DEATH-value =
text / uri
; Value and parameter MUST match.
DEATH-param =/
altid-param / language-param / any-param


Example(s):
DEATH:Aboard the Titanic\, near Newfoundland
DEATH;VALUE=uri:http://example.com/ships/titanic.vcf
DEATH;VALUE=uri:41.731944,-49.945833



 TOC 

6.  Acknowledgements

The author of this draft would like thank the authors of draft-ietf-vcarddav-vcardrev-13, because most of the texts are copied from there.



 TOC 

7. 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/