Internet Engineering Task Force (IETF) S. Perreault
Request for Comments: 6350 Viagenie
Obsoletes: 2425, 2426, 4770 August 2011
Updates: 2739
Category: Standards Track
ISSN: 2070-1721
Internet Engineering Task Force (IETF) S. Perreault
Request for Comments: 6350 Viagenie
Obsoletes: 2425, 2426, 4770 August 2011
Updates: 2739
Category: Standards Track
ISSN: 2070-1721
vCard Format Specification
vCard格式规范
Abstract
摘要
This document defines the vCard data format for representing and exchanging a variety of information about individuals and other entities (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.). This document obsoletes RFCs 2425, 2426, and 4770, and updates RFC 2739.
本文件定义了vCard数据格式，用于表示和交换有关个人和其他实体的各种信息（例如，格式化和结构化的名称和交付地址、电子邮件地址、多个电话号码、照片、徽标、音频剪辑等）。本文件淘汰了RFC 2425、2426和4770，并更新了RFC 2739。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
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/rfc6350.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6350.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 IETF信托基金和确定为文件作者的人员。版权所有。
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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
本文件可能包含2008年11月10日之前发布或公开的IETF文件或IETF贡献中的材料。控制某些材料版权的人员可能未授予IETF信托允许在IETF标准流程之外修改此类材料的权利。在未从控制此类材料版权的人员处获得充分许可的情况下，不得在IETF标准流程之外修改本文件，也不得在IETF标准流程之外创建其衍生作品，除了将其格式化以RFC形式发布或将其翻译成英语以外的其他语言。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. vCard Format Specification . . . . . . . . . . . . . . . . . . 5
3.1. Charset . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Line Delimiting and Folding . . . . . . . . . . . . . . . 5
3.3. ABNF Format Definition . . . . . . . . . . . . . . . . . . 6
3.4. Property Value Escaping . . . . . . . . . . . . . . . . . 9
4. Property Value Data Types . . . . . . . . . . . . . . . . . . 9
4.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.3. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP . . 12
4.3.1. DATE . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.3.2. TIME . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3.3. DATE-TIME . . . . . . . . . . . . . . . . . . . . . . 13
4.3.4. DATE-AND-OR-TIME . . . . . . . . . . . . . . . . . . . 14
4.3.5. TIMESTAMP . . . . . . . . . . . . . . . . . . . . . . 14
4.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.5. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.7. UTC-OFFSET . . . . . . . . . . . . . . . . . . . . . . . . 15
4.8. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . 16
5. Property Parameters . . . . . . . . . . . . . . . . . . . . . 16
5.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.2. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.3. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.4. ALTID . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.5. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.6. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.7. MEDIATYPE . . . . . . . . . . . . . . . . . . . . . . . . 20
5.8. CALSCALE . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.9. SORT-AS . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.10. GEO . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.11. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. vCard Format Specification . . . . . . . . . . . . . . . . . . 5
3.1. Charset . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Line Delimiting and Folding . . . . . . . . . . . . . . . 5
3.3. ABNF Format Definition . . . . . . . . . . . . . . . . . . 6
3.4. Property Value Escaping . . . . . . . . . . . . . . . . . 9
4. Property Value Data Types . . . . . . . . . . . . . . . . . . 9
4.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.3. DATE, TIME, DATE-TIME, DATE-AND-OR-TIME, and TIMESTAMP . . 12
4.3.1. DATE . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.3.2. TIME . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3.3. DATE-TIME . . . . . . . . . . . . . . . . . . . . . . 13
4.3.4. DATE-AND-OR-TIME . . . . . . . . . . . . . . . . . . . 14
4.3.5. TIMESTAMP . . . . . . . . . . . . . . . . . . . . . . 14
4.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.5. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.7. UTC-OFFSET . . . . . . . . . . . . . . . . . . . . . . . . 15
4.8. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . 16
5. Property Parameters . . . . . . . . . . . . . . . . . . . . . 16
5.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.2. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.3. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.4. ALTID . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.5. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.6. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.7. MEDIATYPE . . . . . . . . . . . . . . . . . . . . . . . . 20
5.8. CALSCALE . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.9. SORT-AS . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.10. GEO . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.11. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 23
6.1. General Properties . . . . . . . . . . . . . . . . . . . . 23
6.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 23
6.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 23
6.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1.4. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.5. XML . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.2. Identification Properties . . . . . . . . . . . . . . . . 28
6.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 29
6.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 30
6.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.2.6. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . 31
6.2.7. GENDER . . . . . . . . . . . . . . . . . . . . . . . . 32
6.3. Delivery Addressing Properties . . . . . . . . . . . . . . 32
6.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.4. Communications Properties . . . . . . . . . . . . . . . . 34
6.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 36
6.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.5. Geographical Properties . . . . . . . . . . . . . . . . . 37
6.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.6. Organizational Properties . . . . . . . . . . . . . . . . 39
6.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 39
6.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 41
6.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 42
6.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 43
6.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 43
6.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 44
6.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.7.5. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 45
6.7.6. UID . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.7.7. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . 47
6.7.8. URL . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.7.9. VERSION . . . . . . . . . . . . . . . . . . . . . . . 48
6.8. Security Properties . . . . . . . . . . . . . . . . . . . 48
6.8.1. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 49
6.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 49
6.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 50
6.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 50
6. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 23
6.1. General Properties . . . . . . . . . . . . . . . . . . . . 23
6.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 23
6.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 23
6.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1.4. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.5. XML . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.2. Identification Properties . . . . . . . . . . . . . . . . 28
6.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 29
6.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 30
6.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.2.6. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . 31
6.2.7. GENDER . . . . . . . . . . . . . . . . . . . . . . . . 32
6.3. Delivery Addressing Properties . . . . . . . . . . . . . . 32
6.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.4. Communications Properties . . . . . . . . . . . . . . . . 34
6.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 36
6.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.5. Geographical Properties . . . . . . . . . . . . . . . . . 37
6.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.6. Organizational Properties . . . . . . . . . . . . . . . . 39
6.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 39
6.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 41
6.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 42
6.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 43
6.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 43
6.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 44
6.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.7.5. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 45
6.7.6. UID . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.7.7. CLIENTPIDMAP . . . . . . . . . . . . . . . . . . . . . 47
6.7.8. URL . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.7.9. VERSION . . . . . . . . . . . . . . . . . . . . . . . 48
6.8. Security Properties . . . . . . . . . . . . . . . . . . . 48
6.8.1. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 49
6.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 49
6.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 50
6.9.3. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 50
6.10. Extended Properties and Parameters . . . . . . . . . . . . 51
7. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 51
7.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 51
7.1.1. Matching vCard Instances . . . . . . . . . . . . . . . 51
7.1.2. Matching Property Instances . . . . . . . . . . . . . 52
7.1.3. PID Matching . . . . . . . . . . . . . . . . . . . . . 52
7.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.2.1. Creation . . . . . . . . . . . . . . . . . . . . . . . 53
7.2.2. Initial Sharing . . . . . . . . . . . . . . . . . . . 53
7.2.3. Adding and Sharing a Property . . . . . . . . . . . . 54
7.2.4. Simultaneous Editing . . . . . . . . . . . . . . . . . 54
7.2.5. Global Context Simplification . . . . . . . . . . . . 56
8. Example: Author's vCard . . . . . . . . . . . . . . . . . . . 56
9. Security Considerations . . . . . . . . . . . . . . . . . . . 57
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 58
10.1. Media Type Registration . . . . . . . . . . . . . . . . . 58
10.2. Registering New vCard Elements . . . . . . . . . . . . . . 59
10.2.1. Registration Procedure . . . . . . . . . . . . . . . . 59
10.2.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 60
10.2.3. Registration Template for Properties . . . . . . . . . 61
10.2.4. Registration Template for Parameters . . . . . . . . . 61
10.2.5. Registration Template for Value Data Types . . . . . . 62
10.2.6. Registration Template for Values . . . . . . . . . . . 62
10.3. Initial vCard Elements Registries . . . . . . . . . . . . 63
10.3.1. Properties Registry . . . . . . . . . . . . . . . . . 64
10.3.2. Parameters Registry . . . . . . . . . . . . . . . . . 65
10.3.3. Value Data Types Registry . . . . . . . . . . . . . . 65
10.3.4. Values Registries . . . . . . . . . . . . . . . . . . 66
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 69
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69
12.1. Normative References . . . . . . . . . . . . . . . . . . . 69
12.2. Informative References . . . . . . . . . . . . . . . . . . 71
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 73
A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 73
A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 73
A.3. New Properties and Parameters . . . . . . . . . . . . . . 73
6.10. Extended Properties and Parameters . . . . . . . . . . . . 51
7. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 51
7.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 51
7.1.1. Matching vCard Instances . . . . . . . . . . . . . . . 51
7.1.2. Matching Property Instances . . . . . . . . . . . . . 52
7.1.3. PID Matching . . . . . . . . . . . . . . . . . . . . . 52
7.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.2.1. Creation . . . . . . . . . . . . . . . . . . . . . . . 53
7.2.2. Initial Sharing . . . . . . . . . . . . . . . . . . . 53
7.2.3. Adding and Sharing a Property . . . . . . . . . . . . 54
7.2.4. Simultaneous Editing . . . . . . . . . . . . . . . . . 54
7.2.5. Global Context Simplification . . . . . . . . . . . . 56
8. Example: Author's vCard . . . . . . . . . . . . . . . . . . . 56
9. Security Considerations . . . . . . . . . . . . . . . . . . . 57
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 58
10.1. Media Type Registration . . . . . . . . . . . . . . . . . 58
10.2. Registering New vCard Elements . . . . . . . . . . . . . . 59
10.2.1. Registration Procedure . . . . . . . . . . . . . . . . 59
10.2.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 60
10.2.3. Registration Template for Properties . . . . . . . . . 61
10.2.4. Registration Template for Parameters . . . . . . . . . 61
10.2.5. Registration Template for Value Data Types . . . . . . 62
10.2.6. Registration Template for Values . . . . . . . . . . . 62
10.3. Initial vCard Elements Registries . . . . . . . . . . . . 63
10.3.1. Properties Registry . . . . . . . . . . . . . . . . . 64
10.3.2. Parameters Registry . . . . . . . . . . . . . . . . . 65
10.3.3. Value Data Types Registry . . . . . . . . . . . . . . 65
10.3.4. Values Registries . . . . . . . . . . . . . . . . . . 66
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 69
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69
12.1. Normative References . . . . . . . . . . . . . . . . . . . 69
12.2. Informative References . . . . . . . . . . . . . . . . . . 71
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 73
A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 73
A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 73
A.3. New Properties and Parameters . . . . . . . . . . . . . . 73
Electronic address books have become ubiquitous. Their increased presence on portable, connected devices as well as the diversity of platforms that exchange contact data call for a standard. This memo defines the vCard format, which allows the capture and exchange of information normally stored within an address book or directory application.
电子通讯簿已变得无处不在。他们越来越多地出现在便携式连接设备上，以及交换联系人数据的平台的多样性都需要一个标准。此备忘录定义vCard格式，允许捕获和交换通常存储在通讯簿或目录应用程序中的信息。
A high-level overview of the differences from RFCs 2425 and 2426 can be found in Appendix A.
附录A中对RFCs 2425和2426的差异进行了详细概述。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”应按照[RFC2119]中的说明进行解释。
The text/vcard MIME content type (hereafter known as "vCard"; see Section 10.1) contains contact information, typically pertaining to a single contact or group of contacts. The content consists of one or more lines in the format given below.
文本/vcard MIME内容类型（以下称为“vcard”；参见第10.1节）包含联系人信息，通常与单个联系人或联系人组有关。内容由以下格式的一行或多行组成。
The charset (see [RFC3536] for internationalization terminology) for vCard is UTF-8 as defined in [RFC3629]. There is no way to override this. It is invalid to specify a value other than "UTF-8" in the "charset" MIME parameter (see Section 10.1).
vCard的字符集（国际化术语见[RFC3536]）为[RFC3629]中定义的UTF-8。没有办法推翻这一点。在“字符集”MIME参数中指定“UTF-8”以外的值是无效的（参见第10.1节）。
Individual lines within vCard are delimited by the [RFC5322] line break, which is a CRLF sequence (U+000D followed by U+000A). Long logical lines of text can be split into a multiple-physical-line representation using the following folding technique. Content lines SHOULD be folded to a maximum width of 75 octets, excluding the line break. Multi-octet characters MUST remain contiguous. The rationale for this folding process can be found in [RFC5322], Section 2.1.1.
vCard中的各行由[RFC5322]换行符分隔，这是一个CRLF序列（U+000D后接U+000A）。使用以下折叠技术，可以将文本的长逻辑行拆分为多个物理行表示。内容行应折叠到最大宽度为75个八位字节，不包括换行符。多个八位字符必须保持连续。该折叠过程的基本原理见[RFC5322]，第2.1.1节。
A logical line MAY be continued on the next physical line anywhere between two characters by inserting a CRLF immediately followed by a single white space character (space (U+0020) or horizontal tab (U+0009)). The folded line MUST contain at least one character. Any sequence of CRLF followed immediately by a single white space
通过插入一个CRLF，紧接着一个空白字符（空格（U+0020）或水平制表符（U+0009）），可以在两个字符之间的任何位置的下一个物理行上继续逻辑行。折叠行必须至少包含一个字符。紧接着一个空格的任何CRLF序列
character is ignored (removed) when processing the content type. For example, the line:
处理内容类型时忽略（删除）字符。例如，行：
NOTE:This is a long description that exists on a long line.
注意：这是一个长线描述。
can be represented as:
可表示为：
NOTE:This is a long description that exists on a long line.
注意：这是一个长线描述。
It could also be represented as:
它还可以表示为：
NOTE:This is a long descrip tion that exists o n a long line.
注：这是一个长线描述。
The process of moving from this folded multiple-line representation of a property definition to its single-line representation is called unfolding. Unfolding is accomplished by regarding CRLF immediately followed by a white space character (namely, HTAB (U+0009) or SPACE (U+0020)) as equivalent to no characters at all (i.e., the CRLF and single white space character are removed).
从特性定义的折叠多行表示移动到其单线表示的过程称为展开。展开是通过将紧跟在CRLF后面的空白字符（即HTAB（U+0009）或空格（U+0020））视为完全不包含字符（即，删除CRLF和单个空白字符）来完成的。
Note: It is possible for very simple implementations to generate improperly folded lines in the middle of a UTF-8 multi-octet sequence. For this reason, implementations SHOULD unfold lines in such a way as to properly restore the original sequence.
注意：非常简单的实现可以在UTF-8多八位字节序列的中间生成不正确折叠的行。因此，实现应该以正确恢复原始序列的方式展开行。
Note: Unfolding is done differently than in [RFC5322]. Unfolding in [RFC5322] only removes the CRLF, not the space following it.
注意：展开的方式与[RFC5322]中的方式不同。在[RFC5322]中展开只会删除CRLF，而不会删除它后面的空间。
Folding is done after any content encoding of a type value. Unfolding is done before any decoding of a type value in a content line.
折叠是在对类型值进行任何内容编码之后完成的。展开是在对内容行中的类型值进行任何解码之前完成的。
The following ABNF uses the notation of [RFC5234], which also defines CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT.
以下ABNF使用了[RFC5234]符号，它还定义了CRLF、WSP、DQUOTE、VCHAR、ALPHA和DIGIT。
vcard-entity = 1*vcard
vcard-entity = 1*vcard
vcard = "BEGIN:VCARD" CRLF "VERSION:4.0" CRLF 1*contentline "END:VCARD" CRLF ; A vCard object MUST include the VERSION and FN properties. ; VERSION MUST come immediately after BEGIN:VCARD.
vcard=“开始：vcard“CRLF”版本：4.0“CRLF 1*内容行”结束：vcard“CRLF”；vCard对象必须包含版本和FN属性；版本必须在BEGIN:VCARD之后立即提供。
contentline = [group "."] name *(";" param) ":" value CRLF
; When parsing a content line, folded lines must first
; be unfolded according to the unfolding procedure
; described in Section 3.2.
; When generating a content line, lines longer than 75
; characters SHOULD be folded according to the folding
; procedure described in Section 3.2.
contentline = [group "."] name *(";" param) ":" value CRLF
; When parsing a content line, folded lines must first
; be unfolded according to the unfolding procedure
; described in Section 3.2.
; When generating a content line, lines longer than 75
; characters SHOULD be folded according to the folding
; procedure described in Section 3.2.
group = 1*(ALPHA / DIGIT / "-")
name = "SOURCE" / "KIND" / "FN" / "N" / "NICKNAME"
/ "PHOTO" / "BDAY" / "ANNIVERSARY" / "GENDER" / "ADR" / "TEL"
/ "EMAIL" / "IMPP" / "LANG" / "TZ" / "GEO" / "TITLE" / "ROLE"
/ "LOGO" / "ORG" / "MEMBER" / "RELATED" / "CATEGORIES"
/ "NOTE" / "PRODID" / "REV" / "SOUND" / "UID" / "CLIENTPIDMAP"
/ "URL" / "KEY" / "FBURL" / "CALADRURI" / "CALURI" / "XML"
/ iana-token / x-name
; Parsing of the param and value is based on the "name" as
; defined in ABNF sections below.
; Group and name are case-insensitive.
group = 1*(ALPHA / DIGIT / "-")
name = "SOURCE" / "KIND" / "FN" / "N" / "NICKNAME"
/ "PHOTO" / "BDAY" / "ANNIVERSARY" / "GENDER" / "ADR" / "TEL"
/ "EMAIL" / "IMPP" / "LANG" / "TZ" / "GEO" / "TITLE" / "ROLE"
/ "LOGO" / "ORG" / "MEMBER" / "RELATED" / "CATEGORIES"
/ "NOTE" / "PRODID" / "REV" / "SOUND" / "UID" / "CLIENTPIDMAP"
/ "URL" / "KEY" / "FBURL" / "CALADRURI" / "CALURI" / "XML"
/ iana-token / x-name
; Parsing of the param and value is based on the "name" as
; defined in ABNF sections below.
; Group and name are case-insensitive.
iana-token = 1*(ALPHA / DIGIT / "-")
; identifier registered with IANA
iana-token = 1*(ALPHA / DIGIT / "-")
; identifier registered with IANA
x-name = "x-" 1*(ALPHA / DIGIT / "-")
; Names that begin with "x-" or "X-" are
; reserved for experimental use, not intended for released
; products, or for use in bilateral agreements.
x-name = "x-" 1*(ALPHA / DIGIT / "-")
; Names that begin with "x-" or "X-" are
; reserved for experimental use, not intended for released
; products, or for use in bilateral agreements.
param = language-param / value-param / pref-param / pid-param / type-param / geo-parameter / tz-parameter / sort-as-param / calscale-param / any-param ; Allowed parameters depend on property name.
参数=语言参数/值参数/预参数/pid参数/类型参数/地理参数/tz参数/排序为参数/calscale参数/任意参数；允许的参数取决于属性名称。
param-value = *SAFE-CHAR / DQUOTE *QSAFE-CHAR DQUOTE
param-value = *SAFE-CHAR / DQUOTE *QSAFE-CHAR DQUOTE
any-param = (iana-token / x-name) "=" param-value *("," param-value)
any-param = (iana-token / x-name) "=" param-value *("," param-value)
NON-ASCII = UTF8-2 / UTF8-3 / UTF8-4
; UTF8-{2,3,4} are defined in [RFC3629]
NON-ASCII = UTF8-2 / UTF8-3 / UTF8-4
; UTF8-{2,3,4} are defined in [RFC3629]
QSAFE-CHAR = WSP / "!" / %x23-7E / NON-ASCII
; Any character except CTLs, DQUOTE
QSAFE-CHAR = WSP / "!" / %x23-7E / NON-ASCII
; Any character except CTLs, DQUOTE
SAFE-CHAR = WSP / "!" / %x23-39 / %x3C-7E / NON-ASCII
; Any character except CTLs, DQUOTE, ";", ":"
SAFE-CHAR = WSP / "!" / %x23-39 / %x3C-7E / NON-ASCII
; Any character except CTLs, DQUOTE, ";", ":"
VALUE-CHAR = WSP / VCHAR / NON-ASCII
; Any textual character
VALUE-CHAR = WSP / VCHAR / NON-ASCII
; Any textual character
A line that begins with a white space character is a continuation of the previous line, as described in Section 3.2. The white space character and immediately preceeding CRLF should be discarded when reconstructing the original line. Note that this line-folding convention differs from that found in [RFC5322], in that the sequence <CRLF><WSP> found anywhere in the content indicates a continued line and should be removed.
如第3.2节所述，以空白字符开头的行是前一行的延续。重建原始行时，应丢弃空白字符和紧随其后的CRLF。请注意，此行折叠约定与[RFC5322]中的不同之处在于，内容中任何位置的序列<CRLF><WSP>表示连续行，应删除。
Property names and parameter names are case-insensitive (e.g., the property name "fn" is the same as "FN" and "Fn"). Parameter values MAY be case-sensitive or case-insensitive, depending on their definition. Parameter values that are not explicitly defined as being case-sensitive are case-insensitive. Based on experience with vCard 3 interoperability, it is RECOMMENDED that property and parameter names be upper-case on output.
属性名称和参数名称不区分大小写（例如，属性名称“fn”与“fn”和“fn”相同）。参数值可能区分大小写，也可能不区分大小写，具体取决于其定义。未明确定义为区分大小写的参数值不区分大小写。根据vCard 3互操作性的经验，建议在输出时属性和参数名称应为大写。
The group construct is used to group related properties together. The group name is a syntactic convention used to indicate that all property names prefaced with the same group name SHOULD be grouped together when displayed by an application. It has no other significance. Implementations that do not understand or support grouping MAY simply strip off any text before a "." to the left of the type name and present the types and values as normal.
组构造用于将相关属性分组在一起。组名是一种语法约定，用于指示当应用程序显示时，以相同组名开头的所有属性名应分组在一起。它没有其他意义。不理解或不支持分组的实现可以简单地删除类型名称左侧“.”之前的任何文本，并按正常方式显示类型和值。
Property cardinalities are indicated using the following notation, which is based on ABNF (see [RFC5234], Section 3.6):
使用以下基于ABNF的符号表示属性基数（见[RFC5234]，第3.6节）：
+-------------+--------------------------------------------------+
| Cardinality | Meaning |
+-------------+--------------------------------------------------+
| 1 | Exactly one instance per vCard MUST be present. |
| *1 | Exactly one instance per vCard MAY be present. |
| 1* | One or more instances per vCard MUST be present. |
| * | One or more instances per vCard MAY be present. |
+-------------+--------------------------------------------------+
+-------------+--------------------------------------------------+
| Cardinality | Meaning |
+-------------+--------------------------------------------------+
| 1 | Exactly one instance per vCard MUST be present. |
| *1 | Exactly one instance per vCard MAY be present. |
| 1* | One or more instances per vCard MUST be present. |
| * | One or more instances per vCard MAY be present. |
+-------------+--------------------------------------------------+
Properties defined in a vCard instance may have multiple values depending on the property cardinality. The general rule for encoding multi-valued properties is to simply create a new content line for each value (including the property name). However, it should be noted that some value types support encoding multiple values in a single content line by separating the values with a comma ",". This approach has been taken for several of the content types defined below (date, time, integer, float).
vCard实例中定义的属性可能具有多个值，具体取决于属性基数。编码多值属性的一般规则是为每个值（包括属性名称）创建一个新的内容行。但是，应注意的是，某些值类型支持在单个内容行中编码多个值，方法是使用逗号“，”分隔这些值。下面定义的几种内容类型（日期、时间、整数、浮点）都采用了这种方法。
Some properties may contain one or more values delimited by a COMMA character (U+002C). Therefore, a COMMA character in a value MUST be escaped with a BACKSLASH character (U+005C), even for properties that don't allow multiple instances (for consistency).
某些属性可能包含一个或多个由逗号字符（U+002C）分隔的值。因此，值中的逗号字符必须用反斜杠字符（U+005C）转义，即使对于不允许多个实例的属性也是如此（为了一致性）。
Some properties (e.g., N and ADR) comprise multiple fields delimited by a SEMICOLON character (U+003B). Therefore, a SEMICOLON in a field of such a "compound" property MUST be escaped with a BACKSLASH character. SEMICOLON characters in non-compound properties MAY be escaped. On input, an escaped SEMICOLON character is never a field separator. An unescaped SEMICOLON character may be a field separator, depending on the property in which it appears.
某些属性（如N和ADR）包含多个由分号字符（U+003B）分隔的字段。因此，此类“复合”属性字段中的分号必须使用反斜杠字符转义。非复合属性中的分号字符可以转义。在输入时，转义分号字符永远不是字段分隔符。未设置分号的字符可以是字段分隔符，具体取决于它出现的属性。
Furthermore, some fields of compound properties may contain a list of values delimited by a COMMA character. Therefore, a COMMA character in one of a field's values MUST be escaped with a BACKSLASH character, even for fields that don't allow multiple values (for consistency). Compound properties allowing multiple instances MUST NOT be encoded in a single content line.
此外，复合属性的某些字段可能包含由逗号分隔的值列表。因此，字段值之一中的逗号字符必须用反斜杠字符转义，即使对于不允许多个值的字段也是如此（为了一致性）。允许多个实例的复合属性不能编码在单个内容行中。
Finally, BACKSLASH characters in values MUST be escaped with a BACKSLASH character. NEWLINE (U+000A) characters in values MUST be encoded by two characters: a BACKSLASH followed by either an 'n' (U+006E) or an 'N' (U+004E).
最后，值中的反斜杠字符必须用反斜杠字符转义。值中的换行符（U+000A）必须由两个字符编码：反斜杠后跟“n”（U+006E）或“n”（U+004E）。
In all other cases, escaping MUST NOT be used.
在所有其他情况下，不得使用逃逸。
Standard value types are defined below.
标准值类型定义如下。
value = text
/ text-list
/ date-list
/ time-list
/ date-time-list
/ date-and-or-time-list
/ timestamp-list
/ boolean
/ integer-list
/ float-list
/ URI ; from Section 3 of [RFC3986]
/ utc-offset
/ Language-Tag
/ iana-valuespec
; Actual value type depends on property name and VALUE parameter.
value = text
/ text-list
/ date-list
/ time-list
/ date-time-list
/ date-and-or-time-list
/ timestamp-list
/ boolean
/ integer-list
/ float-list
/ URI ; from Section 3 of [RFC3986]
/ utc-offset
/ Language-Tag
/ iana-valuespec
; Actual value type depends on property name and VALUE parameter.
text = *TEXT-CHAR
text = *TEXT-CHAR
TEXT-CHAR = "\\" / "\," / "\n" / WSP / NON-ASCII
/ %x21-2B / %x2D-5B / %x5D-7E
; Backslashes, commas, and newlines must be encoded.
TEXT-CHAR = "\\" / "\," / "\n" / WSP / NON-ASCII
/ %x21-2B / %x2D-5B / %x5D-7E
; Backslashes, commas, and newlines must be encoded.
component = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII
/ %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E
list-component = component *("," component)
component = "\\" / "\," / "\;" / "\n" / WSP / NON-ASCII
/ %x21-2B / %x2D-3A / %x3C-5B / %x5D-7E
list-component = component *("," component)
text-list = text *("," text)
date-list = date *("," date)
time-list = time *("," time)
date-time-list = date-time *("," date-time)
date-and-or-time-list = date-and-or-time *("," date-and-or-time)
timestamp-list = timestamp *("," timestamp)
integer-list = integer *("," integer)
float-list = float *("," float)
text-list = text *("," text)
date-list = date *("," date)
time-list = time *("," time)
date-time-list = date-time *("," date-time)
date-and-or-time-list = date-and-or-time *("," date-and-or-time)
timestamp-list = timestamp *("," timestamp)
integer-list = integer *("," integer)
float-list = float *("," float)
boolean = "TRUE" / "FALSE"
integer = [sign] 1*DIGIT
float = [sign] 1*DIGIT ["." 1*DIGIT]
boolean = "TRUE" / "FALSE"
integer = [sign] 1*DIGIT
float = [sign] 1*DIGIT ["." 1*DIGIT]
sign = "+" / "-"
sign = "+" / "-"
year = 4DIGIT ; 0000-9999
month = 2DIGIT ; 01-12
day = 2DIGIT ; 01-28/29/30/31 depending on month and leap year
hour = 2DIGIT ; 00-23
minute = 2DIGIT ; 00-59
second = 2DIGIT ; 00-58/59/60 depending on leap second
zone = utc-designator / utc-offset
utc-designator = %x5A ; uppercase "Z"
year = 4DIGIT ; 0000-9999
month = 2DIGIT ; 01-12
day = 2DIGIT ; 01-28/29/30/31 depending on month and leap year
hour = 2DIGIT ; 00-23
minute = 2DIGIT ; 00-59
second = 2DIGIT ; 00-58/59/60 depending on leap second
zone = utc-designator / utc-offset
utc-designator = %x5A ; uppercase "Z"
date = year [month day]
/ year "-" month
/ "--" month [day]
/ "--" "-" day
date-noreduc = year month day
/ "--" month day
/ "--" "-" day
date-complete = year month day
date = year [month day]
/ year "-" month
/ "--" month [day]
/ "--" "-" day
date-noreduc = year month day
/ "--" month day
/ "--" "-" day
date-complete = year month day
time = hour [minute [second]] [zone]
/ "-" minute [second] [zone]
/ "-" "-" second [zone]
time-notrunc = hour [minute [second]] [zone]
time-complete = hour minute second [zone]
time = hour [minute [second]] [zone]
/ "-" minute [second] [zone]
/ "-" "-" second [zone]
time-notrunc = hour [minute [second]] [zone]
time-complete = hour minute second [zone]
time-designator = %x54 ; uppercase "T"
date-time = date-noreduc time-designator time-notrunc
timestamp = date-complete time-designator time-complete
time-designator = %x54 ; uppercase "T"
date-time = date-noreduc time-designator time-notrunc
timestamp = date-complete time-designator time-complete
date-and-or-time = date-time / date / time-designator time
date-and-or-time = date-time / date / time-designator time
utc-offset = sign hour [minute]
utc偏移=符号小时[分钟]
Language-Tag = <Language-Tag, defined in [RFC5646], Section 2.1>
Language-Tag = <Language-Tag, defined in [RFC5646], Section 2.1>
iana-valuespec = <value-spec, see Section 12>
; a publicly defined valuetype format, registered
; with IANA, as defined in Section 12 of this
; document.
iana-valuespec = <value-spec, see Section 12>
; a publicly defined valuetype format, registered
; with IANA, as defined in Section 12 of this
; document.
"text": The "text" value type should be used to identify values that contain human-readable text. As for the language, it is controlled by the LANGUAGE property parameter defined in Section 5.1.
“文本”：应使用“文本”值类型来标识包含人类可读文本的值。对于语言，它由第5.1节中定义的语言属性参数控制。
Examples for "text":
“文本”示例：
this is a text value this is one value,this is another this is a single value\, with a comma encoded
这是一个文本值这是一个值，这是另一个值这是单个值\，用逗号编码
A formatted text line break in a text value type MUST be represented as the character sequence backslash (U+005C) followed by a Latin small letter n (U+006E) or a Latin capital letter N (U+004E), that is, "\n" or "\N".
文本值类型中的格式化文本换行符必须表示为字符序列反斜杠（U+005C），后跟拉丁小写字母n（U+006E）或拉丁大写字母n（U+004E），即“\n”或“\n”。
For example, a multiple line NOTE value of:
例如，多行注释值为：
Mythical Manager Hyjinx Software Division BabsCo, Inc.
Hyjinx软件部神话经理BabsCo，Inc。
could be represented as:
可以表示为：
NOTE:Mythical Manager\nHyjinx Software Division\n BabsCo\, Inc.\n
注：Mythical Manager\nHyjinx软件部门\n BabsCo\，Inc.\n
demonstrating the \n literal formatted line break technique, the CRLF-followed-by-space line folding technique, and the backslash escape technique.
演示\n文字格式的换行技术、CRLF后跟空格折线技术和反斜杠转义技术。
"uri": The "uri" value type should be used to identify values that are referenced by a Uniform Resource Identifier (URI) instead of encoded in-line. These value references might be used if the value is too large, or otherwise undesirable to include directly. The format for the URI is as defined in Section 3 of [RFC3986]. Note that the value of a property of type "uri" is what the URI points to, not the URI itself.
“uri”：应该使用“uri”值类型来标识由统一资源标识符（uri）引用的值，而不是在线编码的值。如果值太大或不希望直接包含，则可以使用这些值引用。URI的格式如[RFC3986]第3节所定义。注意，“uri”类型属性的值是uri指向的，而不是uri本身。
Examples for "uri":
“uri”的示例：
http://www.example.com/my/picture.jpg
ldap://ldap.example.com/cn=babs%20jensen
http://www.example.com/my/picture.jpg
ldap://ldap.example.com/cn=babs%20jensen
"date", "time", "date-time", "date-and-or-time", and "timestamp": Each of these value types is based on the definitions in [ISO.8601.2004]. Multiple such values can be specified using the comma-separated notation.
“日期”、“时间”、“日期-时间”、“日期和/或时间”以及“时间戳”：这些值类型均基于[ISO.8601.2004]中的定义。可以使用逗号分隔符号指定多个这样的值。
Only the basic format is supported.
仅支持基本格式。
A calendar date as specified in [ISO.8601.2004], Section 4.1.2.
[ISO.8601.2004]第4.1.2节规定的日历日期。
Reduced accuracy, as specified in [ISO.8601.2004], Sections 4.1.2.3 a) and b), but not c), is permitted.
根据[ISO.8601.2004]第4.1.2.3节a）和b）的规定，允许降低精度，但不允许降低c）。
Expanded representation, as specified in [ISO.8601.2004], Section 4.1.4, is forbidden.
禁止[ISO.8601.2004]第4.1.4节规定的扩展表示。
Truncated representation, as specified in [ISO.8601.2000], Sections 5.2.1.3 d), e), and f), is permitted.
允许使用[ISO.8601.2000]第5.2.1.3 d）、e）和f）节规定的截断表示法。
Examples for "date":
“日期”的示例：
19850412
1985-04
1985
--0412
---12
19850412
1985-04
1985
--0412
---12
Note the use of YYYY-MM in the second example above. YYYYMM is disallowed to prevent confusion with YYMMDD. Note also that YYYY-MM-DD is disallowed since we are using the basic format instead of the extended format.
注意上面第二个示例中使用的YYYY-MM。不允许使用YYYYMM，以防止与YYMMDD混淆。还要注意，YYYY-MM-DD是不允许的，因为我们使用的是基本格式而不是扩展格式。
A time of day as specified in [ISO.8601.2004], Section 4.2.
[ISO.8601.2004]第4.2节中规定的时间。
Reduced accuracy, as specified in [ISO.8601.2004], Section 4.2.2.3, is permitted.
允许按照[ISO.8601.2004]第4.2.2.3节的规定降低精度。
Representation with decimal fraction, as specified in [ISO.8601.2004], Section 4.2.2.4, is forbidden.
禁止使用[ISO.8601.2004]第4.2.2.4节规定的小数表示。
The midnight hour is always represented by 00, never 24 (see [ISO.8601.2004], Section 4.2.3).
午夜时刻始终用00表示，而不是24（见[ISO.8601.2004]第4.2.3节）。
Truncated representation, as specified in [ISO.8601.2000], Sections 5.3.1.4 a), b), and c), is permitted.
允许使用[ISO.8601.2000]第5.3.1.4 a）、b）和c）节规定的截断表示法。
Examples for "time":
“时间”的例子：
102200 1022 10 -2200 --00 102200Z 102200-0800
102200 1022 10-2200--00 102200Z 102200-0800
A date and time of day combination as specified in [ISO.8601.2004], Section 4.3.
[ISO.8601.2004]第4.3节中规定的日期和时间组合。
Truncation of the date part, as specified in [ISO.8601.2000], Section 5.4.2 c), is permitted.
允许按照[ISO.8601.2000]第5.4.2 c）节的规定截断日期部分。
Examples for "date-time":
“日期-时间”示例：
19961022T140000
--1022T1400
---22T14
19961022T140000
--1022T1400
---22T14
Either a DATE-TIME, a DATE, or a TIME value. To allow unambiguous interpretation, a stand-alone TIME value is always preceded by a "T".
日期时间、日期或时间值。为了进行明确的解释，独立时间值的前面总是有一个“T”。
Examples for "date-and-or-time":
“日期或时间”示例：
19961022T140000
--1022T1400
---22T14
19850412
1985-04
1985
--0412
---12
T102200
T1022
T10
T-2200
T--00
T102200Z
T102200-0800
19961022T140000
--1022T1400
---22T14
19850412
1985-04
1985
--0412
---12
T102200
T1022
T10
T-2200
T--00
T102200Z
T102200-0800
A complete date and time of day combination as specified in [ISO.8601.2004], Section 4.3.2.
[ISO.8601.2004]第4.3.2节中规定的完整日期和时间组合。
Examples for "timestamp":
“时间戳”示例：
19961022T140000 19961022T140000Z 19961022T140000-05 19961022T140000-0500
19961022T140000 19961022T140000Z 19961022T140000-05 19961022T140000-0500
"boolean": The "boolean" value type is used to express boolean values. These values are case-insensitive.
“布尔”：布尔值类型用于表示布尔值。这些值不区分大小写。
Examples:
示例：
TRUE false True
真假假真
"integer": The "integer" value type is used to express signed integers in decimal format. If sign is not specified, the value is assumed positive "+". Multiple "integer" values can be specified using the comma-separated notation. The maximum value is 9223372036854775807, and the minimum value is -9223372036854775808. These limits correspond to a signed 64-bit integer using two's-complement arithmetic.
“整型”：整型值类型用于以十进制格式表示有符号整数。如果未指定符号，则该值假定为正“+”。可以使用逗号分隔符号指定多个“整数值”。最大值为9223372036854775807，最小值为-9223372036854775808。这些限制对应于使用二补运算的有符号64位整数。
Examples:
示例：
1234567890 -1234556790 +1234556790,432109876
1234567890 -1234556790 +1234556790,432109876
"float": The "float" value type is used to express real numbers. If sign is not specified, the value is assumed positive "+". Multiple "float" values can be specified using the comma-separated notation. Implementations MUST support a precision equal or better than that of the IEEE "binary64" format [IEEE.754.2008].
“浮点”：浮点值类型用于表示实数。如果未指定符号，则该值假定为正“+”。可以使用逗号分隔的表示法指定多个“浮点”值。实现必须支持与IEEE“binary64”格式相同或更好的精度[IEEE.754.2008]。
Note: Scientific notation is disallowed. Implementers wishing to use their favorite language's %f formatting should be careful.
注：不允许使用科学记数法。希望使用其喜爱语言的%f格式的实现者应小心。
Examples:
示例：
20.30 1000000.0000001 1.333,3.14
20.30 1000000.0000001 1.333,3.14
"utc-offset": The "utc-offset" value type specifies that the property value is a signed offset from UTC. This value type can be specified in the TZ property.
“utc偏移量”：“utc偏移量”值类型指定属性值是utc的有符号偏移量。可以在TZ属性中指定此值类型。
The value type is an offset from Coordinated Universal Time (UTC). It is specified as a positive or negative difference in units of hours and minutes (e.g., +hhmm). The time is specified as a 24-hour clock. Hour values are from 00 to 23, and minute values are from 00 to 59. Hour and minutes are 2 digits with high-order zeroes required to maintain digit count. The basic format for ISO 8601 UTC offsets MUST be used.
值类型是与协调世界时（UTC）的偏移量。它被指定为以小时和分钟为单位的正差或负差（例如，+hhmm）。时间指定为24小时时钟。小时值从00到23，分钟值从00到59。小时和分钟为2位数字，需要高阶零来保持数字计数。必须使用ISO 8601 UTC偏移量的基本格式。
"language-tag": A single language tag, as defined in [RFC5646].
“语言标记”：如[RFC5646]中所定义的单一语言标记。
A property can have attributes associated with it. These "property parameters" contain meta-information about the property or the property value. In some cases, the property parameter can be multi-valued in which case the property parameter value elements are separated by a COMMA (U+002C).
属性可以具有与其关联的属性。这些“属性参数”包含有关属性或属性值的元信息。在某些情况下，属性参数可以是多值的，在这种情况下，属性参数值元素由逗号（U+002C）分隔。
Property parameter value elements that contain the COLON (U+003A), SEMICOLON (U+003B), or COMMA (U+002C) character separators MUST be specified as quoted-string text values. Property parameter values MUST NOT contain the DQUOTE (U+0022) character. The DQUOTE character is used as a delimiter for parameter values that contain restricted characters or URI text.
必须将包含冒号（U+003A）、分号（U+003B）或逗号（U+002C）字符分隔符的属性参数值元素指定为带引号的字符串文本值。属性参数值不能包含DQUOTE（U+0022）字符。DQUOTE字符用作包含受限字符或URI文本的参数值的分隔符。
Applications MUST ignore x-param and iana-param values they don't recognize.
应用程序必须忽略它们无法识别的x-param和iana-param值。
The LANGUAGE property parameter is used to identify data in multiple languages. There is no concept of "default" language, except as specified by any "Content-Language" MIME header parameter that is present [RFC3282]. The value of the LANGUAGE property parameter is a language tag as defined in Section 2 of [RFC5646].
LANGUAGE属性参数用于以多种语言标识数据。没有“默认”语言的概念，除非由存在的任何“内容语言”MIME头参数指定[RFC3282]。LANGUAGE属性参数的值是[RFC5646]第2节中定义的语言标记。
Examples:
示例：
ROLE;LANGUAGE=tr:hoca
ROLE;LANGUAGE=tr:hoca
ABNF:
荷兰银行：
language-param = "LANGUAGE=" Language-Tag ; Language-Tag is defined in section 2.1 of RFC 5646
language param=“language=”语言标签；语言标记在RFC 5646第2.1节中定义
The VALUE parameter is OPTIONAL, used to identify the value type (data type) and format of the value. The use of these predefined formats is encouraged even if the value parameter is not explicitly used. By defining a standard set of value types and their formats, existing parsing and processing code can be leveraged. The
VALUE参数是可选的，用于标识值类型（数据类型）和值的格式。即使未明确使用value参数，也鼓励使用这些预定义格式。通过定义一组标准的值类型及其格式，可以利用现有的解析和处理代码。这个
predefined data type values MUST NOT be repeated in COMMA-separated value lists except within the N, NICKNAME, ADR, and CATEGORIES properties.
预定义的数据类型值不得在逗号分隔的值列表中重复，N、昵称、ADR和类别属性中除外。
ABNF:
荷兰银行：
value-param = "VALUE=" value-type
value param=“value=”值类型
value-type = "text"
/ "uri"
/ "date"
/ "time"
/ "date-time"
/ "date-and-or-time"
/ "timestamp"
/ "boolean"
/ "integer"
/ "float"
/ "utc-offset"
/ "language-tag"
/ iana-token ; registered as described in section 12
/ x-name
value-type = "text"
/ "uri"
/ "date"
/ "time"
/ "date-time"
/ "date-and-or-time"
/ "timestamp"
/ "boolean"
/ "integer"
/ "float"
/ "utc-offset"
/ "language-tag"
/ iana-token ; registered as described in section 12
/ x-name
The PREF parameter is OPTIONAL and is used to indicate that the corresponding instance of a property is preferred by the vCard author. Its value MUST be an integer between 1 and 100 that quantifies the level of preference. Lower values correspond to a higher level of preference, with 1 being most preferred.
PREF参数是可选的，用于指示vCard作者首选属性的相应实例。其值必须是1到100之间的整数，用于量化偏好级别。较低的值对应较高的偏好水平，1是最优先的。
When the parameter is absent, the default MUST be to interpret the property instance as being least preferred.
如果缺少该参数，则默认值必须是将属性实例解释为最不首选。
Note that the value of this parameter is to be interpreted only in relation to values assigned to other instances of the same property in the same vCard. A given value, or the absence of a value, MUST NOT be interpreted on its own.
请注意，此参数的值仅与分配给同一vCard中相同属性的其他实例的值相关。不得自行解释给定值或缺少值。
This parameter MAY be applied to any property that allows multiple instances.
此参数可应用于允许多个实例的任何属性。
ABNF:
荷兰银行：
pref-param = "PREF=" (1*2DIGIT / "100") ; An integer between 1 and 100.
pref param=“pref=”（1*2DIGIT/“100”）；介于1和100之间的整数。
The ALTID parameter is used to "tag" property instances as being alternative representations of the same logical property. For example, translations of a property in multiple languages generates multiple property instances having different LANGUAGE (Section 5.1) parameter that are tagged with the same ALTID value.
ALTID参数用于将属性实例“标记”为同一逻辑属性的替代表示形式。例如，以多种语言翻译属性会生成多个属性实例，这些属性实例具有不同的语言（第5.1节）参数，并使用相同的ALTID值进行标记。
This parameter's value is treated as an opaque string. Its sole purpose is to be compared for equality against other ALTID parameter values.
此参数的值被视为不透明字符串。其唯一目的是与其他ALTID参数值进行相等性比较。
Two property instances are considered alternative representations of the same logical property if and only if their names as well as the value of their ALTID parameters are identical. Property instances without the ALTID parameter MUST NOT be considered an alternative representation of any other property instance. Values for the ALTID parameter are not globally unique: they MAY be reused for different property names.
当且仅当两个属性实例的名称及其ALTID参数的值相同时，才将其视为同一逻辑属性的替代表示形式。不带ALTID参数的属性实例不得视为任何其他属性实例的替代表示形式。ALTID参数的值不是全局唯一的：它们可以用于不同的属性名称。
Property instances having the same ALTID parameter value count as 1 toward cardinality. Therefore, since N (Section 6.2.2) has cardinality *1 and TITLE (Section 6.6.1) has cardinality *, these three examples would be legal:
属性实例的ALTID参数值计数与基数1相同。因此，由于N（第6.2.2节）具有基数*1，而TITLE（第6.6.1节）具有基数*，这三个示例是合法的：
N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
N;ALTID=1;LANGUAGE=en:Yamada;Taro;;;
(<U+XXXX> denotes a UTF8-encoded Unicode character.)
N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
N;ALTID=1;LANGUAGE=en:Yamada;Taro;;;
(<U+XXXX> denotes a UTF8-encoded Unicode character.)
TITLE;ALTID=1;LANGUAGE=fr:Patron
TITLE;ALTID=1;LANGUAGE=en:Boss
TITLE;ALTID=1;LANGUAGE=fr:Patron
TITLE;ALTID=1;LANGUAGE=en:Boss
TITLE;ALTID=1;LANGUAGE=fr:Patron
TITLE;ALTID=1;LANGUAGE=en:Boss
TITLE;ALTID=2;LANGUAGE=en:Chief vCard Evangelist
TITLE;ALTID=1;LANGUAGE=fr:Patron
TITLE;ALTID=1;LANGUAGE=en:Boss
TITLE;ALTID=2;LANGUAGE=en:Chief vCard Evangelist
while this one would not:
而这一条不会：
N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
N:Yamada;Taro;;;
(Two instances of the N property.)
N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
N:Yamada;Taro;;;
(Two instances of the N property.)
and these three would be legal but questionable:
这三个是合法的，但值得怀疑：
TITLE;ALTID=1;LANGUAGE=fr:Patron TITLE;ALTID=2;LANGUAGE=en:Boss (Should probably have the same ALTID value.)
标题高度=1；语言=fr：用户名称；高度=2；LANGUAGE=en:Boss（应该具有相同的ALTID值。）
TITLE;ALTID=1;LANGUAGE=fr:Patron TITLE:LANGUAGE=en:Boss (Second line should probably have ALTID=1.)
标题高度=1；LANGUAGE=fr:Patron TITLE:LANGUAGE=en:Boss（第二行可能应该有ALTID=1。）
N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
N;ALTID=1;LANGUAGE=en:Yamada;Taro;;;
N;ALTID=1;LANGUAGE=en:Smith;John;;;
(The last line should probably have ALTID=2. But that would be
illegal because N has cardinality *1.)
N;ALTID=1;LANGUAGE=jp:<U+5C71><U+7530>;<U+592A><U+90CE>;;;
N;ALTID=1;LANGUAGE=en:Yamada;Taro;;;
N;ALTID=1;LANGUAGE=en:Smith;John;;;
(The last line should probably have ALTID=2. But that would be
illegal because N has cardinality *1.)
The ALTID property MAY also be used in may contexts other than with the LANGUAGE parameter. Here's an example with two representations of the same photo in different file formats:
ALTID属性也可用于除LANGUAGE参数之外的其他上下文中。下面是一个以不同文件格式对同一张照片进行两种表示的示例：
PHOTO;ALTID=1:data:image/jpeg;base64,... PHOTO;ALTID=1;data:image/jp2;base64,...
照片ALTID=1：数据：图像/jpeg；base64，。。。照片高度=1；资料：image/jp2；base64，。。。
ABNF:
荷兰银行：
altid-param = "ALTID=" param-value
altid param=“altid=”参数值
The PID parameter is used to identify a specific property among multiple instances. It plays a role analogous to the UID property (Section 6.7.6) on a per-property instead of per-vCard basis. It MAY appear more than once in a given property. It MUST NOT appear on properties that may have only one instance per vCard. Its value is either a single small positive integer or a pair of small positive integers separated by a dot. Multiple values may be encoded in a single PID parameter by separating the values with a comma ",". See Section 7 for more details on its usage.
PID参数用于标识多个实例中的特定属性。它的作用类似于UID属性（第6.7.6节），是基于每个属性，而不是基于每个vCard。它可能在给定属性中出现多次。它不能出现在每个vCard只能有一个实例的属性上。它的值可以是单个小正整数，也可以是由点分隔的一对小正整数。通过使用逗号“，”分隔值，可以在单个PID参数中对多个值进行编码。有关其用法的更多详细信息，请参见第7节。
ABNF:
荷兰银行：
pid-param = "PID=" pid-value *("," pid-value)
pid-value = 1*DIGIT ["." 1*DIGIT]
pid-param = "PID=" pid-value *("," pid-value)
pid-value = 1*DIGIT ["." 1*DIGIT]
The TYPE parameter has multiple, different uses. In general, it is a way of specifying class characteristics of the associated property. Most of the time, its value is a comma-separated subset of a predefined enumeration. In this document, the following properties make use of this parameter: FN, NICKNAME, PHOTO, ADR, TEL, EMAIL, IMPP, LANG, TZ, GEO, TITLE, ROLE, LOGO, ORG, RELATED, CATEGORIES,
类型参数有多种不同的用途。通常，它是指定关联属性的类特征的一种方法。大多数情况下，其值是预定义枚举的逗号分隔子集。在本文档中，以下属性使用此参数：FN、昵称、照片、ADR、电话、电子邮件、IMPP、LANG、TZ、GEO、标题、角色、徽标、组织、相关、类别，
NOTE, SOUND, URL, KEY, FBURL, CALADRURI, and CALURI. The TYPE parameter MUST NOT be applied on other properties defined in this document.
注释、声音、URL、键、FBURL、CALADRURI和CALURI。类型参数不得应用于此文档中定义的其他属性。
The "work" and "home" values act like tags. The "work" value implies that the property is related to an individual's work place, while the "home" value implies that the property is related to an individual's personal life. When neither "work" nor "home" is present, it is implied that the property is related to both an individual's work place and personal life in the case that the KIND property's value is "individual", or to none in other cases.
“工作”和“家庭”值的作用类似于标记。“工作”价值意味着财产与个人的工作场所有关，“家庭”价值意味着财产与个人的个人生活有关。当既不存在“工作”也不存在“家庭”时，如果实物财产的价值为“个人”，则意味着该财产与个人的工作场所和个人生活相关，或者在其他情况下与任何财产无关。
ABNF:
荷兰银行：
type-param = "TYPE=" type-value *("," type-value)
type-param = "TYPE=" type-value *("," type-value)
type-value = "work" / "home" / type-param-tel
/ type-param-related / iana-token / x-name
; This is further defined in individual property sections.
type-value = "work" / "home" / type-param-tel
/ type-param-related / iana-token / x-name
; This is further defined in individual property sections.
The MEDIATYPE parameter is used with properties whose value is a URI. Its use is OPTIONAL. It provides a hint to the vCard consumer application about the media type [RFC2046] of the resource identified by the URI. Some URI schemes do not need this parameter. For example, the "data" scheme allows the media type to be explicitly indicated as part of the URI [RFC2397]. Another scheme, "http", provides the media type as part of the URI resolution process, with the Content-Type HTTP header [RFC2616]. The MEDIATYPE parameter is intended to be used with URI schemes that do not provide such functionality (e.g., "ftp" [RFC1738]).
MEDIATYPE参数与值为URI的属性一起使用。它的使用是可选的。它向vCard使用者应用程序提供有关URI标识的资源的媒体类型[RFC2046]的提示。某些URI方案不需要此参数。例如，“数据”方案允许将媒体类型显式指示为URI的一部分[RFC2397]。另一个方案“http”提供媒体类型作为URI解析过程的一部分，内容类型为http头[RFC2616]。MEDIATYPE参数用于不提供此类功能的URI方案（例如，“ftp”[RFC1738]）。
ABNF:
荷兰银行：
mediatype-param = "MEDIATYPE=" mediatype
mediatype = type-name "/" subtype-name *( ";" attribute "=" value )
; "attribute" and "value" are from [RFC2045]
; "type-name" and "subtype-name" are from [RFC4288]
mediatype-param = "MEDIATYPE=" mediatype
mediatype = type-name "/" subtype-name *( ";" attribute "=" value )
; "attribute" and "value" are from [RFC2045]
; "type-name" and "subtype-name" are from [RFC4288]
The CALSCALE parameter is identical to the CALSCALE property in iCalendar (see [RFC5545], Section 3.7.1). It is used to define the calendar system in which a date or date-time value is expressed. The only value specified by iCalendar is "gregorian", which stands for the Gregorian system. It is the default when the parameter is absent. Additional values may be defined in extension documents and
CALSCALE参数与iCalendar中的CALSCALE属性相同（请参见[RFC5545]，第3.7.1节）。它用于定义表示日期或日期时间值的日历系统。iCalendar指定的唯一值是“gregorian”，代表公历制。当参数不存在时，它是默认值。附加值可在扩展文档和
registered with IANA (see Section 10.3.4). A vCard implementation MUST ignore properties with a CALSCALE parameter value that it does not understand.
在IANA注册（见第10.3.4节）。vCard实现必须忽略具有其不理解的CALSCALE参数值的属性。
ABNF:
荷兰银行：
calscale-param = "CALSCALE=" calscale-value
calscale参数=“calscale=”calscale值
calscale-value = "gregorian" / iana-token / x-name
calscale-value = "gregorian" / iana-token / x-name
The "sort-as" parameter is used to specify the string to be used for national-language-specific sorting. Without this information, sorting algorithms could incorrectly sort this vCard within a sequence of sorted vCards. When this property is present in a vCard, then the given strings are used for sorting the vCard.
“sort as”参数用于指定用于特定于国家语言的排序的字符串。如果没有这些信息，排序算法可能会在已排序的vCard序列中错误地排序此vCard。当vCard中存在此属性时，将使用给定字符串对vCard进行排序。
This parameter's value is a comma-separated list that MUST have as many or fewer elements as the corresponding property value has components. This parameter's value is case-sensitive.
此参数的值是以逗号分隔的列表，其元素数量必须与相应属性值的组件数量相同或更少。此参数的值区分大小写。
ABNF:
荷兰银行：
sort-as-param = "SORT-AS=" sort-as-value
排序为param=“sort-as=”排序为值
sort-as-value = param-value *("," param-value)
按值排序=参数值*（“，”参数值）
Examples: For the case of surname and given name sorting, the following examples define common sort string usage with the N property.
示例：对于姓氏和给定名称排序，以下示例使用N属性定义常见的排序字符串用法。
FN:Rene van der Harten N;SORT-AS="Harten,Rene":van der Harten;Rene,J.;Sir;R.D.O.N.
FN:Rene van der Harten N；SORT-AS=“Harten，Rene”：范德哈顿；雷内，J。；先生R.D.O.N。
FN:Robert Pau Shou Chang
N;SORT-AS="Pau Shou Chang,Robert":Shou Chang;Robert,Pau;;
FN:Robert Pau Shou Chang
N;SORT-AS="Pau Shou Chang,Robert":Shou Chang;Robert,Pau;;
FN:Osamu Koura
N;SORT-AS="Koura,Osamu":Koura;Osamu;;
FN:Osamu Koura
N;SORT-AS="Koura,Osamu":Koura;Osamu;;
FN:Oscar del Pozo
N;SORT-AS="Pozo,Oscar":del Pozo Triscon;Oscar;;
FN:Oscar del Pozo
N;SORT-AS="Pozo,Oscar":del Pozo Triscon;Oscar;;
FN:Chistine d'Aboville
N;SORT-AS="Aboville,Christine":d'Aboville;Christine;;
FN:Chistine d'Aboville
N;SORT-AS="Aboville,Christine":d'Aboville;Christine;;
FN:H. James de Mann
N;SORT-AS="Mann,James":de Mann;Henry,James;;
FN:H. James de Mann
N;SORT-AS="Mann,James":de Mann;Henry,James;;
If sorted by surname, the results would be:
如果按姓氏排序，结果将是：
Christine d'Aboville Rene van der Harten Osamu Koura H. James de Mann Robert Pau Shou Chang Oscar del Pozo
克里斯汀·阿博维尔·雷内·范德哈顿·奥萨姆·库拉H.詹姆斯·德曼·罗伯特·鲍寿昌·奥斯卡·德尔波佐
If sorted by given name, the results would be:
如果按给定名称排序，结果将为：
Christine d'Aboville H. James de Mann Osamu Koura Oscar del Pozo Rene van der Harten Robert Pau Shou Chang
克里斯汀·达博维尔H.詹姆斯·德曼·奥萨姆·库拉·奥斯卡·德尔波佐·雷内·范德哈顿·罗伯特·鲍寿昌
The GEO parameter can be used to indicate global positioning information that is specific to an address. Its value is the same as that of the GEO property (see Section 6.5.2).
GEO参数可用于指示特定于某个地址的全球定位信息。其值与GEO财产的值相同（见第6.5.2节）。
ABNF:
荷兰银行：
geo-parameter = "GEO=" DQUOTE URI DQUOTE
geo parameter=“geo=”DQUOTE URI DQUOTE
The TZ parameter can be used to indicate time zone information that is specific to an address. Its value is the same as that of the TZ property.
TZ参数可用于指示特定于地址的时区信息。其值与TZ属性的值相同。
ABNF:
荷兰银行：
tz-parameter = "TZ=" (param-value / DQUOTE URI DQUOTE)
tz-parameter = "TZ=" (param-value / DQUOTE URI DQUOTE)
What follows is an enumeration of the standard vCard properties.
下面是标准vCard属性的枚举。
Purpose: To denote the beginning of a syntactic entity within a text/vcard content-type.
目的：表示文本/vcard内容类型中语法实体的开头。
Value type: text
值类型：文本
Cardinality: 1
基数：1
Special notes: The content entity MUST begin with the BEGIN property with a value of "VCARD". The value is case-insensitive.
特别说明：内容实体必须以值为“VCARD”的begin属性开头。该值不区分大小写。
The BEGIN property is used in conjunction with the END property to delimit an entity containing a related set of properties within a text/vcard content-type. This construct can be used instead of including multiple vCards as body parts inside of a multipart/ alternative MIME message. It is provided for applications that wish to define content that can contain multiple entities within the same text/vcard content-type or to define content that can be identifiable outside of a MIME environment.
BEGIN属性与END属性结合使用，用于在文本/vcard内容类型中分隔包含一组相关属性的实体。可以使用此结构，而不是将多个vCard作为多部分/备选MIME消息的主体部分。它适用于希望定义可以在同一文本/vcard内容类型中包含多个实体的内容或定义可以在MIME环境之外识别的内容的应用程序。
ABNF:
荷兰银行：
BEGIN-param = 0" " ; no parameter allowed BEGIN-value = "VCARD"
开始参数=0“”；不允许参数BEGIN value=“VCARD”
Example:
例子：
BEGIN:VCARD
开始：VCARD
Purpose: To denote the end of a syntactic entity within a text/vcard content-type.
目的：表示文本/vcard内容类型中语法实体的结尾。
Value type: text
值类型：文本
Cardinality: 1
基数：1
Special notes: The content entity MUST end with the END type with a value of "VCARD". The value is case-insensitive.
特别说明：内容实体必须以值为“VCARD”的结束类型结尾。该值不区分大小写。
The END property is used in conjunction with the BEGIN property to delimit an entity containing a related set of properties within a text/vcard content-type. This construct can be used instead of or in addition to wrapping separate sets of information inside additional MIME headers. It is provided for applications that wish to define content that can contain multiple entities within the same text/vcard content-type or to define content that can be identifiable outside of a MIME environment.
END属性与BEGIN属性结合使用，用于在text/vcard内容类型中分隔包含一组相关属性的实体。这个构造可以用来代替或补充在附加MIME头中包装单独的信息集。它适用于希望定义可以在同一文本/vcard内容类型中包含多个实体的内容或定义可以在MIME环境之外识别的内容的应用程序。
ABNF:
荷兰银行：
END-param = 0" " ; no parameter allowed END-value = "VCARD"
结束参数=0“”；不允许参数结束值=“VCARD”
Example:
例子：
END:VCARD
完:VCARD
Purpose: To identify the source of directory information contained in the content type.
目的：标识内容类型中包含的目录信息的源。
Value type: uri
值类型：uri
Cardinality: *
基数：*
Special notes: The SOURCE property is used to provide the means by which applications knowledgable in the given directory service protocol can obtain additional or more up-to-date information from the directory service. It contains a URI as defined in [RFC3986] and/or other information referencing the vCard to which the information pertains. When directory information is available from more than one source, the sending entity can pick what it considers to be the best source, or multiple SOURCE properties can be included.
特别说明：SOURCE属性用于提供一种方法，通过该方法，给定目录服务协议中已知的应用程序可以从目录服务获取更多或更多最新信息。它包含[RFC3986]中定义的URI和/或引用该信息所属vCard的其他信息。当目录信息来自多个源时，发送实体可以选择它认为最好的源，或者可以包括多个源属性。
ABNF:
荷兰银行：
SOURCE-param = "VALUE=uri" / pid-param / pref-param / altid-param
/ mediatype-param / any-param
SOURCE-value = URI
SOURCE-param = "VALUE=uri" / pid-param / pref-param / altid-param
/ mediatype-param / any-param
SOURCE-value = URI
Examples:
示例：
SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US
SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US
SOURCE:http://directory.example.com/addressbooks/jdoe/
Jean%20Dupont.vcf
SOURCE:http://directory.example.com/addressbooks/jdoe/
Jean%20Dupont.vcf
Purpose: To specify the kind of object the vCard represents.
目的：指定vCard表示的对象类型。
Value type: A single text value.
值类型：单个文本值。
Cardinality: *1
基数：*1
Special notes: The value may be one of the following:
特别注意：该值可以是以下值之一：
"individual" for a vCard representing a single person or entity. This is the default kind of vCard.
“个人”表示代表单个个人或实体的vCard。这是vCard的默认类型。
"group" for a vCard representing a group of persons or entities. The group's member entities can be other vCards or other types of entities, such as email addresses or web sites. A group vCard will usually contain MEMBER properties to specify the members of the group, but it is not required to. A group vCard without MEMBER properties can be considered an abstract grouping, or one whose members are known empirically (perhaps "IETF Participants" or "Republican U.S. Senators").
“组”表示代表一组人员或实体的vCard。集团的成员实体可以是其他vCard或其他类型的实体，如电子邮件地址或网站。组vCard通常包含用于指定组成员的成员属性，但不需要这样做。没有成员属性的组vCard可以被视为一个抽象的分组，或者其成员是经验上已知的（可能是“IETF参与者”或“美国共和党参议员”）。
All properties in a group vCard apply to the group as a whole, and not to any particular MEMBER. For example, an EMAIL property might specify the address of a mailing list associated with the group, and an IMPP property might refer to a group chat room.
组vCard中的所有属性都适用于整个组，而不适用于任何特定成员。例如，电子邮件属性可能指定与组关联的邮件列表的地址，IMPP属性可能引用组聊天室。
"org" for a vCard representing an organization. An organization vCard will not (in fact, MUST NOT) contain MEMBER properties, and so these are something of a cross between "individual" and "group". An organization is a single entity, but not a person. It might represent a business or government, a department or division within a business or government, a club, an association, or the like.
代表组织的vCard的“org”。组织vCard不包含（事实上，必须不包含）成员属性，因此这些属性在某种程度上是“个人”和“组”的交叉。一个组织是一个单一的实体，而不是一个人。它可能代表企业或政府、企业或政府内的部门或部门、俱乐部、协会等。
All properties in an organization vCard apply to the organization as a whole, as is the case with a group vCard. For example, an EMAIL property might specify the address of a contact point for the organization.
组织vCard中的所有属性都应用于整个组织，就像组vCard一样。例如，电子邮件属性可以指定组织的联系人地址。
"location" for a named geographical place. A location vCard will usually contain a GEO property, but it is not required to. A location vCard without a GEO property can be considered an abstract location, or one whose definition is known empirically (perhaps "New England" or "The Seashore").
指定地理位置的“位置”。位置vCard通常包含地理属性，但不要求包含。没有地理属性的位置vCard可以被视为一个抽象位置，或者其定义在经验上是已知的（可能是“新英格兰”或“海滨”）。
All properties in a location vCard apply to the location itself, and not with any entity that might exist at that location. For example, in a vCard for an office building, an ADR property might give the mailing address for the building, and a TEL property might specify the telephone number of the receptionist.
位置vCard中的所有属性都适用于该位置本身，而不适用于该位置可能存在的任何实体。例如，在办公楼的vCard中，ADR属性可能会给出办公楼的邮寄地址，而TEL属性可能会指定接待员的电话号码。
An x-name. vCards MAY include private or experimental values for KIND. Remember that x-name values are not intended for general use and are unlikely to interoperate.
一个x-名字。vCard可能包括实物的私有值或实验值。请记住，x-name值不适用于一般用途，不太可能进行互操作。
An iana-token. Additional values may be registered with IANA (see Section 10.3.4). A new value's specification document MUST specify which properties make sense for that new kind of vCard and which do not.
iana代币。可向IANA登记附加值（见第10.3.4节）。新值的规范文档必须指定哪些属性对新类型的vCard有意义，哪些没有意义。
Implementations MUST support the specific string values defined above. If this property is absent, "individual" MUST be assumed as the default. If this property is present but the implementation does not understand its value (the value is an x-name or iana-token that the implementation does not support), the implementation SHOULD act in a neutral way, which usually means treating the vCard as though its kind were "individual". The presence of MEMBER properties MAY, however, be taken as an indication that the unknown kind is an extension of "group".
实现必须支持上面定义的特定字符串值。如果缺少此属性，则必须假定“个人”为默认值。如果存在此属性，但实现不了解其值（该值是实现不支持的x名称或iana标记），则实现应以中立的方式运行，这通常意味着将vCard视为“单独的”。然而，成员属性的存在可被视为表示未知类型是“组”的扩展。
Clients often need to visually distinguish contacts based on what they represent, and the KIND property provides a direct way for them to do so. For example, when displaying contacts in a list, an icon could be displayed next to each one, using distinctive icons for the different kinds; a client might use an outline of a single person to represent an "individual", an outline of multiple people to represent a "group", and so on. Alternatively, or in addition, a client might choose to segregate different kinds of vCards to different panes, tabs, or selections in the user interface.
客户通常需要根据联系人所代表的内容直观地区分联系人，而KIND属性为他们提供了一种直接的方法。例如，当在列表中显示联系人时，可以在每个联系人旁边显示一个图标，使用不同类型的独特图标；客户可以使用一个人的轮廓来表示“个人”，使用多个人的轮廓来表示“群体”，等等。或者，客户机可以选择将不同类型的vCard隔离到用户界面中的不同窗格、选项卡或选项中。
Some clients might also make functional distinctions among the kinds, ignoring "location" vCards for some purposes and considering only "location" vCards for others.
一些客户可能也会对不同种类的vCard进行功能区分，在某些情况下忽略“位置”vCard，而在其他情况下只考虑“位置”vCard。
When designing those sorts of visual and functional distinctions, client implementations have to decide how to fit unsupported kinds into the scheme. What icon is used for them? The one for "individual"? A unique one, such as an icon of a question mark? Which tab do they go into? It is beyond the scope of this specification to answer these questions, but these are things implementers need to consider.
在设计这些视觉和功能差异时，客户机实现必须决定如何将不受支持的类型融入方案中。他们使用什么图标？“个人”的那个？一个独特的图标，比如问号的图标？他们要付哪个账单？回答这些问题超出了本规范的范围，但这些是实现者需要考虑的问题。
ABNF:
荷兰银行：
KIND-param = "VALUE=text" / any-param
KIND-value = "individual" / "group" / "org" / "location"
/ iana-token / x-name
KIND-param = "VALUE=text" / any-param
KIND-value = "individual" / "group" / "org" / "location"
/ iana-token / x-name
Example:
例子：
This represents someone named Jane Doe working in the marketing department of the North American division of ABC Inc.
这是ABC公司北美分部市场营销部的Jane Doe。
BEGIN:VCARD
VERSION:4.0
KIND:individual
FN:Jane Doe
ORG:ABC\, Inc.;North American Division;Marketing
END:VCARD
BEGIN:VCARD
VERSION:4.0
KIND:individual
FN:Jane Doe
ORG:ABC\, Inc.;North American Division;Marketing
END:VCARD
This represents the department itself, commonly known as ABC Marketing.
这代表了部门本身，通常称为ABC营销。
BEGIN:VCARD
VERSION:4.0
KIND:org
FN:ABC Marketing
ORG:ABC\, Inc.;North American Division;Marketing
END:VCARD
BEGIN:VCARD
VERSION:4.0
KIND:org
FN:ABC Marketing
ORG:ABC\, Inc.;North American Division;Marketing
END:VCARD
Purpose: To include extended XML-encoded vCard data in a plain vCard.
目的：在普通vCard中包含扩展的XML编码vCard数据。
Value type: A single text value.
值类型：单个文本值。
Cardinality: *
基数：*
Special notes: The content of this property is a single XML 1.0 [W3C.REC-xml-20081126] element whose namespace MUST be explicitly specified using the xmlns attribute and MUST NOT be the vCard 4
特别注意：此属性的内容是一个XML 1.0[W3C.REC-XML-20081126]元素，其命名空间必须使用xmlns属性显式指定，并且不能是vCard 4
namespace ("urn:ietf:params:xml:ns:vcard-4.0"). (This implies that it cannot duplicate a standard vCard property.) The element is to be interpreted as if it was contained in a <vcard> element, as defined in [RFC6351].
名称空间（“urn:ietf:params:xml:ns:vcard-4.0”）。（这意味着它不能复制标准vCard属性。）按照[RFC6351]中的定义，该元素将被解释为包含在<vCard>元素中。
The fragment is subject to normal line folding and escaping, i.e., replace all backslashes with "\\", then replace all newlines with "\n", then fold long lines.
片段进行正常的折线和转义，即用“\\”替换所有反斜杠，然后用“\n”替换所有换行，然后折叠长线。
Support for this property is OPTIONAL, but implementations of this specification MUST preserve instances of this property when propagating vCards.
对此属性的支持是可选的，但在传播vCard时，此规范的实现必须保留此属性的实例。
See [RFC6351] for more information on the intended use of this property.
有关该物业预期用途的更多信息，请参见[RFC6351]。
ABNF:
荷兰银行：
XML-param = "VALUE=text" / altid-param
XML-value = text
XML-param = "VALUE=text" / altid-param
XML-value = text
These types are used to capture information associated with the identification and naming of the entity associated with the vCard.
这些类型用于捕获与vCard关联的实体的标识和命名相关的信息。
Purpose: To specify the formatted text corresponding to the name of the object the vCard represents.
目的：指定与vCard表示的对象名称相对应的格式化文本。
Value type: A single text value.
值类型：单个文本值。
Cardinality: 1*
基数：1*
Special notes: This property is based on the semantics of the X.520 Common Name attribute [CCITT.X520.1988]. The property MUST be present in the vCard object.
特别说明：此属性基于X.520通用名称属性[CCITT.X520.1988]的语义。该属性必须存在于vCard对象中。
ABNF:
荷兰银行：
FN-param = "VALUE=text" / type-param / language-param / altid-param
/ pid-param / pref-param / any-param
FN-value = text
FN-param = "VALUE=text" / type-param / language-param / altid-param
/ pid-param / pref-param / any-param
FN-value = text
Example:
例子：
FN:Mr. John Q. Public\, Esq.
FN:John Q.Public先生，Esq。
Purpose: To specify the components of the name of the object the vCard represents.
目的：指定vCard表示的对象名称的组件。
Value type: A single structured text value. Each component can have multiple values.
值类型：单个结构化文本值。每个组件可以有多个值。
Cardinality: *1
基数：*1
Special note: The structured property value corresponds, in sequence, to the Family Names (also known as surnames), Given Names, Additional Names, Honorific Prefixes, and Honorific Suffixes. The text components are separated by the SEMICOLON character (U+003B). Individual text components can include multiple text values separated by the COMMA character (U+002C). This property is based on the semantics of the X.520 individual name attributes [CCITT.X520.1988]. The property SHOULD be present in the vCard object when the name of the object the vCard represents follows the X.520 model.
特别注意：结构化属性值按顺序对应于姓氏（也称为姓氏）、给定名称、附加名称、敬语前缀和敬语后缀。文本组件由分号字符（U+003B）分隔。单个文本组件可以包括由逗号字符（U+002C）分隔的多个文本值。此属性基于X.520单个名称属性的语义[CCITT.X520.1988]。当vCard表示的对象的名称遵循X.520模型时，vCard对象中应存在该属性。
The SORT-AS parameter MAY be applied to this property.
SORT-AS参数可应用于此属性。
ABNF:
荷兰银行：
N-param = "VALUE=text" / sort-as-param / language-param
/ altid-param / any-param
N-value = list-component 4(";" list-component)
N-param = "VALUE=text" / sort-as-param / language-param
/ altid-param / any-param
N-value = list-component 4(";" list-component)
Examples:
示例：
N:Public;John;Quinlan;Mr.;Esq.
N：公众；厕所；昆兰；先生Esq。
N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
史蒂文森；厕所；腓力，保罗；博士Jr.，医学博士，A.C.P。
Purpose: To specify the text corresponding to the nickname of the object the vCard represents.
目的：指定vCard所代表对象的昵称对应的文本。
Value type: One or more text values separated by a COMMA character (U+002C).
值类型：由逗号字符（U+002C）分隔的一个或多个文本值。
Cardinality: *
基数：*
Special note: The nickname is the descriptive name given instead of or in addition to the one belonging to the object the vCard represents. It can also be used to specify a familiar form of a proper name specified by the FN or N properties.
特别注意：昵称是一个描述性名称，而不是vCard所代表对象的名称，或者是该名称的附加名称。它还可以用于指定FN或N属性指定的专有名称的熟悉形式。
ABNF:
荷兰银行：
NICKNAME-param = "VALUE=text" / type-param / language-param
/ altid-param / pid-param / pref-param / any-param
NICKNAME-value = text-list
NICKNAME-param = "VALUE=text" / type-param / language-param
/ altid-param / pid-param / pref-param / any-param
NICKNAME-value = text-list
Examples:
示例：
NICKNAME:Robbie
绰号：罗比
NICKNAME:Jim,Jimmie
绰号：吉姆，吉米
NICKNAME;TYPE=work:Boss
NICKNAME;TYPE=work:Boss
Purpose: To specify an image or photograph information that annotates some aspect of the object the vCard represents.
目的：指定图像或照片信息，以注释vCard所代表对象的某些方面。
Value type: A single URI.
值类型：单个URI。
Cardinality: *
基数：*
ABNF:
荷兰银行：
PHOTO-param = "VALUE=uri" / altid-param / type-param
/ mediatype-param / pref-param / pid-param / any-param
PHOTO-value = URI
PHOTO-param = "VALUE=uri" / altid-param / type-param
/ mediatype-param / pref-param / pid-param / any-param
PHOTO-value = URI
Examples:
示例：
PHOTO:http://www.example.com/pub/photos/jqpublic.gif
PHOTO:http://www.example.com/pub/photos/jqpublic.gif
PHOTO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhv
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...remainder of base64-encoded data...>
PHOTO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhv
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...remainder of base64-encoded data...>
Purpose: To specify the birth date of the object the vCard represents.
目的：指定vCard所代表对象的出生日期。
Value type: The default is a single date-and-or-time value. It can also be reset to a single text value.
值类型：默认为单个日期和/或时间值。也可以将其重置为单个文本值。
Cardinality: *1
基数：*1
ABNF:
荷兰银行：
BDAY-param = BDAY-param-date / BDAY-param-text BDAY-value = date-and-or-time / text ; Value and parameter MUST match.
b日期参数=b日期参数日期/b日期参数文本b日期值=日期和/或时间/text；值和参数必须匹配。
BDAY-param-date = "VALUE=date-and-or-time"
BDAY-param-text = "VALUE=text" / language-param
BDAY-param-date = "VALUE=date-and-or-time"
BDAY-param-text = "VALUE=text" / language-param
BDAY-param =/ altid-param / calscale-param / any-param ; calscale-param can only be present when BDAY-value is ; date-and-or-time and actually contains a date or date-time.
b日期参数=/altid参数/calscale参数/任意参数；calscale参数只能在BDAY值为时出现；日期和/或时间，实际包含日期或日期时间。
Examples:
示例：
BDAY:19960415
BDAY:--0415
BDAY;19531015T231000Z
BDAY;VALUE=text:circa 1800
BDAY:19960415
BDAY:--0415
BDAY;19531015T231000Z
BDAY;VALUE=text:circa 1800
Purpose: The date of marriage, or equivalent, of the object the vCard represents.
目的：vCard所代表对象的结婚日期或同等日期。
Value type: The default is a single date-and-or-time value. It can also be reset to a single text value.
值类型：默认为单个日期和/或时间值。也可以将其重置为单个文本值。
Cardinality: *1
基数：*1
ABNF:
荷兰银行：
ANNIVERSARY-param = "VALUE=" ("date-and-or-time" / "text")
ANNIVERSARY-value = date-and-or-time / text
; Value and parameter MUST match.
ANNIVERSARY-param = "VALUE=" ("date-and-or-time" / "text")
ANNIVERSARY-value = date-and-or-time / text
; Value and parameter MUST match.
ANNIVERSARY-param =/ altid-param / calscale-param / any-param ; calscale-param can only be present when ANNIVERSARY-value is ; date-and-or-time and actually contains a date or date-time.
周年参数=/altid参数/calscale参数/任何参数；calscale参数只能在周年值为时出现；日期和/或时间，实际包含日期或日期时间。
Examples:
示例：
ANNIVERSARY:19960415
周年纪念：19960415
Purpose: To specify the components of the sex and gender identity of the object the vCard represents.
目的：指定vCard所代表对象的性别和性别标识的组成部分。
Value type: A single structured value with two components. Each component has a single text value.
值类型：包含两个组件的单个结构化值。每个组件都有一个文本值。
Cardinality: *1
基数：*1
Special notes: The components correspond, in sequence, to the sex (biological), and gender identity. Each component is optional.
特别说明：这些成分按顺序对应于性别（生物学）和性别身份。每个组件都是可选的。
Sex component: A single letter. M stands for "male", F stands for "female", O stands for "other", N stands for "none or not applicable", U stands for "unknown".
性别成分：一个字母。M代表“男性”，F代表“女性”，O代表“其他”，N代表“无或不适用”，U代表“未知”。
Gender identity component: Free-form text.
性别认同部分：自由形式文本。
ABNF:
荷兰银行：
GENDER-param = "VALUE=text" / any-param
GENDER-value = sex [";" text]
GENDER-param = "VALUE=text" / any-param
GENDER-value = sex [";" text]
sex = "" / "M" / "F" / "O" / "N" / "U"
sex = "" / "M" / "F" / "O" / "N" / "U"
Examples:
示例：
GENDER:M
GENDER:F
GENDER:M;Fellow
GENDER:F;grrrl
GENDER:O;intersex
GENDER:;it's complicated
GENDER:M
GENDER:F
GENDER:M;Fellow
GENDER:F;grrrl
GENDER:O;intersex
GENDER:;it's complicated
These types are concerned with information related to the delivery addressing or label for the vCard object.
这些类型涉及与vCard对象的传递地址或标签相关的信息。
Purpose: To specify the components of the delivery address for the vCard object.
目的：指定vCard对象的传递地址的组件。
Value type: A single structured text value, separated by the SEMICOLON character (U+003B).
值类型：单个结构化文本值，由分号字符（U+003B）分隔。
Cardinality: *
基数：*
Special notes: The structured type value consists of a sequence of
address components. The component values MUST be specified in
their corresponding position. The structured type value
corresponds, in sequence, to
the post office box;
the extended address (e.g., apartment or suite number);
the street address;
the locality (e.g., city);
the region (e.g., state or province);
the postal code;
the country name (full name in the language specified in
Section 5.1).
Special notes: The structured type value consists of a sequence of
address components. The component values MUST be specified in
their corresponding position. The structured type value
corresponds, in sequence, to
the post office box;
the extended address (e.g., apartment or suite number);
the street address;
the locality (e.g., city);
the region (e.g., state or province);
the postal code;
the country name (full name in the language specified in
Section 5.1).
When a component value is missing, the associated component separator MUST still be specified.
缺少组件值时，仍必须指定关联的组件分隔符。
Experience with vCard 3 has shown that the first two components (post office box and extended address) are plagued with many interoperability issues. To ensure maximal interoperability, their values SHOULD be empty.
vCard 3的经验表明，前两个组件（邮政信箱和扩展地址）存在许多互操作性问题。为了确保最大的互操作性，它们的值应该为空。
The text components are separated by the SEMICOLON character (U+003B). Where it makes semantic sense, individual text components can include multiple text values (e.g., a "street" component with multiple lines) separated by the COMMA character (U+002C).
文本组件由分号字符（U+003B）分隔。在语义上有意义的地方，单个文本组件可以包括多个文本值（例如，具有多行的“street”组件），由逗号字符（U+002C）分隔。
The property can include the "PREF" parameter to indicate the preferred delivery address when more than one address is specified.
属性可以包含“PREF”参数，以在指定多个地址时指示首选的传递地址。
The GEO and TZ parameters MAY be used with this property.
GEO和TZ参数可用于此属性。
The property can also include a "LABEL" parameter to present a delivery address label for the address. Its value is a plain-text string representing the formatted address. Newlines are encoded as \n, as they are for property values.
该属性还可以包含一个“LABEL”参数，以显示该地址的传递地址标签。它的值是表示格式化地址的纯文本字符串。换行符编码为\n，正如它们用于属性值一样。
ABNF:
荷兰银行：
label-param = "LABEL=" param-value
label param=“label=”参数值
ADR-param = "VALUE=text" / label-param / language-param
/ geo-parameter / tz-parameter / altid-param / pid-param
/ pref-param / type-param / any-param
ADR-param = "VALUE=text" / label-param / language-param
/ geo-parameter / tz-parameter / altid-param / pid-param
/ pref-param / type-param / any-param
ADR-value = ADR-component-pobox ";" ADR-component-ext ";"
ADR-component-street ";" ADR-component-locality ";"
ADR-component-region ";" ADR-component-code ";"
ADR-component-country
ADR-component-pobox = list-component
ADR-component-ext = list-component
ADR-component-street = list-component
ADR-component-locality = list-component
ADR-component-region = list-component
ADR-component-code = list-component
ADR-component-country = list-component
ADR-value = ADR-component-pobox ";" ADR-component-ext ";"
ADR-component-street ";" ADR-component-locality ";"
ADR-component-region ";" ADR-component-code ";"
ADR-component-country
ADR-component-pobox = list-component
ADR-component-ext = list-component
ADR-component-street = list-component
ADR-component-locality = list-component
ADR-component-region = list-component
ADR-component-code = list-component
ADR-component-country = list-component
Example: In this example, the post office box and the extended address are absent.
示例：在这个示例中，没有邮政信箱和扩展地址。
ADR;GEO="geo:12.3457,78.910";LABEL="Mr. John Q. Public, Esq.\n Mail Drop: TNE QB\n123 Main Street\nAny Town, CA 91921-1234\n U.S.A.":;;123 Main Street;Any Town;CA;91921-1234;U.S.A.
药品不良反应；GEO=“GEO:12.3457,78.910”；LABEL=“John Q.Public先生，Esq.\n投递邮件：美国加利福尼亚州南镇QB\n123 Main Street\n 91921-1234:；；主街123号;；任何城镇；钙；91921-1234;美国
These properties describe information about how to communicate with the object the vCard represents.
这些属性描述有关如何与vCard表示的对象通信的信息。
Purpose: To specify the telephone number for telephony communication with the object the vCard represents.
目的：指定与vCard表示的对象进行电话通信的电话号码。
Value type: By default, it is a single free-form text value (for backward compatibility with vCard 3), but it SHOULD be reset to a URI value. It is expected that the URI scheme will be "tel", as specified in [RFC3966], but other schemes MAY be used.
值类型：默认情况下，它是一个单独的自由格式文本值（用于与vCard 3的向后兼容性），但应该重置为URI值。如[RFC3966]所述，URI方案预计为“tel”，但也可使用其他方案。
Cardinality: *
基数：*
Special notes: This property is based on the X.520 Telephone Number attribute [CCITT.X520.1988].
特别说明：此属性基于X.520电话号码属性[CCITT.X520.1988]。
The property can include the "PREF" parameter to indicate a preferred-use telephone number.
该属性可以包括“PREF”参数，以指示首选的使用电话号码。
The property can include the parameter "TYPE" to specify intended use for the telephone number. The predefined values for the TYPE parameter are:
属性可以包括参数“TYPE”，以指定电话号码的预期用途。类型参数的预定义值为：
+-----------+-------------------------------------------------------+
| Value | Description |
+-----------+-------------------------------------------------------+
| text | Indicates that the telephone number supports text |
| | messages (SMS). |
| voice | Indicates a voice telephone number. |
| fax | Indicates a facsimile telephone number. |
| cell | Indicates a cellular or mobile telephone number. |
| video | Indicates a video conferencing telephone number. |
| pager | Indicates a paging device telephone number. |
| textphone | Indicates a telecommunication device for people with |
| | hearing or speech difficulties. |
+-----------+-------------------------------------------------------+
+-----------+-------------------------------------------------------+
| Value | Description |
+-----------+-------------------------------------------------------+
| text | Indicates that the telephone number supports text |
| | messages (SMS). |
| voice | Indicates a voice telephone number. |
| fax | Indicates a facsimile telephone number. |
| cell | Indicates a cellular or mobile telephone number. |
| video | Indicates a video conferencing telephone number. |
| pager | Indicates a paging device telephone number. |
| textphone | Indicates a telecommunication device for people with |
| | hearing or speech difficulties. |
+-----------+-------------------------------------------------------+
The default type is "voice". These type parameter values can be specified as a parameter list (e.g., TYPE=text;TYPE=voice) or as a value list (e.g., TYPE="text,voice"). The default can be overridden to another set of values by specifying one or more alternate values. For example, the default TYPE of "voice" can be reset to a VOICE and FAX telephone number by the value list TYPE="voice,fax".
默认类型为“语音”。这些类型参数值可以指定为参数列表（例如，type=text；type=voice）或值列表（例如，type=“text，voice”）。通过指定一个或多个备用值，可以将默认值替换为另一组值。例如，“语音”的默认类型可以通过值列表TYPE=“voice，FAX”重置为语音和传真电话号码。
If this property's value is a URI that can also be used for instant messaging, the IMPP (Section 6.4.3) property SHOULD be used in addition to this property.
如果此属性的值是也可用于即时消息的URI，则除此属性外，还应使用IMPP（第6.4.3节）属性。
ABNF:
荷兰银行：
TEL-param = TEL-text-param / TEL-uri-param TEL-value = TEL-text-value / TEL-uri-value ; Value and parameter MUST match.
TEL-param=TEL-text-param/TEL-uri-param-TEL-value=TEL-text-value/TEL-uri-value；值和参数必须匹配。
TEL-text-param = "VALUE=text" TEL-text-value = text
TEL text param=“VALUE=text”TEL text VALUE=text
TEL-uri-param = "VALUE=uri" / mediatype-param
TEL-uri-value = URI
TEL-uri-param = "VALUE=uri" / mediatype-param
TEL-uri-value = URI
TEL-param =/ type-param / pid-param / pref-param / altid-param
/ any-param
TEL-param =/ type-param / pid-param / pref-param / altid-param
/ any-param
type-param-tel = "text" / "voice" / "fax" / "cell" / "video"
/ "pager" / "textphone" / iana-token / x-name
; type-param-tel MUST NOT be used with a property other than TEL.
type-param-tel = "text" / "voice" / "fax" / "cell" / "video"
/ "pager" / "textphone" / iana-token / x-name
; type-param-tel MUST NOT be used with a property other than TEL.
Example:
例子：
TEL;VALUE=uri;PREF=1;TYPE="voice,home":tel:+1-555-555-5555;ext=5555
TEL;VALUE=uri;TYPE=home:tel:+33-01-23-45-67
TEL;VALUE=uri;PREF=1;TYPE="voice,home":tel:+1-555-555-5555;ext=5555
TEL;VALUE=uri;TYPE=home:tel:+33-01-23-45-67
Purpose: To specify the electronic mail address for communication with the object the vCard represents.
目的：指定与vCard所代表对象通信的电子邮件地址。
Value type: A single text value.
值类型：单个文本值。
Cardinality: *
基数：*
Special notes: The property can include tye "PREF" parameter to indicate a preferred-use email address when more than one is specified.
特别注意：当指定了多个电子邮件地址时，该属性可以包含tye“PREF”参数，以指示首选的使用电子邮件地址。
Even though the value is free-form UTF-8 text, it is likely to be interpreted by a Mail User Agent (MUA) as an "addr-spec", as defined in [RFC5322], Section 3.4.1. Readers should also be aware of the current work toward internationalized email addresses [RFC5335bis].
即使该值是自由格式UTF-8文本，邮件用户代理（MUA）也可能将其解释为[RFC5322]第3.4.1节中定义的“addr规范”。读者还应了解目前针对国际化电子邮件地址[RFC5335bis]的工作。
ABNF:
荷兰银行：
EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param
/ altid-param / any-param
EMAIL-value = text
EMAIL-param = "VALUE=text" / pid-param / pref-param / type-param
/ altid-param / any-param
EMAIL-value = text
Example:
例子：
EMAIL;TYPE=work:jqpublic@xyz.example.com
EMAIL;TYPE=work:jqpublic@xyz.example.com
EMAIL;PREF=1:jane_doe@example.com
EMAIL;PREF=1:jane_doe@example.com
Purpose: To specify the URI for instant messaging and presence protocol communications with the object the vCard represents.
目的：指定与vCard表示的对象进行即时消息和状态协议通信的URI。
Value type: A single URI.
值类型：单个URI。
Cardinality: *
基数：*
Special notes: The property may include the "PREF" parameter to indicate that this is a preferred address and has the same semantics as the "PREF" parameter in a TEL property.
特别注意：属性可能包含“PREF”参数，以指示这是首选地址，并且与TEL属性中的“PREF”参数具有相同的语义。
If this property's value is a URI that can be used for voice and/or video, the TEL property (Section 6.4.1) SHOULD be used in addition to this property.
如果此属性的值是可用于语音和/或视频的URI，则除此属性外，还应使用TEL属性（第6.4.1节）。
This property is adapted from [RFC4770], which is made obsolete by this document.
此属性改编自[RFC4770]，本文件将其作废。
ABNF:
荷兰银行：
IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
IMPP-value = URI
IMPP-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
IMPP-value = URI
Example:
例子：
IMPP;PREF=1:xmpp:alice@example.com
IMPP;PREF=1:xmpp:alice@example.com
Purpose: To specify the language(s) that may be used for contacting the entity associated with the vCard.
目的：指定可用于联系与vCard关联的实体的语言。
Value type: A single language-tag value.
值类型：单一语言标记值。
Cardinality: *
基数：*
ABNF:
荷兰银行：
LANG-param = "VALUE=language-tag" / pid-param / pref-param
/ altid-param / type-param / any-param
LANG-value = Language-Tag
LANG-param = "VALUE=language-tag" / pid-param / pref-param
/ altid-param / type-param / any-param
LANG-value = Language-Tag
Example:
例子：
LANG;TYPE=work;PREF=1:en
LANG;TYPE=work;PREF=2:fr
LANG;TYPE=home:fr
LANG;TYPE=work;PREF=1:en
LANG;TYPE=work;PREF=2:fr
LANG;TYPE=home:fr
These properties are concerned with information associated with geographical positions or regions associated with the object the vCard represents.
这些属性涉及与vCard表示的对象相关的地理位置或区域相关的信息。
Purpose: To specify information related to the time zone of the object the vCard represents.
目的：指定与vCard所代表对象的时区相关的信息。
Value type: The default is a single text value. It can also be reset to a single URI or utc-offset value.
值类型：默认为单个文本值。也可以将其重置为单个URI或utc偏移量值。
Cardinality: *
基数：*
Special notes: It is expected that names from the public-domain Olson database [TZ-DB] will be used, but this is not a restriction. See also [IANA-TZ].
特别说明：预计将使用公共域Olson数据库[TZ-DB]中的名称，但这不是限制。另见[IANA-TZ]。
Efforts are currently being directed at creating a standard URI scheme for expressing time zone information. Usage of such a scheme would ensure a high level of interoperability between implementations that support it.
目前正在努力创建一个用于表示时区信息的标准URI方案。使用这样一个方案将确保支持它的实现之间的高度互操作性。
Note that utc-offset values SHOULD NOT be used because the UTC offset varies with time -- not just because of the usual daylight saving time shifts that occur in may regions, but often entire regions will "re-base" their overall offset. The actual offset may be +/- 1 hour (or perhaps a little more) than the one given.
请注意，不应使用utc偏移量值，因为utc偏移量随时间而变化——这不仅是因为5个地区通常会发生夏令时偏移，而且通常整个地区都会“重新确定”其总偏移量。实际偏移量可能比给定偏移量+/-1小时（或稍多一点）。
ABNF:
荷兰银行：
TZ-param = "VALUE=" ("text" / "uri" / "utc-offset")
TZ-value = text / URI / utc-offset
; Value and parameter MUST match.
TZ-param = "VALUE=" ("text" / "uri" / "utc-offset")
TZ-value = text / URI / utc-offset
; Value and parameter MUST match.
TZ-param =/ altid-param / pid-param / pref-param / type-param
/ mediatype-param / any-param
TZ-param =/ altid-param / pid-param / pref-param / type-param
/ mediatype-param / any-param
Examples:
示例：
TZ:Raleigh/North America
TZ:罗利/北美
TZ;VALUE=utc-offset:-0500 ; Note: utc-offset format is NOT RECOMMENDED.
TZ；值=utc偏移量：-0500；注意：不建议使用utc偏移格式。
Purpose: To specify information related to the global positioning of the object the vCard represents.
目的：指定与vCard所代表对象的全球定位相关的信息。
Value type: A single URI.
值类型：单个URI。
Cardinality: *
基数：*
Special notes: The "geo" URI scheme [RFC5870] is particularly well suited for this property, but other schemes MAY be used.
特别说明：“geo”URI方案[RFC5870]特别适合此属性，但也可以使用其他方案。
ABNF:
荷兰银行：
GEO-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
GEO-value = URI
GEO-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
GEO-value = URI
Example:
例子：
GEO:geo:37.386013,-122.082932
地理：地理：37.386013，-122.082932
These properties are concerned with information associated with characteristics of the organization or organizational units of the object that the vCard represents.
这些属性与vCard表示的对象的组织或组织单位的特征相关联的信息有关。
Purpose: To specify the position or job of the object the vCard represents.
目的：指定vCard所代表对象的位置或作业。
Value type: A single text value.
值类型：单个文本值。
Cardinality: *
基数：*
Special notes: This property is based on the X.520 Title attribute [CCITT.X520.1988].
特别说明：此属性基于X.520标题属性[CCITT.X520.1988]。
ABNF:
荷兰银行：
TITLE-param = "VALUE=text" / language-param / pid-param
/ pref-param / altid-param / type-param / any-param
TITLE-value = text
TITLE-param = "VALUE=text" / language-param / pid-param
/ pref-param / altid-param / type-param / any-param
TITLE-value = text
Example:
例子：
TITLE:Research Scientist
标题：研究科学家
Purpose: To specify the function or part played in a particular situation by the object the vCard represents.
目的：指定vCard所代表的对象在特定情况下发挥的功能或作用。
Value type: A single text value.
值类型：单个文本值。
Cardinality: *
基数：*
Special notes: This property is based on the X.520 Business Category explanatory attribute [CCITT.X520.1988]. This property is included as an organizational type to avoid confusion with the semantics of the TITLE property and incorrect usage of that property when the semantics of this property is intended.
特别说明：此属性基于X.520业务类别解释属性[CCITT.X520.1988]。此属性作为组织类型包含，以避免与TITLE属性的语义混淆，以及在使用此属性的语义时不正确地使用该属性。
ABNF:
荷兰银行：
ROLE-param = "VALUE=text" / language-param / pid-param / pref-param
/ type-param / altid-param / any-param
ROLE-value = text
ROLE-param = "VALUE=text" / language-param / pid-param / pref-param
/ type-param / altid-param / any-param
ROLE-value = text
Example:
例子：
ROLE:Project Leader
职位：项目负责人
Purpose: To specify a graphic image of a logo associated with the object the vCard represents.
目的：指定与vCard表示的对象关联的徽标的图形图像。
Value type: A single URI.
值类型：单个URI。
Cardinality: *
基数：*
ABNF:
荷兰银行：
LOGO-param = "VALUE=uri" / language-param / pid-param / pref-param
/ type-param / mediatype-param / altid-param / any-param
LOGO-value = URI
LOGO-param = "VALUE=uri" / language-param / pid-param / pref-param
/ type-param / mediatype-param / altid-param / any-param
LOGO-value = URI
Examples:
示例：
LOGO:http://www.example.com/pub/logos/abccorp.jpg
LOGO:http://www.example.com/pub/logos/abccorp.jpg
LOGO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvc
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of base64-encoded data...>
LOGO:data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvc
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of base64-encoded data...>
Purpose: To specify the organizational name and units associated with the vCard.
目的：指定与vCard关联的组织名称和单位。
Value type: A single structured text value consisting of components separated by the SEMICOLON character (U+003B).
值类型：由分号字符（U+003B）分隔的组件组成的单个结构化文本值。
Cardinality: *
基数：*
Special notes: The property is based on the X.520 Organization Name and Organization Unit attributes [CCITT.X520.1988]. The property value is a structured type consisting of the organization name, followed by zero or more levels of organizational unit names.
特别说明：该属性基于X.520组织名称和组织单位属性[CCITT.X520.1988]。属性值是由组织名称构成的结构化类型，后跟零级或多层组织单位名称。
The SORT-AS parameter MAY be applied to this property.
SORT-AS参数可应用于此属性。
ABNF:
荷兰银行：
ORG-param = "VALUE=text" / sort-as-param / language-param
/ pid-param / pref-param / altid-param / type-param
/ any-param
ORG-value = component *(";" component)
ORG-param = "VALUE=text" / sort-as-param / language-param
/ pid-param / pref-param / altid-param / type-param
/ any-param
ORG-value = component *(";" component)
Example: A property value consisting of an organizational name, organizational unit #1 name, and organizational unit #2 name.
示例：由组织名称、组织单位#1名称和组织单位#2名称组成的属性值。
ORG:ABC\, Inc.;North American Division;Marketing
ORG:ABC\, Inc.;North American Division;Marketing
Purpose: To include a member in the group this vCard represents.
目的：将成员包括在此vCard所代表的组中。
Value type: A single URI. It MAY refer to something other than a vCard object. For example, an email distribution list could employ the "mailto" URI scheme [RFC6068] for efficiency.
值类型：单个URI。它可能指的不是vCard对象。例如，为了提高效率，电子邮件分发列表可以使用“mailto”URI方案[RFC6068]。
Cardinality: *
基数：*
Special notes: This property MUST NOT be present unless the value of the KIND property is "group".
特别说明：除非种类属性的值为“组”，否则此属性不得存在。
ABNF:
荷兰银行：
MEMBER-param = "VALUE=uri" / pid-param / pref-param / altid-param
/ mediatype-param / any-param
MEMBER-value = URI
MEMBER-param = "VALUE=uri" / pid-param / pref-param / altid-param
/ mediatype-param / any-param
MEMBER-value = URI
Examples:
示例：
BEGIN:VCARD
VERSION:4.0
KIND:group
FN:The Doe family
MEMBER:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af
MEMBER:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519
END:VCARD
BEGIN:VCARD
VERSION:4.0
FN:John Doe
UID:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af
END:VCARD
BEGIN:VCARD
VERSION:4.0
FN:Jane Doe
UID:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519
END:VCARD
BEGIN:VCARD
VERSION:4.0
KIND:group
FN:The Doe family
MEMBER:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af
MEMBER:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519
END:VCARD
BEGIN:VCARD
VERSION:4.0
FN:John Doe
UID:urn:uuid:03a0e51f-d1aa-4385-8a53-e29025acd8af
END:VCARD
BEGIN:VCARD
VERSION:4.0
FN:Jane Doe
UID:urn:uuid:b8767877-b4a1-4c70-9acc-505d3819e519
END:VCARD
BEGIN:VCARD
VERSION:4.0
KIND:group
FN:Funky distribution list
MEMBER:mailto:subscriber1@example.com
MEMBER:xmpp:subscriber2@example.com
MEMBER:sip:subscriber3@example.com
MEMBER:tel:+1-418-555-5555
END:VCARD
BEGIN:VCARD
VERSION:4.0
KIND:group
FN:Funky distribution list
MEMBER:mailto:subscriber1@example.com
MEMBER:xmpp:subscriber2@example.com
MEMBER:sip:subscriber3@example.com
MEMBER:tel:+1-418-555-5555
END:VCARD
Purpose: To specify a relationship between another entity and the entity represented by this vCard.
目的：指定另一个实体与此vCard表示的实体之间的关系。
Value type: A single URI. It can also be reset to a single text value. The text value can be used to specify textual information.
值类型：单个URI。也可以将其重置为单个文本值。文本值可用于指定文本信息。
Cardinality: *
基数：*
Special notes: The TYPE parameter MAY be used to characterize the related entity. It contains a comma-separated list of values that are registered with IANA as described in Section 10.2. The registry is pre-populated with the values defined in [xfn]. This document also specifies two additional values:
特别说明：类型参数可用于描述相关实体。它包含一个逗号分隔的值列表，这些值在IANA中注册，如第10.2节所述。注册表预先填充了[xfn]中定义的值。本文件还规定了两个附加值：
agent: an entity who may sometimes act on behalf of the entity associated with the vCard.
代理：有时可能代表与vCard相关的实体行事的实体。
emergency: indicates an emergency contact
紧急：表示紧急联系人
ABNF:
荷兰银行：
RELATED-param = RELATED-param-uri / RELATED-param-text RELATED-value = URI / text ; Parameter and value MUST match.
相关参数=相关参数uri/相关参数文本相关值=uri/文本；参数和值必须匹配。
RELATED-param-uri = "VALUE=uri" / mediatype-param
RELATED-param-text = "VALUE=text" / language-param
RELATED-param-uri = "VALUE=uri" / mediatype-param
RELATED-param-text = "VALUE=text" / language-param
RELATED-param =/ pid-param / pref-param / altid-param / type-param
/ any-param
RELATED-param =/ pid-param / pref-param / altid-param / type-param
/ any-param
type-param-related = related-type-value *("," related-type-value) ; type-param-related MUST NOT be used with a property other than ; RELATED.
类型参数相关=相关类型值*（“，”相关类型值）；type param related不能与以下属性一起使用：；相关的
related-type-value = "contact" / "acquaintance" / "friend" / "met"
/ "co-worker" / "colleague" / "co-resident"
/ "neighbor" / "child" / "parent"
/ "sibling" / "spouse" / "kin" / "muse"
/ "crush" / "date" / "sweetheart" / "me"
/ "agent" / "emergency"
related-type-value = "contact" / "acquaintance" / "friend" / "met"
/ "co-worker" / "colleague" / "co-resident"
/ "neighbor" / "child" / "parent"
/ "sibling" / "spouse" / "kin" / "muse"
/ "crush" / "date" / "sweetheart" / "me"
/ "agent" / "emergency"
Examples:
示例：
RELATED;TYPE=friend:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 RELATED;TYPE=contact:http://example.com/directory/jdoe.vcf RELATED;TYPE=co-worker;VALUE=text:Please contact my assistant Jane Doe for any inquiries.
相关的类型=朋友：urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6相关；类型=联系人：http://example.com/directory/jdoe.vcf 相关的类型=同事；VALUE=text：如有任何疑问，请联系我的助手Jane Doe。
These properties are concerned with additional explanations, such as that related to informational notes or revisions specific to the vCard.
这些属性与其他解释有关，例如与vCard特定的信息注释或修订相关的解释。
Purpose: To specify application category information about the vCard, also known as "tags".
目的：指定有关vCard的应用程序类别信息，也称为“标记”。
Value type: One or more text values separated by a COMMA character (U+002C).
值类型：由逗号字符（U+002C）分隔的一个或多个文本值。
Cardinality: *
基数：*
ABNF:
荷兰银行：
CATEGORIES-param = "VALUE=text" / pid-param / pref-param
/ type-param / altid-param / any-param
CATEGORIES-value = text-list
CATEGORIES-param = "VALUE=text" / pid-param / pref-param
/ type-param / altid-param / any-param
CATEGORIES-value = text-list
Example:
例子：
CATEGORIES:TRAVEL AGENT
类别：旅行社
CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
类别：互联网、IETF、工业、信息技术
Purpose: To specify supplemental information or a comment that is associated with the vCard.
目的：指定与vCard相关的补充信息或注释。
Value type: A single text value.
值类型：单个文本值。
Cardinality: *
基数：*
Special notes: The property is based on the X.520 Description attribute [CCITT.X520.1988].
特别说明：该属性基于X.520描述属性[CCITT.X520.1988]。
ABNF:
荷兰银行：
NOTE-param = "VALUE=text" / language-param / pid-param / pref-param
/ type-param / altid-param / any-param
NOTE-value = text
NOTE-param = "VALUE=text" / language-param / pid-param / pref-param
/ type-param / altid-param / any-param
NOTE-value = text
Example:
例子：
NOTE:This fax number is operational 0800 to 1715 EST\, Mon-Fri.
注：此传真号码为美国东部时间周一至周五0800至1715。
Purpose: To specify the identifier for the product that created the vCard object.
目的：为创建vCard对象的产品指定标识符。
Type value: A single text value.
类型值：单个文本值。
Cardinality: *1
基数：*1
Special notes: Implementations SHOULD use a method such as that specified for Formal Public Identifiers in [ISO9070] or for Universal Resource Names in [RFC3406] to ensure that the text value is unique.
特别说明：实现应使用[ISO9070]中为正式公共标识符或[RFC3406]中为通用资源名称指定的方法，以确保文本值是唯一的。
ABNF:
荷兰银行：
PRODID-param = "VALUE=text" / any-param
PRODID-value = text
PRODID-param = "VALUE=text" / any-param
PRODID-value = text
Example:
例子：
PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
Purpose: To specify revision information about the current vCard.
目的：指定有关当前vCard的修订信息。
Value type: A single timestamp value.
值类型：单个时间戳值。
Cardinality: *1
基数：*1
Special notes: The value distinguishes the current revision of the information in this vCard for other renditions of the information.
特别说明：该值将此vCard中信息的当前版本与其他版本的信息区分开来。
ABNF:
荷兰银行：
REV-param = "VALUE=timestamp" / any-param
REV-value = timestamp
REV-param = "VALUE=timestamp" / any-param
REV-value = timestamp
Example:
例子：
REV:19951031T222710Z
版次：19951031T222710Z
Purpose: To specify a digital sound content information that annotates some aspect of the vCard. This property is often used to specify the proper pronunciation of the name property value of the vCard.
目的：指定用于注释vCard某些方面的数字声音内容信息。此属性通常用于指定vCard的name属性值的正确发音。
Value type: A single URI.
值类型：单个URI。
Cardinality: *
基数：*
ABNF:
荷兰银行：
SOUND-param = "VALUE=uri" / language-param / pid-param / pref-param
/ type-param / mediatype-param / altid-param
/ any-param
SOUND-value = URI
SOUND-param = "VALUE=uri" / language-param / pid-param / pref-param
/ type-param / mediatype-param / altid-param
/ any-param
SOUND-value = URI
Example:
例子：
SOUND:CID:JOHNQPUBLIC.part8.19960229T080000.xyzMail@example.com
SOUND:CID:JOHNQPUBLIC.part8.19960229T080000.xyzMail@example.com
SOUND:data:audio/basic;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIh
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of base64-encoded data...>
SOUND:data:audio/basic;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIh
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of base64-encoded data...>
Purpose: To specify a value that represents a globally unique identifier corresponding to the entity associated with the vCard.
目的：指定一个值，该值表示与vCard关联的实体相对应的全局唯一标识符。
Value type: A single URI value. It MAY also be reset to free-form text.
值类型：单个URI值。也可以将其重置为自由格式文本。
Cardinality: *1
基数：*1
Special notes: This property is used to uniquely identify the object that the vCard represents. The "uuid" URN namespace defined in [RFC4122] is particularly well suited to this task, but other URI schemes MAY be used. Free-form text MAY also be used.
特别说明：此属性用于唯一标识vCard表示的对象。[RFC4122]中定义的“uuid”URN命名空间特别适合于此任务，但也可以使用其他URI方案。也可以使用自由格式文本。
ABNF:
荷兰银行：
UID-param = UID-uri-param / UID-text-param UID-value = UID-uri-value / UID-text-value ; Value and parameter MUST match.
UID-param=UID-uri-param/UID-text-param-UID-value=UID-uri-value/UID-text-value；值和参数必须匹配。
UID-uri-param = "VALUE=uri" UID-uri-value = URI
UID uri param=“VALUE=uri”UID uri VALUE=uri
UID-text-param = "VALUE=text" UID-text-value = text
UID text param=“VALUE=text”UID text VALUE=text
UID-param =/ any-param
UID param=/任何参数
Example:
例子：
UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
Purpose: To give a global meaning to a local PID source identifier.
目的：为本地PID源标识符赋予全局含义。
Value type: A semicolon-separated pair of values. The first field is a small integer corresponding to the second field of a PID parameter instance. The second field is a URI. The "uuid" URN namespace defined in [RFC4122] is particularly well suited to this task, but other URI schemes MAY be used.
值类型：以分号分隔的一对值。第一个字段是一个小整数，对应于PID参数实例的第二个字段。第二个字段是URI。[RFC4122]中定义的“uuid”URN命名空间特别适合于此任务，但也可以使用其他URI方案。
Cardinality: *
基数：*
Special notes: PID source identifiers (the source identifier is the second field in a PID parameter instance) are small integers that only have significance within the scope of a single vCard instance. Each distinct source identifier present in a vCard MUST have an associated CLIENTPIDMAP. See Section 7 for more details on the usage of CLIENTPIDMAP.
特别说明：PID源标识符（源标识符是PID参数实例中的第二个字段）是小整数，仅在单个vCard实例的范围内有效。vCard中存在的每个不同的源标识符必须具有关联的CLIENTPIDMAP。有关CLIENTPIDMAP用法的更多详细信息，请参见第7节。
PID source identifiers MUST be strictly positive. Zero is not allowed.
PID源标识符必须严格为正。不允许为零。
As a special exception, the PID parameter MUST NOT be applied to this property.
作为特殊例外，PID参数不得应用于此属性。
ABNF:
荷兰银行：
CLIENTPIDMAP-param = any-param
CLIENTPIDMAP-value = 1*DIGIT ";" URI
CLIENTPIDMAP-param = any-param
CLIENTPIDMAP-value = 1*DIGIT ";" URI
Example:
例子：
TEL;PID=3.1,4.2;VALUE=uri:tel:+1-555-555-5555
EMAIL;PID=4.1,5.2:jdoe@example.com
CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b
CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5
TEL;PID=3.1,4.2;VALUE=uri:tel:+1-555-555-5555
EMAIL;PID=4.1,5.2:jdoe@example.com
CLIENTPIDMAP:1;urn:uuid:3df403f4-5924-4bb7-b077-3c711d9eb34b
CLIENTPIDMAP:2;urn:uuid:d89c9c7a-2e1b-4832-82de-7e992d95faa5
Purpose: To specify a uniform resource locator associated with the object to which the vCard refers. Examples for individuals include personal web sites, blogs, and social networking site identifiers.
目的：指定与vCard引用的对象关联的统一资源定位器。个人示例包括个人网站、博客和社交网站标识符。
Cardinality: *
基数：*
Value type: A single uri value.
值类型：单个uri值。
ABNF:
荷兰银行：
URL-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
URL-value = URI
URL-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
URL-value = URI
Example:
例子：
URL:http://example.org/restaurant.french/~chezchic.html
URL:http://example.org/restaurant.french/~chezchic.html
Purpose: To specify the version of the vCard specification used to format this vCard.
目的：指定用于格式化此vCard的vCard规范版本。
Value type: A single text value.
值类型：单个文本值。
Cardinality: 1
基数：1
Special notes: This property MUST be present in the vCard object, and it must appear immediately after BEGIN:VCARD. The value MUST be "4.0" if the vCard corresponds to this specification. Note that earlier versions of vCard allowed this property to be placed anywhere in the vCard object, or even to be absent.
特别说明：此属性必须出现在vCard对象中，并且必须在BEGIN:vCard之后立即出现。如果vCard符合本规范，则该值必须为“4.0”。请注意，vCard的早期版本允许将此属性放置在vCard对象中的任何位置，甚至不存在。
ABNF:
荷兰银行：
VERSION-param = "VALUE=text" / any-param
VERSION-value = "4.0"
VERSION-param = "VALUE=text" / any-param
VERSION-value = "4.0"
Example:
例子：
VERSION:4.0
版本：4.0
These properties are concerned with the security of communication pathways or access to the vCard.
这些属性与通信路径或vCard访问的安全性有关。
Purpose: To specify a public key or authentication certificate associated with the object that the vCard represents.
目的：指定与vCard表示的对象关联的公钥或身份验证证书。
Value type: A single URI. It can also be reset to a text value.
值类型：单个URI。也可以将其重置为文本值。
Cardinality: *
基数：*
ABNF:
荷兰银行：
KEY-param = KEY-uri-param / KEY-text-param KEY-value = KEY-uri-value / KEY-text-value ; Value and parameter MUST match.
键参数=键uri参数/键文本参数键值=键uri值/键文本值；值和参数必须匹配。
KEY-uri-param = "VALUE=uri" / mediatype-param
KEY-uri-value = URI
KEY-uri-param = "VALUE=uri" / mediatype-param
KEY-uri-value = URI
KEY-text-param = "VALUE=text" KEY-text-value = text
键文本参数=“值=文本”键文本值=文本
KEY-param =/ altid-param / pid-param / pref-param / type-param
/ any-param
KEY-param =/ altid-param / pid-param / pref-param / type-param
/ any-param
Examples:
示例：
KEY:http://www.example.com/keys/jdoe.cer
KEY:http://www.example.com/keys/jdoe.cer
KEY;MEDIATYPE=application/pgp-keys:ftp://example.com/keys/jdoe
KEY;MEDIATYPE=application/pgp-keys:ftp://example.com/keys/jdoe
KEY:data:application/pgp-keys;base64,MIICajCCAdOgAwIBAgICBE
UwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05l
<... remainder of base64-encoded data ...>
KEY:data:application/pgp-keys;base64,MIICajCCAdOgAwIBAgICBE
UwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05l
<... remainder of base64-encoded data ...>
These properties are further specified in [RFC2739].
[RFC2739]中进一步规定了这些特性。
Purpose: To specify the URI for the busy time associated with the object that the vCard represents.
目的：指定与vCard表示的对象关联的繁忙时间的URI。
Value type: A single URI value.
值类型：单个URI值。
Cardinality: *
基数：*
Special notes: Where multiple FBURL properties are specified, the default FBURL property is indicated with the PREF parameter. The FTP [RFC1738] or HTTP [RFC2616] type of URI points to an iCalendar [RFC5545] object associated with a snapshot of the next few weeks or months of busy time data. If the iCalendar object is represented as a file or document, its file extension should be ".ifb".
特别注意：如果指定了多个FBURL属性，则默认FBURL属性将使用PREF参数指示。FTP[RFC1738]或HTTP[RFC2616]类型的URI指向与接下来几周或几个月繁忙时间数据的快照相关联的iCalendar[RFC5545]对象。如果iCalendar对象表示为文件或文档，则其文件扩展名应为“.ifb”。
ABNF:
荷兰银行：
FBURL-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
FBURL-value = URI
FBURL-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
FBURL-value = URI
Examples:
示例：
FBURL;PREF=1:http://www.example.com/busy/janedoe
FBURL;MEDIATYPE=text/calendar:ftp://example.com/busy/project-a.ifb
FBURL;PREF=1:http://www.example.com/busy/janedoe
FBURL;MEDIATYPE=text/calendar:ftp://example.com/busy/project-a.ifb
Purpose: To specify the calendar user address [RFC5545] to which a scheduling request [RFC5546] should be sent for the object represented by the vCard.
目的：指定日历用户地址[RFC5545]，vCard表示的对象的调度请求[RFC5546]应发送到该地址。
Value type: A single URI value.
值类型：单个URI值。
Cardinality: *
基数：*
Special notes: Where multiple CALADRURI properties are specified, the default CALADRURI property is indicated with the PREF parameter.
特别注意：如果指定了多个CALADRURI属性，则默认的CALADRURI属性用PREF参数表示。
ABNF:
荷兰银行：
CALADRURI-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
CALADRURI-value = URI
CALADRURI-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
CALADRURI-value = URI
Example:
例子：
CALADRURI;PREF=1:mailto:janedoe@example.com
CALADRURI:http://example.com/calendar/jdoe
CALADRURI;PREF=1:mailto:janedoe@example.com
CALADRURI:http://example.com/calendar/jdoe
Purpose: To specify the URI for a calendar associated with the object represented by the vCard.
目的：为与vCard表示的对象关联的日历指定URI。
Value type: A single URI value.
值类型：单个URI值。
Cardinality: *
基数：*
Special notes: Where multiple CALURI properties are specified, the default CALURI property is indicated with the PREF parameter. The property should contain a URI pointing to an iCalendar [RFC5545]
特别注意：如果指定了多个CALURI属性，则默认的CALURI属性用PREF参数表示。属性应包含指向iCalendar[RFC5545]的URI
object associated with a snapshot of the user's calendar store. If the iCalendar object is represented as a file or document, its file extension should be ".ics".
与用户日历存储的快照关联的对象。如果iCalendar对象表示为文件或文档，则其文件扩展名应为“.ics”。
ABNF:
荷兰银行：
CALURI-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
CALURI-value = URI
CALURI-param = "VALUE=uri" / pid-param / pref-param / type-param
/ mediatype-param / altid-param / any-param
CALURI-value = URI
Examples:
示例：
CALURI;PREF=1:http://cal.example.com/calA
CALURI;MEDIATYPE=text/calendar:ftp://ftp.example.com/calA.ics
CALURI;PREF=1:http://cal.example.com/calA
CALURI;MEDIATYPE=text/calendar:ftp://ftp.example.com/calA.ics
The properties and parameters defined by this document can be extended. Non-standard, private properties and parameters with a name starting with "X-" may be defined bilaterally between two cooperating agents without outside registration or standardization.
可以扩展此文档定义的属性和参数。名称以“X-”开头的非标准私有属性和参数可在两个合作代理之间进行双边定义，无需外部注册或标准化。
vCard data often needs to be synchronized between devices. In this context, synchronization is defined as the intelligent merging of two representations of the same object. vCard 4.0 includes mechanisms to aid this process.
vCard数据通常需要在设备之间同步。在此上下文中，同步被定义为同一对象的两个表示的智能合并。vCard 4.0包括帮助此过程的机制。
Two mechanisms are available: the UID property is used to match multiple instances of the same vCard, while the PID parameter is used to match multiple instances of the same property.
有两种机制可用：UID属性用于匹配同一vCard的多个实例，而PID参数用于匹配同一属性的多个实例。
The term "matching" is used here to mean recognizing that two instances are in fact representations of the same object. For example, a single vCard that is shared with someone results in two vCard instances. After they have evolved separately, they still represent the same object, and therefore may be matched by a synchronization engine.
术语“匹配”在这里用于表示认识到两个实例实际上是同一对象的表示。例如，与某人共享的单个vCard会导致两个vCard实例。在它们分别进化之后，它们仍然表示相同的对象，因此可以通过同步引擎进行匹配。
vCard instances for which the UID properties (Section 6.7.6) are equivalent MUST be matched. Equivalence is determined as specified in [RFC3986], Section 6.
必须匹配UID属性（第6.7.6节）等效的vCard实例。根据[RFC3986]第6节的规定确定等效性。
In all other cases, vCard instances MAY be matched at the discretion of the synchronization engine.
在所有其他情况下，同步引擎可自行决定是否匹配vCard实例。
Property instances belonging to unmatched vCards MUST NOT be matched.
属于不匹配vCard的属性实例不能匹配。
Property instances whose name (e.g., EMAIL, TEL, etc.) is not the same MUST NOT be matched.
名称（如电子邮件、电话等）不同的属性实例不得匹配。
Property instances whose name is CLIENTPIDMAP are handled separately and MUST NOT be matched. The synchronization MUST ensure that there is consistency of CLIENTPIDMAPs among matched vCard instances.
名称为CLIENTPIDMAP的属性实例是单独处理的，不能匹配。同步必须确保在匹配的vCard实例之间存在CLIENTPIDMAPs的一致性。
Property instances belonging to matched vCards, whose name is the same, and whose maximum cardinality is 1, MUST be matched.
属于匹配vCard的属性实例（名称相同，最大基数为1）必须匹配。
Property instances belonging to matched vCards, whose name is the same, and whose PID parameters match, MUST be matched. See Section 7.1.3 for details on PID matching.
属于匹配vCard的属性实例（其名称相同且PID参数匹配）必须匹配。有关PID匹配的详细信息，请参见第7.1.3节。
In all other cases, property instances MAY be matched at the discretion of the synchronization engine.
在所有其他情况下，同步引擎可以自行决定是否匹配属性实例。
Two PID values for which the first fields are equivalent represent the same local value.
第一个字段等效的两个PID值表示相同的局部值。
Two PID values representing the same local value and for which the second fields point to CLIENTPIDMAP properties whose second field URIs are equivalent (as specified in [RFC3986], Section 6) also represent the same global value.
两个PID值表示相同的局部值，第二个字段指向第二个字段URI等效的CLIENTPIDMAP属性（如[RFC3986]第6节所述），也表示相同的全局值。
PID parameters for which at least one pair of their values represent the same global value MUST be matched.
必须匹配至少一对值表示相同全局值的PID参数。
In all other cases, PID parameters MAY be matched at the discretion of the synchronization engine.
在所有其他情况下，同步引擎可自行决定匹配PID参数。
For example, PID value "5.1", in the first vCard below, and PID value "5.2", in the second vCard below, represent the same global value.
例如，下面第一个vCard中的PID值“5.1”和下面第二个vCard中的PID值“5.2”表示相同的全局值。
BEGIN:VCARD
VERSION:4.0
EMAIL;PID=4.2,5.1:jdoe@example.com
CLIENTPIDMAP:1;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527
CLIENTPIDMAP:2;urn:uuid:42bcd5a7-1699-4514-87b4-056edf68e9cc
END:VCARD
BEGIN:VCARD
VERSION:4.0
EMAIL;PID=4.2,5.1:jdoe@example.com
CLIENTPIDMAP:1;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527
CLIENTPIDMAP:2;urn:uuid:42bcd5a7-1699-4514-87b4-056edf68e9cc
END:VCARD
BEGIN:VCARD
VERSION:4.0
EMAIL;PID=5.1,5.2:john@example.com
CLIENTPIDMAP:1;urn:uuid:0c75c629-6a8d-4d5e-a07f-1bb35846854d
CLIENTPIDMAP:2;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527
END:VCARD
BEGIN:VCARD
VERSION:4.0
EMAIL;PID=5.1,5.2:john@example.com
CLIENTPIDMAP:1;urn:uuid:0c75c629-6a8d-4d5e-a07f-1bb35846854d
CLIENTPIDMAP:2;urn:uuid:3eef374e-7179-4196-a914-27358c3e6527
END:VCARD
The following simple vCard is first created on a given device.
以下简单vCard首先在给定设备上创建。
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN;PID=1.1:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN;PID=1.1:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD
This new vCard is assigned the UID "urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1" by the creating device. The FN and EMAIL properties are assigned the same local value of 1, and this value is given global context by associating it with "urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556", which represents the creating device. We are at liberty to reuse the same local value since instances of different properties will never be matched. The N property has no PID because it is forbidden by its maximum cardinality of 1.
创建设备为该新vCard分配了UID“urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1”。FN和电子邮件属性被赋予相同的本地值1，该值通过将其与表示创建设备的“urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556”相关联而被赋予全局上下文。我们可以自由地重用相同的局部值，因为不同属性的实例永远不会匹配。N属性没有PID，因为它的最大基数为1。
This vCard is shared with a second device. Upon inspecting the UID property, the second device understands that this is a new vCard (i.e., unmatched) and thus the synchronization results in a simple copy.
此vCard与第二台设备共享。在检查UID属性后，第二个设备知道这是一个新的vCard（即，不匹配），因此同步会产生一个简单的副本。
A new phone number is created on the first device, then the vCard is shared with the second device. This is what the second device receives:
在第一台设备上创建新的电话号码，然后与第二台设备共享vCard。这是第二台设备接收的内容：
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN;PID=1.1:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN;PID=1.1:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD
Upon inspecting the UID property, the second device matches the vCard it received to the vCard that it already has stored. It then starts comparing the properties of the two vCards in same-named pairs.
检查UID属性后，第二个设备将其接收的vCard与已存储的vCard进行匹配。然后开始比较同一命名对中两个vCard的属性。
The FN properties are matched because the PID parameters have the same global value. Since the property value is the same, no update takes place.
FN属性是匹配的，因为PID参数具有相同的全局值。由于属性值相同，因此不会进行更新。
The N properties are matched automatically because their maximum cardinality is 1. Since the property value is the same, no update takes place.
N个属性自动匹配，因为它们的最大基数为1。由于属性值相同，因此不会进行更新。
The EMAIL properties are matched because the PID parameters have the same global value. Since the property value is the same, no update takes place.
电子邮件属性是匹配的，因为PID参数具有相同的全局值。由于属性值相同，因此不会进行更新。
The TEL property in the new vCard is not matched to any in the stored vCard because no property in the stored vCard has the same name. Therefore, this property is copied from the new vCard to the stored vCard.
新vCard中的TEL属性与存储vCard中的任何属性都不匹配，因为存储vCard中没有具有相同名称的属性。因此，此属性将从新vCard复制到存储的vCard。
The CLIENTPIDMAP property is handled separately by the synchronization engine. It ensures that it is consistent with the stored one. If it was not, the results would be up to the synchronization engine, and thus undefined by this document.
CLIENTPIDMAP属性由同步引擎单独处理。它确保它与存储的一致。如果不是，结果将由同步引擎决定，因此本文档未定义。
A new email address and a new phone number are added to the vCard on each of the two devices, and then a new synchronization event happens. Here are the vCards that are communicated to each other:
两台设备上的vCard都会添加新的电子邮件地址和电话号码，然后会发生新的同步事件。以下是相互通信的vCard：
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN;PID=1.1:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
EMAIL;PID=2.1:boss@example.com
TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
TEL;PID=2.1;VALUE=uri:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN;PID=1.1:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
EMAIL;PID=2.1:boss@example.com
TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
TEL;PID=2.1;VALUE=uri:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN;PID=1.1:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
EMAIL;PID=2.2:ceo@example.com
TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
TEL;PID=2.2;VALUE=uri:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
END:VCARD
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN;PID=1.1:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
EMAIL;PID=2.2:ceo@example.com
TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
TEL;PID=2.2;VALUE=uri:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
END:VCARD
On the first device, the same PID source identifier (1) is reused for the new EMAIL and TEL properties. On the second device, a new source identifier (2) is generated, and a corresponding CLIENTPIDMAP property is created. It contains the second device's identifier, "urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee".
在第一个设备上，相同的PID源标识符（1）被重新用于新的电子邮件和电话属性。在第二个设备上，生成新的源标识符（2），并创建相应的CLIENTPIDMAP属性。它包含第二个设备的标识符“urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee”。
The new EMAIL properties are unmatched on both sides since the PID global value is new in both cases. The sync thus results in a copy on both sides.
由于PID全局值在这两种情况下都是新的，因此新的电子邮件属性在两侧都是不匹配的。因此，同步会在两侧产生一个副本。
Although the situation appears to be the same for the TEL properties, in this case, the synchronization engine is particularly smart and matches the two new TEL properties even though their PID global values are different. Note that in this case, the rules of Section 7.1.2 state that two properties MAY be matched at the discretion of the synchronization engine. Therefore, the two properties are merged.
尽管TEL属性的情况似乎相同，但在本例中，同步引擎特别智能，并匹配两个新的TEL属性，即使它们的PID全局值不同。请注意，在这种情况下，第7.1.2节的规则规定，同步引擎可自行决定匹配两个属性。因此，这两个属性合并。
All this results in the following vCard, which is stored on both devices:
所有这些都会产生以下vCard，该vCard存储在两个设备上：
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
EMAIL;PID=2.1:boss@example.com
EMAIL;PID=2.2:ceo@example.com
TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
TEL;PID=2.1,2.2;VALUE=uri:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
END:VCARD
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
EMAIL;PID=2.1:boss@example.com
EMAIL;PID=2.2:ceo@example.com
TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
TEL;PID=2.1,2.2;VALUE=uri:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
END:VCARD
The two devices finish their synchronization procedure by simplifying their global contexts. Since they haven't talked to any other device, the following vCard is for all purposes equivalent to the above. It is also shorter.
这两个设备通过简化全局上下文来完成同步过程。由于他们没有与任何其他设备通话，因此以下vCard在所有方面都与上述vCard等效。它也比较短。
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
EMAIL;PID=2.1:boss@example.com
EMAIL;PID=3.1:ceo@example.com
TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
TEL;PID=2.1;VALUE=uri:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD
BEGIN:VCARD
VERSION:4.0
UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
FN:J. Doe
N:Doe;J.;;;
EMAIL;PID=1.1:jdoe@example.com
EMAIL;PID=2.1:boss@example.com
EMAIL;PID=3.1:ceo@example.com
TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
TEL;PID=2.1;VALUE=uri:tel:+1-666-666-6666
CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
END:VCARD
The details of global context simplification are unspecified by this document. They are left up to the synchronization engine. This example is merely intended to illustrate the possibility, which investigating would be, in the author's opinion, worthwhile.
本文件未详细说明全局上下文简化的细节。它们留给同步引擎处理。这个例子仅仅是为了说明这种可能性，在作者看来，调查这种可能性是值得的。
BEGIN:VCARD
VERSION:4.0
FN:Simon Perreault
N:Perreault;Simon;;;ing. jr,M.Sc.
BDAY:--0203
ANNIVERSARY:20090808T1430-0500
GENDER:M
BEGIN:VCARD
VERSION:4.0
FN:Simon Perreault
N:Perreault;Simon;;;ing. jr,M.Sc.
BDAY:--0203
ANNIVERSARY:20090808T1430-0500
GENDER:M
LANG;PREF=1:fr
LANG;PREF=2:en
ORG;TYPE=work:Viagenie
ADR;TYPE=work:;Suite D2-630;2875 Laurier;
Quebec;QC;G1V 2M2;Canada
TEL;VALUE=uri;TYPE="work,voice";PREF=1:tel:+1-418-656-9254;ext=102
TEL;VALUE=uri;TYPE="work,cell,voice,video,text":tel:+1-418-262-6501
EMAIL;TYPE=work:simon.perreault@viagenie.ca
GEO;TYPE=work:geo:46.772673,-71.282945
KEY;TYPE=work;VALUE=uri:
http://www.viagenie.ca/simon.perreault/simon.asc
TZ:-0500
URL;TYPE=home:http://nomis80.org
END:VCARD
LANG;PREF=1:fr
LANG;PREF=2:en
ORG;TYPE=work:Viagenie
ADR;TYPE=work:;Suite D2-630;2875 Laurier;
Quebec;QC;G1V 2M2;Canada
TEL;VALUE=uri;TYPE="work,voice";PREF=1:tel:+1-418-656-9254;ext=102
TEL;VALUE=uri;TYPE="work,cell,voice,video,text":tel:+1-418-262-6501
EMAIL;TYPE=work:simon.perreault@viagenie.ca
GEO;TYPE=work:geo:46.772673,-71.282945
KEY;TYPE=work;VALUE=uri:
http://www.viagenie.ca/simon.perreault/simon.asc
TZ:-0500
URL;TYPE=home:http://nomis80.org
END:VCARD
o Internet mail is often used to transport vCards and is subject to many well-known security attacks, including monitoring, replay, and forgery. Care should be taken by any directory service in allowing information to leave the scope of the service itself, where any access controls or confidentiality can no longer be guaranteed. Applications should also take care to display directory data in a "safe" environment.
o Internet邮件通常用于传输vCard，并受到许多众所周知的安全攻击，包括监视、重播和伪造。任何目录服务在允许信息离开服务范围时都应小心，因为在这种情况下，任何访问控制或机密性都不再能够得到保证。应用程序还应注意在“安全”环境中显示目录数据。
o vCards can carry cryptographic keys or certificates, as described in Section 6.8.1.
o vCard可以携带加密密钥或证书，如第6.8.1节所述。
o vCards often carry information that can be sensitive (e.g., birthday, address, and phone information). Although vCards have no inherent authentication or confidentiality provisions, they can easily be carried by any security mechanism that transfers MIME objects to address authentication or confidentiality (e.g., S/MIME [RFC5751], OpenPGP [RFC4880]). In cases where the confidentiality or authenticity of information contained in vCard is a concern, the vCard SHOULD be transported using one of these secure mechanisms. The KEY property (Section 6.8.1) can be used to transport the public key used by these mechanisms.
o vCard通常携带敏感信息（例如生日、地址和电话信息）。尽管vCard没有固有的身份验证或机密性规定，但任何传输MIME对象以解决身份验证或机密性的安全机制（例如S/MIME[RFC5751]，OpenPGP[RFC4880]）都可以轻松携带vCard。如果担心vCard中包含的信息的机密性或真实性，则应使用这些安全机制之一传输vCard。密钥属性（第6.8.1节）可用于传输这些机制使用的公钥。
o The information in a vCard may become out of date. In cases where the vitality of data is important to an originator of a vCard, the SOURCE property (Section 6.1.3) SHOULD be specified. In addition, the "REV" type described in Section 6.7.4 can be specified to indicate the last time that the vCard data was updated.
o vCard中的信息可能会过时。如果数据的生命力对vCard的发起人很重要，则应指定源属性（第6.1.3节）。此外，可以指定第6.7.4节中描述的“版本”类型，以指示vCard数据上次更新的时间。
o Many vCard properties may be used to transport URIs. Please refer to [RFC3986], Section 7, for considerations related to URIs.
o 许多vCard属性可用于传输URI。有关URI的注意事项，请参考[RFC3986]第7节。
IANA has registered the following Media Type (in <http://www.iana.org/>) and marked the text/directory Media Type as DEPRECATED.
IANA已注册以下媒体类型（在<http://www.iana.org/>)并将文本/目录媒体类型标记为已弃用。
To: ietf-types@iana.org
致：ietf-types@iana.org
Subject: Registration of media type text/vcard
主题：媒体类型文本/vcard的注册
Type name: text
类型名称：text
Subtype name: vcard
子类型名称：vcard
Required parameters: none
所需参数：无
Optional parameters: version
可选参数：版本
The "version" parameter is to be interpreted identically as the VERSION vCard property. If this parameter is present, all vCards in a text/vcard body part MUST have a VERSION property with value identical to that of this MIME parameter.
“版本”参数的解释与版本vCard属性相同。如果存在此参数，则文本/vcard正文部分中的所有vcard必须具有与此MIME参数值相同的VERSION属性。
"charset": as defined for text/plain [RFC2046]; encodings other than UTF-8 [RFC3629] MUST NOT be used.
“字符集”：定义为文本/普通[RFC2046]；不得使用UTF-8[RFC3629]以外的编码。
Encoding considerations: 8bit
编码注意事项：8位
Security considerations: See Section 9.
安全注意事项：见第9节。
Interoperability considerations: The text/vcard media type is intended to identify vCard data of any version. There are older specifications of vCard [RFC2426][vCard21] still in common use. While these formats are similar, they are not strictly compatible. In general, it is necessary to inspect the value of the VERSION property (see Section 6.7.9) for identifying the standard to which a given vCard object conforms.
互操作性注意事项：文本/vcard介质类型旨在标识任何版本的vcard数据。vCard[RFC2426][vCard21]的旧规格仍在普遍使用。虽然这些格式相似，但并不完全兼容。通常，有必要检查版本属性的值（见第6.7.9节），以确定给定vCard对象符合的标准。
In addition, the following media types are known to have been used to refer to vCard data. They should be considered deprecated in favor of text/vcard.
此外，已知以下介质类型已用于引用vCard数据。应将其视为不推荐使用的文本/vcard。
* text/directory * text/directory; profile=vcard * text/x-vcard
* text/目录*text/目录；配置文件=vcard*文本/x-vcard
Published specification: RFC 6350
已发布规范：RFC 6350
Applications that use this media type: They are numerous, diverse, and include mail user agents, instant messaging clients, address book applications, directory servers, and customer relationship management software.
使用此媒体类型的应用程序：它们数量众多、种类繁多，包括邮件用户代理、即时消息客户端、通讯簿应用程序、目录服务器和客户关系管理软件。
Additional information:
其他信息：
Magic number(s):
幻数：
File extension(s): .vcf .vcard
文件扩展名：.vcf.vcard
Macintosh file type code(s):
Macintosh文件类型代码：
Person & email address to contact for further information: vCard
discussion mailing list <vcarddav@ietf.org>
Person & email address to contact for further information: vCard
discussion mailing list <vcarddav@ietf.org>
Intended usage: COMMON
预期用途：普通
Restrictions on usage: none
使用限制：无
Author: Simon Perreault
作者：西蒙·佩雷尔特
Change controller: IETF
更改控制器：IETF
This section defines the process for registering new or modified vCard elements (i.e., properties, parameters, value data types, and values) with IANA.
本节定义了向IANA注册新的或修改的vCard元素（即属性、参数、值数据类型和值）的过程。
The IETF has created a mailing list, vcarddav@ietf.org, which can be used for public discussion of vCard element proposals prior to registration. Use of the mailing list is strongly encouraged. The IESG has appointed a designated expert who will monitor the vcarddav@ietf.org mailing list and review registrations.
IETF已经创建了一个邮件列表，vcarddav@ietf.org，可用于注册前vCard元素提案的公开讨论。强烈鼓励使用邮件列表。IESG已经任命了一名指定专家，负责监督vcarddav@ietf.org邮件列表和审查注册。
Registration of new vCard elements MUST be reviewed by the designated expert and published in an RFC. A Standards Track RFC is REQUIRED for the registration of new value data types that modify existing properties. A Standards Track RFC is also REQUIRED for registration of vCard elements that modify vCard elements previously documented in a Standards Track RFC.
新vCard元件的注册必须由指定专家审查，并在RFC中公布。注册修改现有属性的新值数据类型需要标准跟踪RFC。注册vCard元素时还需要标准跟踪RFC，该vCard元素可修改先前记录在标准跟踪RFC中的vCard元素。
The registration procedure begins when a completed registration template, defined in the sections below, is sent to vcarddav@ietf.org and iana@iana.org. Within two weeks, the designated expert is expected to tell IANA and the submitter of the registration whether the registration is approved, approved with minor changes, or rejected with cause. When a registration is rejected with cause, it can be re-submitted if the concerns listed in the cause are addressed. Decisions made by the designated expert can be appealed to the IESG Applications Area Director, then to the IESG. They follow the normal appeals procedure for IESG decisions.
当以下各节中定义的已完成注册模板发送到时，注册过程开始vcarddav@ietf.org和iana@iana.org. 在两周内，指定专家将告知IANA和注册提交人注册是否被批准、批准时有微小变更还是有理由拒绝。当有理由拒绝注册时，如果原因中列出的问题得到解决，则可以重新提交注册。指定专家做出的决定可向IESG应用领域总监提出上诉，然后再向IESG提出上诉。他们遵循IESG裁决的正常上诉程序。
Once the registration procedure concludes successfully, IANA creates or modifies the corresponding record in the vCard registry. The completed registration template is discarded.
注册过程成功结束后，IANA将在vCard注册表中创建或修改相应的记录。已完成的注册模板将被丢弃。
An RFC specifying new vCard elements MUST include the completed registration templates, which MAY be expanded with additional information. These completed templates are intended to go in the body of the document, not in the IANA Considerations section.
指定新vCard元素的RFC必须包括已完成的注册模板，该模板可以用其他信息展开。这些已完成的模板将放在文档正文中，而不是IANA注意事项部分。
Finally, note that there is an XML representation for vCard defined in [RFC6351]. An XML representation SHOULD be defined for new vCard elements.
最后，请注意，[RFC6351]中定义了vCard的XML表示形式。应为新vCard元素定义XML表示。
The vendor namespace is used for vCard elements associated with commercially available products. "Vendor" or "producer" are construed as equivalent and very broadly in this context.
供应商名称空间用于与商用产品关联的vCard元素。“供应商”或“生产商”在本上下文中被解释为等效且非常广泛。
A registration may be placed in the vendor namespace by anyone who needs to interchange files associated with the particular product. However, the registration formally belongs to the vendor or organization handling the vCard elements in the namespace being registered. Changes to the specification will be made at their request, as discussed in subsequent sections.
任何需要交换与特定产品关联的文件的人都可以将注册放在供应商名称空间中。但是，注册正式属于处理注册名称空间中vCard元素的供应商或组织。如后续章节所述，将根据其要求对规范进行更改。
vCard elements belonging to the vendor namespace will be distinguished by the "VND-" prefix. This is followed by an IANA-registered Private Enterprise Number (PEN), a dash, and a vCard element designation of the vendor's choosing (e.g., "VND-123456- MUDPIE").
属于供应商名称空间的vCard元素将通过“VND-”前缀进行区分。然后是IANA注册的私营企业编号（PEN）、破折号和供应商选择的vCard元素名称（例如，“VND-123456-MUDPIE”）。
While public exposure and review of vCard elements to be registered in the vendor namespace are not required, using the vcarddav@ietf.org mailing list for review is strongly encouraged to improve the quality of those specifications. Registrations in the vendor namespace may be submitted directly to the IANA.
虽然不需要公开和审查要在供应商名称空间中注册的vCard元素，但使用vcarddav@ietf.org强烈鼓励审查邮件列表，以提高这些规范的质量。供应商名称空间中的注册可以直接提交给IANA。
A property is defined by completing the following template.
属性是通过完成以下模板定义的。
Namespace: Empty for the global namespace, "VND-NNNN-" for a vendor-specific property (where NNNN is replaced by the vendor's PEN).
命名空间：对于供应商特定属性的全局命名空间“VND-NNNN-”为空（其中NNNN由供应商的笔替换）。
Property name: The name of the property.
属性名称：属性的名称。
Purpose: The purpose of the property. Give a short but clear description.
目的：财产的目的。给出一个简短但清晰的描述。
Value type: Any of the valid value types for the property value needs to be specified. The default value type also needs to be specified.
值类型：需要指定属性值的任何有效值类型。还需要指定默认值类型。
Cardinality: See Section 6.
基数：见第6节。
Property parameters: Any of the valid property parameters for the property MUST be specified.
属性参数：必须指定属性的任何有效属性参数。
Description: Any special notes about the property, how it is to be used, etc.
描述：关于该物业的任何特别说明，如何使用等。
Format definition: The ABNF for the property definition needs to be specified.
格式定义：需要指定属性定义的ABNF。
Example(s): One or more examples of instances of the property need to be specified.
示例：需要指定属性实例的一个或多个示例。
A parameter is defined by completing the following template.
通过完成以下模板定义参数。
Namespace: Empty for the global namespace, "VND-NNNN-" for a vendor-specific property (where NNNN is replaced by the vendor's PEN).
命名空间：对于供应商特定属性的全局命名空间“VND-NNNN-”为空（其中NNNN由供应商的笔替换）。
Parameter name: The name of the parameter.
参数名称：参数的名称。
Purpose: The purpose of the parameter. Give a short but clear description.
用途：参数的用途。给出一个简短但清晰的描述。
Description: Any special notes about the parameter, how it is to be used, etc.
描述：有关参数、如何使用参数等的任何特殊说明。
Format definition: The ABNF for the parameter definition needs to be specified.
格式定义：需要指定参数定义的ABNF。
Example(s): One or more examples of instances of the parameter need to be specified.
示例：需要指定参数实例的一个或多个示例。
A value data type is defined by completing the following template.
值数据类型是通过完成以下模板定义的。
Value name: The name of the value type.
值名称：值类型的名称。
Purpose: The purpose of the value type. Give a short but clear description.
目的：值类型的目的。给出一个简短但清晰的描述。
Description: Any special notes about the value type, how it is to be used, etc.
说明：有关值类型、如何使用等的任何特殊说明。
Format definition: The ABNF for the value type definition needs to be specified.
格式定义：需要指定值类型定义的ABNF。
Example(s): One or more examples of instances of the value type need to be specified.
示例：需要指定值类型实例的一个或多个示例。
A value is defined by completing the following template.
通过完成以下模板定义值。
Value: The value literal.
Value：值文本。
Purpose: The purpose of the value. Give a short but clear description.
目的：价值的目的。给出一个简短但清晰的描述。
Conformance: The vCard properties and/or parameters that can take this value needs to be specified.
一致性：需要指定可接受此值的vCard属性和/或参数。
Example(s): One or more examples of instances of the value need to be specified.
示例：需要指定值实例的一个或多个示例。
The following is a fictitious example of a registration of a vCard value:
以下是虚拟的vCard值注册示例：
Value: supervisor
价值观：主管
Purpose: It means that the related entity is the direct hierarchical superior (i.e., supervisor or manager) of the entity this vCard represents.
目的：这意味着相关实体是该vCard所代表实体的直接层级上级（即主管或经理）。
Conformance: This value can be used with the "TYPE" parameter applied on the "RELATED" property.
一致性：该值可与应用于“相关”属性的“类型”参数一起使用。
Example(s):
示例：
RELATED;TYPE=supervisor:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
RELATED;TYPE=supervisor:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
The IANA has created and will maintain the following registries for vCard elements with pointers to appropriate reference documents. The registries are grouped together under the heading "vCard Elements".
IANA已经为vCard元素创建并将维护以下注册表，其中包含指向适当参考文档的指针。这些登记册在“vCard要素”标题下分组。
The following table has been used to initialize the properties registry.
下表已用于初始化属性注册表。
+-----------+--------------+-------------------------+
| Namespace | Property | Reference |
+-----------+--------------+-------------------------+
| | SOURCE | RFC 6350, Section 6.1.3 |
| | KIND | RFC 6350, Section 6.1.4 |
| | XML | RFC 6350, Section 6.1.5 |
| | FN | RFC 6350, Section 6.2.1 |
| | N | RFC 6350, Section 6.2.2 |
| | NICKNAME | RFC 6350, Section 6.2.3 |
| | PHOTO | RFC 6350, Section 6.2.4 |
| | BDAY | RFC 6350, Section 6.2.5 |
| | ANNIVERSARY | RFC 6350, Section 6.2.6 |
| | GENDER | RFC 6350, Section 6.2.7 |
| | ADR | RFC 6350, Section 6.3.1 |
| | TEL | RFC 6350, Section 6.4.1 |
| | EMAIL | RFC 6350, Section 6.4.2 |
| | IMPP | RFC 6350, Section 6.4.3 |
| | LANG | RFC 6350, Section 6.4.4 |
| | TZ | RFC 6350, Section 6.5.1 |
| | GEO | RFC 6350, Section 6.5.2 |
| | TITLE | RFC 6350, Section 6.6.1 |
| | ROLE | RFC 6350, Section 6.6.2 |
| | LOGO | RFC 6350, Section 6.6.3 |
| | ORG | RFC 6350, Section 6.6.4 |
| | MEMBER | RFC 6350, Section 6.6.5 |
| | RELATED | RFC 6350, Section 6.6.6 |
| | CATEGORIES | RFC 6350, Section 6.7.1 |
| | NOTE | RFC 6350, Section 6.7.2 |
| | PRODID | RFC 6350, Section 6.7.3 |
| | REV | RFC 6350, Section 6.7.4 |
| | SOUND | RFC 6350, Section 6.7.5 |
| | UID | RFC 6350, Section 6.7.6 |
| | CLIENTPIDMAP | RFC 6350, Section 6.7.7 |
| | URL | RFC 6350, Section 6.7.8 |
| | VERSION | RFC 6350, Section 6.7.9 |
| | KEY | RFC 6350, Section 6.8.1 |
| | FBURL | RFC 6350, Section 6.9.1 |
| | CALADRURI | RFC 6350, Section 6.9.2 |
| | CALURI | RFC 6350, Section 6.9.3 |
+-----------+--------------+-------------------------+
+-----------+--------------+-------------------------+
| Namespace | Property | Reference |
+-----------+--------------+-------------------------+
| | SOURCE | RFC 6350, Section 6.1.3 |
| | KIND | RFC 6350, Section 6.1.4 |
| | XML | RFC 6350, Section 6.1.5 |
| | FN | RFC 6350, Section 6.2.1 |
| | N | RFC 6350, Section 6.2.2 |
| | NICKNAME | RFC 6350, Section 6.2.3 |
| | PHOTO | RFC 6350, Section 6.2.4 |
| | BDAY | RFC 6350, Section 6.2.5 |
| | ANNIVERSARY | RFC 6350, Section 6.2.6 |
| | GENDER | RFC 6350, Section 6.2.7 |
| | ADR | RFC 6350, Section 6.3.1 |
| | TEL | RFC 6350, Section 6.4.1 |
| | EMAIL | RFC 6350, Section 6.4.2 |
| | IMPP | RFC 6350, Section 6.4.3 |
| | LANG | RFC 6350, Section 6.4.4 |
| | TZ | RFC 6350, Section 6.5.1 |
| | GEO | RFC 6350, Section 6.5.2 |
| | TITLE | RFC 6350, Section 6.6.1 |
| | ROLE | RFC 6350, Section 6.6.2 |
| | LOGO | RFC 6350, Section 6.6.3 |
| | ORG | RFC 6350, Section 6.6.4 |
| | MEMBER | RFC 6350, Section 6.6.5 |
| | RELATED | RFC 6350, Section 6.6.6 |
| | CATEGORIES | RFC 6350, Section 6.7.1 |
| | NOTE | RFC 6350, Section 6.7.2 |
| | PRODID | RFC 6350, Section 6.7.3 |
| | REV | RFC 6350, Section 6.7.4 |
| | SOUND | RFC 6350, Section 6.7.5 |
| | UID | RFC 6350, Section 6.7.6 |
| | CLIENTPIDMAP | RFC 6350, Section 6.7.7 |
| | URL | RFC 6350, Section 6.7.8 |
| | VERSION | RFC 6350, Section 6.7.9 |
| | KEY | RFC 6350, Section 6.8.1 |
| | FBURL | RFC 6350, Section 6.9.1 |
| | CALADRURI | RFC 6350, Section 6.9.2 |
| | CALURI | RFC 6350, Section 6.9.3 |
+-----------+--------------+-------------------------+
The following table has been used to initialize the parameters registry.
下表已用于初始化参数注册表。
+-----------+-----------+------------------------+
| Namespace | Parameter | Reference |
+-----------+-----------+------------------------+
| | LANGUAGE | RFC 6350, Section 5.1 |
| | VALUE | RFC 6350, Section 5.2 |
| | PREF | RFC 6350, Section 5.3 |
| | ALTID | RFC 6350, Section 5.4 |
| | PID | RFC 6350, Section 5.5 |
| | TYPE | RFC 6350, Section 5.6 |
| | MEDIATYPE | RFC 6350, Section 5.7 |
| | CALSCALE | RFC 6350, Section 5.8 |
| | SORT-AS | RFC 6350, Section 5.9 |
| | GEO | RFC 6350, Section 5.10 |
| | TZ | RFC 6350, Section 5.11 |
+-----------+-----------+------------------------+
+-----------+-----------+------------------------+
| Namespace | Parameter | Reference |
+-----------+-----------+------------------------+
| | LANGUAGE | RFC 6350, Section 5.1 |
| | VALUE | RFC 6350, Section 5.2 |
| | PREF | RFC 6350, Section 5.3 |
| | ALTID | RFC 6350, Section 5.4 |
| | PID | RFC 6350, Section 5.5 |
| | TYPE | RFC 6350, Section 5.6 |
| | MEDIATYPE | RFC 6350, Section 5.7 |
| | CALSCALE | RFC 6350, Section 5.8 |
| | SORT-AS | RFC 6350, Section 5.9 |
| | GEO | RFC 6350, Section 5.10 |
| | TZ | RFC 6350, Section 5.11 |
+-----------+-----------+------------------------+
The following table has been used to initialize the parameters registry.
下表已用于初始化参数注册表。
+------------------+-------------------------+
| Value Data Type | Reference |
+------------------+-------------------------+
| BOOLEAN | RFC 6350, Section 4.4 |
| DATE | RFC 6350, Section 4.3.1 |
| DATE-AND-OR-TIME | RFC 6350, Section 4.3.4 |
| DATE-TIME | RFC 6350, Section 4.3.3 |
| FLOAT | RFC 6350, Section 4.6 |
| INTEGER | RFC 6350, Section 4.5 |
| LANGUAGE-TAG | RFC 6350, Section 4.8 |
| TEXT | RFC 6350, Section 4.1 |
| TIME | RFC 6350, Section 4.3.2 |
| TIMESTAMP | RFC 6350, Section 4.3.5 |
| URI | RFC 6350, Section 4.2 |
| UTC-OFFSET | RFC 6350, Section 4.7 |
+------------------+-------------------------+
+------------------+-------------------------+
| Value Data Type | Reference |
+------------------+-------------------------+
| BOOLEAN | RFC 6350, Section 4.4 |
| DATE | RFC 6350, Section 4.3.1 |
| DATE-AND-OR-TIME | RFC 6350, Section 4.3.4 |
| DATE-TIME | RFC 6350, Section 4.3.3 |
| FLOAT | RFC 6350, Section 4.6 |
| INTEGER | RFC 6350, Section 4.5 |
| LANGUAGE-TAG | RFC 6350, Section 4.8 |
| TEXT | RFC 6350, Section 4.1 |
| TIME | RFC 6350, Section 4.3.2 |
| TIMESTAMP | RFC 6350, Section 4.3.5 |
| URI | RFC 6350, Section 4.2 |
| UTC-OFFSET | RFC 6350, Section 4.7 |
+------------------+-------------------------+
Separate tables are used for property and parameter values.
属性值和参数值使用单独的表。
The following table is to be used to initialize the property values registry.
下表用于初始化属性值注册表。
+----------+------------+-------------------------+
| Property | Value | Reference |
+----------+------------+-------------------------+
| BEGIN | VCARD | RFC 6350, Section 6.1.1 |
| END | VCARD | RFC 6350, Section 6.1.2 |
| KIND | individual | RFC 6350, Section 6.1.4 |
| KIND | group | RFC 6350, Section 6.1.4 |
| KIND | org | RFC 6350, Section 6.1.4 |
| KIND | location | RFC 6350, Section 6.1.4 |
+----------+------------+-------------------------+
+----------+------------+-------------------------+
| Property | Value | Reference |
+----------+------------+-------------------------+
| BEGIN | VCARD | RFC 6350, Section 6.1.1 |
| END | VCARD | RFC 6350, Section 6.1.2 |
| KIND | individual | RFC 6350, Section 6.1.4 |
| KIND | group | RFC 6350, Section 6.1.4 |
| KIND | org | RFC 6350, Section 6.1.4 |
| KIND | location | RFC 6350, Section 6.1.4 |
+----------+------------+-------------------------+
The following table has been used to initialize the parameter values registry.
下表已用于初始化参数值注册表。
+------------------------+-----------+--------------+---------------+
| Property | Parameter | Value | Reference |
+------------------------+-----------+--------------+---------------+
| FN, NICKNAME, PHOTO, | TYPE | work | RFC 6350, |
| ADR, TEL, EMAIL, IMPP, | | | Section 5.6 |
| LANG, TZ, GEO, TITLE, | | | |
| ROLE, LOGO, ORG, | | | |
| RELATED, CATEGORIES, | | | |
| NOTE, SOUND, URL, KEY, | | | |
| FBURL, CALADRURI, and | | | |
| CALURI | | | |
| FN, NICKNAME, PHOTO, | TYPE | home | RFC 6350, |
| ADR, TEL, EMAIL, IMPP, | | | Section 5.6 |
| LANG, TZ, GEO, TITLE, | | | |
| ROLE, LOGO, ORG, | | | |
| RELATED, CATEGORIES, | | | |
| NOTE, SOUND, URL, KEY, | | | |
| FBURL, CALADRURI, and | | | |
| CALURI | | | |
| TEL | TYPE | text | RFC 6350, |
| | | | Section 6.4.1 |
| TEL | TYPE | voice | RFC 6350, |
| | | | Section 6.4.1 |
| TEL | TYPE | fax | RFC 6350, |
| | | | Section 6.4.1 |
| TEL | TYPE | cell | RFC 6350, |
| | | | Section 6.4.1 |
| TEL | TYPE | video | RFC 6350, |
| | | | Section 6.4.1 |
| TEL | TYPE | pager | RFC 6350, |
| | | | Section 6.4.1 |
| TEL | TYPE | textphone | RFC 6350, |
| | | | Section 6.4.1 |
| BDAY, ANNIVERSARY | CALSCALE | gregorian | RFC 6350, |
| | | | Section 5.8 |
| RELATED | TYPE | contact | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | acquaintance | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | friend | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | met | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
+------------------------+-----------+--------------+---------------+
| Property | Parameter | Value | Reference |
+------------------------+-----------+--------------+---------------+
| FN, NICKNAME, PHOTO, | TYPE | work | RFC 6350, |
| ADR, TEL, EMAIL, IMPP, | | | Section 5.6 |
| LANG, TZ, GEO, TITLE, | | | |
| ROLE, LOGO, ORG, | | | |
| RELATED, CATEGORIES, | | | |
| NOTE, SOUND, URL, KEY, | | | |
| FBURL, CALADRURI, and | | | |
| CALURI | | | |
| FN, NICKNAME, PHOTO, | TYPE | home | RFC 6350, |
| ADR, TEL, EMAIL, IMPP, | | | Section 5.6 |
| LANG, TZ, GEO, TITLE, | | | |
| ROLE, LOGO, ORG, | | | |
| RELATED, CATEGORIES, | | | |
| NOTE, SOUND, URL, KEY, | | | |
| FBURL, CALADRURI, and | | | |
| CALURI | | | |
| TEL | TYPE | text | RFC 6350, |
| | | | Section 6.4.1 |
| TEL | TYPE | voice | RFC 6350, |
| | | | Section 6.4.1 |
| TEL | TYPE | fax | RFC 6350, |
| | | | Section 6.4.1 |
| TEL | TYPE | cell | RFC 6350, |
| | | | Section 6.4.1 |
| TEL | TYPE | video | RFC 6350, |
| | | | Section 6.4.1 |
| TEL | TYPE | pager | RFC 6350, |
| | | | Section 6.4.1 |
| TEL | TYPE | textphone | RFC 6350, |
| | | | Section 6.4.1 |
| BDAY, ANNIVERSARY | CALSCALE | gregorian | RFC 6350, |
| | | | Section 5.8 |
| RELATED | TYPE | contact | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | acquaintance | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | friend | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | met | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | co-worker | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | colleague | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | co-resident | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | neighbor | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | child | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | parent | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | sibling | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | spouse | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | kin | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | muse | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | crush | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | date | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | sweetheart | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | me | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | agent | RFC 6350, |
| | | | Section 6.6.6 |
| RELATED | TYPE | emergency | RFC 6350, |
| | | | Section 6.6.6 |
+------------------------+-----------+--------------+---------------+
| RELATED | TYPE | co-worker | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | colleague | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | co-resident | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | neighbor | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | child | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | parent | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | sibling | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | spouse | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | kin | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | muse | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | crush | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | date | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | sweetheart | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | me | RFC 6350, |
| | | | Section 6.6.6 |
| | | | and [xfn] |
| RELATED | TYPE | agent | RFC 6350, |
| | | | Section 6.6.6 |
| RELATED | TYPE | emergency | RFC 6350, |
| | | | Section 6.6.6 |
+------------------------+-----------+--------------+---------------+
The authors would like to thank Tim Howes, Mark Smith, and Frank Dawson, the original authors of [RFC2425] and [RFC2426], Pete Resnick, who got this effort started and provided help along the way, as well as the following individuals who have participated in the drafting, review, and discussion of this memo:
作者要感谢[RFC2425]和[RFC2426]的原始作者Tim Howes、Mark Smith和Frank Dawson、Pete Resnick，他们开始了这项工作并在这一过程中提供了帮助，以及以下参与起草、审查和讨论本备忘录的个人：
Aki Niemi, Andy Mabbett, Alexander Mayrhofer, Alexey Melnikov, Anil Srivastava, Barry Leiba, Ben Fortuna, Bernard Desruisseaux, Bernie Hoeneisen, Bjoern Hoehrmann, Caleb Richardson, Chris Bryant, Chris Newman, Cyrus Daboo, Daisuke Miyakawa, Dan Brickley, Dan Mosedale, Dany Cauchie, Darryl Champagne, Dave Thewlis, Filip Navara, Florian Zeitz, Helge Hess, Jari Urpalainen, Javier Godoy, Jean-Luc Schellens, Joe Hildebrand, Jose Luis Gayosso, Joseph Smarr, Julian Reschke, Kepeng Li, Kevin Marks, Kevin Wu Won, Kurt Zeilenga, Lisa Dusseault, Marc Blanchet, Mark Paterson, Markus Lorenz, Michael Haardt, Mike Douglass, Nick Levinson, Peter K. Sheerin, Peter Mogensen, Peter Saint-Andre, Renato Iannella, Rohit Khare, Sly Gryphon, Stephane Bortzmeyer, Tantek Celik, and Zoltan Ordogh.
阿基·尼米、安迪·马贝特、亚历山大·梅尔霍夫、亚历克赛·梅尔尼科夫、阿尼尔·斯利瓦斯塔瓦、巴里·莱巴、本·福图纳、伯纳德·德鲁伊斯、伯尼·霍内森、比约恩·霍尔曼、卡勒布·理查森、克里斯·布莱恩特、克里斯·纽曼、赛勒斯·达布、三宅川大辅、丹·布里克利、丹·莫塞代尔、丹尼·考奇、达里尔·香槟、戴夫·泰利斯、菲利普·纳瓦拉、弗洛里安·泽茨、，海尔格·赫斯、贾里·厄帕莱宁、贾维尔·戈多伊、让·吕克·舍伦斯、乔·希尔德布兰德、何塞·路易斯·加约索、约瑟夫·斯马尔、朱利安·雷什克、李克鹏、凯文·马克斯、凯文·吴元、库尔特·泽林加、丽莎·杜肖奥、马克·布兰切特、马克·帕特森、马库斯·洛伦兹、迈克尔·哈尔德、迈克·道格拉斯、尼克·莱文森、彼得·谢林、彼得·莫根森、彼得·圣安德烈、，Renato Iannella、Rohit Khare、Sly Gryphon、Stephane Bortzmeyer、Tantek Celik和Zoltan Ordogh。
[CCITT.X520.1988] International Telephone and Telegraph Consultative Committee, "Information Technology - Open Systems Interconnection - The Directory: Selected Attribute Types", CCITT Recommendation X.520, November 1988.
[CCITT.X520.1988]国际电话电报咨询委员会，“信息技术-开放系统互连-目录：选定的属性类型”，CCITT建议X.520，1988年11月。
[IEEE.754.2008] Institute of Electrical and Electronics Engineers, "Standard for Binary Floating-Point Arithmetic", IEEE Standard 754, August 2008.
[IEEE.754.2008]电气和电子工程师协会，“二进制浮点算法标准”，IEEE标准754，2008年8月。
[ISO.8601.2000] International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, December 2000.
[ISO.8601.2000]国际标准化组织，“数据元素和交换格式-信息交换-日期和时间的表示”，ISO标准86012000年12月。
[ISO.8601.2004] International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, December 2004.
[ISO.8601.2004]国际标准化组织，“数据元素和交换格式-信息交换-日期和时间的表示”，ISO标准86012004年12月。
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996.
[RFC2045]Freed，N.和N.Borenstein，“多用途Internet邮件扩展（MIME）第一部分：Internet邮件正文格式”，RFC 20451996年11月。
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, November 1996.
[RFC2046]Freed，N.和N.Borenstein，“多用途Internet邮件扩展（MIME）第二部分：媒体类型”，RFC 20461996年11月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2739] Small, T., Hennessy, D., and F. Dawson, "Calendar Attributes for vCard and LDAP", RFC 2739, January 2000.
[RFC2739]斯莫尔，T.，轩尼诗，D.，和F.道森，“vCard和LDAP的日历属性”，RFC 2739，2000年1月。
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003.
[RFC3629]Yergeau，F.，“UTF-8，ISO 10646的转换格式”，STD 63，RFC 3629，2003年11月。
[RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966, December 2004.
[RFC3966]Schulzrinne，H.，“电话号码的电话URI”，RFC 3966，2004年12月。
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.
[RFC3986]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，2005年1月。
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally Unique IDentifier (UUID) URN Namespace", RFC 4122, July 2005.
[RFC4122]Leach，P.，Mealling，M.和R.Salz，“通用唯一标识符（UUID）URN名称空间”，RFC 4122，2005年7月。
[RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and Registration Procedures", BCP 13, RFC 4288, December 2005.
[RFC4288]Freed，N.和J.Klensin，“介质类型规范和注册程序”，BCP 13，RFC 4288，2005年12月。
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5234]Crocker，D.和P.Overell，“语法规范的扩充BNF:ABNF”，STD 68，RFC 5234，2008年1月。
[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, October 2008.
[RFC5322]Resnick，P.，Ed.“互联网信息格式”，RFC5222008年10月。
[RFC5545] Desruisseaux, B., "Internet Calendaring and Scheduling Core Object Specification (iCalendar)", RFC 5545, September 2009.
[RFC5545]Desruisseaux，B.“互联网日历和调度核心对象规范（iCalendar）”，RFC 55452009年9月。
[RFC5546] Daboo, C., "iCalendar Transport-Independent Interoperability Protocol (iTIP)", RFC 5546, December 2009.
[RFC5546]Daboo，C.，“iCalendar传输独立互操作性协议（iTIP）”，RFC5462009年12月。
[RFC5646] Phillips, A. and M. Davis, "Tags for Identifying Languages", BCP 47, RFC 5646, September 2009.
[RFC5646]Phillips，A.和M.Davis，“识别语言的标记”，BCP 47，RFC 5646，2009年9月。
[RFC5870] Mayrhofer, A. and C. Spanring, "A Uniform Resource Identifier for Geographic Locations ('geo' URI)", RFC 5870, June 2010.
[RFC5870]Mayrhofer，A.和C.Sparing，“地理位置的统一资源标识符（‘地理’URI）”，RFC 58702010年6月。
[RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC 6351, August 2011.
[RFC6351]Perreault，S.，“xCard:vCard XML表示”，RFC6351，2011年8月。
[W3C.REC-xml-20081126] Maler, E., Yergeau, F., Sperberg-McQueen, C., Paoli, J., and T. Bray, "Extensible Markup Language (XML) 1.0 (Fifth Edition)", World Wide Web Consortium Recommendation REC-xml-20081126, November 2008, <http://www.w3.org/TR/2008/REC-xml-20081126>.
[W3C.REC-xml-20081126]Maler，E.，Yergeau，F.，Sperberg McQueen，C.，Paoli，J.，和T.Bray，“可扩展标记语言（xml）1.0（第五版）”，万维网联盟建议REC-xml-20081126，2008年11月<http://www.w3.org/TR/2008/REC-xml-20081126>.
[xfn] Celik, T., Mullenweg, M., and E. Meyer, "XFN 1.1 profile", <http://gmpg.org/xfn/11>.
[xfn]Celik，T.，Mullenweg，M.，和E.Meyer，“xfn 1.1概要文件”<http://gmpg.org/xfn/11>.
[IANA-TZ] Lear, E. and P. Eggert, "IANA Procedures for Maintaining the Timezone Database", Work in Progress, May 2011.
[IANA-TZ]Lear，E.和P.Eggert，“IANA维护时区数据库的程序”，正在进行的工作，2011年5月。
[ISO9070] International Organization for Standardization, "Information Processing - SGML support facilities - Registration Procedures for Public Text Owner Identifiers", ISO 9070, April 1991.
[ISO9070]国际标准化组织，“信息处理-SGML支持设施-公共文本所有者标识符的注册程序”，ISO 9070，1991年4月。
[RFC1738] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform Resource Locators (URL)", RFC 1738, December 1994.
[RFC1738]Berners Lee，T.，Masinter，L.，和M.McCahill，“统一资源定位器（URL）”，RFC 17381994年12月。
[RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397, August 1998.
[RFC2397]Masinter，L.“数据”URL方案”，RFC 2397，1998年8月。
[RFC2425] Howes, T., Smith, M., and F. Dawson, "A MIME Content-Type for Directory Information", RFC 2425, September 1998.
[RFC2425]Howes，T.，Smith，M.，和F.Dawson，“目录信息的MIME内容类型”，RFC 24251998年9月。
[RFC2426] Dawson, F. and T. Howes, "vCard MIME Directory Profile", RFC 2426, September 1998.
[RFC2426]Dawson，F.和T.Howes，“vCard MIME目录配置文件”，RFC 2426，1998年9月。
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC2616]菲尔丁，R.，盖蒂斯，J.，莫卧儿，J.，弗莱斯蒂克，H.，马斯特，L.，利奇，P.，和T.伯纳斯李，“超文本传输协议——HTTP/1.1”，RFC 2616，1999年6月。
[RFC3282] Alvestrand, H., "Content Language Headers", RFC 3282, May 2002.
[RFC3282]Alvestrand，H.，“内容语言标题”，RFC 3282，2002年5月。
[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002.
[RFC3406]Daigle，L.，van Gulik，D.，Iannella，R.，和P.Faltstrom，“统一资源名称（URN）命名空间定义机制”，BCP 66，RFC 3406，2002年10月。
[RFC3536] Hoffman, P., "Terminology Used in Internationalization in the IETF", RFC 3536, May 2003.
[RFC3536]Hoffman，P.，“IETF国际化中使用的术语”，RFC3536，2003年5月。
[RFC4770] Jennings, C. and J. Reschke, Ed., "vCard Extensions for Instant Messaging (IM)", RFC 4770, January 2007.
[RFC4770]Jennings，C.和J.Reschke，编辑，“即时消息（IM）的vCard扩展”，RFC 47702007年1月。
[RFC4880] Callas, J., Donnerhacke, L., Finney, H., Shaw, D., and R. Thayer, "OpenPGP Message Format", RFC 4880, November 2007.
[RFC4880]Callas，J.，Donnerhacke，L.，Finney，H.，Shaw，D.，和R.Thayer，“OpenPGP消息格式”，RFC 48802007年11月。
[RFC5335bis] Yang, A. and S. Steele, "Internationalized Email Headers", Work in Progress, July 2011.
[RFC5335bis]Yang，A.和S.Steele，“国际化电子邮件标题”，正在进行的工作，2011年7月。
[RFC5751] Ramsdell, B. and S. Turner, "Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification", RFC 5751, January 2010.
[RFC5751]Ramsdell，B.和S.Turner，“安全/多用途Internet邮件扩展（S/MIME）版本3.2消息规范”，RFC 57512010年1月。
[RFC6068] Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto' URI Scheme", RFC 6068, October 2010.
[RFC6068]Duerst，M.，Masinter，L.，和J.Zawinski，“mailto”URI方案”，RFC 6068，2010年10月。
[TZ-DB] Olson, A., "Time zone code and data", <ftp://elsie.nci.nih.gov/pub/>.
[TZ-DB]奥尔森，A.，“时区代码和数据”<ftp://elsie.nci.nih.gov/pub/>.
[vCard21] Internet Mail Consortium, "vCard - The Electronic Business Card Version 2.1", September 1996.
[vCard21]互联网邮件联盟，“vCard-电子名片2.1版”，1996年9月。
This appendix contains a high-level overview of the major changes that have been made in the vCard specification from RFCs 2425 and 2426. It is incomplete, as it only lists the most important changes.
本附录概述了RFCs 2425和2426在vCard规范中所做的主要更改。它是不完整的，因为它只列出了最重要的更改。
o [RFC2425] and [RFC2426] have been merged.
o [RFC2425]和[RFC2426]已合并。
o vCard is now not only a MIME type but a stand-alone format.
o vCard现在不仅是一种MIME类型，而且是一种独立的格式。
o A proper MIME type registration form has been included.
o 已包括一份适当的MIME类型登记表。
o UTF-8 is now the only possible character set.
o UTF-8现在是唯一可能的字符集。
o New vCard elements can be registered from IANA.
o 可以从IANA注册新的vCard元素。
o The CONTEXT and CHARSET parameters are no more.
o 上下文和字符集参数不再存在。
o The NAME, MAILER, LABEL, and CLASS properties are no more.
o 名称、邮件程序、标签和类属性不再存在。
o The "intl", "dom", "postal", and "parcel" TYPE parameter values for the ADR property have been removed.
o ADR属性的“intl”、“dom”、“postal”和“parcel”类型参数值已删除。
o In-line vCards (such as the value of the AGENT property) are no longer supported.
o 不再支持内嵌vCard（例如代理属性的值）。
o The KIND, GENDER, LANG, ANNIVERSARY, XML, and CLIENTPIDMAP properties have been added.
o 添加了种类、性别、语言、周年纪念、XML和CLIENTPIDMAP属性。
o [RFC2739], which defines the FBURL, CALADRURI, CAPURI, and CALURI properties, has been merged in.
o [RFC2739]定义了FBURL、CALADRURI、CAPURI和CALURI属性，已合并到中。
o [RFC4770], which defines the IMPP property, has been merged in.
o 定义IMPP属性的[RFC4770]已合并到中。
o The "work" and "home" TYPE parameter values are now applicable to many more properties.
o “work”和“home”类型参数值现在适用于更多的特性。
o The "pref" value of the TYPE parameter is now a parameter of its own, with a positive integer value indicating the level of preference.
o 类型参数的“pref”值现在是它自己的参数，带有一个正整数值表示首选级别。
o The ALTID and PID parameters have been added.
o 增加了ALTID和PID参数。
o The MEDIATYPE parameter has been added and replaces the TYPE parameter when it was used for indicating the media type of the property's content.
o 已添加MEDIATYPE参数，并在使用该参数指示属性内容的媒体类型时替换类型参数。
Author's Address
作者地址
Simon Perreault Viagenie 2875 Laurier, suite D2-630 Quebec, QC G1V 2M2 Canada
Simon Perreault Viagenie 2875 Laurier，加拿大魁北克QC G1V 2M2 D2-630套房
Phone: +1 418 656 9254
EMail: simon.perreault@viagenie.ca
URI: http://www.viagenie.ca
Phone: +1 418 656 9254
EMail: simon.perreault@viagenie.ca
URI: http://www.viagenie.ca