Network Working Group B. Desruisseaux, Ed.
Request for Comments: 5545 Oracle
Obsoletes: 2445 September 2009
Category: Standards Track
Network Working Group B. Desruisseaux, Ed.
Request for Comments: 5545 Oracle
Obsoletes: 2445 September 2009
Category: Standards Track
Internet Calendaring and Scheduling Core Object Specification (iCalendar)
Internet日历和调度核心对象规范（iCalendar）
Abstract
摘要
This document defines the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol.
本文档定义了iCalendar数据格式，用于表示和交换日历和日程安排信息，如事件、待办事项、日记条目和忙/闲信息，与任何特定的日历服务或协议无关。
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright and License Notice
版权及许可证公告
Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2009 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 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
本文件可能包含2008年11月10日之前发布或公开的IETF文件或IETF贡献中的材料。控制某些材料版权的人员可能未授予IETF信托允许在IETF标准流程之外修改此类材料的权利。未从控制此类材料版权的人员处获得适当的许可证，不得在IETF标准流程之外修改本文件，并且不得在IETF标准流程之外创建其衍生作品，除非用于格式化
it for publication as an RFC or to translate it into languages other than English.
它可以作为RFC出版或翻译成英语以外的其他语言。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Basic Grammar and Conventions . . . . . . . . . . . . . . . . 6
2.1. Formatting Conventions . . . . . . . . . . . . . . . . . 6
2.2. Related Memos . . . . . . . . . . . . . . . . . . . . . . 7
3. iCalendar Object Specification . . . . . . . . . . . . . . . 8
3.1. Content Lines . . . . . . . . . . . . . . . . . . . . . . 8
3.1.1. List and Field Separators . . . . . . . . . . . . . . 11
3.1.2. Multiple Values . . . . . . . . . . . . . . . . . . . 11
3.1.3. Binary Content . . . . . . . . . . . . . . . . . . . 11
3.1.4. Character Set . . . . . . . . . . . . . . . . . . . . 12
3.2. Property Parameters . . . . . . . . . . . . . . . . . . . 12
3.2.1. Alternate Text Representation . . . . . . . . . . . . 13
3.2.2. Common Name . . . . . . . . . . . . . . . . . . . . . 15
3.2.3. Calendar User Type . . . . . . . . . . . . . . . . . 15
3.2.4. Delegators . . . . . . . . . . . . . . . . . . . . . 16
3.2.5. Delegatees . . . . . . . . . . . . . . . . . . . . . 16
3.2.6. Directory Entry Reference . . . . . . . . . . . . . . 17
3.2.7. Inline Encoding . . . . . . . . . . . . . . . . . . . 17
3.2.8. Format Type . . . . . . . . . . . . . . . . . . . . . 18
3.2.9. Free/Busy Time Type . . . . . . . . . . . . . . . . . 19
3.2.10. Language . . . . . . . . . . . . . . . . . . . . . . 20
3.2.11. Group or List Membership . . . . . . . . . . . . . . 20
3.2.12. Participation Status . . . . . . . . . . . . . . . . 21
3.2.13. Recurrence Identifier Range . . . . . . . . . . . . . 22
3.2.14. Alarm Trigger Relationship . . . . . . . . . . . . . 23
3.2.15. Relationship Type . . . . . . . . . . . . . . . . . . 24
3.2.16. Participation Role . . . . . . . . . . . . . . . . . 25
3.2.17. RSVP Expectation . . . . . . . . . . . . . . . . . . 25
3.2.18. Sent By . . . . . . . . . . . . . . . . . . . . . . . 26
3.2.19. Time Zone Identifier . . . . . . . . . . . . . . . . 26
3.2.20. Value Data Types . . . . . . . . . . . . . . . . . . 28
3.3. Property Value Data Types . . . . . . . . . . . . . . . . 29
3.3.1. Binary . . . . . . . . . . . . . . . . . . . . . . . 29
3.3.2. Boolean . . . . . . . . . . . . . . . . . . . . . . . 30
3.3.3. Calendar User Address . . . . . . . . . . . . . . . . 30
3.3.4. Date . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3.5. Date-Time . . . . . . . . . . . . . . . . . . . . . . 31
3.3.6. Duration . . . . . . . . . . . . . . . . . . . . . . 34
3.3.7. Float . . . . . . . . . . . . . . . . . . . . . . . . 35
3.3.8. Integer . . . . . . . . . . . . . . . . . . . . . . . 35
3.3.9. Period of Time . . . . . . . . . . . . . . . . . . . 36
3.3.10. Recurrence Rule . . . . . . . . . . . . . . . . . . . 37
3.3.11. Text . . . . . . . . . . . . . . . . . . . . . . . . 45
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Basic Grammar and Conventions . . . . . . . . . . . . . . . . 6
2.1. Formatting Conventions . . . . . . . . . . . . . . . . . 6
2.2. Related Memos . . . . . . . . . . . . . . . . . . . . . . 7
3. iCalendar Object Specification . . . . . . . . . . . . . . . 8
3.1. Content Lines . . . . . . . . . . . . . . . . . . . . . . 8
3.1.1. List and Field Separators . . . . . . . . . . . . . . 11
3.1.2. Multiple Values . . . . . . . . . . . . . . . . . . . 11
3.1.3. Binary Content . . . . . . . . . . . . . . . . . . . 11
3.1.4. Character Set . . . . . . . . . . . . . . . . . . . . 12
3.2. Property Parameters . . . . . . . . . . . . . . . . . . . 12
3.2.1. Alternate Text Representation . . . . . . . . . . . . 13
3.2.2. Common Name . . . . . . . . . . . . . . . . . . . . . 15
3.2.3. Calendar User Type . . . . . . . . . . . . . . . . . 15
3.2.4. Delegators . . . . . . . . . . . . . . . . . . . . . 16
3.2.5. Delegatees . . . . . . . . . . . . . . . . . . . . . 16
3.2.6. Directory Entry Reference . . . . . . . . . . . . . . 17
3.2.7. Inline Encoding . . . . . . . . . . . . . . . . . . . 17
3.2.8. Format Type . . . . . . . . . . . . . . . . . . . . . 18
3.2.9. Free/Busy Time Type . . . . . . . . . . . . . . . . . 19
3.2.10. Language . . . . . . . . . . . . . . . . . . . . . . 20
3.2.11. Group or List Membership . . . . . . . . . . . . . . 20
3.2.12. Participation Status . . . . . . . . . . . . . . . . 21
3.2.13. Recurrence Identifier Range . . . . . . . . . . . . . 22
3.2.14. Alarm Trigger Relationship . . . . . . . . . . . . . 23
3.2.15. Relationship Type . . . . . . . . . . . . . . . . . . 24
3.2.16. Participation Role . . . . . . . . . . . . . . . . . 25
3.2.17. RSVP Expectation . . . . . . . . . . . . . . . . . . 25
3.2.18. Sent By . . . . . . . . . . . . . . . . . . . . . . . 26
3.2.19. Time Zone Identifier . . . . . . . . . . . . . . . . 26
3.2.20. Value Data Types . . . . . . . . . . . . . . . . . . 28
3.3. Property Value Data Types . . . . . . . . . . . . . . . . 29
3.3.1. Binary . . . . . . . . . . . . . . . . . . . . . . . 29
3.3.2. Boolean . . . . . . . . . . . . . . . . . . . . . . . 30
3.3.3. Calendar User Address . . . . . . . . . . . . . . . . 30
3.3.4. Date . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3.5. Date-Time . . . . . . . . . . . . . . . . . . . . . . 31
3.3.6. Duration . . . . . . . . . . . . . . . . . . . . . . 34
3.3.7. Float . . . . . . . . . . . . . . . . . . . . . . . . 35
3.3.8. Integer . . . . . . . . . . . . . . . . . . . . . . . 35
3.3.9. Period of Time . . . . . . . . . . . . . . . . . . . 36
3.3.10. Recurrence Rule . . . . . . . . . . . . . . . . . . . 37
3.3.11. Text . . . . . . . . . . . . . . . . . . . . . . . . 45
3.3.12. Time . . . . . . . . . . . . . . . . . . . . . . . . 46
3.3.13. URI . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.3.14. UTC Offset . . . . . . . . . . . . . . . . . . . . . 49
3.4. iCalendar Object . . . . . . . . . . . . . . . . . . . . 49
3.5. Property . . . . . . . . . . . . . . . . . . . . . . . . 50
3.6. Calendar Components . . . . . . . . . . . . . . . . . . . 50
3.6.1. Event Component . . . . . . . . . . . . . . . . . . . 52
3.6.2. To-Do Component . . . . . . . . . . . . . . . . . . . 56
3.6.3. Journal Component . . . . . . . . . . . . . . . . . . 58
3.6.4. Free/Busy Component . . . . . . . . . . . . . . . . . 60
3.6.5. Time Zone Component . . . . . . . . . . . . . . . . . 63
3.6.6. Alarm Component . . . . . . . . . . . . . . . . . . . 72
3.7. Calendar Properties . . . . . . . . . . . . . . . . . . . 77
3.7.1. Calendar Scale . . . . . . . . . . . . . . . . . . . 77
3.7.2. Method . . . . . . . . . . . . . . . . . . . . . . . 78
3.7.3. Product Identifier . . . . . . . . . . . . . . . . . 79
3.7.4. Version . . . . . . . . . . . . . . . . . . . . . . . 80
3.8. Component Properties . . . . . . . . . . . . . . . . . . 81
3.8.1. Descriptive Component Properties . . . . . . . . . . 81
3.8.1.1. Attachment . . . . . . . . . . . . . . . . . . . 81
3.8.1.2. Categories . . . . . . . . . . . . . . . . . . . 82
3.8.1.3. Classification . . . . . . . . . . . . . . . . . 83
3.8.1.4. Comment . . . . . . . . . . . . . . . . . . . . . 84
3.8.1.5. Description . . . . . . . . . . . . . . . . . . . 85
3.8.1.6. Geographic Position . . . . . . . . . . . . . . . 87
3.8.1.7. Location . . . . . . . . . . . . . . . . . . . . 88
3.8.1.8. Percent Complete . . . . . . . . . . . . . . . . 89
3.8.1.9. Priority . . . . . . . . . . . . . . . . . . . . 90
3.8.1.10. Resources . . . . . . . . . . . . . . . . . . . . 92
3.8.1.11. Status . . . . . . . . . . . . . . . . . . . . . 93
3.8.1.12. Summary . . . . . . . . . . . . . . . . . . . . . 94
3.8.2. Date and Time Component Properties . . . . . . . . . 95
3.8.2.1. Date-Time Completed . . . . . . . . . . . . . . . 95
3.8.2.2. Date-Time End . . . . . . . . . . . . . . . . . . 96
3.8.2.3. Date-Time Due . . . . . . . . . . . . . . . . . . 97
3.8.2.4. Date-Time Start . . . . . . . . . . . . . . . . . 99
3.8.2.5. Duration . . . . . . . . . . . . . . . . . . . . 100
3.8.2.6. Free/Busy Time . . . . . . . . . . . . . . . . . 101
3.8.2.7. Time Transparency . . . . . . . . . . . . . . . . 102
3.8.3. Time Zone Component Properties . . . . . . . . . . . 103
3.8.3.1. Time Zone Identifier . . . . . . . . . . . . . . 103
3.8.3.2. Time Zone Name . . . . . . . . . . . . . . . . . 105
3.8.3.3. Time Zone Offset From . . . . . . . . . . . . . . 106
3.8.3.4. Time Zone Offset To . . . . . . . . . . . . . . . 106
3.8.3.5. Time Zone URL . . . . . . . . . . . . . . . . . . 107
3.8.4. Relationship Component Properties . . . . . . . . . . 108
3.8.4.1. Attendee . . . . . . . . . . . . . . . . . . . . 108
3.8.4.2. Contact . . . . . . . . . . . . . . . . . . . . . 111
3.3.12. Time . . . . . . . . . . . . . . . . . . . . . . . . 46
3.3.13. URI . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.3.14. UTC Offset . . . . . . . . . . . . . . . . . . . . . 49
3.4. iCalendar Object . . . . . . . . . . . . . . . . . . . . 49
3.5. Property . . . . . . . . . . . . . . . . . . . . . . . . 50
3.6. Calendar Components . . . . . . . . . . . . . . . . . . . 50
3.6.1. Event Component . . . . . . . . . . . . . . . . . . . 52
3.6.2. To-Do Component . . . . . . . . . . . . . . . . . . . 56
3.6.3. Journal Component . . . . . . . . . . . . . . . . . . 58
3.6.4. Free/Busy Component . . . . . . . . . . . . . . . . . 60
3.6.5. Time Zone Component . . . . . . . . . . . . . . . . . 63
3.6.6. Alarm Component . . . . . . . . . . . . . . . . . . . 72
3.7. Calendar Properties . . . . . . . . . . . . . . . . . . . 77
3.7.1. Calendar Scale . . . . . . . . . . . . . . . . . . . 77
3.7.2. Method . . . . . . . . . . . . . . . . . . . . . . . 78
3.7.3. Product Identifier . . . . . . . . . . . . . . . . . 79
3.7.4. Version . . . . . . . . . . . . . . . . . . . . . . . 80
3.8. Component Properties . . . . . . . . . . . . . . . . . . 81
3.8.1. Descriptive Component Properties . . . . . . . . . . 81
3.8.1.1. Attachment . . . . . . . . . . . . . . . . . . . 81
3.8.1.2. Categories . . . . . . . . . . . . . . . . . . . 82
3.8.1.3. Classification . . . . . . . . . . . . . . . . . 83
3.8.1.4. Comment . . . . . . . . . . . . . . . . . . . . . 84
3.8.1.5. Description . . . . . . . . . . . . . . . . . . . 85
3.8.1.6. Geographic Position . . . . . . . . . . . . . . . 87
3.8.1.7. Location . . . . . . . . . . . . . . . . . . . . 88
3.8.1.8. Percent Complete . . . . . . . . . . . . . . . . 89
3.8.1.9. Priority . . . . . . . . . . . . . . . . . . . . 90
3.8.1.10. Resources . . . . . . . . . . . . . . . . . . . . 92
3.8.1.11. Status . . . . . . . . . . . . . . . . . . . . . 93
3.8.1.12. Summary . . . . . . . . . . . . . . . . . . . . . 94
3.8.2. Date and Time Component Properties . . . . . . . . . 95
3.8.2.1. Date-Time Completed . . . . . . . . . . . . . . . 95
3.8.2.2. Date-Time End . . . . . . . . . . . . . . . . . . 96
3.8.2.3. Date-Time Due . . . . . . . . . . . . . . . . . . 97
3.8.2.4. Date-Time Start . . . . . . . . . . . . . . . . . 99
3.8.2.5. Duration . . . . . . . . . . . . . . . . . . . . 100
3.8.2.6. Free/Busy Time . . . . . . . . . . . . . . . . . 101
3.8.2.7. Time Transparency . . . . . . . . . . . . . . . . 102
3.8.3. Time Zone Component Properties . . . . . . . . . . . 103
3.8.3.1. Time Zone Identifier . . . . . . . . . . . . . . 103
3.8.3.2. Time Zone Name . . . . . . . . . . . . . . . . . 105
3.8.3.3. Time Zone Offset From . . . . . . . . . . . . . . 106
3.8.3.4. Time Zone Offset To . . . . . . . . . . . . . . . 106
3.8.3.5. Time Zone URL . . . . . . . . . . . . . . . . . . 107
3.8.4. Relationship Component Properties . . . . . . . . . . 108
3.8.4.1. Attendee . . . . . . . . . . . . . . . . . . . . 108
3.8.4.2. Contact . . . . . . . . . . . . . . . . . . . . . 111
3.8.4.3. Organizer . . . . . . . . . . . . . . . . . . . . 113
3.8.4.4. Recurrence ID . . . . . . . . . . . . . . . . . . 114
3.8.4.5. Related To . . . . . . . . . . . . . . . . . . . 117
3.8.4.6. Uniform Resource Locator . . . . . . . . . . . . 118
3.8.4.7. Unique Identifier . . . . . . . . . . . . . . . . 119
3.8.5. Recurrence Component Properties . . . . . . . . . . . 120
3.8.5.1. Exception Date-Times . . . . . . . . . . . . . . 120
3.8.5.2. Recurrence Date-Times . . . . . . . . . . . . . . 122
3.8.5.3. Recurrence Rule . . . . . . . . . . . . . . . . . 124
3.8.6. Alarm Component Properties . . . . . . . . . . . . . 134
3.8.6.1. Action . . . . . . . . . . . . . . . . . . . . . 134
3.8.6.2. Repeat Count . . . . . . . . . . . . . . . . . . 135
3.8.6.3. Trigger . . . . . . . . . . . . . . . . . . . . . 135
3.8.7. Change Management Component Properties . . . . . . . 138
3.8.7.1. Date-Time Created . . . . . . . . . . . . . . . . 138
3.8.7.2. Date-Time Stamp . . . . . . . . . . . . . . . . . 139
3.8.7.3. Last Modified . . . . . . . . . . . . . . . . . . 140
3.8.7.4. Sequence Number . . . . . . . . . . . . . . . . . 141
3.8.8. Miscellaneous Component Properties . . . . . . . . . 142
3.8.8.1. IANA Properties . . . . . . . . . . . . . . . . . 142
3.8.8.2. Non-Standard Properties . . . . . . . . . . . . . 142
3.8.8.3. Request Status . . . . . . . . . . . . . . . . . 144
4. iCalendar Object Examples . . . . . . . . . . . . . . . . . . 146
5. Recommended Practices . . . . . . . . . . . . . . . . . . . . 150
6. Internationalization Considerations . . . . . . . . . . . . . 151
7. Security Considerations . . . . . . . . . . . . . . . . . . . 151
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 151
8.1. iCalendar Media Type Registration . . . . . . . . . . . . 151
8.2. New iCalendar Elements Registration . . . . . . . . . . . 155
8.2.1. iCalendar Elements Registration Procedure . . . . . . 155
8.2.2. Registration Template for Components . . . . . . . . 155
8.2.3. Registration Template for Properties . . . . . . . . 156
8.2.4. Registration Template for Parameters . . . . . . . . 156
8.2.5. Registration Template for Value Data Types . . . . . 157
8.2.6. Registration Template for Values . . . . . . . . . . 157
8.3. Initial iCalendar Elements Registries . . . . . . . . . . 158
8.3.1. Components Registry . . . . . . . . . . . . . . . . . 158
8.3.2. Properties Registry . . . . . . . . . . . . . . . . . 158
8.3.3. Parameters Registry . . . . . . . . . . . . . . . . . 161
8.3.4. Value Data Types Registry . . . . . . . . . . . . . . 162
8.3.5. Calendar User Types Registry . . . . . . . . . . . . 162
8.3.6. Free/Busy Time Types Registry . . . . . . . . . . . . 163
8.3.7. Participation Statuses Registry . . . . . . . . . . . 163
8.3.8. Relationship Types Registry . . . . . . . . . . . . . 164
8.3.9. Participation Roles Registry . . . . . . . . . . . . 164
8.3.10. Actions Registry . . . . . . . . . . . . . . . . . . 165
8.3.11. Classifications Registry . . . . . . . . . . . . . . 165
8.3.12. Methods Registry . . . . . . . . . . . . . . . . . . 165
3.8.4.3. Organizer . . . . . . . . . . . . . . . . . . . . 113
3.8.4.4. Recurrence ID . . . . . . . . . . . . . . . . . . 114
3.8.4.5. Related To . . . . . . . . . . . . . . . . . . . 117
3.8.4.6. Uniform Resource Locator . . . . . . . . . . . . 118
3.8.4.7. Unique Identifier . . . . . . . . . . . . . . . . 119
3.8.5. Recurrence Component Properties . . . . . . . . . . . 120
3.8.5.1. Exception Date-Times . . . . . . . . . . . . . . 120
3.8.5.2. Recurrence Date-Times . . . . . . . . . . . . . . 122
3.8.5.3. Recurrence Rule . . . . . . . . . . . . . . . . . 124
3.8.6. Alarm Component Properties . . . . . . . . . . . . . 134
3.8.6.1. Action . . . . . . . . . . . . . . . . . . . . . 134
3.8.6.2. Repeat Count . . . . . . . . . . . . . . . . . . 135
3.8.6.3. Trigger . . . . . . . . . . . . . . . . . . . . . 135
3.8.7. Change Management Component Properties . . . . . . . 138
3.8.7.1. Date-Time Created . . . . . . . . . . . . . . . . 138
3.8.7.2. Date-Time Stamp . . . . . . . . . . . . . . . . . 139
3.8.7.3. Last Modified . . . . . . . . . . . . . . . . . . 140
3.8.7.4. Sequence Number . . . . . . . . . . . . . . . . . 141
3.8.8. Miscellaneous Component Properties . . . . . . . . . 142
3.8.8.1. IANA Properties . . . . . . . . . . . . . . . . . 142
3.8.8.2. Non-Standard Properties . . . . . . . . . . . . . 142
3.8.8.3. Request Status . . . . . . . . . . . . . . . . . 144
4. iCalendar Object Examples . . . . . . . . . . . . . . . . . . 146
5. Recommended Practices . . . . . . . . . . . . . . . . . . . . 150
6. Internationalization Considerations . . . . . . . . . . . . . 151
7. Security Considerations . . . . . . . . . . . . . . . . . . . 151
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 151
8.1. iCalendar Media Type Registration . . . . . . . . . . . . 151
8.2. New iCalendar Elements Registration . . . . . . . . . . . 155
8.2.1. iCalendar Elements Registration Procedure . . . . . . 155
8.2.2. Registration Template for Components . . . . . . . . 155
8.2.3. Registration Template for Properties . . . . . . . . 156
8.2.4. Registration Template for Parameters . . . . . . . . 156
8.2.5. Registration Template for Value Data Types . . . . . 157
8.2.6. Registration Template for Values . . . . . . . . . . 157
8.3. Initial iCalendar Elements Registries . . . . . . . . . . 158
8.3.1. Components Registry . . . . . . . . . . . . . . . . . 158
8.3.2. Properties Registry . . . . . . . . . . . . . . . . . 158
8.3.3. Parameters Registry . . . . . . . . . . . . . . . . . 161
8.3.4. Value Data Types Registry . . . . . . . . . . . . . . 162
8.3.5. Calendar User Types Registry . . . . . . . . . . . . 162
8.3.6. Free/Busy Time Types Registry . . . . . . . . . . . . 163
8.3.7. Participation Statuses Registry . . . . . . . . . . . 163
8.3.8. Relationship Types Registry . . . . . . . . . . . . . 164
8.3.9. Participation Roles Registry . . . . . . . . . . . . 164
8.3.10. Actions Registry . . . . . . . . . . . . . . . . . . 165
8.3.11. Classifications Registry . . . . . . . . . . . . . . 165
8.3.12. Methods Registry . . . . . . . . . . . . . . . . . . 165
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 165
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 166
10.1. Normative References . . . . . . . . . . . . . . . . . . 166
10.2. Informative References . . . . . . . . . . . . . . . . . 167
Appendix A. Differences from RFC 2445 . . . . . . . . . . . . . 169
A.1. New Restrictions . . . . . . . . . . . . . . . . . . . . 169
A.2. Restrictions Removed . . . . . . . . . . . . . . . . . . 169
A.3. Deprecated Features . . . . . . . . . . . . . . . . . . . 169
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 165
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 166
10.1. Normative References . . . . . . . . . . . . . . . . . . 166
10.2. Informative References . . . . . . . . . . . . . . . . . 167
Appendix A. Differences from RFC 2445 . . . . . . . . . . . . . 169
A.1. New Restrictions . . . . . . . . . . . . . . . . . . . . 169
A.2. Restrictions Removed . . . . . . . . . . . . . . . . . . 169
A.3. Deprecated Features . . . . . . . . . . . . . . . . . . . 169
The use of calendaring and scheduling has grown considerably in the last decade. Enterprise and inter-enterprise business has become dependent on rapid scheduling of events and actions using this information technology. This memo is intended to progress the level of interoperability possible between dissimilar calendaring and scheduling applications. This memo defines a MIME content type for exchanging electronic calendaring and scheduling information. The Internet Calendaring and Scheduling Core Object Specification, or iCalendar, allows for the capture and exchange of information normally stored within a calendaring and scheduling application; such as a Personal Information Manager (PIM) or a Group-Scheduling product.
日历和日程安排的使用在过去十年中有了很大的发展。企业和企业间业务已变得依赖于使用此信息技术快速安排事件和行动。本备忘录旨在提高不同日历和日程安排应用程序之间可能的互操作性级别。此备忘录定义了用于交换电子日历和日程安排信息的MIME内容类型。Internet日历和调度核心对象规范或iCalendar允许捕获和交换通常存储在日历和调度应用程序中的信息；例如个人信息管理器（PIM）或组调度产品。
The iCalendar format is suitable as an exchange format between applications or systems. The format is defined in terms of a MIME content type. This will enable the object to be exchanged using several transports, including but not limited to SMTP, HTTP, a file system, desktop interactive protocols such as the use of a memory-based clipboard or drag/drop interactions, point-to-point asynchronous communication, wired-network transport, or some form of unwired transport such as infrared.
iCalendar格式适合作为应用程序或系统之间的交换格式。该格式是根据MIME内容类型定义的。这将使对象能够使用多种传输进行交换，包括但不限于SMTP、HTTP、文件系统、桌面交互协议（如使用基于内存的剪贴板或拖放交互）、点对点异步通信、有线网络传输或某种形式的非自愿传输（如红外）。
The memo also provides for the definition of iCalendar object methods that will map this content type to a set of messages for supporting calendaring and scheduling operations such as requesting, replying to, modifying, and canceling meetings or appointments, to-dos, and journal entries. The iCalendar object methods can be used to define other calendaring and scheduling operations such as requesting for and replying with free/busy time data. Such a scheduling protocol is defined in the iCalendar Transport-independent Interoperability Protocol (iTIP) defined in [2446bis].
备忘录还提供了iCalendar对象方法的定义，这些方法将此内容类型映射到一组消息，以支持日历和日程安排操作，例如请求、回复、修改和取消会议或约会、待办事项和日记条目。iCalendar对象方法可用于定义其他日历和日程安排操作，如请求和回复忙/闲时间数据。此类调度协议在[2446bis]中定义的iCalendar传输独立互操作性协议（iTIP）中定义。
The memo also includes a formal grammar for the content type based on the Internet ABNF defined in [RFC5234]. This ABNF is required for the implementation of parsers and to serve as the definitive reference when ambiguities or questions arise in interpreting the descriptive prose definition of the memo. Additional restrictions
备忘录还包括基于[RFC5234]中定义的互联网ABNF的内容类型的正式语法。该ABNF用于解析器的实现，并在解释备忘录的描述性散文定义时出现歧义或问题时作为最终参考。附加限制
that could not easily be expressed with the ABNF syntax are specified as comments in the ABNF. Comments with normative statements should be treated as such.
无法用ABNF语法轻松表达的内容在ABNF中指定为注释。带有规范性陈述的评论应按此处理。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
This memo makes use of both a descriptive prose and a more formal notation for defining the calendaring and scheduling format.
本备忘录使用描述性散文和更正式的符号来定义日历和日程安排格式。
The notation used in this memo is the ABNF notation of [RFC5234]. Readers intending on implementing the format defined in this memo should be familiar with this notation in order to properly interpret the specifications of this memo.
本备忘录中使用的符号为[RFC5234]的ABNF符号。打算实施本备忘录中定义的格式的读者应熟悉此符号，以便正确解释本备忘录的规范。
All numeric values used in this memo are given in decimal notation.
本备忘录中使用的所有数值均以十进制表示。
All names of properties, property parameters, enumerated property values, and property parameter values are case-insensitive. However, all other property values are case-sensitive, unless otherwise stated.
属性、属性参数、枚举属性值和属性参数值的所有名称都不区分大小写。但是，除非另有说明，否则所有其他属性值都区分大小写。
Note: All indented editorial notes, such as this one, are intended to provide the reader with additional information. The information is not essential to the building of an implementation conformant with this memo. The information is provided to highlight a particular feature or characteristic of the memo.
注：所有缩进的编辑注释，如本注释，旨在向读者提供额外信息。这些信息对于构建符合本备忘录要求的实施不是必不可少的。提供这些信息是为了突出备忘录的特定功能或特征。
The format for the iCalendar object is based on the syntax of the text/directory media type [RFC2425]. While the iCalendar object is not a profile of the text/directory media type [RFC2425], it does reuse a number of the elements from the [RFC2425] specification.
iCalendar对象的格式基于文本/目录媒体类型[RFC2425]的语法。虽然iCalendar对象不是文本/目录媒体类型[RFC2425]的配置文件，但它确实重用了[RFC2425]规范中的许多元素。
The elements defined in this memo are defined in prose. Many of the terms used to describe these have common usage that is different than the standards usage of this memo. In order to reference, within this memo, elements of the calendaring and scheduling model, core object (this memo), or interoperability protocol [2446bis] some formatting conventions have been used. Calendaring and scheduling roles are referred to in quoted-strings of text with the first character of each word in uppercase. For example, "Organizer" refers to a role of a "Calendar User" within the scheduling protocol defined by [2446bis]. Calendar components defined by this memo are referred to
本备忘录中定义的要素以散文形式定义。用于描述这些内容的许多术语具有与本备忘录标准用法不同的通用用法。为了在本备忘录中引用日历和调度模型、核心对象（本备忘录）或互操作性协议[2446bis]的元素，使用了一些格式约定。日历和日程安排角色在带引号的文本字符串中引用，每个单词的第一个字符都是大写的。例如，“组织者”是指[2446bis]定义的调度协议中的“日历用户”角色。此备忘录定义的日历组件是指
with capitalized, quoted-strings of text. All calendar components start with the letter "V". For example, "VEVENT" refers to the event calendar component, "VTODO" refers to the to-do calendar component, and "VJOURNAL" refers to the daily journal calendar component. Scheduling methods defined by iTIP [2446bis] are referred to with capitalized, quoted-strings of text. For example, "REQUEST" refers to the method for requesting a scheduling calendar component be created or modified, and "REPLY" refers to the method a recipient of a request uses to update their status with the "Organizer" of the calendar component.
带大写引号的文本字符串。所有日历组件都以字母“V”开头。例如，“VEVENT”指的是事件日历组件，“VTODO”指的是待办日历组件，“VJOURNAL”指的是每日日志日历组件。iTIP[2446bis]定义的调度方法使用大写、带引号的文本字符串。例如，“请求”指的是请求创建或修改日程安排日历组件的方法，“回复”指的是请求接收者使用日历组件的“组织者”更新其状态的方法。
The properties defined by this memo are referred to with capitalized, quoted-strings of text, followed by the word "property". For example, "ATTENDEE" property refers to the iCalendar property used to convey the calendar address of a calendar user. Property parameters defined by this memo are referred to with lowercase, quoted-strings of text, followed by the word "parameter". For example, "value" parameter refers to the iCalendar property parameter used to override the default value type for a property value. Enumerated values defined by this memo are referred to with capitalized text, either alone or followed by the word "value". For example, the "MINUTELY" value can be used with the "FREQ" component of the "RECUR" value type to specify repeating components based on an interval of one minute or more.
本备忘录定义的属性以大写、带引号的文本字符串表示，后跟“属性”一词。例如，“ATTENDEE”属性指用于传递日历用户日历地址的iCalendar属性。本备忘录定义的属性参数使用小写、带引号的文本字符串表示，后跟单词“parameter”。例如，“值”参数是指用于替代特性值的默认值类型的iCalendar特性参数。本备忘录定义的枚举值用大写文本表示，单独或后跟“值”一词。例如，“分钟”值可与“重现”值类型的“频率”分量一起使用，以指定基于一分钟或更长时间间隔的重复分量。
The following table lists the different characters from the [US-ASCII] character set that is referenced in this document. For each character, the table specifies the character name used throughout this document, along with its US-ASCII decimal codepoint.
下表列出了本文档中引用的[US-ASCII]字符集的不同字符。对于每个字符，该表指定了本文档中使用的字符名及其US-ASCII十进制代码点。
+------------------------+-------------------+
| Character name | Decimal codepoint |
+------------------------+-------------------+
| HTAB | 9 |
| LF | 10 |
| CR | 13 |
| DQUOTE | 22 |
| SPACE | 32 |
| PLUS SIGN | 43 |
| COMMA | 44 |
| HYPHEN-MINUS | 45 |
| PERIOD | 46 |
| SOLIDUS | 47 |
| COLON | 58 |
| SEMICOLON | 59 |
| LATIN CAPITAL LETTER N | 78 |
| LATIN CAPITAL LETTER T | 84 |
| LATIN CAPITAL LETTER X | 88 |
| LATIN CAPITAL LETTER Z | 90 |
| BACKSLASH | 92 |
| LATIN SMALL LETTER N | 110 |
+------------------------+-------------------+
+------------------------+-------------------+
| Character name | Decimal codepoint |
+------------------------+-------------------+
| HTAB | 9 |
| LF | 10 |
| CR | 13 |
| DQUOTE | 22 |
| SPACE | 32 |
| PLUS SIGN | 43 |
| COMMA | 44 |
| HYPHEN-MINUS | 45 |
| PERIOD | 46 |
| SOLIDUS | 47 |
| COLON | 58 |
| SEMICOLON | 59 |
| LATIN CAPITAL LETTER N | 78 |
| LATIN CAPITAL LETTER T | 84 |
| LATIN CAPITAL LETTER X | 88 |
| LATIN CAPITAL LETTER Z | 90 |
| BACKSLASH | 92 |
| LATIN SMALL LETTER N | 110 |
+------------------------+-------------------+
Implementers will need to be familiar with several other memos that, along with this memo, form a framework for Internet calendaring and scheduling standards. This memo specifies a core specification of objects, value types, properties, and property parameters.
实施者需要熟悉其他几个备忘录，这些备忘录与本备忘录一起构成了互联网日历和日程安排标准的框架。此备忘录指定对象、值类型、属性和属性参数的核心规范。
o iTIP [2446bis] specifies an interoperability protocol for scheduling between different implementations;
o iTIP[2446bis]指定了一个互操作性协议，用于不同实现之间的调度；
o iCalendar Message-Based Interoperability Protocol (iMIP) [2447bis] specifies an Internet email binding for [2446bis].
o iCalendar基于消息的互操作性协议（iMIP）[2447bis]指定了[2446bis]的Internet电子邮件绑定。
This memo does not attempt to repeat the specification of concepts or definitions from these other memos. Where possible, references are made to the memo that provides for the specification of these concepts or definitions.
本备忘录不试图重复其他备忘录中的概念或定义说明。在可能的情况下，参考备忘录，其中规定了这些概念或定义的规范。
The following sections define the details of a Calendaring and Scheduling Core Object Specification. The Calendaring and Scheduling Core Object is a collection of calendaring and scheduling information. Typically, this information will consist of an iCalendar stream with one or more iCalendar objects. The body of the
以下各节定义了日历和调度核心对象规范的详细信息。日历和日程安排核心对象是日历和日程安排信息的集合。通常，此信息将由包含一个或多个iCalendar对象的iCalendar流组成。主体
iCalendar object consists of a sequence of calendar properties and one or more calendar components.
iCalendar对象由一系列日历属性和一个或多个日历组件组成。
Section 3.1 defines the content line format; Section 3.2 defines the property parameter format; Section 3.3 defines the data types for property values; Section 3.4 defines the iCalendar object format; Section 3.5 defines the iCalendar property format; Section 3.6 defines the calendar component format; Section 3.7 defines calendar properties; and Section 3.8 defines calendar component properties.
第3.1节定义了内容行格式；第3.2节定义了属性参数格式；第3.3节定义了属性值的数据类型；第3.4节定义了iCalendar对象格式；第3.5节定义了iCalendar属性格式；第3.6节定义了日历组件格式；第3.7节定义了日历属性；第3.8节定义了日历组件属性。
This information is intended to be an integral part of the MIME content type registration. In addition, this information can be used independent of such content registration. In particular, this memo has direct applicability for use as a calendaring and scheduling exchange format in file-, memory-, or network-based transport mechanisms.
此信息是MIME内容类型注册的一个组成部分。此外，可以独立于此类内容注册使用此信息。特别是，此备忘录直接适用于在基于文件、内存或网络的传输机制中用作日历和计划交换格式。
The iCalendar object is organized into individual lines of text, called content lines. Content lines are delimited by a line break, which is a CRLF sequence (CR character followed by LF character).
iCalendar对象被组织成单独的文本行，称为内容行。内容行由换行符分隔，换行符是CRLF序列（CR字符后跟LF字符）。
Lines of text SHOULD NOT be longer than 75 octets, excluding the line break. Long content lines SHOULD be split into a multiple line representations using a line "folding" technique. That is, a long line can be split between any two characters by inserting a CRLF immediately followed by a single linear white-space character (i.e., SPACE or HTAB). Any sequence of CRLF followed immediately by a single linear white-space character is ignored (i.e., removed) when processing the content type.
文本行不应超过75个八位字节，不包括换行符。长内容行应使用行“折叠”技术拆分为多行表示。也就是说，通过插入紧跟在单个线性空白字符（即空格或HTAB）之后的CRLF，可以在任意两个字符之间拆分长行。处理内容类型时，将忽略（即删除）紧跟单个线性空白字符的任何CRLF序列。
For example, the line:
例如，行：
DESCRIPTION:This is a long description that exists on a long line.
描述：这是一个存在于长行上的长描述。
Can be represented as:
可表示为：
DESCRIPTION:This is a lo ng description that exists on a long line.
描述：这是一个长线描述。
The process of moving from this folded multiple-line representation to its single-line representation is called "unfolding". Unfolding is accomplished by removing the CRLF and the linear white-space character that immediately follows.
从折叠的多行表示移动到单线表示的过程称为“展开”。展开是通过删除CRLF和紧接其后的线性空白字符来完成的。
When parsing a content line, folded lines MUST first be unfolded according to the unfolding procedure described above.
解析内容行时，必须首先根据上述展开过程展开折叠行。
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 need to unfold lines in such a way to properly restore the original sequence.
注意：非常简单的实现可以在UTF-8多八位字节序列的中间生成不正确折叠的行。因此，实现需要以这样的方式展开线，以正确地恢复原始序列。
The content information associated with an iCalendar object is formatted using a syntax similar to that defined by [RFC2425]. That is, the content information consists of CRLF-separated content lines.
与iCalendar对象关联的内容信息使用类似于[RFC2425]定义的语法进行格式化。也就是说，内容信息由CRLF分隔的内容行组成。
The following notation defines the lines of content in an iCalendar object:
以下符号定义iCalendar对象中的内容行：
contentline = name *(";" param ) ":" value CRLF
; This ABNF is just a general definition for an initial parsing
; of the content line into its property name, parameter list,
; and value string
contentline = name *(";" param ) ":" value CRLF
; This ABNF is just a general definition for an initial parsing
; of the content line into its property name, parameter list,
; and value string
; When parsing a content line, folded lines MUST first
; be unfolded according to the unfolding procedure
; described above. When generating a content line, lines
; longer than 75 octets SHOULD be folded according to
; the folding procedure described above.
; When parsing a content line, folded lines MUST first
; be unfolded according to the unfolding procedure
; described above. When generating a content line, lines
; longer than 75 octets SHOULD be folded according to
; the folding procedure described above.
name = iana-token / x-name
name = iana-token / x-name
iana-token = 1*(ALPHA / DIGIT / "-")
; iCalendar identifier registered with IANA
iana-token = 1*(ALPHA / DIGIT / "-")
; iCalendar identifier registered with IANA
x-name = "X-" [vendorid "-"] 1*(ALPHA / DIGIT / "-") ; Reserved for experimental use.
x-name=“x-”[vendorid“-“]1*（字母/数字/“-”）；保留供实验使用。
vendorid = 3*(ALPHA / DIGIT)
; Vendor identification
vendorid = 3*(ALPHA / DIGIT)
; Vendor identification
param = param-name "=" param-value *("," param-value)
; Each property defines the specific ABNF for the parameters
; allowed on the property. Refer to specific properties for
; precise parameter ABNF.
param = param-name "=" param-value *("," param-value)
; Each property defines the specific ABNF for the parameters
; allowed on the property. Refer to specific properties for
; precise parameter ABNF.
param-name = iana-token / x-name
param-name = iana-token / x-name
param-value = paramtext / quoted-string
param-value = paramtext / quoted-string
paramtext = *SAFE-CHAR
paramtext = *SAFE-CHAR
value = *VALUE-CHAR
value = *VALUE-CHAR
quoted-string = DQUOTE *QSAFE-CHAR DQUOTE
quoted string=DQUOTE*QSAFE-CHAR DQUOTE
QSAFE-CHAR = WSP / %x21 / %x23-7E / NON-US-ASCII
; Any character except CONTROL and DQUOTE
QSAFE-CHAR = WSP / %x21 / %x23-7E / NON-US-ASCII
; Any character except CONTROL and DQUOTE
SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E
/ NON-US-ASCII
; Any character except CONTROL, DQUOTE, ";", ":", ","
SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E
/ NON-US-ASCII
; Any character except CONTROL, DQUOTE, ";", ":", ","
VALUE-CHAR = WSP / %x21-7E / NON-US-ASCII
; Any textual character
VALUE-CHAR = WSP / %x21-7E / NON-US-ASCII
; Any textual character
NON-US-ASCII = UTF8-2 / UTF8-3 / UTF8-4
; UTF8-2, UTF8-3, and UTF8-4 are defined in [RFC3629]
NON-US-ASCII = UTF8-2 / UTF8-3 / UTF8-4
; UTF8-2, UTF8-3, and UTF8-4 are defined in [RFC3629]
CONTROL = %x00-08 / %x0A-1F / %x7F
; All the controls except HTAB
CONTROL = %x00-08 / %x0A-1F / %x7F
; All the controls except HTAB
The property value component of a content line has a format that is property specific. Refer to the section describing each property for a definition of this format.
内容行的属性值组件具有特定于属性的格式。有关此格式的定义，请参阅描述每个属性的部分。
All names of properties, property parameters, enumerated property values and property parameter values are case-insensitive. However, all other property values are case-sensitive, unless otherwise stated.
属性、属性参数、枚举属性值和属性参数值的所有名称都不区分大小写。但是，除非另有说明，否则所有其他属性值都区分大小写。
Some properties and parameters allow a list of values. Values in a list of values MUST be separated by a COMMA character. There is no significance to the order of values in a list. For those parameter values (such as those that specify URI values) that are specified in quoted-strings, the individual quoted-strings are separated by a COMMA character.
某些属性和参数允许值列表。值列表中的值必须用逗号分隔。列表中的值顺序没有意义。对于在带引号的字符串中指定的参数值（例如指定URI值的参数值），各个带引号的字符串用逗号分隔。
Some property values are defined in terms of multiple parts. These structured property values MUST have their value parts separated by a SEMICOLON character.
某些特性值是根据多个零件定义的。这些结构化属性值的值部分必须用分号字符分隔。
Some properties allow a list of parameters. Each property parameter in a list of property parameters MUST be separated by a SEMICOLON character.
某些属性允许参数列表。属性参数列表中的每个属性参数必须用分号字符分隔。
Property parameters with values containing a COLON character, a SEMICOLON character or a COMMA character MUST be placed in quoted text.
具有包含冒号字符、分号字符或逗号字符的值的属性参数必须放置在带引号的文本中。
For example, in the following properties, a SEMICOLON is used to separate property parameters from each other and a COMMA character is used to separate property values in a value list.
例如，在以下属性中，分号用于分隔属性参数，逗号用于分隔值列表中的属性值。
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT:mailto:
jsmith@example.com
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT:mailto:
jsmith@example.com
RDATE;VALUE=DATE:19970304,19970504,19970704,19970904
RDATE;VALUE=DATE:19970304,19970504,19970704,19970904
Some properties defined in the iCalendar object can have multiple values. The general rule for encoding multi-valued items is to simply create a new content line for each value, including the property name. However, it should be noted that some properties support encoding multiple values in a single property by separating the values with a COMMA character. Individual property definitions should be consulted for determining whether a specific property allows multiple values and in which of these two forms. Multi-valued properties MUST NOT be used to specify multiple language variants of the same value. Calendar applications SHOULD display all values.
在iCalendar对象中定义的某些特性可以具有多个值。编码多值项的一般规则是为每个值（包括属性名）创建一个新的内容行。但是，应注意的是，某些属性支持通过使用逗号字符分隔值在单个属性中对多个值进行编码。在确定特定属性是否允许多个值以及这两种形式中的哪种形式时，应参考各个属性定义。多值属性不得用于指定相同值的多个语言变体。日历应用程序应显示所有值。
Binary content information in an iCalendar object SHOULD be referenced using a URI within a property value. That is, the binary content information SHOULD be placed in an external MIME entity that can be referenced by a URI from within the iCalendar object. In applications where this is not feasible, binary content information can be included within an iCalendar object, but only after first encoding it into text using the "BASE64" encoding method defined in [RFC4648]. Inline binary content SHOULD only be used in applications whose special circumstances demand that an iCalendar object be expressed as a single entity. A property containing inline binary content information MUST specify the "ENCODING" property parameter. Binary content information placed external to the iCalendar object MUST be referenced by a uniform resource identifier (URI).
应使用属性值中的URI引用iCalendar对象中的二进制内容信息。也就是说，二进制内容信息应该放在外部MIME实体中，该实体可以由iCalendar对象中的URI引用。在不可行的应用程序中，二进制内容信息可以包含在iCalendar对象中，但必须先使用[RFC4648]中定义的“BASE64”编码方法将其编码为文本。内联二进制内容只能在特殊情况要求将iCalendar对象表示为单个实体的应用程序中使用。包含内联二进制内容信息的属性必须指定“ENCODING”属性参数。放置在iCalendar对象外部的二进制内容信息必须由统一资源标识符（URI）引用。
The following example specifies an "ATTACH" property that references an attachment external to the iCalendar object with a URI reference:
以下示例指定了一个“ATTACH”属性，该属性使用URI引用引用iCalendar对象外部的附件：
ATTACH:http://example.com/public/quarterly-report.doc
ATTACH:http://example.com/public/quarterly-report.doc
The following example specifies an "ATTACH" property with inline binary encoded content information:
以下示例指定了具有内联二进制编码内容信息的“ATTACH”属性：
ATTACH;FMTTYPE=text/plain;ENCODING=BASE64;VALUE=BINARY:VGhlIH
F1aWNrIGJyb3duIGZveCBqdW1wcyBvdmVyIHRoZSBsYXp5IGRvZy4
ATTACH;FMTTYPE=text/plain;ENCODING=BASE64;VALUE=BINARY:VGhlIH
F1aWNrIGJyb3duIGZveCBqdW1wcyBvdmVyIHRoZSBsYXp5IGRvZy4
There is not a property parameter to declare the charset used in a property value. The default charset for an iCalendar stream is UTF-8 as defined in [RFC3629].
没有用于声明属性值中使用的字符集的属性参数。iCalendar流的默认字符集是[RFC3629]中定义的UTF-8。
The "charset" Content-Type parameter MUST be used in MIME transports to specify the charset being used.
MIME传输中必须使用“charset”内容类型参数来指定正在使用的字符集。
A property can have attributes with which it is associated. These "property parameters" contain meta-information about the property or the property value. Property parameters are provided to specify such information as the location of an alternate text representation for a property value, the language of a text property value, the value type of the property value, and other attributes.
属性可以具有与其关联的属性。这些“属性参数”包含有关属性或属性值的元信息。属性参数用于指定诸如属性值的替代文本表示的位置、文本属性值的语言、属性值的值类型以及其他属性等信息。
Property parameter values that contain the COLON, SEMICOLON, or COMMA character separators MUST be specified as quoted-string text values. Property parameter values MUST NOT contain the DQUOTE character. The DQUOTE character is used as a delimiter for parameter values that contain restricted characters or URI text. For example:
必须将包含冒号、分号或逗号字符分隔符的属性参数值指定为带引号的字符串文本值。属性参数值不能包含DQUOTE字符。DQUOTE字符用作包含受限字符或URI文本的参数值的分隔符。例如：
DESCRIPTION;ALTREP="cid:part1.0001@example.org":The Fall'98 Wild
Wizards Conference - - Las Vegas\, NV\, USA
DESCRIPTION;ALTREP="cid:part1.0001@example.org":The Fall'98 Wild
Wizards Conference - - Las Vegas\, NV\, USA
Property parameter values that are not in quoted-strings are case-insensitive.
不在带引号字符串中的属性参数值不区分大小写。
The general property parameters defined by this memo are defined by the following notation:
本备忘录定义的一般属性参数由以下符号定义：
icalparameter = altrepparam ; Alternate text representation
/ cnparam ; Common name
/ cutypeparam ; Calendar user type
/ delfromparam ; Delegator
/ deltoparam ; Delegatee
/ dirparam ; Directory entry
/ encodingparam ; Inline encoding
/ fmttypeparam ; Format type
/ fbtypeparam ; Free/busy time type
/ languageparam ; Language for text
/ memberparam ; Group or list membership
/ partstatparam ; Participation status
/ rangeparam ; Recurrence identifier range
/ trigrelparam ; Alarm trigger relationship
/ reltypeparam ; Relationship type
/ roleparam ; Participation role
/ rsvpparam ; RSVP expectation
/ sentbyparam ; Sent by
/ tzidparam ; Reference to time zone object
/ valuetypeparam ; Property value data type
/ other-param
icalparameter = altrepparam ; Alternate text representation
/ cnparam ; Common name
/ cutypeparam ; Calendar user type
/ delfromparam ; Delegator
/ deltoparam ; Delegatee
/ dirparam ; Directory entry
/ encodingparam ; Inline encoding
/ fmttypeparam ; Format type
/ fbtypeparam ; Free/busy time type
/ languageparam ; Language for text
/ memberparam ; Group or list membership
/ partstatparam ; Participation status
/ rangeparam ; Recurrence identifier range
/ trigrelparam ; Alarm trigger relationship
/ reltypeparam ; Relationship type
/ roleparam ; Participation role
/ rsvpparam ; RSVP expectation
/ sentbyparam ; Sent by
/ tzidparam ; Reference to time zone object
/ valuetypeparam ; Property value data type
/ other-param
other-param = (iana-param / x-param)
other-param = (iana-param / x-param)
iana-param = iana-token "=" param-value *("," param-value) ; Some other IANA-registered iCalendar parameter.
iana参数=iana标记“=”参数值*（“，”参数值）；其他一些IANA注册了iCalendar参数。
x-param = x-name "=" param-value *("," param-value) ; A non-standard, experimental parameter.
x-param=x-name“=”参数值*（“，”参数值）；一个非标准的实验参数。
Applications MUST ignore x-param and iana-param values they don't recognize.
应用程序必须忽略它们无法识别的x-param和iana-param值。
Parameter Name: ALTREP
参数名称：ALTREP
Purpose: To specify an alternate text representation for the property value.
目的：为属性值指定替代文本表示形式。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
altrepparam = "ALTREP" "=" DQUOTE uri DQUOTE
altrepparam=“ALTREP”“=”DQUOTE uri DQUOTE
Description: This parameter specifies a URI that points to an alternate representation for a textual property value. A property specifying this parameter MUST also include a value that reflects
描述：此参数指定指向文本属性值的替代表示形式的URI。指定此参数的属性还必须包含反映
the default representation of the text value. The URI parameter value MUST be specified in a quoted-string.
文本值的默认表示形式。URI参数值必须在带引号的字符串中指定。
Note: While there is no restriction imposed on the URI schemes allowed for this parameter, Content Identifier (CID) [RFC2392], HTTP [RFC2616], and HTTPS [RFC2818] are the URI schemes most commonly used by current implementations.
注意：虽然对该参数允许的URI方案没有限制，但内容标识符（CID）[RFC2392]、HTTP[RFC2616]和HTTPS[RFC2818]是当前实现最常用的URI方案。
Example:
例子：
DESCRIPTION;ALTREP="CID:part3.msg.970415T083000@example.com":
Project XYZ Review Meeting will include the following agenda
items: (a) Market Overview\, (b) Finances\, (c) Project Man
agement
DESCRIPTION;ALTREP="CID:part3.msg.970415T083000@example.com":
Project XYZ Review Meeting will include the following agenda
items: (a) Market Overview\, (b) Finances\, (c) Project Man
agement
The "ALTREP" property parameter value might point to a "text/html" content portion.
“ALTREP”属性参数值可能指向“text/html”内容部分。
Content-Type:text/html
Content-Id:<part3.msg.970415T083000@example.com>
Content-Type:text/html
Content-Id:<part3.msg.970415T083000@example.com>
<html>
<head>
<title></title>
</head>
<body>
<p>
<b>Project XYZ Review Meeting</b> will include
the following agenda items:
<ol>
<li>Market Overview</li>
<li>Finances</li>
<li>Project Management</li>
</ol>
</p>
</body>
</html>
<html>
<head>
<title></title>
</head>
<body>
<p>
<b>Project XYZ Review Meeting</b> will include
the following agenda items:
<ol>
<li>Market Overview</li>
<li>Finances</li>
<li>Project Management</li>
</ol>
</p>
</body>
</html>
Parameter Name: CN
参数名称：CN
Purpose: To specify the common name to be associated with the calendar user specified by the property.
目的：指定与属性指定的日历用户关联的公用名称。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
cnparam = "CN" "=" param-value
cnparam=“CN”“=”参数值
Description: This parameter can be specified on properties with a CAL-ADDRESS value type. The parameter specifies the common name to be associated with the calendar user specified by the property. The parameter value is text. The parameter value can be used for display text to be associated with the calendar address specified by the property.
描述：此参数可以在具有CAL-ADDRESS值类型的属性上指定。该参数指定要与属性指定的日历用户关联的公用名称。参数值为文本。参数值可用于显示与属性指定的日历地址关联的文本。
Example:
例子：
ORGANIZER;CN="John Smith":mailto:jsmith@example.com
ORGANIZER;CN="John Smith":mailto:jsmith@example.com
Parameter Name: CUTYPE
参数名称：CUTYPE
Purpose: To identify the type of calendar user specified by the property.
目的：标识属性指定的日历用户类型。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
cutypeparam = "CUTYPE" "="
("INDIVIDUAL" ; An individual
/ "GROUP" ; A group of individuals
/ "RESOURCE" ; A physical resource
/ "ROOM" ; A room resource
/ "UNKNOWN" ; Otherwise not known
/ x-name ; Experimental type
/ iana-token) ; Other IANA-registered
; type
; Default is INDIVIDUAL
cutypeparam = "CUTYPE" "="
("INDIVIDUAL" ; An individual
/ "GROUP" ; A group of individuals
/ "RESOURCE" ; A physical resource
/ "ROOM" ; A room resource
/ "UNKNOWN" ; Otherwise not known
/ x-name ; Experimental type
/ iana-token) ; Other IANA-registered
; type
; Default is INDIVIDUAL
Description: This parameter can be specified on properties with a CAL-ADDRESS value type. The parameter identifies the type of calendar user specified by the property. If not specified on a property that allows this parameter, the default is INDIVIDUAL. Applications MUST treat x-name and iana-token values they don't recognize the same way as they would the UNKNOWN value.
描述：此参数可以在具有CAL-ADDRESS值类型的属性上指定。该参数标识属性指定的日历用户类型。如果未在允许此参数的属性上指定，则默认为单个。应用程序必须处理x-name和iana令牌值，因为它们无法识别未知值。
Example:
例子：
ATTENDEE;CUTYPE=GROUP:mailto:ietf-calsch@example.org
ATTENDEE;CUTYPE=GROUP:mailto:ietf-calsch@example.org
Parameter Name: DELEGATED-FROM
参数名称：委托自
Purpose: To specify the calendar users that have delegated their participation to the calendar user specified by the property.
目的：指定已将其参与委派给属性指定的日历用户的日历用户。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
delfromparam = "DELEGATED-FROM" "=" DQUOTE cal-address DQUOTE *("," DQUOTE cal-address DQUOTE)
delfromparam=“委托-从”“=”DQUOTE校准地址DQUOTE*（“，”DQUOTE校准地址DQUOTE）
Description: This parameter can be specified on properties with a CAL-ADDRESS value type. This parameter specifies those calendar users that have delegated their participation in a group-scheduled event or to-do to the calendar user specified by the property. The individual calendar address parameter values MUST each be specified in a quoted-string.
描述：此参数可以在具有CAL-ADDRESS值类型的属性上指定。此参数指定已将其在组计划事件或待办事项中的参与委派给属性指定的日历用户的日历用户。每个日历地址参数值必须在带引号的字符串中指定。
Example:
例子：
ATTENDEE;DELEGATED-FROM="mailto:jsmith@example.com":mailto:
jdoe@example.com
ATTENDEE;DELEGATED-FROM="mailto:jsmith@example.com":mailto:
jdoe@example.com
Parameter Name: DELEGATED-TO
参数名称：委托给
Purpose: To specify the calendar users to whom the calendar user specified by the property has delegated participation.
目的：指定属性指定的日历用户已委托其参与的日历用户。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
deltoparam = "DELEGATED-TO" "=" DQUOTE cal-address DQUOTE *("," DQUOTE cal-address DQUOTE)
deltoparam=“委托给”“=”DQUOTE校准地址DQUOTE*（“，”DQUOTE校准地址DQUOTE）
Description: This parameter can be specified on properties with a CAL-ADDRESS value type. This parameter specifies those calendar users whom have been delegated participation in a group-scheduled event or to-do by the calendar user specified by the property. The individual calendar address parameter values MUST each be specified in a quoted-string.
描述：此参数可以在具有CAL-ADDRESS值类型的属性上指定。此参数指定由属性指定的日历用户委派参与组计划事件或待办事项的日历用户。每个日历地址参数值必须在带引号的字符串中指定。
Example:
例子：
ATTENDEE;DELEGATED-TO="mailto:jdoe@example.com","mailto:jqpublic
@example.com":mailto:jsmith@example.com
ATTENDEE;DELEGATED-TO="mailto:jdoe@example.com","mailto:jqpublic
@example.com":mailto:jsmith@example.com
Parameter Name: DIR
参数名称：DIR
Purpose: To specify reference to a directory entry associated with the calendar user specified by the property.
目的：指定对与属性指定的日历用户关联的目录项的引用。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
dirparam = "DIR" "=" DQUOTE uri DQUOTE
dirparam=“DIR”“=”DQUOTE uri DQUOTE
Description: This parameter can be specified on properties with a CAL-ADDRESS value type. The parameter specifies a reference to the directory entry associated with the calendar user specified by the property. The parameter value is a URI. The URI parameter value MUST be specified in a quoted-string.
描述：此参数可以在具有CAL-ADDRESS值类型的属性上指定。该参数指定对与属性指定的日历用户关联的目录项的引用。参数值是一个URI。URI参数值必须在带引号的字符串中指定。
Note: While there is no restriction imposed on the URI schemes allowed for this parameter, CID [RFC2392], DATA [RFC2397], FILE [RFC1738], FTP [RFC1738], HTTP [RFC2616], HTTPS [RFC2818], LDAP [RFC4516], and MID [RFC2392] are the URI schemes most commonly used by current implementations.
注意：虽然此参数允许的URI方案没有限制，但CID[RFC2392]、数据[RFC2397]、文件[RFC1738]、FTP[RFC1738]、HTTP[RFC2616]、HTTPS[RFC2818]、LDAP[RFC4516]和MID[RFC2392]是当前实现最常用的URI方案。
Example:
例子：
ORGANIZER;DIR="ldap://example.com:6666/o=ABC%20Industries,
c=US???(cn=Jim%20Dolittle)":mailto:jimdo@example.com
ORGANIZER;DIR="ldap://example.com:6666/o=ABC%20Industries,
c=US???(cn=Jim%20Dolittle)":mailto:jimdo@example.com
Parameter Name: ENCODING
参数名称：编码
Purpose: To specify an alternate inline encoding for the property value.
目的：为属性值指定替代内联编码。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
encodingparam = "ENCODING" "=" ( "8BIT" ; "8bit" text encoding is defined in [RFC2045] / "BASE64" ; "BASE64" binary encoding format is defined in [RFC4648] )
encodingparam=“ENCODING”“=”（[RFC2045]/“BASE64”中定义了8BIT；“8BIT”文本编码；[RFC4648]中定义了“BASE64”二进制编码格式）
Description: This property parameter identifies the inline encoding used in a property value. The default encoding is "8BIT", corresponding to a property value consisting of text. The "BASE64" encoding type corresponds to a property value encoded using the "BASE64" encoding defined in [RFC2045].
描述：此属性参数标识属性值中使用的内联编码。默认编码为“8位”，对应于由文本组成的属性值。“BASE64”编码类型对应于使用[RFC2045]中定义的“BASE64”编码编码的属性值。
If the value type parameter is ";VALUE=BINARY", then the inline encoding parameter MUST be specified with the value ";ENCODING=BASE64".
如果值类型参数为“value=BINARY”，则必须使用值“encoding=BASE64”指定内联编码参数。
Example:
例子：
ATTACH;FMTTYPE=text/plain;ENCODING=BASE64;VALUE=BINARY:TG9yZW 0gaXBzdW0gZG9sb3Igc2l0IGFtZXQsIGNvbnNlY3RldHVyIGFkaXBpc2ljaW 5nIGVsaXQsIHNlZCBkbyBlaXVzbW9kIHRlbXBvciBpbmNpZGlkdW50IHV0IG xhYm9yZSBldCBkb2xvcmUgbWFnbmEgYWxpcXVhLiBVdCBlbmltIGFkIG1pbm ltIHZlbmlhbSwgcXVpcyBub3N0cnVkIGV4ZXJjaXRhdGlvbiB1bGxhbWNvIG xhYm9yaXMgbmlzaSB1dCBhbGlxdWlwIGV4IGVhIGNvbW1vZG8gY29uc2VxdW F0LiBEdWlzIGF1dGUgaXJ1cmUgZG9sb3IgaW4gcmVwcmVoZW5kZXJpdCBpbi B2b2x1cHRhdGUgdmVsaXQgZXNzZSBjaWxsdW0gZG9sb3JlIGV1IGZ1Z2lhdC BudWxsYSBwYXJpYXR1ci4gRXhjZXB0ZXVyIHNpbnQgb2NjYWVjYXQgY3VwaW RhdGF0IG5vbiBwcm9pZGVudCwgc3VudCBpbiBjdWxwYSBxdWkgb2ZmaWNpYS BkZXNlcnVudCBtb2xsaXQgYW5pbSBpZCBlc3QgbGFib3J1bS4=
贴上FMTTYPE=文本/纯文本；编码=BASE64；值=二进制：TG9yZW 0GAXBZDW0GZGG9SB3IGC2L0IGFTZXQSignVnnly3RLDHVYIGFKAXBPC2LJAW 5NigVSAXQSIHNLZCBKBBBBYBLAXVZBW9KIHRLBXBVCIBPGMNpZGLKDW50IHMG XYM9YZSBLDCBKB2xVCMUGBFNBEGYXVCVBLBYGF1PBM LTIHZLBLHbBYBYB9VPCYBUB3N0NVKIGV4ZBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYBYF0LiBEdWlzIGF1dGUgaXJ1cmUgZG9sb3IgaW4gcmVwcmVoZW5kZXJpdCBpbi B2B2X1CHHRGUGMVSAXGZNZZZAWXSDW0GZGGG9SB3JLIGV1IGZ1Z2LHDC BUDWYSBWYXJPYXR1CI4GRXJZB0ZVYYHNPNQGB2NJYWYYXQ3VWAW RHDGF0IG5VBIBWCM9PZGWWWWWZBG3VU5VUDCBJBZZBJDWWYXWYWYBK2ZBZBZBZBQBZBZBZBQBZBZBZBZBZBZ4=
Parameter Name: FMTTYPE
参数名称：FMTTYPE
Purpose: To specify the content type of a referenced object.
目的：指定引用对象的内容类型。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
fmttypeparam = "FMTTYPE" "=" type-name "/" subtype-name ; Where "type-name" and "subtype-name" are ; defined in Section 4.2 of [RFC4288].
fmttypeparam=“FMTTYPE”“=”类型名称”/”子类型名称；其中“类型名称”和“子类型名称”为：；定义见[RFC4288]第4.2节。
Description: This parameter can be specified on properties that are used to reference an object. The parameter specifies the media type [RFC4288] of the referenced object. For example, on the "ATTACH" property, an FTP type URI value does not, by itself,
描述：可以在用于引用对象的属性上指定此参数。该参数指定引用对象的媒体类型[RFC4288]。例如，在“ATTACH”属性上，FTP类型URI值本身并不，
necessarily convey the type of content associated with the resource. The parameter value MUST be the text for either an IANA-registered media type or a non-standard media type.
必须传达与资源关联的内容类型。参数值必须是IANA注册媒体类型或非标准媒体类型的文本。
Example:
例子：
ATTACH;FMTTYPE=application/msword:ftp://example.com/pub/docs/
agenda.doc
ATTACH;FMTTYPE=application/msword:ftp://example.com/pub/docs/
agenda.doc
Parameter Name: FBTYPE
参数名称：FBTYPE
Purpose: To specify the free or busy time type.
目的：指定空闲或繁忙时间类型。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
fbtypeparam = "FBTYPE" "=" ("FREE" / "BUSY"
/ "BUSY-UNAVAILABLE" / "BUSY-TENTATIVE"
/ x-name
; Some experimental iCalendar free/busy type.
/ iana-token)
; Some other IANA-registered iCalendar free/busy type.
fbtypeparam = "FBTYPE" "=" ("FREE" / "BUSY"
/ "BUSY-UNAVAILABLE" / "BUSY-TENTATIVE"
/ x-name
; Some experimental iCalendar free/busy type.
/ iana-token)
; Some other IANA-registered iCalendar free/busy type.
Description: This parameter specifies the free or busy time type. The value FREE indicates that the time interval is free for scheduling. The value BUSY indicates that the time interval is busy because one or more events have been scheduled for that interval. The value BUSY-UNAVAILABLE indicates that the time interval is busy and that the interval can not be scheduled. The value BUSY-TENTATIVE indicates that the time interval is busy because one or more events have been tentatively scheduled for that interval. If not specified on a property that allows this parameter, the default is BUSY. Applications MUST treat x-name and iana-token values they don't recognize the same way as they would the BUSY value.
描述：此参数指定空闲或繁忙时间类型。值FREE表示时间间隔对于调度是自由的。值BUSY表示时间间隔正忙，因为已为该时间间隔安排了一个或多个事件。值BUSY-UNAVAILABLE表示时间间隔正忙，无法安排时间间隔。值BUSY-Tential表示时间间隔正忙，因为一个或多个事件已暂定为该时间间隔。如果未在允许此参数的属性上指定，则默认为忙。应用程序必须处理x-name和iana令牌值，因为它们无法识别繁忙值。
Example: The following is an example of this parameter on a "FREEBUSY" property.
示例：以下是“FREEBUSY”属性上此参数的示例。
FREEBUSY;FBTYPE=BUSY:19980415T133000Z/19980415T170000Z
FREEBUSY;FBTYPE=BUSY:19980415T133000Z/19980415T170000Z
Parameter Name: LANGUAGE
参数名称：语言
Purpose: To specify the language for text values in a property or property parameter.
目的：为属性或属性参数中的文本值指定语言。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
languageparam = "LANGUAGE" "=" language
languageparam=“LANGUAGE”“=”语言
language = Language-Tag ; As defined in [RFC5646].
语言=语言标签；如[RFC5646]中所定义。
Description: This parameter identifies the language of the text in the property value and of all property parameter values of the property. The value of the "LANGUAGE" property parameter is that defined in [RFC5646].
描述：此参数标识属性值中文本的语言以及属性的所有属性参数值的语言。“LANGUAGE”属性参数的值在[RFC5646]中定义。
For transport in a MIME entity, the Content-Language header field can be used to set the default language for the entire body part. Otherwise, no default language is assumed.
对于MIME实体中的传输，可以使用Content Language header字段为整个身体部位设置默认语言。否则，假定没有默认语言。
Example: The following are examples of this parameter on the "SUMMARY" and "LOCATION" properties:
示例：以下是“摘要”和“位置”属性上此参数的示例：
SUMMARY;LANGUAGE=en-US:Company Holiday Party
SUMMARY;LANGUAGE=en-US:Company Holiday Party
LOCATION;LANGUAGE=en:Germany
LOCATION;LANGUAGE=en:Germany
LOCATION;LANGUAGE=no:Tyskland
LOCATION;LANGUAGE=no:Tyskland
Parameter Name: MEMBER
参数名称：成员
Purpose: To specify the group or list membership of the calendar user specified by the property.
目的：指定属性指定的日历用户的组或列表成员身份。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
memberparam = "MEMBER" "=" DQUOTE cal-address DQUOTE *("," DQUOTE cal-address DQUOTE)
memberparam=“MEMBER”“=”DQUOTE校准地址DQUOTE*（“，”DQUOTE校准地址DQUOTE）
Description: This parameter can be specified on properties with a CAL-ADDRESS value type. The parameter identifies the groups or list membership for the calendar user specified by the property. The parameter value is either a single calendar address in a quoted-string or a COMMA-separated list of calendar addresses, each in a quoted-string. The individual calendar address parameter values MUST each be specified in a quoted-string.
描述：此参数可以在具有CAL-ADDRESS值类型的属性上指定。该参数标识属性指定的日历用户的组或列表成员身份。参数值可以是带引号的字符串中的单个日历地址，也可以是以逗号分隔的日历地址列表，每个日历地址都在带引号的字符串中。每个日历地址参数值必须在带引号的字符串中指定。
Example:
例子：
ATTENDEE;MEMBER="mailto:ietf-calsch@example.org":mailto:
jsmith@example.com
ATTENDEE;MEMBER="mailto:ietf-calsch@example.org":mailto:
jsmith@example.com
ATTENDEE;MEMBER="mailto:projectA@example.com","mailto:pr
ojectB@example.com":mailto:janedoe@example.com
ATTENDEE;MEMBER="mailto:projectA@example.com","mailto:pr
ojectB@example.com":mailto:janedoe@example.com
Parameter Name: PARTSTAT
参数名称：PARTSTAT
Purpose: To specify the participation status for the calendar user specified by the property.
目的：指定属性指定的日历用户的参与状态。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
partstatparam = "PARTSTAT" "=" (partstat-event / partstat-todo / partstat-jour)
partstatparam=“PARTSTAT”“=”（PARTSTAT事件/PARTSTAT todo/PARTSTAT jour）
partstat-event = ("NEEDS-ACTION" ; Event needs action
/ "ACCEPTED" ; Event accepted
/ "DECLINED" ; Event declined
/ "TENTATIVE" ; Event tentatively
; accepted
/ "DELEGATED" ; Event delegated
/ x-name ; Experimental status
/ iana-token) ; Other IANA-registered
; status
; These are the participation statuses for a "VEVENT".
; Default is NEEDS-ACTION.
partstat-event = ("NEEDS-ACTION" ; Event needs action
/ "ACCEPTED" ; Event accepted
/ "DECLINED" ; Event declined
/ "TENTATIVE" ; Event tentatively
; accepted
/ "DELEGATED" ; Event delegated
/ x-name ; Experimental status
/ iana-token) ; Other IANA-registered
; status
; These are the participation statuses for a "VEVENT".
; Default is NEEDS-ACTION.
partstat-todo = ("NEEDS-ACTION" ; To-do needs action
/ "ACCEPTED" ; To-do accepted
/ "DECLINED" ; To-do declined
/ "TENTATIVE" ; To-do tentatively
; accepted
partstat-todo = ("NEEDS-ACTION" ; To-do needs action
/ "ACCEPTED" ; To-do accepted
/ "DECLINED" ; To-do declined
/ "TENTATIVE" ; To-do tentatively
; accepted
/ "DELEGATED" ; To-do delegated
/ "COMPLETED" ; To-do completed
; COMPLETED property has
; DATE-TIME completed
/ "IN-PROCESS" ; To-do in process of
; being completed
/ x-name ; Experimental status
/ iana-token) ; Other IANA-registered
; status
; These are the participation statuses for a "VTODO".
; Default is NEEDS-ACTION.
/ "DELEGATED" ; To-do delegated
/ "COMPLETED" ; To-do completed
; COMPLETED property has
; DATE-TIME completed
/ "IN-PROCESS" ; To-do in process of
; being completed
/ x-name ; Experimental status
/ iana-token) ; Other IANA-registered
; status
; These are the participation statuses for a "VTODO".
; Default is NEEDS-ACTION.
partstat-jour = ("NEEDS-ACTION" ; Journal needs action
/ "ACCEPTED" ; Journal accepted
/ "DECLINED" ; Journal declined
/ x-name ; Experimental status
/ iana-token) ; Other IANA-registered
; status
; These are the participation statuses for a "VJOURNAL".
; Default is NEEDS-ACTION.
partstat-jour = ("NEEDS-ACTION" ; Journal needs action
/ "ACCEPTED" ; Journal accepted
/ "DECLINED" ; Journal declined
/ x-name ; Experimental status
/ iana-token) ; Other IANA-registered
; status
; These are the participation statuses for a "VJOURNAL".
; Default is NEEDS-ACTION.
Description: This parameter can be specified on properties with a CAL-ADDRESS value type. The parameter identifies the participation status for the calendar user specified by the property value. The parameter values differ depending on whether they are associated with a group-scheduled "VEVENT", "VTODO", or "VJOURNAL". The values MUST match one of the values allowed for the given calendar component. If not specified on a property that allows this parameter, the default value is NEEDS-ACTION. Applications MUST treat x-name and iana-token values they don't recognize the same way as they would the NEEDS-ACTION value.
描述：此参数可以在具有CAL-ADDRESS值类型的属性上指定。该参数标识由属性值指定的日历用户的参与状态。参数值的不同取决于它们是否与组计划的“VEVENT”、“VTODO”或“VJORY”相关联。这些值必须与给定日历组件允许的值之一匹配。如果未在允许此参数的属性上指定，则默认值为NEEDS-ACTION。应用程序必须处理x-name和iana令牌值，因为它们识别的方式与处理NEEDS-ACTION值的方式不同。
Example:
例子：
ATTENDEE;PARTSTAT=DECLINED:mailto:jsmith@example.com
ATTENDEE;PARTSTAT=DECLINED:mailto:jsmith@example.com
Parameter Name: RANGE
参数名称：范围
Purpose: To specify the effective range of recurrence instances from the instance specified by the recurrence identifier specified by the property.
目的：从属性指定的重复标识符指定的实例中指定重复实例的有效范围。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
rangeparam = "RANGE" "=" "THISANDFUTURE" ; To specify the instance specified by the recurrence identifier ; and all subsequent recurrence instances.
rangeparam=“RANGE”“=”THISANDFUTURE”；指定由重复标识符指定的实例；以及所有后续的重复实例。
Description: This parameter can be specified on a property that specifies a recurrence identifier. The parameter specifies the effective range of recurrence instances that is specified by the property. The effective range is from the recurrence identifier specified by the property. If this parameter is not specified on an allowed property, then the default range is the single instance specified by the recurrence identifier value of the property. The parameter value can only be "THISANDFUTURE" to indicate a range defined by the recurrence identifier and all subsequent instances. The value "THISANDPRIOR" is deprecated by this revision of iCalendar and MUST NOT be generated by applications.
描述：可以在指定重复标识符的属性上指定此参数。该参数指定由属性指定的重复实例的有效范围。有效范围从属性指定的重复标识符开始。如果未在允许的属性上指定此参数，则默认范围为该属性的重复标识符值指定的单个实例。参数值只能是“THISANDFUTURE”，以指示由重复标识符和所有后续实例定义的范围。此版本的iCalendar不推荐使用“ThisandPrevior”值，应用程序不得生成该值。
Example:
例子：
RECURRENCE-ID;RANGE=THISANDFUTURE:19980401T133000Z
RECURRENCE-ID;RANGE=THISANDFUTURE:19980401T133000Z
Parameter Name: RELATED
参数名称：相关
Purpose: To specify the relationship of the alarm trigger with respect to the start or end of the calendar component.
目的：指定报警触发器与日历组件开始或结束的关系。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
trigrelparam = "RELATED" "="
("START" ; Trigger off of start
/ "END") ; Trigger off of end
trigrelparam = "RELATED" "="
("START" ; Trigger off of start
/ "END") ; Trigger off of end
Description: This parameter can be specified on properties that specify an alarm trigger with a "DURATION" value type. The parameter specifies whether the alarm will trigger relative to the start or end of the calendar component. The parameter value START will set the alarm to trigger off the start of the calendar component; the parameter value END will set the alarm to trigger off the end of the calendar component. If the parameter is not specified on an allowable property, then the default is START.
描述：可以在指定具有“持续时间”值类型的报警触发器的属性上指定此参数。该参数指定报警是相对于日历组件的开始还是结束触发。参数值START将设置报警以触发日历组件的启动；参数值END将设置报警以触发日历组件的结束。如果未在允许的属性上指定参数，则默认值为“开始”。
Example:
例子：
TRIGGER;RELATED=END:PT5M
TRIGGER;RELATED=END:PT5M
Parameter Name: RELTYPE
参数名称：RELTYPE
Purpose: To specify the type of hierarchical relationship associated with the calendar component specified by the property.
目的：指定与属性指定的日历组件关联的层次关系类型。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
reltypeparam = "RELTYPE" "="
("PARENT" ; Parent relationship - Default
/ "CHILD" ; Child relationship
/ "SIBLING" ; Sibling relationship
/ iana-token ; Some other IANA-registered
; iCalendar relationship type
/ x-name) ; A non-standard, experimental
; relationship type
reltypeparam = "RELTYPE" "="
("PARENT" ; Parent relationship - Default
/ "CHILD" ; Child relationship
/ "SIBLING" ; Sibling relationship
/ iana-token ; Some other IANA-registered
; iCalendar relationship type
/ x-name) ; A non-standard, experimental
; relationship type
Description: This parameter can be specified on a property that references another related calendar. The parameter specifies the hierarchical relationship type of the calendar component referenced by the property. The parameter value can be PARENT, to indicate that the referenced calendar component is a superior of calendar component; CHILD to indicate that the referenced calendar component is a subordinate of the calendar component; or SIBLING to indicate that the referenced calendar component is a peer of the calendar component. If this parameter is not specified on an allowable property, the default relationship type is PARENT. Applications MUST treat x-name and iana-token values they don't recognize the same way as they would the PARENT value.
描述：可以在引用其他相关日历的属性上指定此参数。该参数指定属性引用的日历组件的层次关系类型。参数值可以是父级，表示引用的日历组件是日历组件的上级；子级，指示引用的日历组件是日历组件的下级；或同级，指示引用的日历组件是日历组件的对等组件。如果未在允许的属性上指定此参数，则默认关系类型为父关系。应用程序必须处理x-name和iana令牌值，因为它们不能以与父值相同的方式识别它们。
Example:
例子：
RELATED-TO;RELTYPE=SIBLING:19960401-080045-4000F192713@
example.com
RELATED-TO;RELTYPE=SIBLING:19960401-080045-4000F192713@
example.com
Parameter Name: ROLE
参数名称：角色
Purpose: To specify the participation role for the calendar user specified by the property.
目的：为属性指定的日历用户指定参与角色。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
roleparam = "ROLE" "="
("CHAIR" ; Indicates chair of the
; calendar entity
/ "REQ-PARTICIPANT" ; Indicates a participant whose
; participation is required
/ "OPT-PARTICIPANT" ; Indicates a participant whose
; participation is optional
/ "NON-PARTICIPANT" ; Indicates a participant who
; is copied for information
; purposes only
/ x-name ; Experimental role
/ iana-token) ; Other IANA role
; Default is REQ-PARTICIPANT
roleparam = "ROLE" "="
("CHAIR" ; Indicates chair of the
; calendar entity
/ "REQ-PARTICIPANT" ; Indicates a participant whose
; participation is required
/ "OPT-PARTICIPANT" ; Indicates a participant whose
; participation is optional
/ "NON-PARTICIPANT" ; Indicates a participant who
; is copied for information
; purposes only
/ x-name ; Experimental role
/ iana-token) ; Other IANA role
; Default is REQ-PARTICIPANT
Description: This parameter can be specified on properties with a CAL-ADDRESS value type. The parameter specifies the participation role for the calendar user specified by the property in the group schedule calendar component. If not specified on a property that allows this parameter, the default value is REQ-PARTICIPANT. Applications MUST treat x-name and iana-token values they don't recognize the same way as they would the REQ-PARTICIPANT value.
描述：此参数可以在具有CAL-ADDRESS值类型的属性上指定。该参数指定由组日程日历组件中的属性指定的日历用户的参与角色。如果未在允许此参数的属性上指定，则默认值为REQ-PARTICIPANT。应用程序必须处理x-name和iana令牌值，因为它们不能识别与REQ-PARTICIPANT值相同的方式。
Example:
例子：
ATTENDEE;ROLE=CHAIR:mailto:mrbig@example.com
ATTENDEE;ROLE=CHAIR:mailto:mrbig@example.com
Parameter Name: RSVP
参数名称：RSVP
Purpose: To specify whether there is an expectation of a favor of a reply from the calendar user specified by the property value.
目的：指定属性值指定的日历用户是否希望得到回复。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
rsvpparam = "RSVP" "=" ("TRUE" / "FALSE")
; Default is FALSE
rsvpparam = "RSVP" "=" ("TRUE" / "FALSE")
; Default is FALSE
Description: This parameter can be specified on properties with a CAL-ADDRESS value type. The parameter identifies the expectation of a reply from the calendar user specified by the property value. This parameter is used by the "Organizer" to request a participation status reply from an "Attendee" of a group-scheduled event or to-do. If not specified on a property that allows this parameter, the default value is FALSE.
描述：此参数可以在具有CAL-ADDRESS值类型的属性上指定。该参数标识由属性值指定的日历用户对回复的期望。“组织者”使用此参数请求团体预定活动或待办事项的“与会者”回复参与状态。如果未在允许此参数的属性上指定，则默认值为FALSE。
Example:
例子：
ATTENDEE;RSVP=TRUE:mailto:jsmith@example.com
ATTENDEE;RSVP=TRUE:mailto:jsmith@example.com
Parameter Name: SENT-BY
参数名称：发送人
Purpose: To specify the calendar user that is acting on behalf of the calendar user specified by the property.
目的：指定代表属性指定的日历用户的日历用户。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
sentbyparam = "SENT-BY" "=" DQUOTE cal-address DQUOTE
sentbyparam=“发送人”“=”DQUOTE校准地址DQUOTE
Description: This parameter can be specified on properties with a CAL-ADDRESS value type. The parameter specifies the calendar user that is acting on behalf of the calendar user specified by the property. The parameter value MUST be a mailto URI as defined in [RFC2368]. The individual calendar address parameter values MUST each be specified in a quoted-string.
描述：此参数可以在具有CAL-ADDRESS值类型的属性上指定。该参数指定代表属性指定的日历用户行事的日历用户。参数值必须是[RFC2368]中定义的mailto URI。每个日历地址参数值必须在带引号的字符串中指定。
Example:
例子：
ORGANIZER;SENT-BY="mailto:sray@example.com":mailto:
jsmith@example.com
ORGANIZER;SENT-BY="mailto:sray@example.com":mailto:
jsmith@example.com
Parameter Name: TZID
参数名称：TZID
Purpose: To specify the identifier for the time zone definition for a time component in the property value.
目的：在属性值中为时间组件的时区定义指定标识符。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
tzidparam = "TZID" "=" [tzidprefix] paramtext
tzidparam=“TZID”“=”[tzidprefix]参数文本
tzidprefix = "/"
tzidprefix=“/”
Description: This parameter MUST be specified on the "DTSTART", "DTEND", "DUE", "EXDATE", and "RDATE" properties when either a DATE-TIME or TIME value type is specified and when the value is neither a UTC or a "floating" time. Refer to the DATE-TIME or TIME value type definition for a description of UTC and "floating time" formats. This property parameter specifies a text value
说明：如果指定了日期-时间或时间值类型，并且该值既不是UTC时间也不是浮动时间，则必须在“DTSTART”、“DTEND”、“DUE”、“EXDATE”和“RDATE”属性中指定此参数。有关UTC和“浮动时间”格式的说明，请参阅日期时间或时间值类型定义。此属性参数指定文本值
that uniquely identifies the "VTIMEZONE" calendar component to be used when evaluating the time portion of the property. The value of the "TZID" property parameter will be equal to the value of the "TZID" property for the matching time zone definition. An individual "VTIMEZONE" calendar component MUST be specified for each unique "TZID" parameter value specified in the iCalendar object.
唯一标识在评估属性的时间部分时要使用的“VTIMEZONE”日历组件的。“TZID”属性参数的值将等于匹配时区定义的“TZID”属性的值。必须为iCalendar对象中指定的每个唯一“TZID”参数值指定单独的“VTIMEZONE”日历组件。
The parameter MUST be specified on properties with a DATE-TIME value if the DATE-TIME is not either a UTC or a "floating" time. Failure to include and follow VTIMEZONE definitions in iCalendar objects may lead to inconsistent understanding of the local time at any given location.
如果日期时间不是UTC或“浮动”时间，则必须在具有日期时间值的属性上指定该参数。未能在iCalendar对象中包含并遵循VTIMEZONE定义可能会导致对任何给定位置的本地时间的理解不一致。
The presence of the SOLIDUS character as a prefix, indicates that this "TZID" represents a unique ID in a globally defined time zone registry (when such registry is defined).
SOLIDUS字符作为前缀的存在表示此“TZID”表示全局定义的时区注册表中的唯一ID（定义该注册表时）。
Note: This document does not define a naming convention for time zone identifiers. Implementers may want to use the naming conventions defined in existing time zone specifications such as the public-domain TZ database [TZDB]. The specification of globally unique time zone identifiers is not addressed by this document and is left for future study.
注意：本文档未定义时区标识符的命名约定。实现者可能希望使用现有时区规范（如公共域TZ数据库[TZDB]）中定义的命名约定。本文件未涉及全局唯一时区标识符的规范，留待将来研究。
The following are examples of this property parameter:
以下是此属性参数的示例：
DTSTART;TZID=America/New_York:19980119T020000
DTSTART;TZID=America/New_York:19980119T020000
DTEND;TZID=America/New_York:19980119T030000
DTEND;TZID=America/New_York:19980119T030000
The "TZID" property parameter MUST NOT be applied to DATE properties and DATE-TIME or TIME properties whose time values are specified in UTC.
“TZID”属性参数不得应用于日期属性和日期时间属性或时间值以UTC指定的时间属性。
The use of local time in a DATE-TIME or TIME value without the "TZID" property parameter is to be interpreted as floating time, regardless of the existence of "VTIMEZONE" calendar components in the iCalendar object.
无论iCalendar对象中是否存在“VTIMEZONE”日历组件，在没有“TZID”属性参数的日期时间或时间值中使用本地时间都将被解释为浮动时间。
For more information, see the sections on the value types DATE-TIME and TIME.
有关详细信息，请参见值类型DATE-TIME和TIME部分。
Parameter Name: VALUE
参数名称：VALUE
Purpose: To explicitly specify the value type format for a property value.
目的：明确指定属性值的值类型格式。
Format Definition: This property parameter is defined by the following notation:
格式定义：此属性参数由以下符号定义：
valuetypeparam = "VALUE" "=" valuetype
valuetypeparam=“VALUE”“=”valuetype
valuetype = ("BINARY"
/ "BOOLEAN"
/ "CAL-ADDRESS"
/ "DATE"
/ "DATE-TIME"
/ "DURATION"
/ "FLOAT"
/ "INTEGER"
/ "PERIOD"
/ "RECUR"
/ "TEXT"
/ "TIME"
/ "URI"
/ "UTC-OFFSET"
/ x-name
; Some experimental iCalendar value type.
/ iana-token)
; Some other IANA-registered iCalendar value type.
valuetype = ("BINARY"
/ "BOOLEAN"
/ "CAL-ADDRESS"
/ "DATE"
/ "DATE-TIME"
/ "DURATION"
/ "FLOAT"
/ "INTEGER"
/ "PERIOD"
/ "RECUR"
/ "TEXT"
/ "TIME"
/ "URI"
/ "UTC-OFFSET"
/ x-name
; Some experimental iCalendar value type.
/ iana-token)
; Some other IANA-registered iCalendar value type.
Description: This parameter specifies the value type and format of the property value. The property values MUST be of a single value type. For example, a "RDATE" property cannot have a combination of DATE-TIME and TIME value types.
说明：此参数指定属性值的值类型和格式。属性值必须为单一值类型。例如，“RDATE”属性不能具有日期-时间和时间值类型的组合。
If the property's value is the default value type, then this parameter need not be specified. However, if the property's default value type is overridden by some other allowable value type, then this parameter MUST be specified.
如果属性的值是默认值类型，则无需指定此参数。但是，如果属性的默认值类型被其他允许的值类型覆盖，则必须指定此参数。
Applications MUST preserve the value data for x-name and iana-token values that they don't recognize without attempting to interpret or parse the value data.
应用程序必须保留其无法识别的x-name和iana令牌值的值数据，而不尝试解释或解析值数据。
The properties in an iCalendar object are strongly typed. The definition of each property restricts the value to be one of the value data types, or simply value types, defined in this section. The value type for a property will either be specified implicitly as the default value type or will be explicitly specified with the "VALUE" parameter. If the value type of a property is one of the alternate valid types, then it MUST be explicitly specified with the "VALUE" parameter.
iCalendar对象中的属性是强类型的。每个属性的定义都将值限制为本节中定义的值数据类型之一，或仅为值类型。属性的值类型将隐式指定为默认值类型，或使用“value”参数显式指定。如果属性的值类型是备用有效类型之一，则必须使用“value”参数显式指定它。
Value Name: BINARY
值名称：二进制
Purpose: This value type is used to identify properties that contain a character encoding of inline binary data. For example, an inline attachment of a document might be included in an iCalendar object.
用途：此值类型用于标识包含内联二进制数据字符编码的属性。例如，文档的内联附件可能包含在iCalendar对象中。
Format Definition: This value type is defined by the following notation:
格式定义：此值类型由以下符号定义：
binary = *(4b-char) [b-end]
; A "BASE64" encoded character string, as defined by [RFC4648].
binary = *(4b-char) [b-end]
; A "BASE64" encoded character string, as defined by [RFC4648].
b-end = (2b-char "==") / (3b-char "=")
b-end = (2b-char "==") / (3b-char "=")
b-char = ALPHA / DIGIT / "+" / "/"
b-char = ALPHA / DIGIT / "+" / "/"
Description: Property values with this value type MUST also include the inline encoding parameter sequence of ";ENCODING=BASE64". That is, all inline binary data MUST first be character encoded using the "BASE64" encoding method defined in [RFC2045]. No additional content value encoding (i.e., BACKSLASH character encoding, see Section 3.3.11) is defined for this value type.
描述：此值类型的属性值还必须包括内联编码参数序列“encoding=BASE64”。也就是说，所有内联二进制数据必须首先使用[RFC2045]中定义的“BASE64”编码方法进行字符编码。没有为该值类型定义额外的内容值编码（即反斜杠字符编码，见第3.3.11节）。
Example: The following is an example of a "BASE64" encoded binary value data:
示例：以下是“BASE64”编码二进制值数据的示例：
ATTACH;FMTTYPE=image/vnd.microsoft.icon;ENCODING=BASE64;VALUE
=BINARY:AAABAAEAEBAQAAEABAAoAQAAFgAAACgAAAAQAAAAIAAAAAEABAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAgIAAAICAgADAwMAA////AAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAMwAAAAAAABNEMQAAAAAAAkQgAAAAAAJEREQgAA
ACECQ0QgEgAAQxQzM0E0AABERCRCREQAADRDJEJEQwAAAhA0QwEQAAAAAERE
AAAAAAAAREQAAAAAAAAkQgAAAAAAAAMgAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAA
ATTACH;FMTTYPE=image/vnd.microsoft.icon;ENCODING=BASE64;VALUE
=BINARY:AAABAAEAEBAQAAEABAAoAQAAFgAAACgAAAAQAAAAIAAAAAEABAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAgIAAAICAgADAwMAA////AAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAMwAAAAAAABNEMQAAAAAAAkQgAAAAAAJEREQgAA
ACECQ0QgEgAAQxQzM0E0AABERCRCREQAADRDJEJEQwAAAhA0QwEQAAAAAERE
AAAAAAAAREQAAAAAAAAkQgAAAAAAAAMgAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAA
Value Name: BOOLEAN
值名称：BOOLEAN
Purpose: This value type is used to identify properties that contain either a "TRUE" or "FALSE" Boolean value.
用途：此值类型用于标识包含“TRUE”或“FALSE”布尔值的属性。
Format Definition: This value type is defined by the following notation:
格式定义：此值类型由以下符号定义：
boolean = "TRUE" / "FALSE"
boolean = "TRUE" / "FALSE"
Description: These values are case-insensitive text. No additional content value encoding (i.e., BACKSLASH character encoding, see Section 3.3.11) is defined for this value type.
说明：这些值是不区分大小写的文本。没有为该值类型定义额外的内容值编码（即反斜杠字符编码，见第3.3.11节）。
Example: The following is an example of a hypothetical property that has a BOOLEAN value type:
示例：以下是具有布尔值类型的假设属性的示例：
TRUE
符合事实的
Value Name: CAL-ADDRESS
值名称：CAL-ADDRESS
Purpose: This value type is used to identify properties that contain a calendar user address.
用途：此值类型用于标识包含日历用户地址的属性。
Format Definition: This value type is defined by the following notation:
格式定义：此值类型由以下符号定义：
cal-address = uri
cal-address = uri
Description: The value is a URI as defined by [RFC3986] or any other IANA-registered form for a URI. When used to address an Internet
描述：该值是[RFC3986]定义的URI或URI的任何其他IANA注册表单。当用于寻址Internet时
email transport address for a calendar user, the value MUST be a mailto URI, as defined by [RFC2368]. No additional content value encoding (i.e., BACKSLASH character encoding, see Section 3.3.11) is defined for this value type.
对于日历用户的电子邮件传输地址，该值必须是[RFC2368]定义的mailto URI。没有为该值类型定义额外的内容值编码（即反斜杠字符编码，见第3.3.11节）。
Example:
例子：
mailto:jane_doe@example.com
邮寄地址：简_doe@example.com
Value Name: DATE
值名称：日期
Purpose: This value type is used to identify values that contain a calendar date.
用途：此值类型用于标识包含日历日期的值。
Format Definition: This value type is defined by the following notation:
格式定义：此值类型由以下符号定义：
date = date-value
date = date-value
date-value = date-fullyear date-month date-mday
date-fullyear = 4DIGIT
date-month = 2DIGIT ;01-12
date-mday = 2DIGIT ;01-28, 01-29, 01-30, 01-31
;based on month/year
date-value = date-fullyear date-month date-mday
date-fullyear = 4DIGIT
date-month = 2DIGIT ;01-12
date-mday = 2DIGIT ;01-28, 01-29, 01-30, 01-31
;based on month/year
Description: If the property permits, multiple "date" values are specified as a COMMA-separated list of values. The format for the value type is based on the [ISO.8601.2004] complete representation, basic format for a calendar date. The textual format specifies a four-digit year, two-digit month, and two-digit day of the month. There are no separator characters between the year, month, and day component text.
描述：如果属性允许，将多个“日期”值指定为逗号分隔的值列表。值类型的格式基于[ISO.8601.2004]完整表示法，即日历日期的基本格式。文本格式指定四位数的年份、两位数的月份和两位数的月份日期。年、月和日组件文本之间没有分隔符。
No additional content value encoding (i.e., BACKSLASH character encoding, see Section 3.3.11) is defined for this value type.
没有为该值类型定义额外的内容值编码（即反斜杠字符编码，见第3.3.11节）。
Example: The following represents July 14, 1997:
示例：以下为1997年7月14日：
19970714
19970714
Value Name: DATE-TIME
值名称：日期时间
Purpose: This value type is used to identify values that specify a precise calendar date and time of day.
用途：此值类型用于标识指定精确日历日期和时间的值。
Format Definition: This value type is defined by the following notation:
格式定义：此值类型由以下符号定义：
date-time = date "T" time ;As specified in the DATE and TIME ;value definitions
日期时间=日期“T”时间；按照日期和时间的规定；值定义
Description: If the property permits, multiple "DATE-TIME" values are specified as a COMMA-separated list of values. No additional content value encoding (i.e., BACKSLASH character encoding, see Section 3.3.11) is defined for this value type.
描述：如果属性允许，将多个“日期-时间”值指定为逗号分隔的值列表。没有为该值类型定义额外的内容值编码（即反斜杠字符编码，见第3.3.11节）。
The "DATE-TIME" value type is used to identify values that contain a precise calendar date and time of day. The format is based on the [ISO.8601.2004] complete representation, basic format for a calendar date and time of day. The text format is a concatenation of the "date", followed by the LATIN CAPITAL LETTER T character, the time designator, followed by the "time" format.
“日期-时间”值类型用于标识包含精确日历日期和时间的值。该格式基于[ISO.8601.2004]完整表示法，即日历日期和时间的基本格式。文本格式是“日期”的串联，后跟拉丁大写字母T字符（时间指示符），后跟“时间”格式。
The "DATE-TIME" value type expresses time values in three forms:
“日期-时间”值类型以三种形式表示时间值：
The form of date and time with UTC offset MUST NOT be used. For example, the following is not valid for a DATE-TIME value:
不得使用带有UTC偏移量的日期和时间格式。例如，以下内容对于日期时间值无效：
19980119T230000-0800 ;Invalid time format
199801119T230000-0800；无效的时间格式
FORM #1: DATE WITH LOCAL TIME
表格#1：日期和当地时间
The date with local time form is simply a DATE-TIME value that does not contain the UTC designator nor does it reference a time zone. For example, the following represents January 18, 1998, at 11 PM:
带有本地时间的日期表单只是一个日期时间值，不包含UTC指示符，也不引用时区。例如，以下为1998年1月18日晚上11时的数据：
19980118T230000
19980118T230000
DATE-TIME values of this type are said to be "floating" and are not bound to any time zone in particular. They are used to represent the same hour, minute, and second value regardless of which time zone is currently being observed. For example, an event can be defined that indicates that an individual will be busy from 11:00 AM to 1:00 PM every day, no matter which time zone the person is in. In these cases, a local time can be specified. The recipient of an iCalendar object with a property value consisting of a local time, without any relative time zone information, SHOULD interpret the value as being fixed to whatever time zone the "ATTENDEE" is in at any given moment. This means that two "Attendees", in different time zones, receiving the same event definition as a floating time, may be participating in the
这种类型的日期时间值被称为“浮动”值，不受任何时区的限制。它们用于表示相同的小时、分钟和秒值，而不管当前正在观察哪个时区。例如，可以定义一个事件，该事件指示个人将在每天上午11:00到下午1:00之间忙碌，无论此人处于哪个时区。在这些情况下，可以指定本地时间。属性值由本地时间组成的iCalendar对象的接收者（无任何相关时区信息）应将该值解释为固定在“与会者”在任何给定时刻所在的任何时区。这意味着两个“与会者”，在不同的时区，接收相同的事件定义作为浮动时间，可能会参与
event at different actual times. Floating time SHOULD only be used where that is the reasonable behavior.
事件发生在不同的实际时间。浮动时间只能在合理的情况下使用。
In most cases, a fixed time is desired. To properly communicate a fixed time in a property value, either UTC time or local time with time zone reference MUST be specified.
在大多数情况下，需要一个固定的时间。要在属性值中正确传递固定时间，必须指定UTC时间或带时区引用的本地时间。
The use of local time in a DATE-TIME value without the "TZID" property parameter is to be interpreted as floating time, regardless of the existence of "VTIMEZONE" calendar components in the iCalendar object.
无论iCalendar对象中是否存在“VTIMEZONE”日历组件，在没有“TZID”属性参数的日期时间值中使用本地时间都将被解释为浮动时间。
FORM #2: DATE WITH UTC TIME
表格2：UTC时间日期
The date with UTC time, or absolute time, is identified by a LATIN CAPITAL LETTER Z suffix character, the UTC designator, appended to the time value. For example, the following represents January 19, 1998, at 0700 UTC:
带有UTC时间或绝对时间的日期由时间值后附加的拉丁大写字母Z后缀字符（UTC指示符）标识。例如，以下表示1998年1月19日协调世界时0700时：
19980119T070000Z
19980119T070000Z
The "TZID" property parameter MUST NOT be applied to DATE-TIME properties whose time values are specified in UTC.
“TZID”属性参数不得应用于时间值以UTC指定的日期-时间属性。
FORM #3: DATE WITH LOCAL TIME AND TIME ZONE REFERENCE
表3：带有当地时间和时区参考的日期
The date and local time with reference to time zone information is identified by the use the "TZID" property parameter to reference the appropriate time zone definition. "TZID" is discussed in detail in Section 3.2.19. For example, the following represents 2:00 A.M. in New York on January 19, 1998:
参考时区信息的日期和本地时间通过使用“TZID”属性参数来参考适当的时区定义来标识。第3.2.19节详细讨论了“TZID”。例如，以下表示1998年1月19日纽约的凌晨2点：
TZID=America/New_York:19980119T020000
TZID=America/New_York:19980119T020000
If, based on the definition of the referenced time zone, the local time described occurs more than once (when changing from daylight to standard time), the DATE-TIME value refers to the first occurrence of the referenced time. Thus, TZID=America/ New_York:20071104T013000 indicates November 4, 2007 at 1:30 A.M. EDT (UTC-04:00). If the local time described does not occur (when changing from standard to daylight time), the DATE-TIME value is interpreted using the UTC offset before the gap in local times. Thus, TZID=America/New_York:20070311T023000 indicates March 11, 2007 at 3:30 A.M. EDT (UTC-04:00), one hour after 1:30 A.M. EST (UTC-05:00).
如果根据参考时区的定义，所述本地时间出现不止一次（从昼时更改为标准时间），则日期时间值指参考时间的第一次出现。因此，TZID=美国/纽约：20071104T013000表示2007年11月4日美国东部夏令时凌晨1:30（UTC-04:00）。如果未出现所述的本地时间（从标准时间更改为夏令时），则使用本地时间间隔前的UTC偏移量解释日期时间值。因此，TZID=美国/纽约：20070311T023000表示2007年3月11日美国东部时间凌晨3:30（UTC-04:00），美国东部时间凌晨1:30（UTC-05:00）后一小时。
A time value MUST only specify the second 60 when specifying a positive leap second. For example:
指定正闰秒时，时间值只能指定秒60。例如：
19970630T235960Z
19970630T235960Z
Implementations that do not support leap seconds SHOULD interpret the second 60 as equivalent to the second 59.
不支持闰秒的实现应将第二个60解释为等同于第二个59。
Example: The following represents July 14, 1997, at 1:30 PM in New York City in each of the three time formats, using the "DTSTART" property.
示例：以下表示1997年7月14日，纽约市下午1:30，使用“DTSTART”属性，采用三种时间格式。
DTSTART:19970714T133000 ; Local time
DTSTART:19970714T173000Z ; UTC time
DTSTART;TZID=America/New_York:19970714T133000
; Local time and time
; zone reference
DTSTART:19970714T133000 ; Local time
DTSTART:19970714T173000Z ; UTC time
DTSTART;TZID=America/New_York:19970714T133000
; Local time and time
; zone reference
Value Name: DURATION
值名称：持续时间
Purpose: This value type is used to identify properties that contain a duration of time.
用途：此值类型用于标识包含持续时间的属性。
Format Definition: This value type is defined by the following notation:
格式定义：此值类型由以下符号定义：
dur-value = (["+"] / "-") "P" (dur-date / dur-time / dur-week)
dur-value = (["+"] / "-") "P" (dur-date / dur-time / dur-week)
dur-date = dur-day [dur-time]
dur-time = "T" (dur-hour / dur-minute / dur-second)
dur-week = 1*DIGIT "W"
dur-hour = 1*DIGIT "H" [dur-minute]
dur-minute = 1*DIGIT "M" [dur-second]
dur-second = 1*DIGIT "S"
dur-day = 1*DIGIT "D"
dur-date = dur-day [dur-time]
dur-time = "T" (dur-hour / dur-minute / dur-second)
dur-week = 1*DIGIT "W"
dur-hour = 1*DIGIT "H" [dur-minute]
dur-minute = 1*DIGIT "M" [dur-second]
dur-second = 1*DIGIT "S"
dur-day = 1*DIGIT "D"
Description: If the property permits, multiple "duration" values are specified by a COMMA-separated list of values. The format is based on the [ISO.8601.2004] complete representation basic format with designators for the duration of time. The format can represent nominal durations (weeks and days) and accurate durations (hours, minutes, and seconds). Note that unlike [ISO.8601.2004], this value type doesn't support the "Y" and "M" designators to specify durations in terms of years and months.
描述：如果属性允许，多个“持续时间”值由逗号分隔的值列表指定。该格式基于[ISO.8601.2004]完整的表示基本格式，并带有持续时间的指示符。该格式可以表示名义持续时间（周和天）和准确持续时间（小时、分钟和秒）。请注意，与[ISO.8601.2004]不同，此值类型不支持“Y”和“M”指示符以年和月为单位指定持续时间。
The duration of a week or a day depends on its position in the calendar. In the case of discontinuities in the time scale, such as the change from standard time to daylight time and back, the computation of the exact duration requires the subtraction or addition of the change of duration of the discontinuity. Leap seconds MUST NOT be considered when computing an exact duration. When computing an exact duration, the greatest order time components MUST be added first, that is, the number of days MUST be added first, followed by the number of hours, number of minutes, and number of seconds.
一周或一天的持续时间取决于其在日历中的位置。对于时间尺度中的不连续性，例如从标准时间到夏时制的变化以及从夏时制到夏时制的变化，精确持续时间的计算需要减去或加上不连续性持续时间的变化。计算准确的持续时间时，不得考虑闰秒。在计算精确的持续时间时，必须首先添加最大订单时间组件，即必须首先添加天数，然后添加小时数、分钟数和秒数。
Negative durations are typically used to schedule an alarm to trigger before an associated time (see Section 3.8.6.3).
负持续时间通常用于安排在相关时间之前触发警报（见第3.8.6.3节）。
No additional content value encoding (i.e., BACKSLASH character encoding, see Section 3.3.11) are defined for this value type.
没有为该值类型定义额外的内容值编码（即反斜杠字符编码，见第3.3.11节）。
Example: A duration of 15 days, 5 hours, and 20 seconds would be:
示例：15天5小时20秒的持续时间为：
P15DT5H0M20S
P15DT5H0M20S
A duration of 7 weeks would be:
7周的持续时间为：
P7W
P7W
Value Name: FLOAT
值名称：FLOAT
Purpose: This value type is used to identify properties that contain a real-number value.
用途：此值类型用于标识包含实数值的属性。
Format Definition: This value type is defined by the following notation:
格式定义：此值类型由以下符号定义：
float = (["+"] / "-") 1*DIGIT ["." 1*DIGIT]
float = (["+"] / "-") 1*DIGIT ["." 1*DIGIT]
Description: If the property permits, multiple "float" values are specified by a COMMA-separated list of values.
描述：如果属性允许，多个“浮点”值由逗号分隔的值列表指定。
No additional content value encoding (i.e., BACKSLASH character encoding, see Section 3.3.11) is defined for this value type.
没有为该值类型定义额外的内容值编码（即反斜杠字符编码，见第3.3.11节）。
Example:
例子：
1000000.0000001 1.333 -3.14
1000000.0000001 1.333 -3.14
Value Name: INTEGER
值名称：整数
Purpose: This value type is used to identify properties that contain a signed integer value.
用途：此值类型用于标识包含带符号整数值的属性。
Format Definition: This value type is defined by the following notation:
格式定义：此值类型由以下符号定义：
integer = (["+"] / "-") 1*DIGIT
integer = (["+"] / "-") 1*DIGIT
Description: If the property permits, multiple "integer" values are specified by a COMMA-separated list of values. The valid range for "integer" is -2147483648 to 2147483647. If the sign is not specified, then the value is assumed to be positive.
描述：如果属性允许，多个“整型”值由逗号分隔的值列表指定。“整数”的有效范围为-2147483648到2147483647。如果未指定符号，则假定该值为正。
No additional content value encoding (i.e., BACKSLASH character encoding, see Section 3.3.11) is defined for this value type.
没有为该值类型定义额外的内容值编码（即反斜杠字符编码，见第3.3.11节）。
Example:
例子：
1234567890 -1234567890 +1234567890 432109876
1234567890 -1234567890 +1234567890 432109876
Value Name: PERIOD
值名称：句点
Purpose: This value type is used to identify values that contain a precise period of time.
用途：此值类型用于标识包含精确时间段的值。
Format Definition: This value type is defined by the following notation:
格式定义：此值类型由以下符号定义：
period = period-explicit / period-start
period = period-explicit / period-start
period-explicit = date-time "/" date-time
; [ISO.8601.2004] complete representation basic format for a
; period of time consisting of a start and end. The start MUST
; be before the end.
period-explicit = date-time "/" date-time
; [ISO.8601.2004] complete representation basic format for a
; period of time consisting of a start and end. The start MUST
; be before the end.
period-start = date-time "/" dur-value
; [ISO.8601.2004] complete representation basic format for a
; period of time consisting of a start and positive duration
; of time.
period-start = date-time "/" dur-value
; [ISO.8601.2004] complete representation basic format for a
; period of time consisting of a start and positive duration
; of time.
Description: If the property permits, multiple "period" values are specified by a COMMA-separated list of values. There are two forms of a period of time. First, a period of time is identified by its start and its end. This format is based on the [ISO.8601.2004] complete representation, basic format for "DATE-TIME" start of the period, followed by a SOLIDUS character followed by the "DATE-TIME" of the end of the period. The start of the period MUST be before the end of the period. Second, a period of time can also be defined by a start and a positive duration of time. The format is based on the [ISO.8601.2004] complete representation, basic format for the "DATE-TIME" start of the period, followed by a SOLIDUS character, followed by the [ISO.8601.2004] basic format for "DURATION" of the period.
描述：如果属性允许，多个“期间”值由逗号分隔的值列表指定。一段时间有两种形式。首先，一段时间是由它的开始和结束来确定的。此格式基于[ISO.8601.2004]完整表示法，即周期开始时的“日期-时间”基本格式，后跟一个索利多士字符，后跟周期结束时的“日期-时间”。期间的开始时间必须早于期间的结束时间。其次，一段时间也可以由一个开始和一个正的持续时间来定义。该格式以[ISO.8601.2004]完整表示法为基础，以基本格式表示期间的“日期-时间”开始，后跟一个索利多士字符，然后是以[ISO.8601.2004]基本格式表示期间的“持续时间”。
Example: The period starting at 18:00:00 UTC, on January 1, 1997 and ending at 07:00:00 UTC on January 2, 1997 would be:
示例：从1997年1月1日18:00:00 UTC开始到1997年1月2日07:00:00 UTC结束的期间为：
19970101T180000Z/19970102T070000Z
19970101T180000Z/19970102T070000Z
The period start at 18:00:00 on January 1, 1997 and lasting 5 hours and 30 minutes would be:
从1997年1月1日18:00:00开始，持续5小时30分钟的时段为：
19970101T180000Z/PT5H30M
19970101T180000Z/PT5H30M
No additional content value encoding (i.e., BACKSLASH character encoding, see Section 3.3.11) is defined for this value type.
没有为该值类型定义额外的内容值编码（即反斜杠字符编码，见第3.3.11节）。
Value Name: RECUR
值名称：RECUR
Purpose: This value type is used to identify properties that contain a recurrence rule specification.
用途：此值类型用于标识包含重复规则规范的属性。
Format Definition: This value type is defined by the following notation:
格式定义：此值类型由以下符号定义：
recur = recur-rule-part *( ";" recur-rule-part )
;
; The rule parts are not ordered in any
; particular sequence.
;
; The FREQ rule part is REQUIRED,
; but MUST NOT occur more than once.
;
; The UNTIL or COUNT rule parts are OPTIONAL,
; but they MUST NOT occur in the same 'recur'.
;
recur = recur-rule-part *( ";" recur-rule-part )
;
; The rule parts are not ordered in any
; particular sequence.
;
; The FREQ rule part is REQUIRED,
; but MUST NOT occur more than once.
;
; The UNTIL or COUNT rule parts are OPTIONAL,
; but they MUST NOT occur in the same 'recur'.
;
; The other rule parts are OPTIONAL, ; but MUST NOT occur more than once.
; 其他规则部分是可选的；但不得发生多次。
recur-rule-part = ( "FREQ" "=" freq )
/ ( "UNTIL" "=" enddate )
/ ( "COUNT" "=" 1*DIGIT )
/ ( "INTERVAL" "=" 1*DIGIT )
/ ( "BYSECOND" "=" byseclist )
/ ( "BYMINUTE" "=" byminlist )
/ ( "BYHOUR" "=" byhrlist )
/ ( "BYDAY" "=" bywdaylist )
/ ( "BYMONTHDAY" "=" bymodaylist )
/ ( "BYYEARDAY" "=" byyrdaylist )
/ ( "BYWEEKNO" "=" bywknolist )
/ ( "BYMONTH" "=" bymolist )
/ ( "BYSETPOS" "=" bysplist )
/ ( "WKST" "=" weekday )
recur-rule-part = ( "FREQ" "=" freq )
/ ( "UNTIL" "=" enddate )
/ ( "COUNT" "=" 1*DIGIT )
/ ( "INTERVAL" "=" 1*DIGIT )
/ ( "BYSECOND" "=" byseclist )
/ ( "BYMINUTE" "=" byminlist )
/ ( "BYHOUR" "=" byhrlist )
/ ( "BYDAY" "=" bywdaylist )
/ ( "BYMONTHDAY" "=" bymodaylist )
/ ( "BYYEARDAY" "=" byyrdaylist )
/ ( "BYWEEKNO" "=" bywknolist )
/ ( "BYMONTH" "=" bymolist )
/ ( "BYSETPOS" "=" bysplist )
/ ( "WKST" "=" weekday )
freq = "SECONDLY" / "MINUTELY" / "HOURLY" / "DAILY"
/ "WEEKLY" / "MONTHLY" / "YEARLY"
freq = "SECONDLY" / "MINUTELY" / "HOURLY" / "DAILY"
/ "WEEKLY" / "MONTHLY" / "YEARLY"
enddate = date / date-time
enddate = date / date-time
byseclist = ( seconds *("," seconds) )
byseclist = ( seconds *("," seconds) )
seconds = 1*2DIGIT ;0 to 60
seconds = 1*2DIGIT ;0 to 60
byminlist = ( minutes *("," minutes) )
byminlist = ( minutes *("," minutes) )
minutes = 1*2DIGIT ;0 to 59
minutes = 1*2DIGIT ;0 to 59
byhrlist = ( hour *("," hour) )
byhrlist = ( hour *("," hour) )
hour = 1*2DIGIT ;0 to 23
hour = 1*2DIGIT ;0 to 23
bywdaylist = ( weekdaynum *("," weekdaynum) )
bywdaylist = ( weekdaynum *("," weekdaynum) )
weekdaynum = [[plus / minus] ordwk] weekday
weekdaynum = [[plus / minus] ordwk] weekday
plus = "+"
plus=“+”
minus = "-"
minus = "-"
ordwk = 1*2DIGIT ;1 to 53
ordwk = 1*2DIGIT ;1 to 53
weekday = "SU" / "MO" / "TU" / "WE" / "TH" / "FR" / "SA"
;Corresponding to SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY,
;FRIDAY, and SATURDAY days of the week.
weekday = "SU" / "MO" / "TU" / "WE" / "TH" / "FR" / "SA"
;Corresponding to SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY,
;FRIDAY, and SATURDAY days of the week.
bymodaylist = ( monthdaynum *("," monthdaynum) )
bymodaylist = ( monthdaynum *("," monthdaynum) )
monthdaynum = [plus / minus] ordmoday
monthdaynum = [plus / minus] ordmoday
ordmoday = 1*2DIGIT ;1 to 31
ordmoday = 1*2DIGIT ;1 to 31
byyrdaylist = ( yeardaynum *("," yeardaynum) )
byyrdaylist = ( yeardaynum *("," yeardaynum) )
yeardaynum = [plus / minus] ordyrday
yeardaynum = [plus / minus] ordyrday
ordyrday = 1*3DIGIT ;1 to 366
ordyrday = 1*3DIGIT ;1 to 366
bywknolist = ( weeknum *("," weeknum) )
bywknolist = ( weeknum *("," weeknum) )
weeknum = [plus / minus] ordwk
weeknum = [plus / minus] ordwk
bymolist = ( monthnum *("," monthnum) )
bymolist = ( monthnum *("," monthnum) )
monthnum = 1*2DIGIT ;1 to 12
monthnum = 1*2DIGIT ;1 to 12
bysplist = ( setposday *("," setposday) )
bysplist = ( setposday *("," setposday) )
setposday = yeardaynum
setposday = yeardaynum
Description: This value type is a structured value consisting of a list of one or more recurrence grammar parts. Each rule part is defined by a NAME=VALUE pair. The rule parts are separated from each other by the SEMICOLON character. The rule parts are not ordered in any particular sequence. Individual rule parts MUST only be specified once. Compliant applications MUST accept rule parts ordered in any sequence, but to ensure backward compatibility with applications that pre-date this revision of iCalendar the FREQ rule part MUST be the first rule part specified in a RECUR value.
描述：此值类型是由一个或多个递归语法部分的列表组成的结构化值。每个规则部分由名称=值对定义。规则部分之间用分号字符分隔。规则部分不按任何特定顺序排序。单个规则部分只能指定一次。符合要求的应用程序必须接受按任意顺序订购的规则部分，但为了确保与iCalendar此版本之前的应用程序向后兼容，FREQ规则部分必须是在RECUR值中指定的第一个规则部分。
The FREQ rule part identifies the type of recurrence rule. This rule part MUST be specified in the recurrence rule. Valid values include SECONDLY, to specify repeating events based on an interval of a second or more; MINUTELY, to specify repeating events based on an interval of a minute or more; HOURLY, to specify repeating events based on an interval of an hour or more; DAILY, to specify repeating events based on an interval of a day or more; WEEKLY, to specify repeating events based on an interval of a week or more; MONTHLY, to specify repeating events based on an interval of a month or more; and YEARLY, to specify repeating events based on an interval of a year or more.
FREQ rule部分标识重复规则的类型。必须在定期规则中指定此规则部分。有效值包括：第二，基于一秒或更长的间隔指定重复事件；以分钟为单位，指定基于一分钟或更长时间间隔的重复事件；每小时，指定基于一小时或更长时间间隔的重复事件；每日，以指定基于一天或更长时间间隔的重复事件；每周，指定基于一周或更长时间间隔的重复事件；每月，以指定基于一个月或更长时间间隔的重复事件；和按年，以指定基于一年或更长时间间隔的重复事件。
The INTERVAL rule part contains a positive integer representing at which intervals the recurrence rule repeats. The default value is "1", meaning every second for a SECONDLY rule, every minute for a MINUTELY rule, every hour for an HOURLY rule, every day for a DAILY rule, every week for a WEEKLY rule, every month for a MONTHLY rule, and every year for a YEARLY rule. For example, within a DAILY rule, a value of "8" means every eight days.
间隔规则部分包含一个正整数，表示重复规则重复的间隔。默认值为“1”，表示秒规则为每秒，分钟规则为每分钟，小时规则为每小时，日规则为每天，周规则为每周，月规则为每月，年规则为每年。例如，在每日规则中，值“8”表示每八天一次。
The UNTIL rule part defines a DATE or DATE-TIME value that bounds the recurrence rule in an inclusive manner. If the value specified by UNTIL is synchronized with the specified recurrence, this DATE or DATE-TIME becomes the last instance of the recurrence. The value of the UNTIL rule part MUST have the same value type as the "DTSTART" property. Furthermore, if the "DTSTART" property is specified as a date with local time, then the UNTIL rule part MUST also be specified as a date with local time. If the "DTSTART" property is specified as a date with UTC time or a date with local time and time zone reference, then the UNTIL rule part MUST be specified as a date with UTC time. In the case of the "STANDARD" and "DAYLIGHT" sub-components the UNTIL rule part MUST always be specified as a date with UTC time. If specified as a DATE-TIME value, then it MUST be specified in a UTC time format. If not present, and the COUNT rule part is also not present, the "RRULE" is considered to repeat forever.
“直到规则”部分定义了一个日期或日期时间值，该值以包容的方式限制重复规则。如果由指定的值与指定的定期同步，则此日期或日期时间将成为定期的最后一个实例。直到规则部分的值必须与“DTSTART”属性具有相同的值类型。此外，如果将“DTSTART”属性指定为带有本地时间的日期，则还必须将直到规则部分指定为带有本地时间的日期。如果将“DTSTART”属性指定为具有UTC时间的日期或具有本地时间和时区引用的日期，则必须将“直到”规则部分指定为具有UTC时间的日期。对于“标准”和“日光”子组件，“直到”规则部分必须始终指定为UTC时间的日期。如果指定为日期时间值，则必须以UTC时间格式指定。如果不存在，并且计数规则部分也不存在，“RRULE”将被视为永远重复。
The COUNT rule part defines the number of occurrences at which to range-bound the recurrence. The "DTSTART" property value always counts as the first occurrence.
计数规则部分定义了要在其范围内限制重复的出现次数。“DTSTART”属性值始终计为第一次出现。
The BYSECOND rule part specifies a COMMA-separated list of seconds within a minute. Valid values are 0 to 60. The BYMINUTE rule part specifies a COMMA-separated list of minutes within an hour. Valid values are 0 to 59. The BYHOUR rule part specifies a COMMA-separated list of hours of the day. Valid values are 0 to 23. The BYSECOND, BYMINUTE and BYHOUR rule parts MUST NOT be specified when the associated "DTSTART" property has a DATE value type. These rule parts MUST be ignored in RECUR value that violate the above requirement (e.g., generated by applications that pre-date this revision of iCalendar).
BYSECOND规则部分指定一分钟内以逗号分隔的秒数列表。有效值为0到60。BYMINUTE规则部分指定一小时内以逗号分隔的分钟列表。有效值为0到59。BYHOUR规则部分指定一天中以逗号分隔的小时列表。有效值为0到23。当关联的“DTSTART”属性具有日期值类型时，不得指定BYSECOND、BYMINUTE和BYHOUR规则部分。这些规则部分必须在重复值中忽略，这些重复值违反了上述要求（例如，由iCalendar本次修订之前的应用程序生成）。
The BYDAY rule part specifies a COMMA-separated list of days of the week; SU indicates Sunday; MO indicates Monday; TU indicates Tuesday; WE indicates Wednesday; TH indicates Thursday; FR indicates Friday; and SA indicates Saturday.
BYDAY规则部分指定一周中以逗号分隔的天数列表；苏表示星期天；莫表示周一；屠表示星期二；我们表示星期三；星期四表示星期四；FR表示星期五；SA表示周六。
Each BYDAY value can also be preceded by a positive (+n) or negative (-n) integer. If present, this indicates the nth occurrence of a specific day within the MONTHLY or YEARLY "RRULE".
每个BYDAY值前面还可以有一个正（+n）或负（-n）整数。如果存在，则表示在每月或每年的“RRULE”中特定日期的第n次出现。
For example, within a MONTHLY rule, +1MO (or simply 1MO) represents the first Monday within the month, whereas -1MO represents the last Monday of the month. The numeric value in a BYDAY rule part with the FREQ rule part set to YEARLY corresponds to an offset within the month when the BYMONTH rule part is present, and corresponds to an offset within the year when the BYWEEKNO or BYMONTH rule parts are present. If an integer modifier is not present, it means all days of this type within the specified frequency. For example, within a MONTHLY rule, MO represents all Mondays within the month. The BYDAY rule part MUST NOT be specified with a numeric value when the FREQ rule part is not set to MONTHLY or YEARLY. Furthermore, the BYDAY rule part MUST NOT be specified with a numeric value with the FREQ rule part set to YEARLY when the BYWEEKNO rule part is specified.
例如，在一个月规则中，+1MO（或简单地说是1MO）表示该月的第一个星期一，而-1MO表示该月的最后一个星期一。频率规则部分设置为“年”的BYDAY规则部分中的数值对应于存在BYMONTH规则部分的月份内的偏移量，并对应于存在BYWEEKNO或BYMONTH规则部分的年份内的偏移量。如果整数修饰符不存在，则表示指定频率内此类型的所有天数。例如，在月度规则中，MO表示该月内的所有周一。当频率规则部分未设置为每月或每年时，BYDAY规则部分不得使用数值指定。此外，当指定BYWEEKNO规则部分时，BYDAY规则部分不得使用FREQ rule part设置为YEARLY的数值指定。
The BYMONTHDAY rule part specifies a COMMA-separated list of days of the month. Valid values are 1 to 31 or -31 to -1. For example, -10 represents the tenth to the last day of the month. The BYMONTHDAY rule part MUST NOT be specified when the FREQ rule part is set to WEEKLY.
BYMONTHDAY规则部分指定以逗号分隔的月份天数列表。有效值为1到31或-31到-1。例如，-10表示一个月的第十天到最后一天。当频率规则部分设置为每周时，不得指定BYMONTHDAY规则部分。
The BYYEARDAY rule part specifies a COMMA-separated list of days of the year. Valid values are 1 to 366 or -366 to -1. For example, -1 represents the last day of the year (December 31st) and -306 represents the 306th to the last day of the year (March 1st). The BYYEARDAY rule part MUST NOT be specified when the FREQ rule part is set to DAILY, WEEKLY, or MONTHLY.
BYYEARDAY规则部分指定一年中以逗号分隔的日期列表。有效值为1到366或-366到-1。例如，-1表示一年中的最后一天（12月31日），-306表示一年中的最后一天（3月1日）的第306次。当频率规则部分设置为每日、每周或每月时，不得指定BYYEARDAY规则部分。
The BYWEEKNO rule part specifies a COMMA-separated list of ordinals specifying weeks of the year. Valid values are 1 to 53 or -53 to -1. This corresponds to weeks according to week numbering as defined in [ISO.8601.2004]. A week is defined as a seven day period, starting on the day of the week defined to be the week start (see WKST). Week number one of the calendar year is the first week that contains at least four (4) days in that calendar year. This rule part MUST NOT be used when the FREQ rule part is set to anything other than YEARLY. For example, 3 represents the third week of the year.
BYWEEKNO规则部分指定一个逗号分隔的序号列表，指定一年中的周数。有效值为1到53或-53到-1。根据[ISO.8601.2004]中定义的周编号，这对应于周。一周定义为七天，从定义为一周开始的一周中的某一天开始（见WKST）。日历年的第一周是该日历年中至少包含四（4）天的第一周。当频率规则部分设置为除“年度”以外的任何内容时，不得使用此规则部分。例如，3代表一年中的第三周。
Note: Assuming a Monday week start, week 53 can only occur when Thursday is January 1 or if it is a leap year and Wednesday is January 1.
注意：假设周一开始，第53周只能在周四为1月1日或闰年，周三为1月1日时出现。
The BYMONTH rule part specifies a COMMA-separated list of months of the year. Valid values are 1 to 12.
BYMONTH规则部分指定一年中以逗号分隔的月份列表。有效值为1到12。
The WKST rule part specifies the day on which the workweek starts. Valid values are MO, TU, WE, TH, FR, SA, and SU. This is
WKST规则部分指定工作周开始的日期。有效值为MO、TU、WE、TH、FR、SA和SU。这是
significant when a WEEKLY "RRULE" has an interval greater than 1, and a BYDAY rule part is specified. This is also significant when in a YEARLY "RRULE" when a BYWEEKNO rule part is specified. The default value is MO.
当每周“RRULE”的间隔大于1，并且指定了BYDAY规则部分时，此值有效。在指定BYWEEKNO规则部分的年度“RRULE”中，这一点也很重要。默认值为MO。
The BYSETPOS rule part specifies a COMMA-separated list of values that corresponds to the nth occurrence within the set of recurrence instances specified by the rule. BYSETPOS operates on a set of recurrence instances in one interval of the recurrence rule. For example, in a WEEKLY rule, the interval would be one week A set of recurrence instances starts at the beginning of the interval defined by the FREQ rule part. Valid values are 1 to 366 or -366 to -1. It MUST only be used in conjunction with another BYxxx rule part. For example "the last work day of the month" could be represented as:
BYSETPOS规则部分指定一个逗号分隔的值列表，该列表对应于规则指定的重复实例集中的第n次出现。BYSETPOS在递归规则的一个间隔内对一组递归实例进行操作。例如，在每周规则中，间隔为一周。一组重复实例从FREQ rule部分定义的间隔开始。有效值为1到366或-366到-1。它只能与另一BYxxx规则部分结合使用。例如，“当月最后一个工作日”可以表示为：
FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-1
FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-1
Each BYSETPOS value can include a positive (+n) or negative (-n) integer. If present, this indicates the nth occurrence of the specific occurrence within the set of occurrences specified by the rule.
每个BYSETPOS值可以包括一个正（+n）或负（-n）整数。如果存在，则表示特定事件在规则指定的事件集中的第n个事件。
Recurrence rules may generate recurrence instances with an invalid date (e.g., February 30) or nonexistent local time (e.g., 1:30 AM on a day where the local time is moved forward by an hour at 1:00 AM). Such recurrence instances MUST be ignored and MUST NOT be counted as part of the recurrence set.
定期规则可能会生成具有无效日期（例如2月30日）或不存在本地时间（例如，当地时间在上午1:00向前移动一小时的一天的1:30 AM）的定期实例。此类重复实例必须忽略，且不得作为重复集的一部分计算。
Information, not contained in the rule, necessary to determine the various recurrence instance start time and dates are derived from the Start Time ("DTSTART") component attribute. For example, "FREQ=YEARLY;BYMONTH=1" doesn't specify a specific day within the month or a time. This information would be the same as what is specified for "DTSTART".
确定各种重复实例开始时间和日期所需的信息（不包含在规则中）来自开始时间（“DTSTART”）组件属性。例如，“FREQ=YEARLY；BYMONTH=1”没有指定月份内的特定日期或时间。此信息与为“DTSTART”指定的信息相同。
BYxxx rule parts modify the recurrence in some manner. BYxxx rule parts for a period of time that is the same or greater than the frequency generally reduce or limit the number of occurrences of the recurrence generated. For example, "FREQ=DAILY;BYMONTH=1" reduces the number of recurrence instances from all days (if BYMONTH rule part is not present) to all days in January. BYxxx rule parts for a period of time less than the frequency generally increase or expand the number of occurrences of the recurrence. For example, "FREQ=YEARLY;BYMONTH=1,2" increases the number of days within the yearly recurrence set from 1 (if BYMONTH rule part is not present) to 2.
BYxxx规则部分以某种方式修改重复。BYxxx规则部分在相同或大于频率的时间段内通常会减少或限制生成的重复次数。例如，“FREQ=DAILY；BYMONTH=1”将重复实例的数量从所有天（如果BYMONTH规则部分不存在）减少到1月份的所有天。BYxxx规则部分在少于频率的时间段内通常会增加或扩大重复出现的次数。例如，“FREQ=YEARLY；BYMONTH=1,2”将年度重复周期集中的天数从1（如果BYMONTH规则部分不存在）增加到2。
If multiple BYxxx rule parts are specified, then after evaluating the specified FREQ and INTERVAL rule parts, the BYxxx rule parts are applied to the current set of evaluated occurrences in the following order: BYMONTH, BYWEEKNO, BYYEARDAY, BYMONTHDAY, BYDAY, BYHOUR, BYMINUTE, BYSECOND and BYSETPOS; then COUNT and UNTIL are evaluated.
如果指定了多个BYxxx规则部分，则在评估指定的频率和间隔规则部分后，BYxxx规则部分将按以下顺序应用于当前评估的事件集：BYMONTH、BYWEEKNO、BYYEARDAY、BYMONTHDAY、BYDAY、BYHOUR、BYMINUTE、BYSECOND和BYSETPOS；然后计数，直到计算。
The table below summarizes the dependency of BYxxx rule part expand or limit behavior on the FREQ rule part value.
下表总结了BYxxx规则部件扩展或限制行为对FREQ规则部件值的依赖关系。
The term "N/A" means that the corresponding BYxxx rule part MUST NOT be used with the corresponding FREQ value.
术语“不适用”表示相应的BYxxx规则部分不得与相应的FREQ值一起使用。
BYDAY has some special behavior depending on the FREQ value and this is described in separate notes below the table.
BYDAY根据FREQ值有一些特殊的行为，这在下表的单独注释中描述。
+----------+--------+--------+-------+-------+------+-------+------+
| |SECONDLY|MINUTELY|HOURLY |DAILY |WEEKLY|MONTHLY|YEARLY|
+----------+--------+--------+-------+-------+------+-------+------+
|BYMONTH |Limit |Limit |Limit |Limit |Limit |Limit |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYWEEKNO |N/A |N/A |N/A |N/A |N/A |N/A |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYYEARDAY |Limit |Limit |Limit |N/A |N/A |N/A |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYMONTHDAY|Limit |Limit |Limit |Limit |N/A |Expand |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYDAY |Limit |Limit |Limit |Limit |Expand|Note 1 |Note 2|
+----------+--------+--------+-------+-------+------+-------+------+
|BYHOUR |Limit |Limit |Limit |Expand |Expand|Expand |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYMINUTE |Limit |Limit |Expand |Expand |Expand|Expand |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYSECOND |Limit |Expand |Expand |Expand |Expand|Expand |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYSETPOS |Limit |Limit |Limit |Limit |Limit |Limit |Limit |
+----------+--------+--------+-------+-------+------+-------+------+
+----------+--------+--------+-------+-------+------+-------+------+
| |SECONDLY|MINUTELY|HOURLY |DAILY |WEEKLY|MONTHLY|YEARLY|
+----------+--------+--------+-------+-------+------+-------+------+
|BYMONTH |Limit |Limit |Limit |Limit |Limit |Limit |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYWEEKNO |N/A |N/A |N/A |N/A |N/A |N/A |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYYEARDAY |Limit |Limit |Limit |N/A |N/A |N/A |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYMONTHDAY|Limit |Limit |Limit |Limit |N/A |Expand |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYDAY |Limit |Limit |Limit |Limit |Expand|Note 1 |Note 2|
+----------+--------+--------+-------+-------+------+-------+------+
|BYHOUR |Limit |Limit |Limit |Expand |Expand|Expand |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYMINUTE |Limit |Limit |Expand |Expand |Expand|Expand |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYSECOND |Limit |Expand |Expand |Expand |Expand|Expand |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYSETPOS |Limit |Limit |Limit |Limit |Limit |Limit |Limit |
+----------+--------+--------+-------+-------+------+-------+------+
Note 1: Limit if BYMONTHDAY is present; otherwise, special expand for MONTHLY.
注1：如果存在BYMONTHDAY，则限制；否则，每月将进行特殊扩展。
Note 2: Limit if BYYEARDAY or BYMONTHDAY is present; otherwise, special expand for WEEKLY if BYWEEKNO present; otherwise, special expand for MONTHLY if BYMONTH present; otherwise, special expand for YEARLY.
注2：如果存在BYYEARDAY或BYMONTHDAY，则限制；否则，如果周末不存在，则每周进行特殊扩展；否则，如果存在BYMONTH，则每月进行特殊扩展；否则，每年都要进行特殊扩展。
Here is an example of evaluating multiple BYxxx rule parts.
下面是一个评估多个BYxxx规则部分的示例。
DTSTART;TZID=America/New_York:19970105T083000
RRULE:FREQ=YEARLY;INTERVAL=2;BYMONTH=1;BYDAY=SU;BYHOUR=8,9;
BYMINUTE=30
DTSTART;TZID=America/New_York:19970105T083000
RRULE:FREQ=YEARLY;INTERVAL=2;BYMONTH=1;BYDAY=SU;BYHOUR=8,9;
BYMINUTE=30
First, the "INTERVAL=2" would be applied to "FREQ=YEARLY" to arrive at "every other year". Then, "BYMONTH=1" would be applied to arrive at "every January, every other year". Then, "BYDAY=SU" would be applied to arrive at "every Sunday in January, every other year". Then, "BYHOUR=8,9" would be applied to arrive at "every Sunday in January at 8 AM and 9 AM, every other year". Then, "BYMINUTE=30" would be applied to arrive at "every Sunday in January at 8:30 AM and 9:30 AM, every other year". Then, lacking information from "RRULE", the second is derived from "DTSTART", to end up in "every Sunday in January at 8:30:00 AM and 9:30:00 AM, every other year". Similarly, if the BYMINUTE, BYHOUR, BYDAY, BYMONTHDAY, or BYMONTH rule part were missing, the appropriate minute, hour, day, or month would have been retrieved from the "DTSTART" property.
首先，“INTERVAL=2”将应用于“FREQ=year”，以达到“每隔一年”。然后，“BYMONTH=1”将被应用于“每年1月，每隔一年”。然后，“BYDAY=SU”将被应用到“一月的每个星期日，每隔一年”。然后，“BYHOUR=8,9”将应用于“一月的每个星期日上午8点和上午9点，每隔一年”。然后，“BYMINUTE=30”将应用于“每隔一年的1月每个星期日上午8:30和上午9:30到达”。然后，由于缺少来自“RRULE”的信息，第二个源于“DTSTART”，以“每隔一年的1月每个星期日上午8:30:00和上午9:30:00”结束。类似地，如果缺少BYMINUTE、BYHOUR、BYDAY、BYMONTHDAY或BYMONTH规则部分，则可以从“DTSTART”属性检索相应的分钟、小时、天或月。
If the computed local start time of a recurrence instance does not exist, or occurs more than once, for the specified time zone, the time of the recurrence instance is interpreted in the same manner as an explicit DATE-TIME value describing that date and time, as specified in Section 3.3.5.
如果计算出的重现实例的本地开始时间在指定时区内不存在，或出现不止一次，则重现实例的时间将以与第3.3.5节规定的描述该日期和时间的显式日期时间值相同的方式进行解释。
No additional content value encoding (i.e., BACKSLASH character encoding, see Section 3.3.11) is defined for this value type.
没有为该值类型定义额外的内容值编码（即反斜杠字符编码，见第3.3.11节）。
Example: The following is a rule that specifies 10 occurrences that occur every other day:
示例：以下规则指定每隔一天发生10次：
FREQ=DAILY;COUNT=10;INTERVAL=2
FREQ=DAILY;COUNT=10;INTERVAL=2
There are other examples specified in Section 3.8.5.3.
第3.8.5.3节规定了其他示例。
Value Name: TEXT
值名称：TEXT
Purpose: This value type is used to identify values that contain human-readable text.
用途：此值类型用于标识包含人类可读文本的值。
Format Definition: This value type is defined by the following notation:
格式定义：此值类型由以下符号定义：
text = *(TSAFE-CHAR / ":" / DQUOTE / ESCAPED-CHAR)
; Folded according to description above
text = *(TSAFE-CHAR / ":" / DQUOTE / ESCAPED-CHAR)
; Folded according to description above
ESCAPED-CHAR = ("\\" / "\;" / "\," / "\N" / "\n")
; \\ encodes \, \N or \n encodes newline
; \; encodes ;, \, encodes ,
ESCAPED-CHAR = ("\\" / "\;" / "\," / "\N" / "\n")
; \\ encodes \, \N or \n encodes newline
; \; encodes ;, \, encodes ,
TSAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-5B /
%x5D-7E / NON-US-ASCII
; Any character except CONTROLs not needed by the current
; character set, DQUOTE, ";", ":", "\", ","
TSAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-5B /
%x5D-7E / NON-US-ASCII
; Any character except CONTROLs not needed by the current
; character set, DQUOTE, ";", ":", "\", ","
Description: If the property permits, multiple TEXT values are specified by a COMMA-separated list of values.
描述：如果属性允许，多个文本值由逗号分隔的值列表指定。
The language in which the text is represented can be controlled by the "LANGUAGE" property parameter.
表示文本的语言可以由“language”属性参数控制。
An intentional formatted text line break MUST only be included in a "TEXT" property value by representing the line break with the character sequence of BACKSLASH, followed by a LATIN SMALL LETTER N or a LATIN CAPITAL LETTER N, that is "\n" or "\N".
有意格式化的文本换行符只能包含在“text”属性值中，方法是用反斜杠字符序列表示换行符，后跟拉丁小写字母N或拉丁大写字母N，即“\N”或“\N”。
The "TEXT" property values may also contain special characters that are used to signify delimiters, such as a COMMA character for lists of values or a SEMICOLON character for structured values. In order to support the inclusion of these special characters in "TEXT" property values, they MUST be escaped with a BACKSLASH character. A BACKSLASH character in a "TEXT" property value MUST be escaped with another BACKSLASH character. A COMMA character in a "TEXT" property value MUST be escaped with a BACKSLASH character. A SEMICOLON character in a "TEXT" property value MUST be escaped with a BACKSLASH character. However, a COLON character in a "TEXT" property value SHALL NOT be escaped with a BACKSLASH character.
“文本”属性值还可能包含用于表示分隔符的特殊字符，例如用于值列表的逗号字符或用于结构化值的分号字符。为了支持在“文本”属性值中包含这些特殊字符，必须使用反斜杠字符对其进行转义。“文本”属性值中的反斜杠字符必须用另一个反斜杠字符转义。“文本”属性值中的逗号字符必须用反斜杠字符转义。“TEXT”属性值中的分号字符必须用反斜杠字符转义。但是，“文本”属性值中的冒号字符不能用反斜杠字符转义。
Example: A multiple line value of:
示例：多行值为：
Project XYZ Final Review Conference Room - 3B Come Prepared.
XYZ项目最终审查会议室-3B准备就绪。
would be represented as:
将代表如下：
Project XYZ Final Review\nConference Room - 3B\nCome Prepared.
项目XYZ最终审查\n会议室-3B\n会议室已准备就绪。
Value Name: TIME
值名称：TIME
Purpose: This value type is used to identify values that contain a time of day.
用途：此值类型用于标识包含一天中某个时间的值。
Format Definition: This value type is defined by the following notation:
格式定义：此值类型由以下符号定义：
time = time-hour time-minute time-second [time-utc]
时间=时-时-分-秒[utc时间]
time-hour = 2DIGIT ;00-23 time-minute = 2DIGIT ;00-59 time-second = 2DIGIT ;00-60 ;The "60" value is used to account for positive "leap" seconds.
时间小时=2位数；00-23时分=2位数；00-59次秒=2位数；00-60 ;“60”值用于说明正“闰秒”。
time-utc = "Z"
time-utc = "Z"
Description: If the property permits, multiple "time" values are specified by a COMMA-separated list of values. No additional content value encoding (i.e., BACKSLASH character encoding, see Section 3.3.11) is defined for this value type.
描述：如果属性允许，多个“时间”值由逗号分隔的值列表指定。没有为该值类型定义额外的内容值编码（即反斜杠字符编码，见第3.3.11节）。
The "TIME" value type is used to identify values that contain a time of day. The format is based on the [ISO.8601.2004] complete representation, basic format for a time of day. The text format consists of a two-digit, 24-hour of the day (i.e., values 00-23), two-digit minute in the hour (i.e., values 00-59), and two-digit seconds in the minute (i.e., values 00-60). The seconds value of 60 MUST only be used to account for positive "leap" seconds. Fractions of a second are not supported by this format.
“时间”值类型用于标识包含一天中某个时间的值。该格式基于[ISO.8601.2004]完整表示法，即一天中某个时间的基本格式。文本格式由一天24小时的两位数（即值00-23）、一小时的两位数分钟（即值00-59）和一分钟的两位数秒（即值00-60）组成。秒值60只能用于说明正“闰”秒。此格式不支持几分之一秒。
In parallel to the "DATE-TIME" definition above, the "TIME" value type expresses time values in three forms:
与上面的“日期-时间”定义类似，“时间”值类型以三种形式表示时间值：
The form of time with UTC offset MUST NOT be used. For example, the following is not valid for a time value:
不得使用UTC偏移的时间形式。例如，以下内容对于时间值无效：
230000-0800 ;Invalid time format
230000-0800 ;无效的时间格式
FORM #1 LOCAL TIME
表1当地时间
The local time form is simply a time value that does not contain the UTC designator nor does it reference a time zone. For example, 11:00 PM:
本地时间表单只是一个时间值，不包含UTC指示符，也不引用时区。例如，晚上11:00：
230000
230000
Time values of this type are said to be "floating" and are not bound to any time zone in particular. They are used to represent the same hour, minute, and second value regardless of which time zone is currently being observed. For example, an event can be defined that indicates that an individual will be busy from 11:00 AM to 1:00 PM every day, no matter which time zone the person is in. In these cases, a local time can be specified. The recipient of an iCalendar object with a property value consisting of a local time, without any relative time zone information, SHOULD interpret the value as being fixed to whatever time zone the "ATTENDEE" is in at any given moment. This means that two "Attendees", may participate in the same event at different UTC times; floating time SHOULD only be used where that is reasonable behavior.
这种类型的时间值称为“浮动”时间值，不受任何时区的限制。它们用于表示相同的小时、分钟和秒值，而不管当前正在观察哪个时区。例如，可以定义一个事件，该事件指示个人将在每天上午11:00到下午1:00之间忙碌，无论此人处于哪个时区。在这些情况下，可以指定本地时间。属性值由本地时间组成的iCalendar对象的接收者（无任何相关时区信息）应将该值解释为固定在“与会者”在任何给定时刻所在的任何时区。这意味着两名“与会者”可以在不同的UTC时间参加同一活动；浮动时间只能在合理的情况下使用。
In most cases, a fixed time is desired. To properly communicate a fixed time in a property value, either UTC time or local time with time zone reference MUST be specified.
在大多数情况下，需要一个固定的时间。要在属性值中正确传递固定时间，必须指定UTC时间或带时区引用的本地时间。
The use of local time in a TIME value without the "TZID" property parameter is to be interpreted as floating time, regardless of the existence of "VTIMEZONE" calendar components in the iCalendar object.
无论iCalendar对象中是否存在“VTIMEZONE”日历组件，在没有“TZID”属性参数的时间值中使用本地时间将被解释为浮动时间。
FORM #2: UTC TIME
表格2：UTC时间
UTC time, or absolute time, is identified by a LATIN CAPITAL LETTER Z suffix character, the UTC designator, appended to the time value. For example, the following represents 07:00 AM UTC:
UTC时间或绝对时间由时间值后附加的拉丁文大写字母Z后缀字符（UTC指示符）标识。例如，以下表示UTC上午7:00：
070000Z
070000Z
The "TZID" property parameter MUST NOT be applied to TIME properties whose time values are specified in UTC.
“TZID”属性参数不得应用于以UTC指定时间值的时间属性。
FORM #3: LOCAL TIME AND TIME ZONE REFERENCE
表3：当地时间和时区参考
The local time with reference to time zone information form is identified by the use the "TZID" property parameter to reference the appropriate time zone definition. "TZID" is discussed in detail in Section 3.2.19.
参考时区信息表单的本地时间通过使用“TZID”属性参数参考适当的时区定义来标识。第3.2.19节详细讨论了“TZID”。
Example: The following represents 8:30 AM in New York in winter, five hours behind UTC, in each of the three formats:
示例：以下表示纽约冬季上午8:30，比UTC晚5小时，三种格式各有一种：
083000 133000Z TZID=America/New_York:083000
083000 133000Z TZID=美国/纽约：083000
Value Name: URI
值名称：URI
Purpose: This value type is used to identify values that contain a uniform resource identifier (URI) type of reference to the property value.
用途：此值类型用于标识包含对属性值引用的统一资源标识符（URI）类型的值。
Format Definition: This value type is defined by the following notation:
格式定义：此值类型由以下符号定义：
uri = <As defined in Section 3 of [RFC3986]>
uri = <As defined in Section 3 of [RFC3986]>
Description: This value type might be used to reference binary information, for values that are large, or otherwise undesirable to include directly in the iCalendar object.
描述：此值类型可用于引用二进制信息，用于较大的值，或不希望直接包含在iCalendar对象中的值。
Property values with this value type MUST follow the generic URI syntax defined in [RFC3986].
具有此值类型的属性值必须遵循[RFC3986]中定义的通用URI语法。
When a property parameter value is a URI value type, the URI MUST be specified as a quoted-string value.
当属性参数值是URI值类型时，必须将URI指定为带引号的字符串值。
No additional content value encoding (i.e., BACKSLASH character encoding, see Section 3.3.11) is defined for this value type.
没有为该值类型定义额外的内容值编码（即反斜杠字符编码，见第3.3.11节）。
Example: The following is a URI for a network file:
示例：以下是网络文件的URI：
http://example.com/my-report.txt
http://example.com/my-report.txt
Value Name: UTC-OFFSET
值名称：UTC-OFFSET
Purpose: This value type is used to identify properties that contain an offset from UTC to local time.
用途：此值类型用于标识包含UTC到本地时间偏移量的属性。
Format Definition: This value type is defined by the following notation:
格式定义：此值类型由以下符号定义：
utc-offset = time-numzone
utc-offset = time-numzone
time-numzone = ("+" / "-") time-hour time-minute [time-second]
time-numzone = ("+" / "-") time-hour time-minute [time-second]
Description: The PLUS SIGN character MUST be specified for positive UTC offsets (i.e., ahead of UTC). The HYPHEN-MINUS character MUST be specified for negative UTC offsets (i.e., behind of UTC). The
说明：必须为正UTC偏移量（即UTC之前）指定加号字符。必须为负UTC偏移量指定连字符-减号（即UTC的后面）。这个
value of "-0000" and "-000000" are not allowed. The time-second, if present, MUST NOT be 60; if absent, it defaults to zero.
不允许使用“-0000”和“-000000”的值。秒时间（如果存在）不得为60；如果不存在，则默认为零。
No additional content value encoding (i.e., BACKSLASH character encoding, see Section 3.3.11) is defined for this value type.
没有为该值类型定义额外的内容值编码（即反斜杠字符编码，见第3.3.11节）。
Example: The following UTC offsets are given for standard time for New York (five hours behind UTC) and Geneva (one hour ahead of UTC):
示例：纽约（比UTC晚五小时）和日内瓦（比UTC早一小时）的标准时间给出了以下UTC偏移量：
-0500
-0500
+0100
+0100
The Calendaring and Scheduling Core Object is a collection of calendaring and scheduling information. Typically, this information will consist of an iCalendar stream with a single iCalendar object. However, multiple iCalendar objects can be sequentially grouped together in an iCalendar stream. The first line and last line of the iCalendar object MUST contain a pair of iCalendar object delimiter strings. The syntax for an iCalendar stream is as follows:
日历和日程安排核心对象是日历和日程安排信息的集合。通常，此信息将由带有单个iCalendar对象的iCalendar流组成。但是，多个iCalendar对象可以在iCalendar流中按顺序分组在一起。iCalendar对象的第一行和最后一行必须包含一对iCalendar对象分隔符字符串。iCalendar流的语法如下所示：
icalstream = 1*icalobject
icalstream = 1*icalobject
icalobject = "BEGIN" ":" "VCALENDAR" CRLF icalbody "END" ":" "VCALENDAR" CRLF
icalobject=“BEGIN”“：”“VCALENDAR”CRLF icalbody“END”“：”“VCALENDAR”CRLF
The following is a simple example of an iCalendar object:
以下是iCalendar对象的简单示例：
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//hacksw/handcal//NONSGML v1.0//EN
BEGIN:VEVENT
UID:19970610T172345Z-AF23B2@example.com
DTSTAMP:19970610T172345Z
DTSTART:19970714T170000Z
DTEND:19970715T040000Z
SUMMARY:Bastille Day Party
END:VEVENT
END:VCALENDAR
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//hacksw/handcal//NONSGML v1.0//EN
BEGIN:VEVENT
UID:19970610T172345Z-AF23B2@example.com
DTSTAMP:19970610T172345Z
DTSTART:19970714T170000Z
DTEND:19970715T040000Z
SUMMARY:Bastille Day Party
END:VEVENT
END:VCALENDAR
A property is the definition of an individual attribute describing a calendar object or a calendar component. A property takes the form defined by the "contentline" notation defined in Section 3.1.
属性是描述日历对象或日历组件的单个属性的定义。属性采用第3.1节中定义的“内容线”符号定义的形式。
The following is an example of a property:
以下是一个属性示例：
DTSTART:19960415T133000Z
DTSTART:19960415T133000Z
This memo imposes no ordering of properties within an iCalendar object.
此备注不强制iCalendar对象内的属性排序。
Property names, parameter names, and enumerated parameter values are case-insensitive. For example, the property name "DUE" is the same as "due" and "Due", DTSTART;TZID=America/New_York:19980714T120000 is the same as DtStart;TzID=America/New_York:19980714T120000.
属性名、参数名和枚举参数值不区分大小写。例如，属性名称“DUE”与“DUE”和“DUE”相同，DTSTART；TZID=美国/纽约：19980714T120000与DtStart相同；TzID=美国/纽约：19980714T1200000。
The body of the iCalendar object consists of a sequence of calendar properties and one or more calendar components. The calendar properties are attributes that apply to the calendar object as a whole. The calendar components are collections of properties that express a particular calendar semantic. For example, the calendar component can specify an event, a to-do, a journal entry, time zone information, free/busy time information, or an alarm.
iCalendar对象的主体由一系列日历属性和一个或多个日历组件组成。日历属性是应用于整个日历对象的属性。日历组件是表示特定日历语义的属性集合。例如，日历组件可以指定事件、待办事项、日志条目、时区信息、忙/闲时间信息或报警。
The body of the iCalendar object is defined by the following notation:
iCalendar对象的主体由以下符号定义：
icalbody = calprops component
icalbody = calprops component
calprops = *(
;
; The following are REQUIRED,
; but MUST NOT occur more than once.
;
prodid / version /
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
calscale / method /
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
calprops = *(
;
; The following are REQUIRED,
; but MUST NOT occur more than once.
;
prodid / version /
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
calscale / method /
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
x-prop / iana-prop ; )
x-prop/iana prop；）
component = 1*(eventc / todoc / journalc / freebusyc /
timezonec / iana-comp / x-comp)
component = 1*(eventc / todoc / journalc / freebusyc /
timezonec / iana-comp / x-comp)
iana-comp = "BEGIN" ":" iana-token CRLF 1*contentline "END" ":" iana-token CRLF
iana comp=“BEGIN”“：”iana令牌CRLF 1*内容行“END”“：”iana令牌CRLF
x-comp = "BEGIN" ":" x-name CRLF 1*contentline "END" ":" x-name CRLF
x-comp=“BEGIN”“：”x-name CRLF 1*内容行“END”“：”x-name CRLF
An iCalendar object MUST include the "PRODID" and "VERSION" calendar properties. In addition, it MUST include at least one calendar component. Special forms of iCalendar objects are possible to publish just busy time (i.e., only a "VFREEBUSY" calendar component) or time zone (i.e., only a "VTIMEZONE" calendar component) information. In addition, a complex iCalendar object that is used to capture a complete snapshot of the contents of a calendar is possible (e.g., composite of many different calendar components). More commonly, an iCalendar object will consist of just a single "VEVENT", "VTODO", or "VJOURNAL" calendar component. Applications MUST ignore x-comp and iana-comp values they don't recognize. Applications that support importing iCalendar objects SHOULD support all of the component types defined in this document, and SHOULD NOT silently drop any components as that can lead to user data loss.
iCalendar对象必须包括“PRODID”和“VERSION”日历属性。此外，它必须至少包含一个日历组件。特殊形式的iCalendar对象可以只发布繁忙时间（即仅“VFREEBUSY”日历组件）或时区（即仅“VTIMEZONE”日历组件）信息。此外，可以使用复杂的iCalendar对象来捕获日历内容的完整快照（例如，许多不同日历组件的组合）。更常见的是，iCalendar对象只包含一个“VEVENT”、“VTODO”或“VJOURNAL”日历组件。应用程序必须忽略它们无法识别的x-comp和iana comp值。支持导入iCalendar对象的应用程序应支持本文档中定义的所有组件类型，并且不应自动删除任何组件，因为这可能导致用户数据丢失。
Component Name: VEVENT
组件名称：VEVENT
Purpose: Provide a grouping of component properties that describe an event.
目的：提供描述事件的组件属性分组。
Format Definition: A "VEVENT" calendar component is defined by the following notation:
格式定义：“VEVENT”日历组件由以下符号定义：
eventc = "BEGIN" ":" "VEVENT" CRLF eventprop *alarmc "END" ":" "VEVENT" CRLF
eventc=“BEGIN”“：“VEVENT”CRLF eventprop*alarmc“END”“：“VEVENT”CRLF
eventprop = *(
;
; The following are REQUIRED,
; but MUST NOT occur more than once.
eventprop = *(
;
; The following are REQUIRED,
; but MUST NOT occur more than once.
;
dtstamp / uid /
;
; The following is REQUIRED if the component
; appears in an iCalendar object that doesn't
; specify the "METHOD" property; otherwise, it
; is OPTIONAL; in any case, it MUST NOT occur
; more than once.
;
dtstart /
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
class / created / description / geo /
last-mod / location / organizer / priority /
seq / status / summary / transp /
url / recurid /
;
; The following is OPTIONAL,
; but SHOULD NOT occur more than once.
;
rrule /
;
; Either 'dtend' or 'duration' MAY appear in
; a 'eventprop', but 'dtend' and 'duration'
; MUST NOT occur in the same 'eventprop'.
;
dtend / duration /
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
attach / attendee / categories / comment /
contact / exdate / rstatus / related /
resources / rdate / x-prop / iana-prop
;
)
;
dtstamp / uid /
;
; The following is REQUIRED if the component
; appears in an iCalendar object that doesn't
; specify the "METHOD" property; otherwise, it
; is OPTIONAL; in any case, it MUST NOT occur
; more than once.
;
dtstart /
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
class / created / description / geo /
last-mod / location / organizer / priority /
seq / status / summary / transp /
url / recurid /
;
; The following is OPTIONAL,
; but SHOULD NOT occur more than once.
;
rrule /
;
; Either 'dtend' or 'duration' MAY appear in
; a 'eventprop', but 'dtend' and 'duration'
; MUST NOT occur in the same 'eventprop'.
;
dtend / duration /
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
attach / attendee / categories / comment /
contact / exdate / rstatus / related /
resources / rdate / x-prop / iana-prop
;
)
Description: A "VEVENT" calendar component is a grouping of component properties, possibly including "VALARM" calendar components, that represents a scheduled amount of time on a calendar. For example, it can be an activity; such as a one-hour long, department meeting from 8:00 AM to 9:00 AM, tomorrow. Generally, an event will take up time on an individual calendar. Hence, the event will appear as an opaque interval in a search for busy time. Alternately, the event can have its Time Transparency
描述：“VEVENT”日历组件是一组组件属性，可能包括“VALARM”日历组件，表示日历上的计划时间量。例如，它可以是一项活动；例如一个一小时的部门会议，从明天上午8:00到9:00。一般来说，一项活动将占用个人日历上的时间。因此，在搜索繁忙时间时，事件将显示为不透明的间隔。或者，事件可以具有时间透明度
set to "TRANSPARENT" in order to prevent blocking of the event in searches for busy time.
设置为“透明”以防止在繁忙时间搜索时阻塞事件。
The "VEVENT" is also the calendar component used to specify an anniversary or daily reminder within a calendar. These events have a DATE value type for the "DTSTART" property instead of the default value type of DATE-TIME. If such a "VEVENT" has a "DTEND" property, it MUST be specified as a DATE value also. The anniversary type of "VEVENT" can span more than one date (i.e., "DTEND" property value is set to a calendar date after the "DTSTART" property value). If such a "VEVENT" has a "DURATION" property, it MUST be specified as a "dur-day" or "dur-week" value.
“VEVENT”也是日历组件，用于指定日历中的周年或每日提醒。这些事件具有“DTSTART”属性的日期值类型，而不是日期时间的默认值类型。如果此类“VEVENT”具有“DTEND”属性，则还必须将其指定为日期值。“VEVENT”的周年纪念类型可以跨越多个日期（即，“DTEND”属性值设置为“DTSTART”属性值之后的日历日期）。如果此类“VEVENT”具有“DURATION”属性，则必须将其指定为“dur day”或“dur week”值。
The "DTSTART" property for a "VEVENT" specifies the inclusive start of the event. For recurring events, it also specifies the very first instance in the recurrence set. The "DTEND" property for a "VEVENT" calendar component specifies the non-inclusive end of the event. For cases where a "VEVENT" calendar component specifies a "DTSTART" property with a DATE value type but no "DTEND" nor "DURATION" property, the event's duration is taken to be one day. For cases where a "VEVENT" calendar component specifies a "DTSTART" property with a DATE-TIME value type but no "DTEND" property, the event ends on the same calendar date and time of day specified by the "DTSTART" property.
“VEVENT”的“DTSTART”属性指定事件的包含性开始。对于重复事件，它还指定重复集中的第一个实例。“VEVENT”日历组件的“DTEND”属性指定事件的非包容性结束。对于“VEVENT”日历组件指定日期值类型为“DTSTART”但没有“DTEND”或“DURATION”属性的“DTSTART”属性的情况，事件的持续时间被视为一天。对于“VEVENT”日历组件指定具有日期时间值类型但没有“DTEND”属性的“DTSTART”属性的情况，事件将在“DTSTART”属性指定的相同日历日期和时间结束。
The "VEVENT" calendar component cannot be nested within another calendar component. However, "VEVENT" calendar components can be related to each other or to a "VTODO" or to a "VJOURNAL" calendar component with the "RELATED-TO" property.
“VEVENT”日历组件不能嵌套在其他日历组件中。但是，“VEVENT”日历组件可以相互关联，也可以与“VTODO”或具有“related-to”属性的“VJOURNAL”日历组件关联。
Example: The following is an example of the "VEVENT" calendar component used to represent a meeting that will also be opaque to searches for busy time:
示例：以下是“VEVENT”日历组件的示例，该组件用于表示对繁忙时间的搜索也是不透明的会议：
BEGIN:VEVENT UID:19970901T130000Z-123401@example.com DTSTAMP:19970901T130000Z DTSTART:19970903T163000Z DTEND:19970903T190000Z SUMMARY:Annual Employee Review CLASS:PRIVATE CATEGORIES:BUSINESS,HUMAN RESOURCES END:VEVENT
开始：VEVENT UID:19970901T130000Z-123401@example.comDTSTAMP:19970901T130000Z DTSTART:19970903T163000Z DTEND:19970903T190000Z摘要：年度员工考核类别：私人类别：业务、人力资源结束：VEVENT
The following is an example of the "VEVENT" calendar component used to represent a reminder that will not be opaque, but rather transparent, to searches for busy time:
以下是“VEVENT”日历组件的一个示例，用于表示一个提醒，该提醒对于搜索繁忙时间而言不是不透明的，而是透明的：
BEGIN:VEVENT UID:19970901T130000Z-123402@example.com DTSTAMP:19970901T130000Z DTSTART:19970401T163000Z DTEND:19970402T010000Z SUMMARY:Laurel is in sensitivity awareness class. CLASS:PUBLIC CATEGORIES:BUSINESS,HUMAN RESOURCES TRANSP:TRANSPARENT END:VEVENT
开始：VEVENT UID:19970901T130000Z-123402@example.comDTSTAMP:19970901T130000Z DTSTART:1997040116300Z DTEND:19970402T010000Z摘要：劳雷尔在敏感性意识课程中。类别：公共类别：业务、人力资源传输：透明端：VEVENT
The following is an example of the "VEVENT" calendar component used to represent an anniversary that will occur annually:
以下是“VEVENT”日历组件的示例，用于表示每年发生的周年纪念：
BEGIN:VEVENT
UID:19970901T130000Z-123403@example.com
DTSTAMP:19970901T130000Z
DTSTART;VALUE=DATE:19971102
SUMMARY:Our Blissful Anniversary
TRANSP:TRANSPARENT
CLASS:CONFIDENTIAL
CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION
RRULE:FREQ=YEARLY
END:VEVENT
BEGIN:VEVENT
UID:19970901T130000Z-123403@example.com
DTSTAMP:19970901T130000Z
DTSTART;VALUE=DATE:19971102
SUMMARY:Our Blissful Anniversary
TRANSP:TRANSPARENT
CLASS:CONFIDENTIAL
CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION
RRULE:FREQ=YEARLY
END:VEVENT
The following is an example of the "VEVENT" calendar component used to represent a multi-day event scheduled from June 28th, 2007 to July 8th, 2007 inclusively. Note that the "DTEND" property is set to July 9th, 2007, since the "DTEND" property specifies the non-inclusive end of the event.
以下是“VEVENT”日历组件的示例，用于表示从2007年6月28日到2007年7月8日（含）的多日活动。请注意，“DTEND”属性设置为2007年7月9日，因为“DTEND”属性指定事件的非包容性结束。
BEGIN:VEVENT
UID:20070423T123432Z-541111@example.com
DTSTAMP:20070423T123432Z
DTSTART;VALUE=DATE:20070628
DTEND;VALUE=DATE:20070709
SUMMARY:Festival International de Jazz de Montreal
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:20070423T123432Z-541111@example.com
DTSTAMP:20070423T123432Z
DTSTART;VALUE=DATE:20070628
DTEND;VALUE=DATE:20070709
SUMMARY:Festival International de Jazz de Montreal
TRANSP:TRANSPARENT
END:VEVENT
Component Name: VTODO
组件名称：VTODO
Purpose: Provide a grouping of calendar properties that describe a to-do.
目的：提供一组描述待办事项的日历属性。
Format Definition: A "VTODO" calendar component is defined by the following notation:
格式定义：“VTODO”日历组件由以下符号定义：
todoc = "BEGIN" ":" "VTODO" CRLF todoprop *alarmc "END" ":" "VTODO" CRLF
todoc=“BEGIN”“：“VTODO”CRLF todoprop*alarmc“END”“：“VTODO”CRLF
todoprop = *(
;
; The following are REQUIRED,
; but MUST NOT occur more than once.
;
dtstamp / uid /
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
class / completed / created / description /
dtstart / geo / last-mod / location / organizer /
percent / priority / recurid / seq / status /
summary / url /
;
; The following is OPTIONAL,
; but SHOULD NOT occur more than once.
;
rrule /
;
; Either 'due' or 'duration' MAY appear in
; a 'todoprop', but 'due' and 'duration'
; MUST NOT occur in the same 'todoprop'.
; If 'duration' appear in a 'todoprop',
; then 'dtstart' MUST also appear in
; the same 'todoprop'.
;
due / duration /
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
attach / attendee / categories / comment / contact /
exdate / rstatus / related / resources /
rdate / x-prop / iana-prop
;
)
todoprop = *(
;
; The following are REQUIRED,
; but MUST NOT occur more than once.
;
dtstamp / uid /
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
class / completed / created / description /
dtstart / geo / last-mod / location / organizer /
percent / priority / recurid / seq / status /
summary / url /
;
; The following is OPTIONAL,
; but SHOULD NOT occur more than once.
;
rrule /
;
; Either 'due' or 'duration' MAY appear in
; a 'todoprop', but 'due' and 'duration'
; MUST NOT occur in the same 'todoprop'.
; If 'duration' appear in a 'todoprop',
; then 'dtstart' MUST also appear in
; the same 'todoprop'.
;
due / duration /
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
attach / attendee / categories / comment / contact /
exdate / rstatus / related / resources /
rdate / x-prop / iana-prop
;
)
Description: A "VTODO" calendar component is a grouping of component properties and possibly "VALARM" calendar components that represent an action-item or assignment. For example, it can be
描述：“VTODO”日历组件是一组组件属性，可能还有代表操作项或任务的“VALARM”日历组件。例如，它可以是
used to represent an item of work assigned to an individual; such as "turn in travel expense today".
用于表示分配给个人的工作项目；例如“今天交差旅费”。
The "VTODO" calendar component cannot be nested within another calendar component. However, "VTODO" calendar components can be related to each other or to a "VEVENT" or to a "VJOURNAL" calendar component with the "RELATED-TO" property.
“VTODO”日历组件不能嵌套在其他日历组件中。但是，“VTODO”日历组件可以相互关联，也可以与“VEVENT”或具有“related-to”属性的“VJOURNAL”日历组件关联。
A "VTODO" calendar component without the "DTSTART" and "DUE" (or "DURATION") properties specifies a to-do that will be associated with each successive calendar date, until it is completed.
不带“DTSTART”和“DUE”（或“DURATION”）属性的“VTODO”日历组件指定一个待办事项，该待办事项将与每个连续日历日期关联，直到完成为止。
Examples: The following is an example of a "VTODO" calendar component that needs to be completed before May 1st, 2007. On midnight May 1st, 2007 this to-do would be considered overdue.
示例：以下是需要在2007年5月1日之前完成的“VTODO”日历组件的示例。2007年5月1日午夜，此待办事项将被视为逾期。
BEGIN:VTODO
UID:20070313T123432Z-456553@example.com
DTSTAMP:20070313T123432Z
DUE;VALUE=DATE:20070501
SUMMARY:Submit Quebec Income Tax Return for 2006
CLASS:CONFIDENTIAL
CATEGORIES:FAMILY,FINANCE
STATUS:NEEDS-ACTION
END:VTODO
BEGIN:VTODO
UID:20070313T123432Z-456553@example.com
DTSTAMP:20070313T123432Z
DUE;VALUE=DATE:20070501
SUMMARY:Submit Quebec Income Tax Return for 2006
CLASS:CONFIDENTIAL
CATEGORIES:FAMILY,FINANCE
STATUS:NEEDS-ACTION
END:VTODO
The following is an example of a "VTODO" calendar component that was due before 1:00 P.M. UTC on July 9th, 2007 and was completed on July 7th, 2007 at 10:00 A.M. UTC.
以下是2007年7月9日下午1:00 UTC之前到期并于2007年7月7日上午10:00 UTC完成的“VTODO”日历组件示例。
BEGIN:VTODO UID:20070514T103211Z-123404@example.com DTSTAMP:20070514T103211Z DTSTART:20070514T110000Z DUE:20070709T130000Z COMPLETED:20070707T100000Z SUMMARY:Submit Revised Internet-Draft PRIORITY:1 STATUS:NEEDS-ACTION END:VTODO
开始：VTODO UID:20070514T103211Z-123404@example.comDTSTAMP:20070514T103211Z DTSTART:20070514T1110000Z到期日期：20070709T130000Z完成日期：20070707T100000Z摘要：提交修订后的互联网草案优先级：1状态：需求-行动结束：VTODO
Component Name: VJOURNAL
组件名称：VJOURNAL
Purpose: Provide a grouping of component properties that describe a journal entry.
目的：提供描述日记账分录的组件属性分组。
Format Definition: A "VJOURNAL" calendar component is defined by the following notation:
格式定义：“VJOURNAL”日历组件由以下符号定义：
journalc = "BEGIN" ":" "VJOURNAL" CRLF jourprop "END" ":" "VJOURNAL" CRLF
journalc=“BEGIN”“：“VJOURNAL”CRLF jourprop“END”“：“VJOURNAL”CRLF
jourprop = *(
;
; The following are REQUIRED,
; but MUST NOT occur more than once.
;
dtstamp / uid /
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
class / created / dtstart /
last-mod / organizer / recurid / seq /
status / summary / url /
;
; The following is OPTIONAL,
; but SHOULD NOT occur more than once.
;
rrule /
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
attach / attendee / categories / comment /
contact / description / exdate / related / rdate /
rstatus / x-prop / iana-prop
;
)
jourprop = *(
;
; The following are REQUIRED,
; but MUST NOT occur more than once.
;
dtstamp / uid /
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
class / created / dtstart /
last-mod / organizer / recurid / seq /
status / summary / url /
;
; The following is OPTIONAL,
; but SHOULD NOT occur more than once.
;
rrule /
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
attach / attendee / categories / comment /
contact / description / exdate / related / rdate /
rstatus / x-prop / iana-prop
;
)
Description: A "VJOURNAL" calendar component is a grouping of component properties that represent one or more descriptive text notes associated with a particular calendar date. The "DTSTART" property is used to specify the calendar date with which the journal entry is associated. Generally, it will have a DATE value data type, but it can also be used to specify a DATE-TIME value data type. Examples of a journal entry include a daily record of a legislative body or a journal entry of individual telephone contacts for the day or an ordered list of accomplishments for the day. The "VJOURNAL" calendar component can also be used to associate a document with a calendar date.
描述：“VJOURNAL”日历组件是一组组件属性，表示与特定日历日期关联的一个或多个描述性文本注释。“DTSTART”属性用于指定与日记账分录关联的日历日期。通常，它将具有日期值数据类型，但也可用于指定日期时间值数据类型。日记账分录的示例包括立法机构的每日记录、当天个人电话联系人的日记账分录或当天的有序成就列表。“VJOURNAL”日历组件还可用于将文档与日历日期关联。
The "VJOURNAL" calendar component does not take up time on a calendar. Hence, it does not play a role in free or busy time searches -- it is as though it has a time transparency value of TRANSPARENT. It is transparent to any such searches.
“VJOURNAL”日历组件不占用日历上的时间。因此，它在忙时或闲时搜索中不起作用——就好像它的时间透明度值为TRANSPARENT一样。它对任何此类搜索都是透明的。
The "VJOURNAL" calendar component cannot be nested within another calendar component. However, "VJOURNAL" calendar components can be related to each other or to a "VEVENT" or to a "VTODO" calendar component, with the "RELATED-TO" property.
“VJOURNAL”日历组件不能嵌套在其他日历组件中。但是，“VJOURNAL”日历组件可以相互关联，也可以使用“related-to”属性与“VEVENT”或“VTODO”日历组件关联。
Example: The following is an example of the "VJOURNAL" calendar component:
示例：以下是“VJOURNAL”日历组件的示例：
BEGIN:VJOURNAL UID:19970901T130000Z-123405@example.com DTSTAMP:19970901T130000Z DTSTART;VALUE=DATE:19970317 SUMMARY:Staff meeting minutes DESCRIPTION:1. Staff meeting: Participants include Joe\, Lisa\, and Bob. Aurora project plans were reviewed. There is currently no budget reserves for this project. Lisa will escalate to management. Next meeting on Tuesday.\n 2. Telephone Conference: ABC Corp. sales representative called to discuss new printer. Promised to get us a demo by Friday.\n3. Henry Miller (Handsoff Insurance): Car was totaled by tree. Is looking into a loaner car. 555-2323 (tel). END:VJOURNAL
开始：VUID:19970901T130000Z-123405@example.comDTSTAMP:19970901T13000Z DTSTART；值=日期：19970317摘要：员工会议记录说明：1。员工会议：参与者包括乔、丽莎和鲍勃。审查了Aurora项目计划。该项目目前没有预算准备金。Lisa将向管理层汇报。下一次会议将在星期二举行。\n 2。电话会议：ABC公司的销售代表打电话来讨论新打印机。答应在星期五之前给我们一个演示。\n3。亨利·米勒（握手保险）：这辆车被树撞坏了。他正在调查一辆借来的车。555-2323（电话）。完:VJOURNAL
Component Name: VFREEBUSY
组件名称：VFREEBUSY
Purpose: Provide a grouping of component properties that describe either a request for free/busy time, describe a response to a request for free/busy time, or describe a published set of busy time.
目的：提供一组组件属性，这些属性描述忙/闲时间请求、对忙/闲时间请求的响应或已发布的忙时间集。
Format Definition: A "VFREEBUSY" calendar component is defined by the following notation:
格式定义：“VFREEBUSY”日历组件由以下符号定义：
freebusyc = "BEGIN" ":" "VFREEBUSY" CRLF fbprop "END" ":" "VFREEBUSY" CRLF
freebusyc=“BEGIN”“：“VFREEBUSY”CRLF fbprop“END”“：“VFREEBUSY”CRLF
fbprop = *(
;
; The following are REQUIRED,
fbprop = *(
;
; The following are REQUIRED,
; but MUST NOT occur more than once.
;
dtstamp / uid /
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
contact / dtstart / dtend /
organizer / url /
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
attendee / comment / freebusy / rstatus / x-prop /
iana-prop
;
)
; but MUST NOT occur more than once.
;
dtstamp / uid /
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
contact / dtstart / dtend /
organizer / url /
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
attendee / comment / freebusy / rstatus / x-prop /
iana-prop
;
)
Description: A "VFREEBUSY" calendar component is a grouping of component properties that represents either a request for free or busy time information, a reply to a request for free or busy time information, or a published set of busy time information.
描述：“VFREEBUSY”日历组件是一组组件属性，表示空闲或繁忙时间信息的请求、对空闲或繁忙时间信息请求的答复，或一组已发布的繁忙时间信息。
When used to request free/busy time information, the "ATTENDEE" property specifies the calendar users whose free/busy time is being requested; the "ORGANIZER" property specifies the calendar user who is requesting the free/busy time; the "DTSTART" and "DTEND" properties specify the window of time for which the free/ busy time is being requested; the "UID" and "DTSTAMP" properties are specified to assist in proper sequencing of multiple free/busy time requests.
当用于请求忙/闲时间信息时，“ATTENDEE”属性指定正在请求其忙/闲时间的日历用户；“ORGANIZER”属性指定请求闲/忙时间的日历用户；“DTSTART”和“DTEND”属性指定请求闲/忙时间的时间窗口；指定“UID”和“DTSTAMP”属性是为了帮助对多个忙/闲时间请求进行正确排序。
When used to reply to a request for free/busy time, the "ATTENDEE" property specifies the calendar user responding to the free/busy time request; the "ORGANIZER" property specifies the calendar user that originally requested the free/busy time; the "FREEBUSY" property specifies the free/busy time information (if it exists); and the "UID" and "DTSTAMP" properties are specified to assist in proper sequencing of multiple free/busy time replies.
当用于答复忙/闲时间请求时，“ATTENDEE”属性指定响应忙/闲时间请求的日历用户；“ORGANIZER”属性指定最初请求闲/忙时间的日历用户；“忙/闲”属性指定忙/闲时间信息（如果存在）；指定“UID”和“DTSTAMP”属性有助于对多个忙/闲回复进行正确排序。
When used to publish busy time, the "ORGANIZER" property specifies the calendar user associated with the published busy time; the "DTSTART" and "DTEND" properties specify an inclusive time window that surrounds the busy time information; the "FREEBUSY" property specifies the published busy time information; and the "DTSTAMP" property specifies the DATE-TIME that iCalendar object was created.
当用于发布繁忙时间时，“组织者”属性指定与发布的繁忙时间关联的日历用户；“DTSTART”和“DTEND”属性指定一个包含繁忙时间信息的时间窗口；“FREEBUSY”属性指定已发布的忙时信息；“DTSTAMP”属性指定创建iCalendar对象的日期和时间。
The "VFREEBUSY" calendar component cannot be nested within another calendar component. Multiple "VFREEBUSY" calendar components can be specified within an iCalendar object. This permits the grouping of free/busy information into logical collections, such as monthly groups of busy time information.
“VFREEBUSY”日历组件不能嵌套在其他日历组件中。可以在iCalendar对象中指定多个“VFREEBUSY”日历组件。这允许将忙/闲信息分组到逻辑集合中，例如忙时间信息的每月分组。
The "VFREEBUSY" calendar component is intended for use in iCalendar object methods involving requests for free time, requests for busy time, requests for both free and busy, and the associated replies.
“VFREEBUSY”日历组件用于iCalendar对象方法，包括空闲时间请求、忙时间请求、忙/闲请求以及相关回复。
Free/Busy information is represented with the "FREEBUSY" property. This property provides a terse representation of time periods. One or more "FREEBUSY" properties can be specified in the "VFREEBUSY" calendar component.
忙/闲信息用“FREEBUSY”属性表示。此属性提供时间段的简洁表示。可以在“VFREEBUSY”日历组件中指定一个或多个“FREEBUSY”属性。
When present in a "VFREEBUSY" calendar component, the "DTSTART" and "DTEND" properties SHOULD be specified prior to any "FREEBUSY" properties.
当出现在“VFREEBUSY”日历组件中时，“DTSTART”和“DTEND”属性应在任何“FREEBUSY”属性之前指定。
The recurrence properties ("RRULE", "RDATE", "EXDATE") are not permitted within a "VFREEBUSY" calendar component. Any recurring events are resolved into their individual busy time periods using the "FREEBUSY" property.
“VFREEBUSY”日历组件中不允许重复属性（“RRULE”、“RDATE”、“EXDATE”）。使用“FREEBUSY”属性将任何重复事件解析为各自的忙时段。
Example: The following is an example of a "VFREEBUSY" calendar component used to request free or busy time information:
示例：以下是用于请求忙/闲时间信息的“vfreebush”日历组件的示例：
BEGIN:VFREEBUSY
UID:19970901T082949Z-FA43EF@example.com
ORGANIZER:mailto:jane_doe@example.com
ATTENDEE:mailto:john_public@example.com
DTSTART:19971015T050000Z
DTEND:19971016T050000Z
DTSTAMP:19970901T083000Z
END:VFREEBUSY
BEGIN:VFREEBUSY
UID:19970901T082949Z-FA43EF@example.com
ORGANIZER:mailto:jane_doe@example.com
ATTENDEE:mailto:john_public@example.com
DTSTART:19971015T050000Z
DTEND:19971016T050000Z
DTSTAMP:19970901T083000Z
END:VFREEBUSY
The following is an example of a "VFREEBUSY" calendar component used to reply to the request with busy time information:
以下是“VFREEBUSY”日历组件的一个示例，用于使用繁忙时间信息回复请求：
BEGIN:VFREEBUSY
UID:19970901T095957Z-76A912@example.com
ORGANIZER:mailto:jane_doe@example.com
ATTENDEE:mailto:john_public@example.com
DTSTAMP:19970901T100000Z
FREEBUSY:19971015T050000Z/PT8H30M,
19971015T160000Z/PT5H30M,19971015T223000Z/PT6H30M
URL:http://example.com/pub/busy/jpublic-01.ifb
COMMENT:This iCalendar file contains busy time information for
the next three months.
END:VFREEBUSY
BEGIN:VFREEBUSY
UID:19970901T095957Z-76A912@example.com
ORGANIZER:mailto:jane_doe@example.com
ATTENDEE:mailto:john_public@example.com
DTSTAMP:19970901T100000Z
FREEBUSY:19971015T050000Z/PT8H30M,
19971015T160000Z/PT5H30M,19971015T223000Z/PT6H30M
URL:http://example.com/pub/busy/jpublic-01.ifb
COMMENT:This iCalendar file contains busy time information for
the next three months.
END:VFREEBUSY
The following is an example of a "VFREEBUSY" calendar component used to publish busy time information:
以下是用于发布繁忙时间信息的“VFREEBUSY”日历组件的示例：
BEGIN:VFREEBUSY
UID:19970901T115957Z-76A912@example.com
DTSTAMP:19970901T120000Z
ORGANIZER:jsmith@example.com
DTSTART:19980313T141711Z
DTEND:19980410T141711Z
FREEBUSY:19980314T233000Z/19980315T003000Z
FREEBUSY:19980316T153000Z/19980316T163000Z
FREEBUSY:19980318T030000Z/19980318T040000Z
URL:http://www.example.com/calendar/busytime/jsmith.ifb
END:VFREEBUSY
BEGIN:VFREEBUSY
UID:19970901T115957Z-76A912@example.com
DTSTAMP:19970901T120000Z
ORGANIZER:jsmith@example.com
DTSTART:19980313T141711Z
DTEND:19980410T141711Z
FREEBUSY:19980314T233000Z/19980315T003000Z
FREEBUSY:19980316T153000Z/19980316T163000Z
FREEBUSY:19980318T030000Z/19980318T040000Z
URL:http://www.example.com/calendar/busytime/jsmith.ifb
END:VFREEBUSY
Component Name: VTIMEZONE
组件名称：VTIMEZONE
Purpose: Provide a grouping of component properties that defines a time zone.
目的：提供定义时区的组件属性分组。
Format Definition: A "VTIMEZONE" calendar component is defined by the following notation:
格式定义：“VTIMEZONE”日历组件由以下符号定义：
timezonec = "BEGIN" ":" "VTIMEZONE" CRLF
*(
;
; 'tzid' is REQUIRED, but MUST NOT occur more
; than once.
;
tzid /
;
timezonec = "BEGIN" ":" "VTIMEZONE" CRLF
*(
;
; 'tzid' is REQUIRED, but MUST NOT occur more
; than once.
;
tzid /
;
; 'last-mod' and 'tzurl' are OPTIONAL,
; but MUST NOT occur more than once.
;
last-mod / tzurl /
;
; One of 'standardc' or 'daylightc' MUST occur
; and each MAY occur more than once.
;
standardc / daylightc /
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
x-prop / iana-prop
;
)
"END" ":" "VTIMEZONE" CRLF
; 'last-mod' and 'tzurl' are OPTIONAL,
; but MUST NOT occur more than once.
;
last-mod / tzurl /
;
; One of 'standardc' or 'daylightc' MUST occur
; and each MAY occur more than once.
;
standardc / daylightc /
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
x-prop / iana-prop
;
)
"END" ":" "VTIMEZONE" CRLF
standardc = "BEGIN" ":" "STANDARD" CRLF tzprop "END" ":" "STANDARD" CRLF
standardc=“开始”：“标准”CRLF tzprop“结束”：“标准”CRLF
daylightc = "BEGIN" ":" "DAYLIGHT" CRLF tzprop "END" ":" "DAYLIGHT" CRLF
daylightc=“BEGIN”“：“DAYLIGHT”CRLF tzprop“END”“：“DAYLIGHT”CRLF
tzprop = *(
;
; The following are REQUIRED,
; but MUST NOT occur more than once.
;
dtstart / tzoffsetto / tzoffsetfrom /
;
; The following is OPTIONAL,
; but SHOULD NOT occur more than once.
;
rrule /
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
comment / rdate / tzname / x-prop / iana-prop
;
)
tzprop = *(
;
; The following are REQUIRED,
; but MUST NOT occur more than once.
;
dtstart / tzoffsetto / tzoffsetfrom /
;
; The following is OPTIONAL,
; but SHOULD NOT occur more than once.
;
rrule /
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
comment / rdate / tzname / x-prop / iana-prop
;
)
Description: A time zone is unambiguously defined by the set of time measurement rules determined by the governing body for a given geographic area. These rules describe, at a minimum, the base
说明：时区由管理机构为给定地理区域确定的一组时间度量规则明确定义。这些规则至少描述了基础
offset from UTC for the time zone, often referred to as the Standard Time offset. Many locations adjust their Standard Time forward or backward by one hour, in order to accommodate seasonal changes in number of daylight hours, often referred to as Daylight Saving Time. Some locations adjust their time by a fraction of an hour. Standard Time is also known as Winter Time. Daylight Saving Time is also known as Advanced Time, Summer Time, or Legal Time in certain countries. The following table shows the changes in time zone rules in effect for New York City starting from 1967. Each line represents a description or rule for a particular observance.
时区的UTC偏移，通常称为标准时间偏移。许多地方将标准时间向前或向后调整一小时，以适应夏时制（通常称为夏令时）数量的季节性变化。一些地点将时间调整了几分之一小时。标准时间也称为冬季时间。夏时制在某些国家也称为高级时间、夏季时间或法定时间。下表显示了自1967年起对纽约市生效的时区规则的变化。每一行代表一个特定遵守的描述或规则。
Effective Observance Rule
有效遵守规则
+-----------+--------------------------+--------+--------------+
| Date | (Date-Time) | Offset | Abbreviation |
+-----------+--------------------------+--------+--------------+
| 1967-1973 | last Sun in Apr, 02:00 | -0400 | EDT |
| | | | |
| 1967-2006 | last Sun in Oct, 02:00 | -0500 | EST |
| | | | |
| 1974-1974 | Jan 6, 02:00 | -0400 | EDT |
| | | | |
| 1975-1975 | Feb 23, 02:00 | -0400 | EDT |
| | | | |
| 1976-1986 | last Sun in Apr, 02:00 | -0400 | EDT |
| | | | |
| 1987-2006 | first Sun in Apr, 02:00 | -0400 | EDT |
| | | | |
| 2007-* | second Sun in Mar, 02:00 | -0400 | EDT |
| | | | |
| 2007-* | first Sun in Nov, 02:00 | -0500 | EST |
+-----------+--------------------------+--------+--------------+
+-----------+--------------------------+--------+--------------+
| Date | (Date-Time) | Offset | Abbreviation |
+-----------+--------------------------+--------+--------------+
| 1967-1973 | last Sun in Apr, 02:00 | -0400 | EDT |
| | | | |
| 1967-2006 | last Sun in Oct, 02:00 | -0500 | EST |
| | | | |
| 1974-1974 | Jan 6, 02:00 | -0400 | EDT |
| | | | |
| 1975-1975 | Feb 23, 02:00 | -0400 | EDT |
| | | | |
| 1976-1986 | last Sun in Apr, 02:00 | -0400 | EDT |
| | | | |
| 1987-2006 | first Sun in Apr, 02:00 | -0400 | EDT |
| | | | |
| 2007-* | second Sun in Mar, 02:00 | -0400 | EDT |
| | | | |
| 2007-* | first Sun in Nov, 02:00 | -0500 | EST |
+-----------+--------------------------+--------+--------------+
Note: The specification of a global time zone registry is not addressed by this document and is left for future study. However, implementers may find the TZ database [TZDB] a useful reference. It is an informal, public-domain collection of time zone information, which is currently being maintained by volunteer Internet participants, and is used in several operating systems. This database contains current and historical time zone information for a wide variety of locations around the globe; it provides a time zone identifier for every unique time zone rule set in actual use since 1970, with historical data going back to the introduction of standard time.
注：本文件未涉及全球时区注册表的规范，留待将来研究。然而，实现者可能会发现TZ数据库[TZDB]是一个有用的参考。它是一个非正式的、公共领域的时区信息集合，目前由志愿互联网参与者维护，并在若干操作系统中使用。该数据库包含全球各种地点的当前和历史时区信息；它为自1970年以来实际使用的每个唯一时区规则集提供时区标识符，历史数据可追溯到标准时间的引入。
Interoperability between two calendaring and scheduling applications, especially for recurring events, to-dos or journal entries, is dependent on the ability to capture and convey date and time information in an unambiguous format. The specification of current time zone information is integral to this behavior.
两个日历和日程安排应用程序之间的互操作性，特别是对于重复事件、待办事项或日记条目，取决于以明确的格式捕获和传递日期和时间信息的能力。当前时区信息的规范是此行为的组成部分。
If present, the "VTIMEZONE" calendar component defines the set of Standard Time and Daylight Saving Time observances (or rules) for a particular time zone for a given interval of time. The "VTIMEZONE" calendar component cannot be nested within other calendar components. Multiple "VTIMEZONE" calendar components can exist in an iCalendar object. In this situation, each "VTIMEZONE" MUST represent a unique time zone definition. This is necessary for some classes of events, such as airline flights, that start in one time zone and end in another.
如果存在，“VTIMEZONE”日历组件，则为给定时间间隔的特定时区定义一组标准时间和夏令时遵守（或规则）。“VTIMEZONE”日历组件不能嵌套在其他日历组件中。iCalendar对象中可以存在多个“VTIMEZONE”日历组件。在这种情况下，每个“VTIMEZONE”必须表示一个唯一的时区定义。这对于某些类别的事件是必要的，例如在一个时区开始，在另一个时区结束的航空航班。
The "VTIMEZONE" calendar component MUST include the "TZID" property and at least one definition of a "STANDARD" or "DAYLIGHT" sub-component. The "STANDARD" or "DAYLIGHT" sub-component MUST include the "DTSTART", "TZOFFSETFROM", and "TZOFFSETTO" properties.
“VTIMEZONE”日历组件必须包括“TZID”属性和至少一个“标准”或“日光”子组件的定义。“标准”或“日光”子组件必须包括“DTSTART”、“TZOFFSETFROM”和“TZOFFSETTO”属性。
An individual "VTIMEZONE" calendar component MUST be specified for each unique "TZID" parameter value specified in the iCalendar object. In addition, a "VTIMEZONE" calendar component, referred to by a recurring calendar component, MUST provide valid time zone information for all recurrence instances.
必须为iCalendar对象中指定的每个唯一“TZID”参数值指定单独的“VTIMEZONE”日历组件。此外，由定期日历组件引用的“VTIMEZONE”日历组件必须为所有定期实例提供有效的时区信息。
Each "VTIMEZONE" calendar component consists of a collection of one or more sub-components that describe the rule for a particular observance (either a Standard Time or a Daylight Saving Time observance). The "STANDARD" sub-component consists of a collection of properties that describe Standard Time. The "DAYLIGHT" sub-component consists of a collection of properties that describe Daylight Saving Time. In general, this collection of properties consists of:
每个“VTIMEZONE”日历组件由一个或多个子组件的集合组成，这些子组件描述特定遵守的规则（标准时间或夏令时遵守）。“标准”子组件由描述标准时间的属性集合组成。“日光”子组件由描述夏令时的属性集合组成。通常，此属性集合包括：
* the first onset DATE-TIME for the observance;
* 庆祝活动的首次开始日期和时间；
* the last onset DATE-TIME for the observance, if a last onset is known;
* 如果知道最后一次发作，则为最后一次发作日期和时间；
* the offset to be applied for the observance;
* 用于遵守的补偿；
* a rule that describes the day and time when the observance takes effect;
* 一种规则，描述了纪念活动生效的日期和时间；
* an optional name for the observance.
* 纪念活动的可选名称。
For a given time zone, there may be multiple unique definitions of the observances over a period of time. Each observance is described using either a "STANDARD" or "DAYLIGHT" sub-component. The collection of these sub-components is used to describe the time zone for a given period of time. The offset to apply at any given time is found by locating the observance that has the last onset date and time before the time in question, and using the offset value from that observance.
对于一个给定的时区，在一段时间内可能有多个唯一的观测定义。使用“标准”或“日光”子组件描述每个遵守情况。这些子组件的集合用于描述给定时间段的时区。在任何给定时间应用的偏移量是通过定位在相关时间之前具有最后开始日期和时间的观测值，并使用该观测值的偏移量值来找到的。
The top-level properties in a "VTIMEZONE" calendar component are:
“VTIMEZONE”日历组件中的顶级属性包括：
The mandatory "TZID" property is a text value that uniquely identifies the "VTIMEZONE" calendar component within the scope of an iCalendar object.
必需的“TZID”属性是一个文本值，用于唯一标识iCalendar对象范围内的“VTIMEZONE”日历组件。
The optional "LAST-MODIFIED" property is a UTC value that specifies the date and time that this time zone definition was last updated.
可选的“LAST-MODIFIED”属性是一个UTC值，用于指定上次更新此时区定义的日期和时间。
The optional "TZURL" property is a url value that points to a published "VTIMEZONE" definition. "TZURL" SHOULD refer to a resource that is accessible by anyone who might need to interpret the object. This SHOULD NOT normally be a "file" URL or other URL that is not widely accessible.
可选的“TZURL”属性是指向已发布的“VTIMEZONE”定义的url值。“TZURL”应该指任何可能需要解释对象的人都可以访问的资源。这通常不应该是“文件”URL或其他无法广泛访问的URL。
The collection of properties that are used to define the "STANDARD" and "DAYLIGHT" sub-components include:
用于定义“标准”和“日光”子组件的特性集合包括：
The mandatory "DTSTART" property gives the effective onset date and local time for the time zone sub-component definition. "DTSTART" in this usage MUST be specified as a date with a local time value.
必填的“DTSTART”属性提供时区子组件定义的有效开始日期和本地时间。此用法中的“DTSTART”必须指定为具有本地时间值的日期。
The mandatory "TZOFFSETFROM" property gives the UTC offset that is in use when the onset of this time zone observance begins. "TZOFFSETFROM" is combined with "DTSTART" to define the effective onset for the time zone sub-component definition. For example, the following represents the time at which the observance of Standard Time took effect in Fall 1967 for New York City:
强制性的“TZOFFSETFROM”属性提供了在开始遵守时区时使用的UTC偏移量。“TZOFFSETFROM”与“DTSTART”相结合，以定义时区子组件定义的有效起始点。例如，以下为1967年秋季纽约市遵守标准时间的时间：
DTSTART:19671029T020000
DTSTART:19671029T020000
TZOFFSETFROM:-0400
TZOFFSETFROM:-0400
The mandatory "TZOFFSETTO" property gives the UTC offset for the time zone sub-component (Standard Time or Daylight Saving Time) when this observance is in use.
强制的“Tzoffetto”属性给出了使用此约定时时区子组件（标准时间或夏令时）的UTC偏移量。
The optional "TZNAME" property is the customary name for the time zone. This could be used for displaying dates.
可选的“TZNAME”属性是时区的惯用名称。这可用于显示日期。
The onset DATE-TIME values for the observance defined by the time zone sub-component is defined by the "DTSTART", "RRULE", and "RDATE" properties.
时区子组件定义的观测开始日期时间值由“DTSTART”、“RRULE”和“RDATE”属性定义。
The "RRULE" property defines the recurrence rule for the onset of the observance defined by this time zone sub-component. Some specific requirements for the usage of "RRULE" for this purpose include:
“RRULE”属性定义了此时区子组件定义的遵守开始的重复规则。为此目的使用“RRULE”的一些具体要求包括：
* If observance is known to have an effective end date, the "UNTIL" recurrence rule parameter MUST be used to specify the last valid onset of this observance (i.e., the UNTIL DATE-TIME will be equal to the last instance generated by the recurrence pattern). It MUST be specified in UTC time.
* 如果已知遵守有一个有效结束日期，则必须使用“直到”重复规则参数来指定该遵守的最后一次有效开始（即，直到日期时间将等于重复模式生成的最后一次实例）。必须以UTC时间指定。
* The "DTSTART" and the "TZOFFSETFROM" properties MUST be used when generating the onset DATE-TIME values (instances) from the "RRULE".
* 从“RRULE”生成起始日期时间值（实例）时，必须使用“DTSTART”和“TZOFFSETFROM”属性。
The "RDATE" property can also be used to define the onset of the observance by giving the individual onset date and times. "RDATE" in this usage MUST be specified as a date with local time value, relative to the UTC offset specified in the "TZOFFSETFROM" property.
“RDATE”属性还可以通过给出单独的开始日期和时间来定义遵守的开始。此用法中的“RDATE”必须指定为具有本地时间值的日期，相对于“TZOFFSETFROM”属性中指定的UTC偏移量。
The optional "COMMENT" property is also allowed for descriptive explanatory text.
可选的“COMMENT”属性也允许用于描述性解释文本。
Example: The following are examples of the "VTIMEZONE" calendar component:
示例：“VTIMEZONE”日历组件的示例如下：
This is an example showing all the time zone rules for New York City since April 30, 1967 at 03:00:00 EDT.
这是一个显示自1967年4月30日美国东部夏令时03:00:00以来纽约市所有时区规则的示例。
BEGIN:VTIMEZONE
TZID:America/New_York
LAST-MODIFIED:20050809T050000Z
BEGIN:DAYLIGHT
DTSTART:19670430T020000
RRULE:FREQ=YEARLY;BYMONTH=4;BYDAY=-1SU;UNTIL=19730429T070000Z
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
BEGIN:STANDARD
BEGIN:VTIMEZONE
TZID:America/New_York
LAST-MODIFIED:20050809T050000Z
BEGIN:DAYLIGHT
DTSTART:19670430T020000
RRULE:FREQ=YEARLY;BYMONTH=4;BYDAY=-1SU;UNTIL=19730429T070000Z
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:19671029T020000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU;UNTIL=20061029T060000Z
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19740106T020000
RDATE:19750223T020000
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:19760425T020000
RRULE:FREQ=YEARLY;BYMONTH=4;BYDAY=-1SU;UNTIL=19860427T070000Z
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:19870405T020000
RRULE:FREQ=YEARLY;BYMONTH=4;BYDAY=1SU;UNTIL=20060402T070000Z
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
END:VTIMEZONE
DTSTART:19671029T020000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU;UNTIL=20061029T060000Z
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19740106T020000
RDATE:19750223T020000
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:19760425T020000
RRULE:FREQ=YEARLY;BYMONTH=4;BYDAY=-1SU;UNTIL=19860427T070000Z
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:19870405T020000
RRULE:FREQ=YEARLY;BYMONTH=4;BYDAY=1SU;UNTIL=20060402T070000Z
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
END:VTIMEZONE
This is an example showing time zone information for New York City using only the "DTSTART" property. Note that this is only suitable for a recurring event that starts on or later than March 11, 2007 at 03:00:00 EDT (i.e., the earliest effective transition date and time) and ends no later than March 9, 2008 at 01:59:59
这是一个仅使用“DTSTART”属性显示纽约市时区信息的示例。请注意，这仅适用于在2007年3月11日或之后美国东部夏令时03:00:00（即最早的有效过渡日期和时间）开始并在2008年3月9日01:59:59之前结束的重复事件
EST (i.e., latest valid date and time for EST in this scenario). For example, this can be used for a recurring event that occurs every Friday, 8:00 A.M.-9:00 A.M., starting June 1, 2007, ending December 31, 2007,
EST（即本场景中EST的最新有效日期和时间）。例如，这可用于从2007年6月1日起至2007年12月31日止每周五上午8:00至9:00发生的重复事件，
BEGIN:VTIMEZONE TZID:America/New_York LAST-MODIFIED:20050809T050000Z BEGIN:STANDARD DTSTART:20071104T020000 TZOFFSETFROM:-0400 TZOFFSETTO:-0500 TZNAME:EST END:STANDARD BEGIN:DAYLIGHT DTSTART:20070311T020000 TZOFFSETFROM:-0500 TZOFFSETTO:-0400 TZNAME:EDT END:DAYLIGHT END:VTIMEZONE
开始：VTIMEZONE TZID:America/New_York上次修改：20050809T050000Z开始：标准DTSTART:20071104T020000 TZOFFSETFROM:-0400 TZOFFSETTO:-0500 TZNAME:EST结束：标准开始：日光DTSTART:20070311T020000 TZOFFSETFROM:-0500 TZNAME:EDT结束：日光结束：VTIMEZONE
This is a simple example showing the current time zone rules for New York City using a "RRULE" recurrence pattern. Note that there is no effective end date to either of the Standard Time or Daylight Time rules. This information would be valid for a recurring event starting today and continuing indefinitely.
这是一个简单的示例，显示了使用“RRULE”重复模式的纽约市当前时区规则。请注意，标准时间或夏令时规则都没有有效的结束日期。此信息对于从今天开始并无限期持续的重复事件有效。
BEGIN:VTIMEZONE
TZID:America/New_York
LAST-MODIFIED:20050809T050000Z
TZURL:http://zones.example.com/tz/America-New_York.ics
BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VTIMEZONE
TZID:America/New_York
LAST-MODIFIED:20050809T050000Z
TZURL:http://zones.example.com/tz/America-New_York.ics
BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
END:VTIMEZONE
This is an example showing a set of rules for a fictitious time zone where the Daylight Time rule has an effective end date (i.e., after that date, Daylight Time is no longer observed).
这是一个示例，显示了虚拟时区的一组规则，其中夏时制规则具有有效的结束日期（即，在该日期之后，夏时制不再被遵守）。
BEGIN:VTIMEZONE
TZID:Fictitious
LAST-MODIFIED:19870101T000000Z
BEGIN:STANDARD
DTSTART:19671029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19870405T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=19980404T070000Z
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VTIMEZONE
TZID:Fictitious
LAST-MODIFIED:19870101T000000Z
BEGIN:STANDARD
DTSTART:19671029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19870405T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=19980404T070000Z
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
END:VTIMEZONE
This is an example showing a set of rules for a fictitious time zone where the first Daylight Time rule has an effective end date. There is a second Daylight Time rule that picks up where the other left off.
此示例显示了虚拟时区的一组规则，其中第一个夏时制规则具有有效的结束日期。还有第二条夏令时规则，从另一条停止的地方开始。
BEGIN:VTIMEZONE
TZID:Fictitious
LAST-MODIFIED:19870101T000000Z
BEGIN:STANDARD
DTSTART:19671029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19870405T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=19980404T070000Z
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:19990424T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=4
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VTIMEZONE
TZID:Fictitious
LAST-MODIFIED:19870101T000000Z
BEGIN:STANDARD
DTSTART:19671029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19870405T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=19980404T070000Z
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:19990424T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=4
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
END:VTIMEZONE
Component Name: VALARM
组件名称：VALARM
Purpose: Provide a grouping of component properties that define an alarm.
目的：提供定义报警的组件属性分组。
Format Definition: A "VALARM" calendar component is defined by the following notation:
格式定义：“VALARM”日历组件由以下符号定义：
alarmc = "BEGIN" ":" "VALARM" CRLF
(audioprop / dispprop / emailprop)
"END" ":" "VALARM" CRLF
alarmc = "BEGIN" ":" "VALARM" CRLF
(audioprop / dispprop / emailprop)
"END" ":" "VALARM" CRLF
audioprop = *(
;
; 'action' and 'trigger' are both REQUIRED,
audioprop = *(
;
; 'action' and 'trigger' are both REQUIRED,
; but MUST NOT occur more than once.
;
action / trigger /
;
; 'duration' and 'repeat' are both OPTIONAL,
; and MUST NOT occur more than once each;
; but if one occurs, so MUST the other.
;
duration / repeat /
;
; The following is OPTIONAL,
; but MUST NOT occur more than once.
;
attach /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
x-prop / iana-prop
;
)
; but MUST NOT occur more than once.
;
action / trigger /
;
; 'duration' and 'repeat' are both OPTIONAL,
; and MUST NOT occur more than once each;
; but if one occurs, so MUST the other.
;
duration / repeat /
;
; The following is OPTIONAL,
; but MUST NOT occur more than once.
;
attach /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
x-prop / iana-prop
;
)
dispprop = *(
;
; The following are REQUIRED,
; but MUST NOT occur more than once.
;
action / description / trigger /
;
; 'duration' and 'repeat' are both OPTIONAL,
; and MUST NOT occur more than once each;
; but if one occurs, so MUST the other.
;
duration / repeat /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
x-prop / iana-prop
;
)
dispprop = *(
;
; The following are REQUIRED,
; but MUST NOT occur more than once.
;
action / description / trigger /
;
; 'duration' and 'repeat' are both OPTIONAL,
; and MUST NOT occur more than once each;
; but if one occurs, so MUST the other.
;
duration / repeat /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
x-prop / iana-prop
;
)
emailprop = *(
;
; The following are all REQUIRED,
; but MUST NOT occur more than once.
;
action / description / trigger / summary /
emailprop = *(
;
; The following are all REQUIRED,
; but MUST NOT occur more than once.
;
action / description / trigger / summary /
;
; The following is REQUIRED,
; and MAY occur more than once.
;
attendee /
;
; 'duration' and 'repeat' are both OPTIONAL,
; and MUST NOT occur more than once each;
; but if one occurs, so MUST the other.
;
duration / repeat /
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
attach / x-prop / iana-prop
;
)
;
; The following is REQUIRED,
; and MAY occur more than once.
;
attendee /
;
; 'duration' and 'repeat' are both OPTIONAL,
; and MUST NOT occur more than once each;
; but if one occurs, so MUST the other.
;
duration / repeat /
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
attach / x-prop / iana-prop
;
)
Description: A "VALARM" calendar component is a grouping of component properties that is a reminder or alarm for an event or a to-do. For example, it may be used to define a reminder for a pending event or an overdue to-do.
描述：“VALARM”日历组件是一组组件属性，是事件或待办事项的提醒或警报。例如，它可用于定义未决事件或过期待办事项的提醒。
The "VALARM" calendar component MUST include the "ACTION" and "TRIGGER" properties. The "ACTION" property further constrains the "VALARM" calendar component in the following ways:
“VALARM”日历组件必须包含“ACTION”和“TRIGGER”属性。“ACTION”属性通过以下方式进一步约束“VALARM”日历组件：
When the action is "AUDIO", the alarm can also include one and only one "ATTACH" property, which MUST point to a sound resource, which is rendered when the alarm is triggered.
当动作为“音频”时，报警还可以包括且仅包括一个“附加”属性，该属性必须指向声音资源，该声音资源在触发报警时呈现。
When the action is "DISPLAY", the alarm MUST also include a "DESCRIPTION" property, which contains the text to be displayed when the alarm is triggered.
当动作为“显示”时，报警还必须包含“描述”属性，该属性包含触发报警时要显示的文本。
When the action is "EMAIL", the alarm MUST include a "DESCRIPTION" property, which contains the text to be used as the message body, a "SUMMARY" property, which contains the text to be used as the message subject, and one or more "ATTENDEE" properties, which contain the email address of attendees to receive the message. It can also include one or more "ATTACH" properties, which are intended to be sent as message attachments. When the alarm is triggered, the email message is sent.
当操作为“电子邮件”时，报警必须包括“说明”属性（包含用作邮件正文的文本）、“摘要”属性（包含用作邮件主题的文本）和一个或多个“与会者”属性（包含接收邮件的与会者的电子邮件地址）。它还可以包括一个或多个“附加”属性，这些属性将作为邮件附件发送。触发警报时，将发送电子邮件消息。
The "VALARM" calendar component MUST only appear within either a "VEVENT" or "VTODO" calendar component. "VALARM" calendar components cannot be nested. Multiple mutually independent
“VALARM”日历组件只能出现在“VEVENT”或“VTODO”日历组件中。“VALARM”日历组件不能嵌套。多元相互独立
"VALARM" calendar components can be specified for a single "VEVENT" or "VTODO" calendar component.
可以为单个“VEVENT”或“VTODO”日历组件指定“VALARM”日历组件。
The "TRIGGER" property specifies when the alarm will be triggered. The "TRIGGER" property specifies a duration prior to the start of an event or a to-do. The "TRIGGER" edge may be explicitly set to be relative to the "START" or "END" of the event or to-do with the "RELATED" parameter of the "TRIGGER" property. The "TRIGGER" property value type can alternatively be set to an absolute calendar date with UTC time.
“触发器”属性指定何时触发报警。“触发器”属性指定事件或待办事项开始之前的持续时间。“触发器”边缘可以显式设置为相对于事件的“开始”或“结束”，或者与“触发器”属性的“相关”参数相关。“触发器”属性值类型也可以设置为UTC时间的绝对日历日期。
In an alarm set to trigger on the "START" of an event or to-do, the "DTSTART" property MUST be present in the associated event or to-do. In an alarm in a "VEVENT" calendar component set to trigger on the "END" of the event, either the "DTEND" property MUST be present, or the "DTSTART" and "DURATION" properties MUST both be present. In an alarm in a "VTODO" calendar component set to trigger on the "END" of the to-do, either the "DUE" property MUST be present, or the "DTSTART" and "DURATION" properties MUST both be present.
在设置为在事件或待办事项“开始”时触发的报警中，“DTSTART”属性必须出现在相关事件或待办事项中。在设置为在事件“结束”时触发的“VEVENT”日历组件中的报警中，“DTEND”属性必须存在，或者“DTSTART”和“DURATION”属性都必须存在。在“VTODO”日历组件中设置为在待办事项“结束”时触发的报警中，“到期”属性必须存在，或者“DTSTART”和“DURATION”属性必须同时存在。
The alarm can be defined such that it triggers repeatedly. A definition of an alarm with a repeating trigger MUST include both the "DURATION" and "REPEAT" properties. The "DURATION" property specifies the delay period, after which the alarm will repeat. The "REPEAT" property specifies the number of additional repetitions that the alarm will be triggered. This repetition count is in addition to the initial triggering of the alarm. Both of these properties MUST be present in order to specify a repeating alarm. If one of these two properties is absent, then the alarm will not repeat beyond the initial trigger.
警报可以定义为重复触发。具有重复触发器的报警定义必须包括“持续时间”和“重复”属性。“DURATION”（持续时间）属性指定延迟时间，在该延迟时间之后，警报将重复。“REPEAT”（重复）属性指定将触发报警的额外重复次数。此重复计数是对警报初始触发的补充。为了指定重复报警，这两个属性都必须存在。如果缺少这两个属性中的一个，则警报将不会在初始触发器之后重复。
The "ACTION" property is used within the "VALARM" calendar component to specify the type of action invoked when the alarm is triggered. The "VALARM" properties provide enough information for a specific action to be invoked. It is typically the responsibility of a "Calendar User Agent" (CUA) to deliver the alarm in the specified fashion. An "ACTION" property value of AUDIO specifies an alarm that causes a sound to be played to alert the user; DISPLAY specifies an alarm that causes a text message to be displayed to the user; and EMAIL specifies an alarm that causes an electronic email message to be delivered to one or more email addresses.
“ACTION”属性在“VALARM”日历组件中用于指定触发报警时调用的操作类型。“VALARM”属性为调用特定操作提供了足够的信息。“日历用户代理”（CUA）通常负责以指定的方式发送警报。音频的“动作”属性值指定一个警报，该警报导致播放声音以提醒用户；DISPLAY（显示）指定导致向用户显示文本消息的报警；电子邮件指定一个警报，该警报导致电子电子邮件发送到一个或多个电子邮件地址。
In an AUDIO alarm, if the optional "ATTACH" property is included, it MUST specify an audio sound resource. The intention is that the sound will be played as the alarm effect. If an "ATTACH" property is specified that does not refer to a sound resource, or
在音频报警中，如果包含可选的“ATTACH”属性，则必须指定音频资源。其目的是将声音作为警报效果播放。如果指定的“附加”属性不引用声音资源，或
if the specified sound resource cannot be rendered (because its format is unsupported, or because it cannot be retrieved), then the CUA or other entity responsible for playing the sound may choose a fallback action, such as playing a built-in default sound, or playing no sound at all.
如果无法呈现指定的声音资源（因为其格式不受支持或无法检索），则CUA或负责播放声音的其他实体可以选择回退操作，例如播放内置默认声音，或根本不播放声音。
In a DISPLAY alarm, the intended alarm effect is for the text value of the "DESCRIPTION" property to be displayed to the user.
在显示报警中，预期报警效果是向用户显示“描述”属性的文本值。
In an EMAIL alarm, the intended alarm effect is for an email message to be composed and delivered to all the addresses specified by the "ATTENDEE" properties in the "VALARM" calendar component. The "DESCRIPTION" property of the "VALARM" calendar component MUST be used as the body text of the message, and the "SUMMARY" property MUST be used as the subject text. Any "ATTACH" properties in the "VALARM" calendar component SHOULD be sent as attachments to the message.
在电子邮件警报中，预期的警报效果是将电子邮件合成并发送到“VALARM”日历组件中“ATTENDEE”属性指定的所有地址。“VALARM”日历组件的“DESCRIPTION”属性必须用作消息的正文，而“SUMMARY”属性必须用作主题文本。“VALARM”日历组件中的任何“ATTACH”属性都应作为邮件附件发送。
Note: Implementations should carefully consider whether they accept alarm components from untrusted sources, e.g., when importing calendar objects from external sources. One reasonable policy is to always ignore alarm components that the calendar user has not set herself, or at least ask for confirmation in such a case.
注意：实现应该仔细考虑他们是否接受来自不可信源的警报组件，例如从外部源导入日历对象。一个合理的策略是始终忽略日历用户未自行设置的报警组件，或者至少在这种情况下要求确认。
Example: The following example is for a "VALARM" calendar component that specifies an audio alarm that will sound at a precise time and repeat 4 more times at 15-minute intervals:
示例：以下示例适用于“VALARM”日历组件，该组件指定一个音频警报，该警报将在精确时间响起，并以15分钟的间隔再重复4次：
BEGIN:VALARM
TRIGGER;VALUE=DATE-TIME:19970317T133000Z
REPEAT:4
DURATION:PT15M
ACTION:AUDIO
ATTACH;FMTTYPE=audio/basic:ftp://example.com/pub/
sounds/bell-01.aud
END:VALARM
BEGIN:VALARM
TRIGGER;VALUE=DATE-TIME:19970317T133000Z
REPEAT:4
DURATION:PT15M
ACTION:AUDIO
ATTACH;FMTTYPE=audio/basic:ftp://example.com/pub/
sounds/bell-01.aud
END:VALARM
The following example is for a "VALARM" calendar component that specifies a display alarm that will trigger 30 minutes before the scheduled start of the event or of the to-do it is associated with and will repeat 2 more times at 15-minute intervals:
以下示例适用于“VALARM”日历组件，该组件指定一个显示警报，该警报将在事件或与其相关的待办事项的计划开始前30分钟触发，并将以15分钟的间隔再重复2次：
BEGIN:VALARM TRIGGER:-PT30M REPEAT:2 DURATION:PT15M ACTION:DISPLAY DESCRIPTION:Breakfast meeting with executive\n team at 8:30 AM EST. END:VALARM
开始：VALARM触发器：-PT30M重复：2持续时间：PT15M操作：显示描述：东部时间上午8:30与执行团队的早餐会议。完:瓦拉姆
The following example is for a "VALARM" calendar component that specifies an email alarm that will trigger 2 days before the scheduled due DATE-TIME of a to-do with which it is associated. It does not repeat. The email has a subject, body, and attachment link.
以下示例适用于“VALARM”日历组件，该组件指定一个电子邮件警报，该警报将在与其关联的待办事项的预定截止日期时间前2天触发。它不会重复。电子邮件包含主题、正文和附件链接。
BEGIN:VALARM
TRIGGER;RELATED=END:-P2D
ACTION:EMAIL
ATTENDEE:mailto:john_doe@example.com
SUMMARY:*** REMINDER: SEND AGENDA FOR WEEKLY STAFF MEETING ***
DESCRIPTION:A draft agenda needs to be sent out to the attendees
to the weekly managers meeting (MGR-LIST). Attached is a
pointer the document template for the agenda file.
ATTACH;FMTTYPE=application/msword:http://example.com/
templates/agenda.doc
END:VALARM
BEGIN:VALARM
TRIGGER;RELATED=END:-P2D
ACTION:EMAIL
ATTENDEE:mailto:john_doe@example.com
SUMMARY:*** REMINDER: SEND AGENDA FOR WEEKLY STAFF MEETING ***
DESCRIPTION:A draft agenda needs to be sent out to the attendees
to the weekly managers meeting (MGR-LIST). Attached is a
pointer the document template for the agenda file.
ATTACH;FMTTYPE=application/msword:http://example.com/
templates/agenda.doc
END:VALARM
The Calendar Properties are attributes that apply to the iCalendar object, as a whole. These properties do not appear within a calendar component. They SHOULD be specified after the "BEGIN:VCALENDAR" delimiter string and prior to any calendar component.
日历属性是应用于iCalendar对象整体的属性。这些属性不显示在日历组件中。它们应该在“BEGIN:VCALENDAR”分隔符字符串之后和任何日历组件之前指定。
Property Name: CALSCALE
物业名称：CALSCALE
Purpose: This property defines the calendar scale used for the calendar information specified in the iCalendar object.
用途：此属性定义用于iCalendar对象中指定的日历信息的日历比例。
Value Type: TEXT
值类型：文本
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property can be specified once in an iCalendar object. The default value is "GREGORIAN".
一致性：此属性可以在iCalendar对象中指定一次。默认值为“格里高利”。
Description: This memo is based on the Gregorian calendar scale. The Gregorian calendar scale is assumed if this property is not specified in the iCalendar object. It is expected that other calendar scales will be defined in other specifications or by future versions of this memo.
说明：本备忘录以公历为基础。如果iCalendar对象中未指定此属性，则假定为公历刻度。预计其他日历刻度将在其他规范或本备忘录的未来版本中定义。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
calscale = "CALSCALE" calparam ":" calvalue CRLF
calscale=“calscale”calparam:“calvalue CRLF
calparam = *(";" other-param)
calparam = *(";" other-param)
calvalue = "GREGORIAN"
calvalue = "GREGORIAN"
Example: The following is an example of this property:
示例：以下是此属性的示例：
CALSCALE:GREGORIAN
CALSCALE:格里高利
Property Name: METHOD
属性名称：方法
Purpose: This property defines the iCalendar object method associated with the calendar object.
用途：此属性定义与日历对象关联的iCalendar对象方法。
Value Type: TEXT
值类型：文本
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property can be specified once in an iCalendar object.
一致性：此属性可以在iCalendar对象中指定一次。
Description: When used in a MIME message entity, the value of this property MUST be the same as the Content-Type "method" parameter value. If either the "METHOD" property or the Content-Type "method" parameter is specified, then the other MUST also be specified.
描述：在MIME消息实体中使用时，此属性的值必须与内容类型“方法”参数值相同。如果指定了“METHOD”属性或内容类型“METHOD”参数，则还必须指定另一个。
No methods are defined by this specification. This is the subject of other specifications, such as the iCalendar Transport-independent Interoperability Protocol (iTIP) defined by [2446bis].
本规范未定义任何方法。这是其他规范的主题，例如[2446bis]定义的iCalendar传输独立互操作性协议（iTIP）。
If this property is not present in the iCalendar object, then a scheduling transaction MUST NOT be assumed. In such cases, the iCalendar object is merely being used to transport a snapshot of
如果iCalendar对象中不存在此属性，则不能假设调度事务。在这种情况下，iCalendar对象仅用于传输
some calendar information; without the intention of conveying a scheduling semantic.
一些日历信息；没有传达调度语义的意图。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
method = "METHOD" metparam ":" metvalue CRLF
method=“method”metparam”：“metvalue CRLF
metparam = *(";" other-param)
metparam = *(";" other-param)
metvalue = iana-token
metvalue = iana-token
Example: The following is a hypothetical example of this property to convey that the iCalendar object is a scheduling request:
示例：以下是此属性的假设示例，用于说明iCalendar对象是调度请求：
METHOD:REQUEST
方法：请求
Property Name: PRODID
属性名称：PRODID
Purpose: This property specifies the identifier for the product that created the iCalendar object.
用途：此属性指定创建iCalendar对象的产品的标识符。
Value Type: TEXT
值类型：文本
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: The property MUST be specified once in an iCalendar object.
一致性：属性必须在iCalendar对象中指定一次。
Description: The vendor of the implementation SHOULD assure that this is a globally unique identifier; using some technique such as an FPI value, as defined in [ISO.9070.1991].
说明：实施供应商应确保这是一个全球唯一标识符；使用某种技术，如[ISO.9070.1991]中定义的FPI值。
This property SHOULD NOT be used to alter the interpretation of an iCalendar object beyond the semantics specified in this memo. For example, it is not to be used to further the understanding of non-standard properties.
此属性不应用于改变iCalendar对象的解释，使其超出本备忘录中指定的语义。例如，它不用于进一步了解非标准特性。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
prodid = "PRODID" pidparam ":" pidvalue CRLF
prodid=“prodid”pidparam”：“pidvalue CRLF
pidparam = *(";" other-param)
pidparam = *(";" other-param)
pidvalue = text ;Any text that describes the product and version ;and that is generally assured of being unique.
pidvalue=文本；描述产品和版本的任何文本；这通常被认为是独一无二的。
Example: The following is an example of this property. It does not imply that English is the default language.
示例：以下是此属性的示例。这并不意味着英语是默认语言。
PRODID:-//ABC Corporation//NONSGML My Product//EN
PRODID:-//ABC Corporation//NONSGML My Product//EN
Property Name: VERSION
属性名称：版本
Purpose: This property specifies the identifier corresponding to the highest version number or the minimum and maximum range of the iCalendar specification that is required in order to interpret the iCalendar object.
用途：此属性指定与解释iCalendar对象所需的iCalendar规范的最高版本号或最小和最大范围相对应的标识符。
Value Type: TEXT
值类型：文本
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property MUST be specified once in an iCalendar object.
一致性：此属性必须在iCalendar对象中指定一次。
Description: A value of "2.0" corresponds to this memo.
说明：值“2.0”对应于此备忘录。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
version = "VERSION" verparam ":" vervalue CRLF
version=“version”verparam:“vervalue CRLF”
verparam = *(";" other-param)
verparam = *(";" other-param)
vervalue = "2.0" ;This memo
/ maxver
/ (minver ";" maxver)
vervalue = "2.0" ;This memo
/ maxver
/ (minver ";" maxver)
minver = <A IANA-registered iCalendar version identifier>
;Minimum iCalendar version needed to parse the iCalendar object.
minver = <A IANA-registered iCalendar version identifier>
;Minimum iCalendar version needed to parse the iCalendar object.
maxver = <A IANA-registered iCalendar version identifier>
;Maximum iCalendar version needed to parse the iCalendar object.
maxver = <A IANA-registered iCalendar version identifier>
;Maximum iCalendar version needed to parse the iCalendar object.
Example: The following is an example of this property:
示例：以下是此属性的示例：
VERSION:2.0
版本：2.0
The following properties can appear within calendar components, as specified by each component property definition.
根据每个组件属性定义的指定，下列属性可以出现在日历组件中。
The following properties specify descriptive information about calendar components.
以下属性指定有关日历组件的说明信息。
Property Name: ATTACH
属性名称：附加
Purpose: This property provides the capability to associate a document object with a calendar component.
用途：此属性提供将文档对象与日历组件关联的功能。
Value Type: The default value type for this property is URI. The value type can also be set to BINARY to indicate inline binary encoded content information.
值类型：此属性的默认值类型为URI。值类型也可以设置为二进制，以指示内联二进制编码的内容信息。
Property Parameters: IANA, non-standard, inline encoding, and value data type property parameters can be specified on this property. The format type parameter can be specified on this property and is RECOMMENDED for inline binary encoded content information.
属性参数：可以在此属性上指定IANA、非标准、内联编码和值数据类型属性参数。可以在此属性上指定format type参数，建议用于内联二进制编码的内容信息。
Conformance: This property can be specified multiple times in a "VEVENT", "VTODO", "VJOURNAL", or "VALARM" calendar component with the exception of AUDIO alarm that only allows this property to occur once.
一致性：此属性可以在“VEVENT”、“VTODO”、“VJOURNAL”或“VALARM”日历组件中多次指定，但仅允许此属性出现一次的音频报警除外。
Description: This property is used in "VEVENT", "VTODO", and "VJOURNAL" calendar components to associate a resource (e.g., document) with the calendar component. This property is used in "VALARM" calendar components to specify an audio sound resource or an email message attachment. This property can be specified as a URI pointing to a resource or as inline binary encoded content.
描述：此属性在“VEVENT”、“VTODO”和“VJOURAL”日历组件中用于将资源（例如文档）与日历组件关联。此属性在“VALARM”日历组件中用于指定音频资源或电子邮件附件。此属性可以指定为指向资源的URI或内联二进制编码内容。
When this property is specified as inline binary encoded content, calendar applications MAY attempt to guess the media type of the resource via inspection of its content if and only if the media type of the resource is not given by the "FMTTYPE" parameter. If the media type remains unknown, calendar applications SHOULD treat it as type "application/octet-stream".
当此属性指定为内联二进制编码内容时，日历应用程序可能会尝试通过检查其内容来猜测资源的媒体类型，如果且仅当“FMTTYPE”参数未给出资源的媒体类型时。如果媒体类型未知，日历应用程序应将其视为“应用程序/八位字节流”类型。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
attach = "ATTACH" attachparam ( ":" uri ) / ( ";" "ENCODING" "=" "BASE64" ";" "VALUE" "=" "BINARY" ":" binary ) CRLF
attach=“attach”attachparam（“：”uri）/（“；”编码“=”BASE64“；”值“=”二进制“：”二进制）CRLF
attachparam = *(
;
; The following is OPTIONAL for a URI value,
; RECOMMENDED for a BINARY value,
; and MUST NOT occur more than once.
;
(";" fmttypeparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
attachparam = *(
;
; The following is OPTIONAL for a URI value,
; RECOMMENDED for a BINARY value,
; and MUST NOT occur more than once.
;
(";" fmttypeparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
Example: The following are examples of this property:
示例：以下是此属性的示例：
ATTACH:CID:jsmith.part3.960817T083000.xyzMail@example.com
ATTACH:CID:jsmith.part3.960817T083000.xyzMail@example.com
ATTACH;FMTTYPE=application/postscript:ftp://example.com/pub/
reports/r-960812.ps
ATTACH;FMTTYPE=application/postscript:ftp://example.com/pub/
reports/r-960812.ps
Property Name: CATEGORIES
属性名称：类别
Purpose: This property defines the categories for a calendar component.
用途：此属性定义日历组件的类别。
Value Type: TEXT
值类型：文本
Property Parameters: IANA, non-standard, and language property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准和语言属性参数。
Conformance: The property can be specified within "VEVENT", "VTODO", or "VJOURNAL" calendar components.
一致性：可以在“VEVENT”、“VTODO”或“VJOURNAL”日历组件中指定该属性。
Description: This property is used to specify categories or subtypes of the calendar component. The categories are useful in searching for a calendar component of a particular type and category. Within the "VEVENT", "VTODO", or "VJOURNAL" calendar components, more than one category can be specified as a COMMA-separated list of categories.
描述：此属性用于指定日历组件的类别或子类型。类别在搜索特定类型和类别的日历组件时非常有用。在“VEVENT”、“VTODO”或“VJOURNAL”日历组件中，可以将多个类别指定为以逗号分隔的类别列表。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
categories = "CATEGORIES" catparam ":" text *("," text) CRLF
categories=“categories”catparam:“text*（，“text”）CRLF
catparam = *(
;
; The following is OPTIONAL,
; but MUST NOT occur more than once.
;
(";" languageparam ) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
catparam = *(
;
; The following is OPTIONAL,
; but MUST NOT occur more than once.
;
(";" languageparam ) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
Example: The following are examples of this property:
示例：以下是此属性的示例：
CATEGORIES:APPOINTMENT,EDUCATION
类别：任用、教育
CATEGORIES:MEETING
类别：会议
Property Name: CLASS
属性名称：类
Purpose: This property defines the access classification for a calendar component.
用途：此属性定义日历组件的访问分类。
Value Type: TEXT
值类型：文本
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: The property can be specified once in a "VEVENT", "VTODO", or "VJOURNAL" calendar components.
一致性：该属性可以在“VEVENT”、“VTODO”或“VJOURNAL”日历组件中指定一次。
Description: An access classification is only one component of the general security system within a calendar application. It provides a method of capturing the scope of the access the calendar owner intends for information within an individual calendar entry. The access classification of an individual iCalendar component is useful when measured along with the other security components of a calendar system (e.g., calendar user authentication, authorization, access rights, access role, etc.). Hence, the semantics of the individual access classifications cannot be completely defined by this memo alone. Additionally, due to the "blind" nature of most exchange processes using this memo, these access classifications cannot serve as an enforcement statement for a system receiving an iCalendar object. Rather, they provide a method for capturing the intention of the calendar owner for the access to the calendar component. If not specified in a component that allows this property, the default value is PUBLIC. Applications MUST treat x-name and iana-token values they don't recognize the same way as they would the PRIVATE value.
描述：访问分类只是日历应用程序中通用安全系统的一个组件。它提供了一种方法，用于捕获日历所有者对单个日历条目中的信息的访问范围。当与日历系统的其他安全组件（例如，日历用户身份验证、授权、访问权限、访问角色等）一起测量时，单个iCalendar组件的访问分类非常有用。因此，单凭本备忘录无法完全定义各个访问分类的语义。此外，由于使用此备忘录的大多数exchange进程的“盲”性质，这些访问分类不能作为接收iCalendar对象的系统的强制声明。相反，它们提供了一种方法，用于捕获日历所有者访问日历组件的意图。如果未在允许此属性的组件中指定，则默认值为PUBLIC。应用程序必须处理x-name和iana令牌值，因为它们不能以与私有值相同的方式识别它们。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
class = "CLASS" classparam ":" classvalue CRLF
class=“class”classparam:“类值CRLF”
classparam = *(";" other-param)
classparam = *(";" other-param)
classvalue = "PUBLIC" / "PRIVATE" / "CONFIDENTIAL" / iana-token
/ x-name
;Default is PUBLIC
classvalue = "PUBLIC" / "PRIVATE" / "CONFIDENTIAL" / iana-token
/ x-name
;Default is PUBLIC
Example: The following is an example of this property:
示例：以下是此属性的示例：
CLASS:PUBLIC
类别：公共
Property Name: COMMENT
属性名称：COMMENT
Purpose: This property specifies non-processing information intended to provide a comment to the calendar user.
目的：此属性指定用于向日历用户提供注释的非处理信息。
Value Type: TEXT
值类型：文本
Property Parameters: IANA, non-standard, alternate text representation, and language property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准、替代文本表示和语言属性参数。
Conformance: This property can be specified multiple times in "VEVENT", "VTODO", "VJOURNAL", and "VFREEBUSY" calendar components as well as in the "STANDARD" and "DAYLIGHT" sub-components.
一致性：可以在“VEVENT”、“VTODO”、“VJOURNAL”和“VFREEBUSY”日历组件以及“STANDARD”和“DAYLIGHT”子组件中多次指定此属性。
Description: This property is used to specify a comment to the calendar user.
描述：此属性用于指定对日历用户的注释。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
comment = "COMMENT" commparam ":" text CRLF
comment=“comment”commparam:“text CRLF”
commparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" altrepparam) / (";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
commparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" altrepparam) / (";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
Example: The following is an example of this property:
示例：以下是此属性的示例：
COMMENT:The meeting really needs to include both ourselves and the customer. We can't hold this meeting without them. As a matter of fact\, the venue for the meeting ought to be at their site. - - John
评论：会议真的需要包括我们自己和客户。没有他们，我们不能召开这次会议。事实上，会议地点应该在他们的现场约翰
Property Name: DESCRIPTION
属性名称：描述
Purpose: This property provides a more complete description of the calendar component than that provided by the "SUMMARY" property.
用途：此属性提供了比“摘要”属性更完整的日历组件描述。
Value Type: TEXT
值类型：文本
Property Parameters: IANA, non-standard, alternate text representation, and language property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准、替代文本表示和语言属性参数。
Conformance: The property can be specified in the "VEVENT", "VTODO", "VJOURNAL", or "VALARM" calendar components. The property can be specified multiple times only within a "VJOURNAL" calendar component.
一致性：该属性可以在“VEVENT”、“VTODO”、“VJOURNAL”或“VALARM”日历组件中指定。只能在“VJOURNAL”日历组件中多次指定该属性。
Description: This property is used in the "VEVENT" and "VTODO" to capture lengthy textual descriptions associated with the activity.
描述：此属性在“VEVENT”和“VTODO”中用于捕获与活动相关联的冗长文本描述。
This property is used in the "VJOURNAL" calendar component to capture one or more textual journal entries.
此属性在“VJOURNAL”日历组件中用于捕获一个或多个文本日志条目。
This property is used in the "VALARM" calendar component to capture the display text for a DISPLAY category of alarm, and to capture the body text for an EMAIL category of alarm.
此属性在“VALARM”日历组件中用于捕获报警显示类别的显示文本，以及捕获报警电子邮件类别的正文文本。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
description = "DESCRIPTION" descparam ":" text CRLF
description=“description”descparam:“text CRLF”
descparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" altrepparam) / (";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
descparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" altrepparam) / (";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
Example: The following is an example of this property with formatted line breaks in the property value:
示例：以下是此属性的一个示例，属性值中有格式化的换行符：
DESCRIPTION:Meeting to provide technical review for "Phoenix" design.\nHappy Face Conference Room. Phoenix design team MUST attend this meeting.\nRSVP to team leader.
描述：为“凤凰”设计提供技术审查的会议。\n快乐面对会议室。Phoenix设计团队必须参加此会议。\n请向团队负责人汇报。
Property Name: GEO
物业名称:GEO
Purpose: This property specifies information related to the global position for the activity specified by a calendar component.
用途：此属性指定与日历组件指定的活动的全局位置相关的信息。
Value Type: FLOAT. The value MUST be two SEMICOLON-separated FLOAT values.
值类型：FLOAT。该值必须是两个分号分隔的浮点值。
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property can be specified in "VEVENT" or "VTODO" calendar components.
一致性：此属性可以在“VEVENT”或“VTODO”日历组件中指定。
Description: This property value specifies latitude and longitude, in that order (i.e., "LAT LON" ordering). The longitude represents the location east or west of the prime meridian as a positive or negative real number, respectively. The longitude and latitude values MAY be specified up to six decimal places, which will allow for accuracy to within one meter of geographical position. Receiving applications MUST accept values of this precision and MAY truncate values of greater precision.
描述：此属性值按该顺序（即“纬度-经度”顺序）指定纬度和经度。经度分别以正数或负数表示本初子午线以东或以西的位置。经度和纬度值最多可指定六位小数，这将允许精度在地理位置一米以内。接收应用程序必须接受此精度的值，并可能截断精度更高的值。
Values for latitude and longitude shall be expressed as decimal fractions of degrees. Whole degrees of latitude shall be represented by a two-digit decimal number ranging from 0 through 90. Whole degrees of longitude shall be represented by a decimal number ranging from 0 through 180. When a decimal fraction of a degree is specified, it shall be separated from the whole number of degrees by a decimal point.
纬度和经度值应以度的小数表示。整个纬度应由0到90之间的两位十进制数字表示。整个经度应由0到180之间的十进制数字表示。如果规定了度数的小数点，则应以小数点将其与度数的整数分开。
Latitudes north of the equator shall be specified by a plus sign (+), or by the absence of a minus sign (-), preceding the digits designating degrees. Latitudes south of the Equator shall be designated by a minus sign (-) preceding the digits designating degrees. A point on the Equator shall be assigned to the Northern Hemisphere.
赤道以北的纬度应在表示度数的数字前加上加号（+），或不加减号（-）。赤道以南的纬度应在表示度数的数字前用减号（-）表示。赤道上的一点应指定给北半球。
Longitudes east of the prime meridian shall be specified by a plus sign (+), or by the absence of a minus sign (-), preceding the digits designating degrees. Longitudes west of the meridian shall be designated by minus sign (-) preceding the digits designating degrees. A point on the prime meridian shall be assigned to the Eastern Hemisphere. A point on the 180th meridian shall be assigned to the Western Hemisphere. One exception to this last convention is permitted. For the special condition of describing a band of latitude around the earth, the East Bounding Coordinate data element shall be assigned the value +180 (180) degrees.
本初子午线以东的经度应在表示度数的数字前加上加号（+），或不加减号（-）。子午线以西的经度应在表示度数的数字前用减号（-）表示。本初子午线上的一点应划归东半球。第180子午线上的一个点应指定给西半球。最后一项公约允许有一个例外。对于描述地球周围纬度带的特殊条件，应为东边界坐标数据元素指定+180（180）度的值。
Any spatial address with a latitude of +90 (90) or -90 degrees will specify the position at the North or South Pole, respectively. The component for longitude may have any legal value.
任何纬度为+90（90）或-90度的空间地址将分别指定北极或南极的位置。经度组件可能具有任何合法值。
With the exception of the special condition described above, this form is specified in [ANSI INCITS 61-1986].
除上述特殊条件外，[ANSI INCITS 61-1986]中规定了该表格。
The simple formula for converting degrees-minutes-seconds into decimal degrees is:
将度数分秒转换为十进制度数的简单公式为：
decimal = degrees + minutes/60 + seconds/3600.
十进制=度+分/60+秒/3600。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
geo = "GEO" geoparam ":" geovalue CRLF
geo=“geo”geoparam:“geovalue CRLF”
geoparam = *(";" other-param)
geoparam = *(";" other-param)
geovalue = float ";" float ;Latitude and Longitude components
地理值=浮动“；”浮动；经纬度分量
Example: The following is an example of this property:
示例：以下是此属性的示例：
GEO:37.386013;-122.082932
地理：37.386013-122.082932
Property Name: LOCATION
属性名称：位置
Purpose: This property defines the intended venue for the activity defined by a calendar component.
用途：此属性定义日历组件定义的活动的预期地点。
Value Type: TEXT
值类型：文本
Property Parameters: IANA, non-standard, alternate text representation, and language property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准、替代文本表示和语言属性参数。
Conformance: This property can be specified in "VEVENT" or "VTODO" calendar component.
一致性：此属性可以在“VEVENT”或“VTODO”日历组件中指定。
Description: Specific venues such as conference or meeting rooms may be explicitly specified using this property. An alternate representation may be specified that is a URI that points to directory information with more structured specification of the location. For example, the alternate representation may specify either an LDAP URL [RFC4516] pointing to an LDAP server entry or a CID URL [RFC2392] pointing to a MIME body part containing a Virtual-Information Card (vCard) [RFC2426] for the location.
说明：可使用此属性明确指定特定场所，如会议室或会议室。可以指定另一种表示形式，即URI，该URI指向具有更结构化的位置规范的目录信息。例如，替代表示可以指定指向LDAP服务器条目的LDAP URL[RFC4516]或指向包含用于该位置的虚拟信息卡（vCard）[RFC2426]的MIME主体部分的CID URL[RFC2392]。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
location = "LOCATION" locparam ":" text CRLF
location=“location”locparam:“文本CRLF”
locparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" altrepparam) / (";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
locparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" altrepparam) / (";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
Example: The following are some examples of this property:
示例：以下是此属性的一些示例：
LOCATION:Conference Room - F123\, Bldg. 002
地点：002栋123层会议室
LOCATION;ALTREP="http://xyzcorp.com/conf-rooms/f123.vcf":
Conference Room - F123\, Bldg. 002
LOCATION;ALTREP="http://xyzcorp.com/conf-rooms/f123.vcf":
Conference Room - F123\, Bldg. 002
Property Name: PERCENT-COMPLETE
属性名称：完成百分比
Purpose: This property is used by an assignee or delegatee of a to-do to convey the percent completion of a to-do to the "Organizer".
用途：此属性由待办事项的受让人或被授权人用于向“组织者”传达待办事项的完成百分比。
Value Type: INTEGER
值类型：整数
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property can be specified once in a "VTODO" calendar component.
一致性：此属性可以在“VTODO”日历组件中指定一次。
Description: The property value is a positive integer between 0 and 100. A value of "0" indicates the to-do has not yet been started. A value of "100" indicates that the to-do has been completed. Integer values in between indicate the percent partially complete.
说明：属性值是介于0和100之间的正整数。值“0”表示待办事项尚未启动。值“100”表示待办事项已完成。介于两者之间的整数值表示部分完成的百分比。
When a to-do is assigned to multiple individuals, the property value indicates the percent complete for that portion of the to-do assigned to the assignee or delegatee. For example, if a to-do is assigned to both individuals "A" and "B". A reply from "A" with a percent complete of "70" indicates that "A" has completed 70% of the to-do assigned to them. A reply from "B" with a percent complete of "50" indicates "B" has completed 50% of the to-do assigned to them.
当一个待办事项分配给多个人时，属性值表示分配给受让人或被委托人的那部分待办事项的完成百分比。例如，如果一个待办事项同时分配给个人“a”和“B”。完成百分比为“70”的“A”回复表示“A”已完成分配给他们的待办事项的70%。完成百分比为“50”的“B”回复表示“B”已完成分配给他们的待办事项的50%。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
percent = "PERCENT-COMPLETE" pctparam ":" integer CRLF
percent=“percent-COMPLETE”pctparam:“整数CRLF”
pctparam = *(";" other-param)
pctparam = *(";" other-param)
Example: The following is an example of this property to show 39% completion:
示例：以下是此属性的示例，显示完成率为39%：
PERCENT-COMPLETE:39
完成百分比：39
Property Name: PRIORITY
属性名称：优先级
Purpose: This property defines the relative priority for a calendar component.
用途：此属性定义日历组件的相对优先级。
Value Type: INTEGER
值类型：整数
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property can be specified in "VEVENT" and "VTODO" calendar components.
一致性：此属性可以在“VEVENT”和“VTODO”日历组件中指定。
Description: This priority is specified as an integer in the range 0 to 9. A value of 0 specifies an undefined priority. A value of 1 is the highest priority. A value of 2 is the second highest priority. Subsequent numbers specify a decreasing ordinal priority. A value of 9 is the lowest priority.
说明：此优先级指定为0到9范围内的整数。值0指定未定义的优先级。值1是最高优先级。值2是第二高优先级。后续数字指定递减的顺序优先级。值9是最低优先级。
A CUA with a three-level priority scheme of "HIGH", "MEDIUM", and "LOW" is mapped into this property such that a property value in the range of 1 to 4 specifies "HIGH" priority. A value of 5 is the normal or "MEDIUM" priority. A value in the range of 6 to 9 is "LOW" priority.
将具有“高”、“中”和“低”三级优先级方案的CUA映射到此属性中，以便1到4范围内的属性值指定“高”优先级。值5是正常或“中等”优先级。介于6到9之间的值为“低”优先级。
A CUA with a priority schema of "A1", "A2", "A3", "B1", "B2", ..., "C3" is mapped into this property such that a property value of 1 specifies "A1", a property value of 2 specifies "A2", a property value of 3 specifies "A3", and so forth up to a property value of 9 specifies "C3".
优先级模式为“A1”、“A2”、“A3”、“B1”、“B2”、…、“C3”的CUA映射到此属性中，使得属性值1指定“A1”，属性值2指定“A2”，属性值3指定“A3”，以此类推，直到属性值9指定“C3”。
Other integer values are reserved for future use.
其他整数值保留供将来使用。
Within a "VEVENT" calendar component, this property specifies a priority for the event. This property may be useful when more than one event is scheduled for a given time period.
在“VEVENT”日历组件中，此属性指定事件的优先级。在给定时间段内计划了多个事件时，此属性可能很有用。
Within a "VTODO" calendar component, this property specified a priority for the to-do. This property is useful in prioritizing multiple action items for a given time period.
在“VTODO”日历组件中，此属性为待办事项指定了优先级。此属性在为给定时间段的多个操作项设置优先级时非常有用。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
priority = "PRIORITY" prioparam ":" priovalue CRLF ;Default is zero (i.e., undefined).
priority=“priority”prioparam:“priovalue CRLF；默认值为零（即未定义）。
prioparam = *(";" other-param)
prioparam = *(";" other-param)
priovalue = integer ;Must be in the range [0..9] ; All other values are reserved for future use.
priovalue=整数；必须在[0..9]范围内；所有其他值保留供将来使用。
Example: The following is an example of a property with the highest priority:
示例：以下是具有最高优先级的属性示例：
PRIORITY:1
优先事项：1
The following is an example of a property with a next highest priority:
以下是具有次高优先级的属性示例：
PRIORITY:2
优先事项：2
The following is an example of a property with no priority. This is equivalent to not specifying the "PRIORITY" property:
以下是没有优先级的属性的示例。这相当于不指定“优先级”属性：
PRIORITY:0
优先级：0
Property Name: RESOURCES
属性名称：资源
Purpose: This property defines the equipment or resources anticipated for an activity specified by a calendar component.
用途：此属性定义日历组件指定的活动预期的设备或资源。
Value Type: TEXT
值类型：文本
Property Parameters: IANA, non-standard, alternate text representation, and language property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准、替代文本表示和语言属性参数。
Conformance: This property can be specified once in "VEVENT" or "VTODO" calendar component.
一致性：此属性可以在“VEVENT”或“VTODO”日历组件中指定一次。
Description: The property value is an arbitrary text. More than one resource can be specified as a COMMA-separated list of resources.
说明：属性值是任意文本。可以将多个资源指定为以逗号分隔的资源列表。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
resources = "RESOURCES" resrcparam ":" text *("," text) CRLF
resources = "RESOURCES" resrcparam ":" text *("," text) CRLF
resrcparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" altrepparam) / (";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
resrcparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" altrepparam) / (";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
Example: The following is an example of this property:
示例：以下是此属性的示例：
RESOURCES:EASEL,PROJECTOR,VCR
资源：画架、投影仪、录像机
RESOURCES;LANGUAGE=fr:Nettoyeur haute pression
RESOURCES;LANGUAGE=fr:Nettoyeur haute pression
Property Name: STATUS
属性名称：状态
Purpose: This property defines the overall status or confirmation for the calendar component.
用途：此属性定义日历组件的总体状态或确认。
Value Type: TEXT
值类型：文本
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property can be specified once in "VEVENT", "VTODO", or "VJOURNAL" calendar components.
一致性：此属性可以在“VEVENT”、“VTODO”或“VJOURNAL”日历组件中指定一次。
Description: In a group-scheduled calendar component, the property is used by the "Organizer" to provide a confirmation of the event to the "Attendees". For example in a "VEVENT" calendar component, the "Organizer" can indicate that a meeting is tentative, confirmed, or cancelled. In a "VTODO" calendar component, the "Organizer" can indicate that an action item needs action, is completed, is in process or being worked on, or has been cancelled. In a "VJOURNAL" calendar component, the "Organizer" can indicate that a journal entry is draft, final, or has been cancelled or removed.
描述：在组计划日历组件中，“组织者”使用该属性向“与会者”提供活动确认。例如，在“VEVENT”日历组件中，“组织者”可以表示会议是暂定的、已确认的或已取消的。在“VTODO”日历组件中，“组织者”可以指示某个操作项需要操作、已完成、正在处理或正在处理或已取消。在“VJOURNAL”日历组件中，“组织者”可以指示日记条目是草稿、最终日记条目或已被取消或删除。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
status = "STATUS" statparam ":" statvalue CRLF
status=“status”statparam:“statvalue CRLF”
statparam = *(";" other-param)
statparam = *(";" other-param)
statvalue = (statvalue-event
/ statvalue-todo
/ statvalue-jour)
statvalue = (statvalue-event
/ statvalue-todo
/ statvalue-jour)
statvalue-event = "TENTATIVE" ;Indicates event is tentative.
/ "CONFIRMED" ;Indicates event is definite.
/ "CANCELLED" ;Indicates event was cancelled.
;Status values for a "VEVENT"
statvalue-event = "TENTATIVE" ;Indicates event is tentative.
/ "CONFIRMED" ;Indicates event is definite.
/ "CANCELLED" ;Indicates event was cancelled.
;Status values for a "VEVENT"
statvalue-todo = "NEEDS-ACTION" ;Indicates to-do needs action.
/ "COMPLETED" ;Indicates to-do completed.
/ "IN-PROCESS" ;Indicates to-do in process of.
/ "CANCELLED" ;Indicates to-do was cancelled.
;Status values for "VTODO".
statvalue-todo = "NEEDS-ACTION" ;Indicates to-do needs action.
/ "COMPLETED" ;Indicates to-do completed.
/ "IN-PROCESS" ;Indicates to-do in process of.
/ "CANCELLED" ;Indicates to-do was cancelled.
;Status values for "VTODO".
statvalue-jour = "DRAFT" ;Indicates journal is draft. / "FINAL" ;Indicates journal is final. / "CANCELLED" ;Indicates journal is removed. ;Status values for "VJOURNAL".
statvalue jour=“草稿”；表示日记账是草稿。/“最终”；表示日记账是最终的。/“取消”；表示日志已删除；“VJOURNAL”的状态值。
Example: The following is an example of this property for a "VEVENT" calendar component:
示例：以下是“VEVENT”日历组件的此属性示例：
STATUS:TENTATIVE
现状：暂定
The following is an example of this property for a "VTODO" calendar component:
以下是“VTODO”日历组件的此属性示例：
STATUS:NEEDS-ACTION
现状：需要和行动
The following is an example of this property for a "VJOURNAL" calendar component:
以下是“VJOURNAL”日历组件的此属性示例：
STATUS:DRAFT
现状：草稿
Property Name: SUMMARY
物业名称：SUMMARY
Purpose: This property defines a short summary or subject for the calendar component.
用途：此属性定义日历组件的简短摘要或主题。
Value Type: TEXT
值类型：文本
Property Parameters: IANA, non-standard, alternate text representation, and language property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准、替代文本表示和语言属性参数。
Conformance: The property can be specified in "VEVENT", "VTODO", "VJOURNAL", or "VALARM" calendar components.
一致性：可以在“VEVENT”、“VTODO”、“VJOURNAL”或“VALARM”日历组件中指定该属性。
Description: This property is used in the "VEVENT", "VTODO", and "VJOURNAL" calendar components to capture a short, one-line summary about the activity or journal entry.
描述：此属性在“VEVENT”、“VTODO”和“VJORY”日历组件中用于捕获有关活动或日记条目的简短的单行摘要。
This property is used in the "VALARM" calendar component to capture the subject of an EMAIL category of alarm.
此属性在“VALARM”日历组件中用于捕获警报电子邮件类别的主题。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
summary = "SUMMARY" summparam ":" text CRLF
summary=“summary”summparam:“文本CRLF”
summparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" altrepparam) / (";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
summparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" altrepparam) / (";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
Example: The following is an example of this property:
示例：以下是此属性的示例：
SUMMARY:Department Party
小结：部门聚会
The following properties specify date and time related information in calendar components.
以下属性指定日历组件中与日期和时间相关的信息。
Property Name: COMPLETED
属性名称：已完成
Purpose: This property defines the date and time that a to-do was actually completed.
用途：此属性定义实际完成待办事项的日期和时间。
Value Type: DATE-TIME
值类型：日期时间
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: The property can be specified in a "VTODO" calendar component. The value MUST be specified as a date with UTC time.
一致性：可以在“VTODO”日历组件中指定该属性。该值必须指定为具有UTC时间的日期。
Description: This property defines the date and time that a to-do was actually completed.
描述：此属性定义实际完成待办事项的日期和时间。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
completed = "COMPLETED" compparam ":" date-time CRLF
completed=“completed”compparam:“日期时间CRLF”
compparam = *(";" other-param)
compparam = *(";" other-param)
Example: The following is an example of this property:
示例：以下是此属性的示例：
COMPLETED:19960401T150000Z
完成日期：19960401500MZ
Property Name: DTEND
属性名称：DTEND
Purpose: This property specifies the date and time that a calendar component ends.
用途：此属性指定日历组件结束的日期和时间。
Value Type: The default value type is DATE-TIME. The value type can be set to a DATE value type.
值类型：默认值类型为日期时间。值类型可以设置为日期值类型。
Property Parameters: IANA, non-standard, value data type, and time zone identifier property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准、值数据类型和时区标识符属性参数。
Conformance: This property can be specified in "VEVENT" or "VFREEBUSY" calendar components.
一致性：此属性可以在“VEVENT”或“VFREEBUSY”日历组件中指定。
Description: Within the "VEVENT" calendar component, this property defines the date and time by which the event ends. The value type of this property MUST be the same as the "DTSTART" property, and its value MUST be later in time than the value of the "DTSTART" property. Furthermore, this property MUST be specified as a date with local time if and only if the "DTSTART" property is also specified as a date with local time.
描述：在“VEVENT”日历组件中，此属性定义事件结束的日期和时间。此属性的值类型必须与“DTSTART”属性相同，并且其值的时间必须晚于“DTSTART”属性的值。此外，当且仅当“DTSTART”属性也指定为带有本地时间的日期时，此属性必须指定为带有本地时间的日期。
Within the "VFREEBUSY" calendar component, this property defines the end date and time for the free or busy time information. The time MUST be specified in the UTC time format. The value MUST be later in time than the value of the "DTSTART" property.
在“VFREEBUSY”日历组件中，此属性定义空闲或忙碌时间信息的结束日期和时间。必须以UTC时间格式指定时间。该值的时间必须晚于“DTSTART”属性的值。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
dtend = "DTEND" dtendparam ":" dtendval CRLF
dtend=“dtend”dtendparam:“dtendval CRLF”
dtendparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
(";" tzidparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
dtendparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
(";" tzidparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
dtendval = date-time / date ;Value MUST match value type
dtendval=日期时间/日期；值必须与值类型匹配
Example: The following is an example of this property:
示例：以下是此属性的示例：
DTEND:19960401T150000Z
数据终端：1996040150000Z
DTEND;VALUE=DATE:19980704
DTEND;VALUE=DATE:19980704
Property Name: DUE
物业名称：到期日
Purpose: This property defines the date and time that a to-do is expected to be completed.
用途：此属性定义预期完成待办事项的日期和时间。
Value Type: The default value type is DATE-TIME. The value type can be set to a DATE value type.
值类型：默认值类型为日期时间。值类型可以设置为日期值类型。
Property Parameters: IANA, non-standard, value data type, and time zone identifier property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准、值数据类型和时区标识符属性参数。
Conformance: The property can be specified once in a "VTODO" calendar component.
一致性：该属性可以在“VTODO”日历组件中指定一次。
Description: This property defines the date and time before which a to-do is expected to be completed. For cases where this property is specified in a "VTODO" calendar component that also specifies a "DTSTART" property, the value type of this property MUST be the same as the "DTSTART" property, and the value of this property
描述：此属性定义预期完成待办事项的日期和时间。对于在同时指定“DTSTART”属性的“VTODO”日历组件中指定此属性的情况，此属性的值类型必须与“DTSTART”属性相同，并且此属性的值
MUST be later in time than the value of the "DTSTART" property. Furthermore, this property MUST be specified as a date with local time if and only if the "DTSTART" property is also specified as a date with local time.
时间必须晚于“DTSTART”属性的值。此外，当且仅当“DTSTART”属性也指定为带有本地时间的日期时，此属性必须指定为带有本地时间的日期。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
due = "DUE" dueparam ":" dueval CRLF
due=“due”dueparam:“dueval CRLF”
dueparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
(";" tzidparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
dueparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
(";" tzidparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
dueval = date-time / date ;Value MUST match value type
dueval=日期时间/日期；值必须与值类型匹配
Example: The following is an example of this property:
示例：以下是此属性的示例：
DUE:19980430T000000Z
到期日：19980430T000000Z
Property Name: DTSTART
属性名称：DTSTART
Purpose: This property specifies when the calendar component begins.
用途：此属性指定日历组件开始的时间。
Value Type: The default value type is DATE-TIME. The time value MUST be one of the forms defined for the DATE-TIME value type. The value type can be set to a DATE value type.
值类型：默认值类型为日期时间。时间值必须是为日期-时间值类型定义的表单之一。值类型可以设置为日期值类型。
Property Parameters: IANA, non-standard, value data type, and time zone identifier property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准、值数据类型和时区标识符属性参数。
Conformance: This property can be specified once in the "VEVENT", "VTODO", or "VFREEBUSY" calendar components as well as in the
一致性：此属性可以在“VEVENT”、“VTODO”或“VFREEBUSY”日历组件以及中指定一次
"STANDARD" and "DAYLIGHT" sub-components. This property is REQUIRED in all types of recurring calendar components that specify the "RRULE" property. This property is also REQUIRED in "VEVENT" calendar components contained in iCalendar objects that don't specify the "METHOD" property.
“标准”和“日光”子组件。指定“RRULE”属性的所有类型的定期日历组件都需要此属性。在不指定“方法”属性的iCalendar对象中包含的“VEVENT”日历组件中，也需要此属性。
Description: Within the "VEVENT" calendar component, this property defines the start date and time for the event.
描述：在“VEVENT”日历组件中，此属性定义事件的开始日期和时间。
Within the "VFREEBUSY" calendar component, this property defines the start date and time for the free or busy time information. The time MUST be specified in UTC time.
在“VFREEBUSY”日历组件中，此属性定义空闲或繁忙时间信息的开始日期和时间。必须以UTC时间指定时间。
Within the "STANDARD" and "DAYLIGHT" sub-components, this property defines the effective start date and time for a time zone specification. This property is REQUIRED within each "STANDARD" and "DAYLIGHT" sub-components included in "VTIMEZONE" calendar components and MUST be specified as a date with local time without the "TZID" property parameter.
在“标准”和“日光”子组件中，此属性定义时区规范的有效开始日期和时间。“VTIMEZONE”日历组件中包含的每个“标准”和“日光”子组件都需要此属性，并且必须指定为带有本地时间的日期，而不带“TZID”属性参数。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
dtstart = "DTSTART" dtstparam ":" dtstval CRLF
dtstart=“dtstart”dtstparam:“dtstval CRLF”
dtstparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
(";" tzidparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
dtstparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
(";" tzidparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
dtstval = date-time / date ;Value MUST match value type
dtstval=日期时间/日期；值必须与值类型匹配
Example: The following is an example of this property:
示例：以下是此属性的示例：
DTSTART:19980118T073000Z
DTSTART:199801118T073000Z
Property Name: DURATION
属性名称：持续时间
Purpose: This property specifies a positive duration of time.
目的：此属性指定正的持续时间。
Value Type: DURATION
值类型：持续时间
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property can be specified in "VEVENT", "VTODO", or "VALARM" calendar components.
一致性：此属性可以在“VEVENT”、“VTODO”或“VALARM”日历组件中指定。
Description: In a "VEVENT" calendar component the property may be used to specify a duration of the event, instead of an explicit end DATE-TIME. In a "VTODO" calendar component the property may be used to specify a duration for the to-do, instead of an explicit due DATE-TIME. In a "VALARM" calendar component the property may be used to specify the delay period prior to repeating an alarm. When the "DURATION" property relates to a "DTSTART" property that is specified as a DATE value, then the "DURATION" property MUST be specified as a "dur-day" or "dur-week" value.
描述：在“VEVENT”日历组件中，该属性可用于指定事件的持续时间，而不是明确的结束日期时间。在“VTODO”日历组件中，该属性可用于指定待办事项的持续时间，而不是明确的截止日期时间。在“VALARM”日历组件中，该属性可用于指定重复报警之前的延迟时间。当“DURATION”属性与指定为日期值的“DTSTART”属性相关时，“DURATION”属性必须指定为“dur day”或“dur week”值。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
duration = "DURATION" durparam ":" dur-value CRLF ;consisting of a positive duration of time.
duration=“duration”durparam:“dur值CRLF；由正的持续时间组成。
durparam = *(";" other-param)
durparam = *(";" other-param)
Example: The following is an example of this property that specifies an interval of time of one hour and zero minutes and zero seconds:
示例：以下是此属性的一个示例，指定了一小时零分零秒的时间间隔：
DURATION:PT1H0M0S
持续时间：PT1H0M0S
The following is an example of this property that specifies an interval of time of 15 minutes.
以下是此属性的示例，指定了15分钟的时间间隔。
DURATION:PT15M
持续时间：15分钟
Property Name: FREEBUSY
属性名称：FREEBUSY
Purpose: This property defines one or more free or busy time intervals.
用途：此属性定义一个或多个忙/闲时间间隔。
Value Type: PERIOD
值类型：期间
Property Parameters: IANA, non-standard, and free/busy time type property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准和忙/闲时间类型的属性参数。
Conformance: The property can be specified in a "VFREEBUSY" calendar component.
一致性：可以在“VFREEBUSY”日历组件中指定该属性。
Description: These time periods can be specified as either a start and end DATE-TIME or a start DATE-TIME and DURATION. The date and time MUST be a UTC time format.
描述：这些时间段可以指定为开始和结束日期时间或开始日期时间和持续时间。日期和时间必须是UTC时间格式。
"FREEBUSY" properties within the "VFREEBUSY" calendar component SHOULD be sorted in ascending order, based on start time and then end time, with the earliest periods first.
“VFREEBUSY”日历组件中的“FREEBUSY”属性应根据开始时间和结束时间按升序排序，最早的时段排在第一位。
The "FREEBUSY" property can specify more than one value, separated by the COMMA character. In such cases, the "FREEBUSY" property values MUST all be of the same "FBTYPE" property parameter type (e.g., all values of a particular "FBTYPE" listed together in a single property).
“FREEBUSY”属性可以指定多个值，用逗号分隔。在这种情况下，“FREEBUSY”属性值必须全部为相同的“FBTYPE”属性参数类型（例如，在单个属性中列出的特定“FBTYPE”的所有值）。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
freebusy = "FREEBUSY" fbparam ":" fbvalue CRLF
freebusy=“freebusy”fbparam:“fbvalue CRLF”
fbparam = *(
;
; The following is OPTIONAL,
; but MUST NOT occur more than once.
;
(";" fbtypeparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
fbparam = *(
;
; The following is OPTIONAL,
; but MUST NOT occur more than once.
;
(";" fbtypeparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
fbvalue = period *("," period) ;Time value MUST be in the UTC time format.
fbvalue=周期*（“，”周期）；时间值必须采用UTC时间格式。
Example: The following are some examples of this property:
示例：以下是此属性的一些示例：
FREEBUSY;FBTYPE=BUSY-UNAVAILABLE:19970308T160000Z/PT8H30M
FREEBUSY;FBTYPE=BUSY-UNAVAILABLE:19970308T160000Z/PT8H30M
FREEBUSY;FBTYPE=FREE:19970308T160000Z/PT3H,19970308T200000Z/PT1H
FREEBUSY;FBTYPE=FREE:19970308T160000Z/PT3H,19970308T200000Z/PT1H
FREEBUSY;FBTYPE=FREE:19970308T160000Z/PT3H,19970308T200000Z/PT1H
,19970308T230000Z/19970309T000000Z
FREEBUSY;FBTYPE=FREE:19970308T160000Z/PT3H,19970308T200000Z/PT1H
,19970308T230000Z/19970309T000000Z
Property Name: TRANSP
物业名称：TRANSP
Purpose: This property defines whether or not an event is transparent to busy time searches.
目的：此属性定义事件对繁忙时间搜索是否透明。
Value Type: TEXT
值类型：文本
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property can be specified once in a "VEVENT" calendar component.
一致性：此属性可以在“VEVENT”日历组件中指定一次。
Description: Time Transparency is the characteristic of an event that determines whether it appears to consume time on a calendar. Events that consume actual time for the individual or resource associated with the calendar SHOULD be recorded as OPAQUE, allowing them to be detected by free/busy time searches. Other events, which do not take up the individual's (or resource's) time SHOULD be recorded as TRANSPARENT, making them invisible to free/ busy time searches.
描述：时间透明度是事件的特征，它决定事件是否在日历上消耗时间。消耗与日历相关的个人或资源的实际时间的事件应记录为不透明，允许空闲/忙碌时间搜索检测到它们。其他不占用个人（或资源）时间的事件应记录为透明，使其对忙/闲时间搜索不可见。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
transp = "TRANSP" transparam ":" transvalue CRLF
transp=“transp”transparam:“transvalue CRLF”
transparam = *(";" other-param)
transparam = *(";" other-param)
transvalue = "OPAQUE"
;Blocks or opaque on busy time searches.
/ "TRANSPARENT"
;Transparent on busy time searches.
;Default value is OPAQUE
transvalue = "OPAQUE"
;Blocks or opaque on busy time searches.
/ "TRANSPARENT"
;Transparent on busy time searches.
;Default value is OPAQUE
Example: The following is an example of this property for an event that is transparent or does not block on free/busy time searches:
示例：以下是透明事件或不阻止忙/闲搜索的事件的此属性示例：
TRANSP:TRANSPARENT
传输：透明
The following is an example of this property for an event that is opaque or blocks on free/busy time searches:
以下是不透明事件或在忙/闲时间搜索时阻塞事件的此属性示例：
TRANSP:OPAQUE
运输：不透明
The following properties specify time zone information in calendar components.
以下属性指定日历组件中的时区信息。
Property Name: TZID
属性名称：TZID
Purpose: This property specifies the text value that uniquely identifies the "VTIMEZONE" calendar component in the scope of an iCalendar object.
用途：此属性指定唯一标识iCalendar对象范围内“VTIMEZONE”日历组件的文本值。
Value Type: TEXT
值类型：文本
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property MUST be specified in a "VTIMEZONE" calendar component.
一致性：必须在“VTIMEZONE”日历组件中指定此属性。
Description: This is the label by which a time zone calendar component is referenced by any iCalendar properties whose value type is either DATE-TIME or TIME and not intended to specify a UTC or a "floating" time. The presence of the SOLIDUS character as a prefix, indicates that this "TZID" represents an unique ID in a globally defined time zone registry (when such registry is defined).
描述：这是任何iCalendar属性引用时区日历组件的标签，iCalendar属性的值类型为日期-时间或时间，不用于指定UTC或“浮动”时间。SOLIDUS字符作为前缀的存在表示此“TZID”表示全局定义的时区注册表中的唯一ID（定义此类注册表时）。
Note: This document does not define a naming convention for time zone identifiers. Implementers may want to use the naming conventions defined in existing time zone specifications such as the public-domain TZ database [TZDB]. The specification of globally unique time zone identifiers is not addressed by this document and is left for future study.
注意：本文档未定义时区标识符的命名约定。实现者可能希望使用现有时区规范（如公共域TZ数据库[TZDB]）中定义的命名约定。本文件未涉及全局唯一时区标识符的规范，留待将来研究。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
tzid = "TZID" tzidpropparam ":" [tzidprefix] text CRLF
tzid=“tzid”tzidropparam”：“[tzidrefix]文本CRLF
tzidpropparam = *(";" other-param)
tzidpropparam = *(";" other-param)
;tzidprefix = "/" ; Defined previously. Just listed here for reader convenience.
;tzidrefix=“/”；以前定义过。为了方便读者，这里列出了。
Example: The following are examples of non-globally unique time zone identifiers:
示例：以下是非全局唯一时区标识符的示例：
TZID:America/New_York
TZID:美国/纽约
TZID:America/Los_Angeles
TZID:美国/洛杉矶
The following is an example of a fictitious globally unique time zone identifier:
以下是虚构的全局唯一时区标识符的示例：
TZID:/example.org/America/New_York
TZID:/example.org/America/New_York
Property Name: TZNAME
属性名称：TZNAME
Purpose: This property specifies the customary designation for a time zone description.
用途：此属性指定时区描述的惯用名称。
Value Type: TEXT
值类型：文本
Property Parameters: IANA, non-standard, and language property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准和语言属性参数。
Conformance: This property can be specified in "STANDARD" and "DAYLIGHT" sub-components.
一致性：该属性可在“标准”和“日光”子组件中指定。
Description: This property specifies a customary name that can be used when displaying dates that occur during the observance defined by the time zone sub-component.
描述：此属性指定一个习惯名称，当显示时区子组件定义的遵守期间发生的日期时，可以使用该名称。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
tzname = "TZNAME" tznparam ":" text CRLF
tzname=“tzname”tznparam:“文本CRLF”
tznparam = *(
;
; The following is OPTIONAL,
; but MUST NOT occur more than once.
;
(";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
tznparam = *(
;
; The following is OPTIONAL,
; but MUST NOT occur more than once.
;
(";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
Example: The following are examples of this property:
示例：以下是此属性的示例：
TZNAME:EST
名称：EST
TZNAME;LANGUAGE=fr-CA:HNE
TZNAME;LANGUAGE=fr-CA:HNE
Property Name: TZOFFSETFROM
属性名称：TZOFFSETFROM
Purpose: This property specifies the offset that is in use prior to this time zone observance.
用途：此属性指定在此时区之前正在使用的偏移量。
Value Type: UTC-OFFSET
值类型：UTC-OFFSET
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property MUST be specified in "STANDARD" and "DAYLIGHT" sub-components.
一致性：必须在“标准”和“日光”子组件中指定该特性。
Description: This property specifies the offset that is in use prior to this time observance. It is used to calculate the absolute time at which the transition to a given observance takes place. This property MUST only be specified in a "VTIMEZONE" calendar component. A "VTIMEZONE" calendar component MUST include this property. The property value is a signed numeric indicating the number of hours and possibly minutes from UTC. Positive numbers represent time zones east of the prime meridian, or ahead of UTC. Negative numbers represent time zones west of the prime meridian, or behind UTC.
描述：此属性指定在此时间之前正在使用的偏移量。它用于计算过渡到给定观测的绝对时间。只能在“VTIMEZONE”日历组件中指定此属性。“VTIMEZONE”日历组件必须包含此属性。属性值是一个有符号的数字，指示距UTC的小时数，可能还有分钟数。正数表示本初子午线以东或UTC之前的时区。负数表示本初子午线以西或UTC之后的时区。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
tzoffsetfrom = "TZOFFSETFROM" frmparam ":" utc-offset CRLF
tzoffsetfrom=“tzoffsetfrom”frmparam:“utc偏移CRLF
frmparam = *(";" other-param)
frmparam = *(";" other-param)
Example: The following are examples of this property:
示例：以下是此属性的示例：
TZOFFSETFROM:-0500
TZOFFSETFROM:-0500
TZOFFSETFROM:+1345
TZOFFSETFROM:+1345
Property Name: TZOFFSETTO
物业名称：Tzoffetto
Purpose: This property specifies the offset that is in use in this time zone observance.
用途：此属性指定在此时区中使用的偏移量。
Value Type: UTC-OFFSET
值类型：UTC-OFFSET
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property MUST be specified in "STANDARD" and "DAYLIGHT" sub-components.
一致性：必须在“标准”和“日光”子组件中指定该特性。
Description: This property specifies the offset that is in use in this time zone observance. It is used to calculate the absolute time for the new observance. The property value is a signed numeric indicating the number of hours and possibly minutes from UTC. Positive numbers represent time zones east of the prime meridian, or ahead of UTC. Negative numbers represent time zones west of the prime meridian, or behind UTC.
描述：此属性指定在此时区中使用的偏移量。它用于计算新活动的绝对时间。属性值是一个有符号的数字，指示距UTC的小时数，可能还有分钟数。正数表示本初子午线以东或UTC之前的时区。负数表示本初子午线以西或UTC之后的时区。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
tzoffsetto = "TZOFFSETTO" toparam ":" utc-offset CRLF
tzoffetto=“tzoffetto”toparam”：“utc偏移CRLF
toparam = *(";" other-param)
toparam = *(";" other-param)
Example: The following are examples of this property:
示例：以下是此属性的示例：
TZOFFSETTO:-0400
佐菲托：-0400
TZOFFSETTO:+1245
佐夫塞托：+1245
Property Name: TZURL
属性名称：TZURL
Purpose: This property provides a means for a "VTIMEZONE" component to point to a network location that can be used to retrieve an up-to-date version of itself.
用途：此属性为“VTIMEZONE”组件提供指向网络位置的方法，该位置可用于检索其自身的最新版本。
Value Type: URI
值类型：URI
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property can be specified in a "VTIMEZONE" calendar component.
一致性：可以在“VTIMEZONE”日历组件中指定此属性。
Description: This property provides a means for a "VTIMEZONE" component to point to a network location that can be used to retrieve an up-to-date version of itself. This provides a hook to handle changes government bodies impose upon time zone definitions. Retrieval of this resource results in an iCalendar object containing a single "VTIMEZONE" component and a "METHOD" property set to PUBLISH.
描述：此属性为“VTIMEZONE”组件提供指向网络位置的方法，该网络位置可用于检索其自身的最新版本。这提供了一个钩子来处理政府机构强加给时区定义的变化。检索此资源会生成一个iCalendar对象，该对象包含一个“VTIMEZONE”组件和一个要发布的“METHOD”属性集。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
tzurl = "TZURL" tzurlparam ":" uri CRLF
tzurl=“tzurl”tzurlparam”：“uri CRLF”
tzurlparam = *(";" other-param)
tzurlparam = *(";" other-param)
Example: The following is an example of this property:
示例：以下是此属性的示例：
TZURL:http://timezones.example.org/tz/America-Los_Angeles.ics
TZURL:http://timezones.example.org/tz/America-Los_Angeles.ics
The following properties specify relationship information in calendar components.
以下属性指定日历组件中的关系信息。
Property Name: ATTENDEE
属性名称：ATTENDEE
Purpose: This property defines an "Attendee" within a calendar component.
用途：此属性定义日历组件中的“与会者”。
Value Type: CAL-ADDRESS
值类型：CAL-ADDRESS
Property Parameters: IANA, non-standard, language, calendar user type, group or list membership, participation role, participation status, RSVP expectation, delegatee, delegator, sent by, common name, or directory entry reference property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准、语言、日历用户类型、组或列表成员资格、参与角色、参与状态、RSVP期望值、被授权人、被授权人、发送人、公用名或目录条目引用属性参数。
Conformance: This property MUST be specified in an iCalendar object that specifies a group-scheduled calendar entity. This property MUST NOT be specified in an iCalendar object when publishing the calendar information (e.g., NOT in an iCalendar object that specifies the publication of a calendar user's busy time, event, to-do, or journal). This property is not specified in an iCalendar object that specifies only a time zone definition or that defines calendar components that are not group-scheduled components, but are components only on a single user's calendar.
一致性：必须在指定组计划日历实体的iCalendar对象中指定此属性。发布日历信息时，不得在iCalendar对象中指定此属性（例如，不得在iCalendar对象中指定日历用户的繁忙时间、事件、待办事项或日记的发布）。在仅指定时区定义的iCalendar对象中，或在定义非组计划组件但仅在单个用户日历上的组件的日历组件中，未指定此属性。
Description: This property MUST only be specified within calendar components to specify participants, non-participants, and the chair of a group-scheduled calendar entity. The property is specified within an "EMAIL" category of the "VALARM" calendar component to specify an email address that is to receive the email type of iCalendar alarm.
描述：此属性只能在日历组件中指定，以指定参与者、非参与者和组计划日历实体的主席。该属性在“VALARM”日历组件的“电子邮件”类别中指定，以指定接收iCalendar警报电子邮件类型的电子邮件地址。
The property parameter "CN" is for the common or displayable name
associated with the calendar address; "ROLE", for the intended
role that the attendee will have in the calendar component;
"PARTSTAT", for the status of the attendee's participation;
"RSVP", for indicating whether the favor of a reply is requested;
"CUTYPE", to indicate the type of calendar user; "MEMBER", to
indicate the groups that the attendee belongs to; "DELEGATED-TO",
to indicate the calendar users that the original request was
delegated to; and "DELEGATED-FROM", to indicate whom the request
was delegated from; "SENT-BY", to indicate whom is acting on
behalf of the "ATTENDEE"; and "DIR", to indicate the URI that
points to the directory information corresponding to the attendee.
These property parameters can be specified on an "ATTENDEE"
property in either a "VEVENT", "VTODO", or "VJOURNAL" calendar
component. They MUST NOT be specified in an "ATTENDEE" property
in a "VFREEBUSY" or "VALARM" calendar component. If the
The property parameter "CN" is for the common or displayable name
associated with the calendar address; "ROLE", for the intended
role that the attendee will have in the calendar component;
"PARTSTAT", for the status of the attendee's participation;
"RSVP", for indicating whether the favor of a reply is requested;
"CUTYPE", to indicate the type of calendar user; "MEMBER", to
indicate the groups that the attendee belongs to; "DELEGATED-TO",
to indicate the calendar users that the original request was
delegated to; and "DELEGATED-FROM", to indicate whom the request
was delegated from; "SENT-BY", to indicate whom is acting on
behalf of the "ATTENDEE"; and "DIR", to indicate the URI that
points to the directory information corresponding to the attendee.
These property parameters can be specified on an "ATTENDEE"
property in either a "VEVENT", "VTODO", or "VJOURNAL" calendar
component. They MUST NOT be specified in an "ATTENDEE" property
in a "VFREEBUSY" or "VALARM" calendar component. If the
"LANGUAGE" property parameter is specified, the identified language applies to the "CN" parameter.
如果指定了“LANGUAGE”属性参数，则标识的语言将应用于“CN”参数。
A recipient delegated a request MUST inherit the "RSVP" and "ROLE" values from the attendee that delegated the request to them.
委派请求的收件人必须从委派请求的与会者处继承“RSVP”和“角色”值。
Multiple attendees can be specified by including multiple "ATTENDEE" properties within the calendar component.
通过在日历组件中包含多个“与会者”属性，可以指定多个与会者。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
attendee = "ATTENDEE" attparam ":" cal-address CRLF
attendee=“attendee”attparam:“cal地址CRLF”
attparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" cutypeparam) / (";" memberparam) /
(";" roleparam) / (";" partstatparam) /
(";" rsvpparam) / (";" deltoparam) /
(";" delfromparam) / (";" sentbyparam) /
(";" cnparam) / (";" dirparam) /
(";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
attparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" cutypeparam) / (";" memberparam) /
(";" roleparam) / (";" partstatparam) /
(";" rsvpparam) / (";" deltoparam) /
(";" delfromparam) / (";" sentbyparam) /
(";" cnparam) / (";" dirparam) /
(";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
Example: The following are examples of this property's use for a to-do:
示例：以下是此属性用于待办事项的示例：
ATTENDEE;MEMBER="mailto:DEV-GROUP@example.com":
mailto:joecool@example.com
ATTENDEE;DELEGATED-FROM="mailto:immud@example.com":
mailto:ildoit@example.com
ATTENDEE;MEMBER="mailto:DEV-GROUP@example.com":
mailto:joecool@example.com
ATTENDEE;DELEGATED-FROM="mailto:immud@example.com":
mailto:ildoit@example.com
The following is an example of this property used for specifying multiple attendees to an event:
以下是用于指定活动的多个参与者的此属性的示例：
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;CN=Henry
Cabot:mailto:hcabot@example.com
ATTENDEE;ROLE=REQ-PARTICIPANT;DELEGATED-FROM="mailto:bob@
example.com";PARTSTAT=ACCEPTED;CN=Jane Doe:mailto:jdoe@
example.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;CN=Henry
Cabot:mailto:hcabot@example.com
ATTENDEE;ROLE=REQ-PARTICIPANT;DELEGATED-FROM="mailto:bob@
example.com";PARTSTAT=ACCEPTED;CN=Jane Doe:mailto:jdoe@
example.com
The following is an example of this property with a URI to the directory information associated with the attendee:
以下是此属性的示例，其中包含与与会者关联的目录信息的URI：
ATTENDEE;CN=John Smith;DIR="ldap://example.com:6666/o=ABC%
20Industries,c=US???(cn=Jim%20Dolittle)":mailto:jimdo@
example.com
ATTENDEE;CN=John Smith;DIR="ldap://example.com:6666/o=ABC%
20Industries,c=US???(cn=Jim%20Dolittle)":mailto:jimdo@
example.com
The following is an example of this property with "delegatee" and "delegator" information for an event:
以下是此属性的示例，其中包含事件的“被授权人”和“被授权人”信息：
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;DELEGATED-FROM=
"mailto:iamboss@example.com";CN=Henry Cabot:mailto:hcabot@
example.com
ATTENDEE;ROLE=NON-PARTICIPANT;PARTSTAT=DELEGATED;DELEGATED-TO=
"mailto:hcabot@example.com";CN=The Big Cheese:mailto:iamboss
@example.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=Jane Doe
:mailto:jdoe@example.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;DELEGATED-FROM=
"mailto:iamboss@example.com";CN=Henry Cabot:mailto:hcabot@
example.com
ATTENDEE;ROLE=NON-PARTICIPANT;PARTSTAT=DELEGATED;DELEGATED-TO=
"mailto:hcabot@example.com";CN=The Big Cheese:mailto:iamboss
@example.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=Jane Doe
:mailto:jdoe@example.com
Example: The following is an example of this property's use when another calendar user is acting on behalf of the "Attendee":
示例：以下是另一个日历用户代表“与会者”行事时此属性的使用示例：
ATTENDEE;SENT-BY=mailto:jan_doe@example.com;CN=John Smith:
mailto:jsmith@example.com
ATTENDEE;SENT-BY=mailto:jan_doe@example.com;CN=John Smith:
mailto:jsmith@example.com
Property Name: CONTACT
属性名称：联系人
Purpose: This property is used to represent contact information or alternately a reference to contact information associated with the calendar component.
用途：此属性用于表示联系人信息，或者表示对与日历组件关联的联系人信息的引用。
Value Type: TEXT
值类型：文本
Property Parameters: IANA, non-standard, alternate text representation, and language property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准、替代文本表示和语言属性参数。
Conformance: This property can be specified in a "VEVENT", "VTODO", "VJOURNAL", or "VFREEBUSY" calendar component.
一致性：可以在“VEVENT”、“VTODO”、“VJOURNAL”或“VFREEBUSY”日历组件中指定此属性。
Description: The property value consists of textual contact information. An alternative representation for the property value can also be specified that refers to a URI pointing to an alternate form, such as a vCard [RFC2426], for the contact information.
描述：属性值由文本联系信息组成。还可以指定属性值的替代表示形式，该表示形式引用指向联系信息的替代形式（例如vCard[RFC2426]）的URI。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
contact = "CONTACT" contparam ":" text CRLF
contact=“contact”contparam:“文本CRLF”
contparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" altrepparam) / (";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
contparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" altrepparam) / (";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
Example: The following is an example of this property referencing textual contact information:
示例：以下是引用文本联系信息的此属性的示例：
CONTACT:Jim Dolittle\, ABC Industries\, +1-919-555-1234
联系人：吉姆·多利特尔\，ABC工业\，+1-919-555-1234
The following is an example of this property with an alternate representation of an LDAP URI to a directory entry containing the contact information:
以下是此属性的一个示例，其中LDAP URI的另一种表示形式是包含联系人信息的目录条目：
CONTACT;ALTREP="ldap://example.com:6666/o=ABC%20Industries\,
c=US???(cn=Jim%20Dolittle)":Jim Dolittle\, ABC Industries\,
+1-919-555-1234
CONTACT;ALTREP="ldap://example.com:6666/o=ABC%20Industries\,
c=US???(cn=Jim%20Dolittle)":Jim Dolittle\, ABC Industries\,
+1-919-555-1234
The following is an example of this property with an alternate representation of a MIME body part containing the contact information, such as a vCard [RFC2426] embedded in a text/ directory media type [RFC2425]:
以下是此属性的示例，其中包含联系人信息的MIME正文部分的替代表示形式，例如嵌入文本/目录媒体类型[RFC2425]中的vCard[RFC2426]：
CONTACT;ALTREP="CID:part3.msg970930T083000SILVER@example.com":
Jim Dolittle\, ABC Industries\, +1-919-555-1234
CONTACT;ALTREP="CID:part3.msg970930T083000SILVER@example.com":
Jim Dolittle\, ABC Industries\, +1-919-555-1234
The following is an example of this property referencing a network resource, such as a vCard [RFC2426] object containing the contact information:
以下是引用网络资源的此属性的示例，例如包含联系人信息的vCard[RFC2426]对象：
CONTACT;ALTREP="http://example.com/pdi/jdoe.vcf":Jim
Dolittle\, ABC Industries\, +1-919-555-1234
CONTACT;ALTREP="http://example.com/pdi/jdoe.vcf":Jim
Dolittle\, ABC Industries\, +1-919-555-1234
Property Name: ORGANIZER
物业名称：组织者
Purpose: This property defines the organizer for a calendar component.
用途：此属性定义日历组件的组织者。
Value Type: CAL-ADDRESS
值类型：CAL-ADDRESS
Property Parameters: IANA, non-standard, language, common name, directory entry reference, and sent-by property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准、语言、公用名、目录条目引用和发送方式属性参数。
Conformance: This property MUST be specified in an iCalendar object that specifies a group-scheduled calendar entity. This property MUST be specified in an iCalendar object that specifies the publication of a calendar user's busy time. This property MUST NOT be specified in an iCalendar object that specifies only a time zone definition or that defines calendar components that are not group-scheduled components, but are components only on a single user's calendar.
一致性：必须在指定组计划日历实体的iCalendar对象中指定此属性。必须在指定日历用户繁忙时间发布的iCalendar对象中指定此属性。不得在仅指定时区定义的iCalendar对象中指定此属性，也不得在定义非组计划组件但仅在单个用户日历上的日历组件的iCalendar对象中指定此属性。
Description: This property is specified within the "VEVENT", "VTODO", and "VJOURNAL" calendar components to specify the organizer of a group-scheduled calendar entity. The property is specified within the "VFREEBUSY" calendar component to specify the calendar user requesting the free or busy time. When publishing a "VFREEBUSY" calendar component, the property is used to specify the calendar that the published busy time came from.
描述：此属性在“VEVENT”、“VTODO”和“VJORY”日历组件中指定，以指定组计划日历实体的组织者。该属性在“vfreebush”日历组件中指定，以指定请求空闲或繁忙时间的日历用户。发布“VFREEBUSY”日历组件时，该属性用于指定发布的繁忙时间来自的日历。
The property has the property parameters "CN", for specifying the common or display name associated with the "Organizer", "DIR", for specifying a pointer to the directory information associated with the "Organizer", "SENT-BY", for specifying another calendar user that is acting on behalf of the "Organizer". The non-standard parameters may also be specified on this property. If the "LANGUAGE" property parameter is specified, the identified language applies to the "CN" parameter value.
该属性具有属性参数“CN”，用于指定与“组织者”、“目录”关联的公共或显示名称，用于指定指向与“组织者”、“发送人”关联的目录信息的指针，用于指定代表“组织者”行事的另一个日历用户。也可以在此属性上指定非标准参数。如果指定了“LANGUAGE”属性参数，则标识的语言将应用于“CN”参数值。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
organizer = "ORGANIZER" orgparam ":" cal-address CRLF
organizer=“orgparam”：“cal地址CRLF”
orgparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" cnparam) / (";" dirparam) / (";" sentbyparam) /
(";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
orgparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" cnparam) / (";" dirparam) / (";" sentbyparam) /
(";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
Example: The following is an example of this property:
示例：以下是此属性的示例：
ORGANIZER;CN=John Smith:mailto:jsmith@example.com
ORGANIZER;CN=John Smith:mailto:jsmith@example.com
The following is an example of this property with a pointer to the directory information associated with the organizer:
以下是此属性的示例，其中包含指向与组织者关联的目录信息的指针：
ORGANIZER;CN=JohnSmith;DIR="ldap://example.com:6666/o=DC%20Ass
ociates,c=US???(cn=John%20Smith)":mailto:jsmith@example.com
ORGANIZER;CN=JohnSmith;DIR="ldap://example.com:6666/o=DC%20Ass
ociates,c=US???(cn=John%20Smith)":mailto:jsmith@example.com
The following is an example of this property used by another calendar user who is acting on behalf of the organizer, with responses intended to be sent back to the organizer, not the other calendar user:
以下是代表组织者的其他日历用户使用的此属性的示例，其响应将发送回组织者，而不是其他日历用户：
ORGANIZER;SENT-BY="mailto:jane_doe@example.com":
mailto:jsmith@example.com
ORGANIZER;SENT-BY="mailto:jane_doe@example.com":
mailto:jsmith@example.com
Property Name: RECURRENCE-ID
属性名称：RECURRENCE-ID
Purpose: This property is used in conjunction with the "UID" and "SEQUENCE" properties to identify a specific instance of a recurring "VEVENT", "VTODO", or "VJOURNAL" calendar component. The property value is the original value of the "DTSTART" property of the recurrence instance.
用途：此属性与“UID”和“SEQUENCE”属性一起使用，以标识重复出现的“VEVENT”、“VTODO”或“VJOURNAL”日历组件的特定实例。属性值是递归实例的“DTSTART”属性的原始值。
Value Type: The default value type is DATE-TIME. The value type can be set to a DATE value type. This property MUST have the same value type as the "DTSTART" property contained within the recurring component. Furthermore, this property MUST be specified as a date with local time if and only if the "DTSTART" property contained within the recurring component is specified as a date with local time.
值类型：默认值类型为日期时间。值类型可以设置为日期值类型。此属性必须与定期组件中包含的“DTSTART”属性具有相同的值类型。此外，当且仅当周期性组件中包含的“DTSTART”属性被指定为具有本地时间的日期时，必须将此属性指定为具有本地时间的日期。
Property Parameters: IANA, non-standard, value data type, time zone identifier, and recurrence identifier range parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准、值数据类型、时区标识符和重复标识符范围参数。
Conformance: This property can be specified in an iCalendar object containing a recurring calendar component.
一致性：可以在包含定期日历组件的iCalendar对象中指定此属性。
Description: The full range of calendar components specified by a recurrence set is referenced by referring to just the "UID" property value corresponding to the calendar component. The "RECURRENCE-ID" property allows the reference to an individual instance within the recurrence set.
描述：通过仅引用与日历组件对应的“UID”属性值来引用定期集指定的全部日历组件。“RECURRENCE-ID”属性允许引用重复集中的单个实例。
If the value of the "DTSTART" property is a DATE type value, then the value MUST be the calendar date for the recurrence instance.
如果“DTSTART”属性的值是日期类型的值，则该值必须是定期实例的日历日期。
The DATE-TIME value is set to the time when the original recurrence instance would occur; meaning that if the intent is to change a Friday meeting to Thursday, the DATE-TIME is still set to the original Friday meeting.
日期时间值设置为原始重复实例发生的时间；这意味着，如果打算将周五会议更改为周四，则日期时间仍然设置为原始的周五会议。
The "RECURRENCE-ID" property is used in conjunction with the "UID" and "SEQUENCE" properties to identify a particular instance of a recurring event, to-do, or journal. For a given pair of "UID" and "SEQUENCE" property values, the "RECURRENCE-ID" value for a recurrence instance is fixed.
“RECURRENCE-ID”属性与“UID”和“SEQUENCE”属性一起使用，以标识定期事件、待办事项或日志的特定实例。对于给定的一对“UID”和“SEQUENCE”属性值，递归实例的“RECURRENCE-ID”值是固定的。
The "RANGE" parameter is used to specify the effective range of recurrence instances from the instance specified by the "RECURRENCE-ID" property value. The value for the range parameter can only be "THISANDFUTURE" to indicate a range defined by the given recurrence instance and all subsequent instances. Subsequent instances are determined by their "RECURRENCE-ID" value and not their current scheduled start time. Subsequent instances defined in separate components are not impacted by the given recurrence instance. When the given recurrence instance is rescheduled, all subsequent instances are also rescheduled by the same time difference. For instance, if the given recurrence instance is rescheduled to start 2 hours later, then all subsequent instances are also rescheduled 2 hours later.
“RANGE”参数用于从“recurrence-ID”属性值指定的实例指定重复实例的有效范围。range参数的值只能是“THISANDFUTURE”，以指示由给定重复实例和所有后续实例定义的范围。后续实例由其“RECURRENCE-ID”值决定，而不是由其当前计划的开始时间决定。在单独组件中定义的后续实例不受给定重复实例的影响。当重新调度给定的重复实例时，所有后续实例也会按相同的时差重新调度。例如，如果将给定的重复实例重新调度为2小时后开始，则所有后续实例也将在2小时后重新调度。
Similarly, if the duration of the given recurrence instance is modified, then all subsequence instances are also modified to have this same duration.
类似地，如果修改了给定重复实例的持续时间，则所有子序列实例也会修改为具有相同的持续时间。
Note: The "RANGE" parameter may not be appropriate to reschedule specific subsequent instances of complex recurring calendar component. Assuming an unbounded recurring calendar component scheduled to occur on Mondays and Wednesdays, the "RANGE" parameter could not be used to reschedule only the future Monday instances to occur on Tuesday instead. In such cases, the calendar application could simply truncate the unbounded recurring calendar component (i.e., with the "COUNT" or "UNTIL" rule parts), and create two new unbounded recurring calendar components for the future instances.
注意：“范围”参数可能不适用于重新安排复杂定期日历组件的特定后续实例。假设计划在星期一和星期三发生的无边界定期日历组件，“范围”参数不能用于仅将未来的星期一实例重新计划在星期二发生。在这种情况下，日历应用程序可以简单地截断无限周期日历组件（即，使用“计数”或“直到”规则部分），并为将来的实例创建两个新的无限周期日历组件。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
recurid = "RECURRENCE-ID" ridparam ":" ridval CRLF
recurid=“RECURRENCE-ID”ridparam:“ridval CRLF”
ridparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
(";" tzidparam) / (";" rangeparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
ridparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
(";" tzidparam) / (";" rangeparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
ridval = date-time / date ;Value MUST match value type
ridval=日期时间/日期；值必须与值类型匹配
Example: The following are examples of this property:
示例：以下是此属性的示例：
RECURRENCE-ID;VALUE=DATE:19960401
RECURRENCE-ID;VALUE=DATE:19960401
RECURRENCE-ID;RANGE=THISANDFUTURE:19960120T120000Z
RECURRENCE-ID;RANGE=THISANDFUTURE:19960120T120000Z
Property Name: RELATED-TO
属性名称：关联到
Purpose: This property is used to represent a relationship or reference between one calendar component and another.
用途：此属性用于表示一个日历组件和另一个日历组件之间的关系或引用。
Value Type: TEXT
值类型：文本
Property Parameters: IANA, non-standard, and relationship type property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准和关系类型属性参数。
Conformance: This property can be specified in the "VEVENT", "VTODO", and "VJOURNAL" calendar components.
一致性：可以在“VEVENT”、“VTODO”和“VJOURNAL”日历组件中指定此属性。
Description: The property value consists of the persistent, globally unique identifier of another calendar component. This value would be represented in a calendar component by the "UID" property.
描述：属性值由另一个日历组件的持久、全局唯一标识符组成。该值将在日历组件中由“UID”属性表示。
By default, the property value points to another calendar component that has a PARENT relationship to the referencing object. The "RELTYPE" property parameter is used to either explicitly state the default PARENT relationship type to the referenced calendar component or to override the default PARENT relationship type and specify either a CHILD or SIBLING relationship. The PARENT relationship indicates that the calendar component is a subordinate of the referenced calendar component. The CHILD relationship indicates that the calendar component is a superior of the referenced calendar component. The SIBLING relationship indicates that the calendar component is a peer of the referenced calendar component.
默认情况下，属性值指向与引用对象具有父关系的另一个日历组件。“RELTYPE”属性参数用于显式地向引用的日历组件声明默认的父关系类型，或替代默认的父关系类型并指定子关系或同级关系。父关系表示日历组件是引用的日历组件的下级。子关系表示日历组件是引用的日历组件的上级。同级关系表示日历组件是引用的日历组件的对等方。
Changes to a calendar component referenced by this property can have an implicit impact on the related calendar component. For example, if a group event changes its start or end date or time, then the related, dependent events will need to have their start and end dates changed in a corresponding way. Similarly, if a PARENT calendar component is cancelled or deleted, then there is an implied impact to the related CHILD calendar components. This property is intended only to provide information on the relationship of calendar components. It is up to the target calendar system to maintain any property implications of this relationship.
对此属性引用的日历组件所做的更改可能会对相关日历组件产生隐式影响。例如，如果组事件更改其开始或结束日期或时间，则相关的从属事件将需要以相应的方式更改其开始和结束日期。类似地，如果父日历组件被取消或删除，则会对相关子日历组件产生隐含影响。此属性仅用于提供有关日历组件关系的信息。由目标日历系统维护此关系的任何财产含义。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
related = "RELATED-TO" relparam ":" text CRLF
related=“related-TO”relparam”：“文本CRLF”
relparam = *(
;
; The following is OPTIONAL,
; but MUST NOT occur more than once.
;
(";" reltypeparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
relparam = *(
;
; The following is OPTIONAL,
; but MUST NOT occur more than once.
;
(";" reltypeparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
The following is an example of this property:
以下是此属性的示例：
RELATED-TO:jsmith.part7.19960817T083000.xyzMail@example.com
相关：jsmith.part7.19960817T083000。xyzMail@example.com
RELATED-TO:19960401-080045-4000F192713-0052@example.com
相关信息：19960401-080045-4000F192713-0052@example.com
Property Name: URL
属性名称：URL
Purpose: This property defines a Uniform Resource Locator (URL) associated with the iCalendar object.
用途：此属性定义与iCalendar对象关联的统一资源定位器（URL）。
Value Type: URI
值类型：URI
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property can be specified once in the "VEVENT", "VTODO", "VJOURNAL", or "VFREEBUSY" calendar components.
一致性：此属性可以在“VEVENT”、“VTODO”、“VJOURNAL”或“VFREEBUSY”日历组件中指定一次。
Description: This property may be used in a calendar component to convey a location where a more dynamic rendition of the calendar information associated with the calendar component can be found. This memo does not attempt to standardize the form of the URI, nor the format of the resource pointed to by the property value. If the URL property and Content-Location MIME header are both specified, they MUST point to the same resource.
描述：此属性可在日历组件中用于传递一个位置，在该位置可以找到与日历组件关联的日历信息的更动态的格式副本。此备忘录不尝试标准化URI的形式，也不尝试标准化属性值所指向的资源的格式。如果URL属性和内容位置MIME头都已指定，则它们必须指向同一资源。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
url = "URL" urlparam ":" uri CRLF
url=“url”urlparam:“uri CRLF”
urlparam = *(";" other-param)
urlparam = *(";" other-param)
Example: The following is an example of this property:
示例：以下是此属性的示例：
URL:http://example.com/pub/calendars/jsmith/mytime.ics
URL:http://example.com/pub/calendars/jsmith/mytime.ics
Property Name: UID
属性名称：UID
Purpose: This property defines the persistent, globally unique identifier for the calendar component.
用途：此属性定义日历组件的持久、全局唯一标识符。
Value Type: TEXT
值类型：文本
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: The property MUST be specified in the "VEVENT", "VTODO", "VJOURNAL", or "VFREEBUSY" calendar components.
一致性：必须在“VEVENT”、“VTODO”、“VJOURNAL”或“VFREEBUSY”日历组件中指定该属性。
Description: The "UID" itself MUST be a globally unique identifier. The generator of the identifier MUST guarantee that the identifier is unique. There are several algorithms that can be used to accomplish this. A good method to assure uniqueness is to put the domain name or a domain literal IP address of the host on which the identifier was created on the right-hand side of an "@", and on the left-hand side, put a combination of the current calendar date and time of day (i.e., formatted in as a DATE-TIME value) along with some other currently unique (perhaps sequential) identifier available on the system (for example, a process id number). Using a DATE-TIME value on the left-hand side and a domain name or domain literal on the right-hand side makes it possible to guarantee uniqueness since no two hosts should be using the same domain name or IP address at the same time. Though other algorithms will work, it is RECOMMENDED that the right-hand side contain some domain identifier (either of the host itself or otherwise) such that the generator of the message identifier can guarantee the uniqueness of the left-hand side within the scope of that domain.
说明：“UID”本身必须是全局唯一标识符。标识符的生成器必须保证标识符是唯一的。有几种算法可以用来实现这一点。确保唯一性的一个好方法是将创建标识符的主机的域名或域文字IP地址放在“@”的右侧，并将当前日历日期和时间（即，格式化为日期时间值）与其他当前唯一的主机一起放在左侧系统上可用的（可能是顺序的）标识符（例如，进程id号）。在左侧使用日期时间值，在右侧使用域名或域文字可以保证唯一性，因为没有两台主机可以同时使用相同的域名或IP地址。虽然其他算法也可以，但建议在右侧包含一些域标识符（主机本身或其他）这样，消息标识符的生成器可以保证该域范围内左侧的唯一性。
This is the method for correlating scheduling messages with the referenced "VEVENT", "VTODO", or "VJOURNAL" calendar component.
这是将调度消息与引用的“VEVENT”、“VTODO”或“VJOURAL”日历组件关联的方法。
The full range of calendar components specified by a recurrence set is referenced by referring to just the "UID" property value corresponding to the calendar component. The "RECURRENCE-ID" property allows the reference to an individual instance within the recurrence set.
通过仅引用与日历组件对应的“UID”属性值，可以引用由重复集指定的全部日历组件。“RECURRENCE-ID”属性允许引用重复集中的单个实例。
This property is an important method for group-scheduling applications to match requests with later replies, modifications, or deletion requests. Calendaring and scheduling applications MUST generate this property in "VEVENT", "VTODO", and "VJOURNAL" calendar components to assure interoperability with other group-scheduling applications. This identifier is created by the calendar system that generates an iCalendar object.
此属性是组调度应用程序将请求与以后的答复、修改或删除请求相匹配的重要方法。日历和调度应用程序必须在“VEVENT”、“VTODO”和“VJOURNAL”日历组件中生成此属性，以确保与其他组调度应用程序的互操作性。此标识符由生成iCalendar对象的日历系统创建。
Implementations MUST be able to receive and persist values of at least 255 octets for this property, but they MUST NOT truncate values in the middle of a UTF-8 multi-octet sequence.
实现必须能够接收和保持至少255个八位字节的值，但是它们不能截断UTF-8多八位字节序列中间的值。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
uid = "UID" uidparam ":" text CRLF
uid=“uid”uidparam:“文本CRLF”
uidparam = *(";" other-param)
uidparam = *(";" other-param)
Example: The following is an example of this property:
示例：以下是此属性的示例：
UID:19960401T080045Z-4000F192713-0052@example.com
UID:19960401T08045Z-4000F192713-0052@example.com
The following properties specify recurrence information in calendar components.
以下属性指定日历组件中的定期信息。
Property Name: EXDATE
属性名称：EXDATE
Purpose: This property defines the list of DATE-TIME exceptions for recurring events, to-dos, journal entries, or time zone definitions.
用途：此属性定义定期事件、待办事项、日记账分录或时区定义的日期-时间异常列表。
Value Type: The default value type for this property is DATE-TIME. The value type can be set to DATE.
值类型：此属性的默认值类型为日期时间。值类型可以设置为日期。
Property Parameters: IANA, non-standard, value data type, and time zone identifier property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准、值数据类型和时区标识符属性参数。
Conformance: This property can be specified in recurring "VEVENT", "VTODO", and "VJOURNAL" calendar components as well as in the "STANDARD" and "DAYLIGHT" sub-components of the "VTIMEZONE" calendar component.
一致性：此属性可以在“VEVENT”、“VTODO”和“VJOURNAL”日历组件以及“VTIMEZONE”日历组件的“STANDARD”和“DAYLIGHT”子组件中指定。
Description: The exception dates, if specified, are used in computing the recurrence set. The recurrence set is the complete set of recurrence instances for a calendar component. The recurrence set is generated by considering the initial "DTSTART" property along with the "RRULE", "RDATE", and "EXDATE" properties contained within the recurring component. The "DTSTART" property defines the first instance in the recurrence set. The "DTSTART" property value SHOULD match the pattern of the recurrence rule, if specified. The recurrence set generated with a "DTSTART" property value that doesn't match the pattern of the rule is undefined. The final recurrence set is generated by gathering all of the start DATE-TIME values generated by any of the specified "RRULE" and "RDATE" properties, and then excluding any start DATE-TIME values specified by "EXDATE" properties. This implies that start DATE-TIME values specified by "EXDATE" properties take precedence over those specified by inclusion properties (i.e., "RDATE" and "RRULE"). When duplicate instances are generated by the "RRULE" and "RDATE" properties, only one recurrence is considered. Duplicate instances are ignored.
描述：异常日期（如果指定）用于计算重复集。重复集是日历组件的完整重复实例集。通过考虑初始“DTSTART”属性以及周期组件中包含的“RRULE”、“RDATE”和“EXDATE”属性，可以生成周期集。“DTSTART”属性定义重复集合中的第一个实例。如果指定，“DTSTART”属性值应与定期规则的模式匹配。未定义使用与规则模式不匹配的“DTSTART”属性值生成的重复集。通过收集由任何指定的“RRULE”和“RDATE”属性生成的所有开始日期时间值，然后排除由“EXDATE”属性指定的任何开始日期时间值，生成最终的定期集。这意味着“EXDATE”属性指定的开始日期时间值优先于包含属性（即“RDATE”和“RRULE”）指定的开始日期时间值。当“RRULE”和“RDATE”属性生成重复实例时，只考虑一次重复。重复的实例将被忽略。
The "EXDATE" property can be used to exclude the value specified in "DTSTART". However, in such cases, the original "DTSTART" date MUST still be maintained by the calendaring and scheduling system because the original "DTSTART" value has inherent usage dependencies by other properties such as the "RECURRENCE-ID".
“EXDATE”属性可用于排除“DTSTART”中指定的值。但是，在这种情况下，日历和调度系统仍必须维护原始“DTSTART”日期，因为原始“DTSTART”值与其他属性（如“RECURRENCE-ID”）具有内在的使用依赖性。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
exdate = "EXDATE" exdtparam ":" exdtval *("," exdtval) CRLF
exdate = "EXDATE" exdtparam ":" exdtval *("," exdtval) CRLF
exdtparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
;
(";" tzidparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
exdtparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
;
(";" tzidparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
exdtval = date-time / date ;Value MUST match value type
exdtval=日期时间/日期；值必须与值类型匹配
Example: The following is an example of this property:
示例：以下是此属性的示例：
EXDATE:19960402T010000Z,19960403T010000Z,19960404T010000Z
出厂日期：19960402T010000Z、19960403T010000Z、19960404T010000Z
Property Name: RDATE
属性名称：RDATE
Purpose: This property defines the list of DATE-TIME values for recurring events, to-dos, journal entries, or time zone definitions.
用途：此属性定义定期事件、待办事项、日记条目或时区定义的日期时间值列表。
Value Type: The default value type for this property is DATE-TIME. The value type can be set to DATE or PERIOD.
值类型：此属性的默认值类型为日期时间。值类型可以设置为日期或期间。
Property Parameters: IANA, non-standard, value data type, and time zone identifier property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准、值数据类型和时区标识符属性参数。
Conformance: This property can be specified in recurring "VEVENT", "VTODO", and "VJOURNAL" calendar components as well as in the "STANDARD" and "DAYLIGHT" sub-components of the "VTIMEZONE" calendar component.
一致性：此属性可以在“VEVENT”、“VTODO”和“VJOURNAL”日历组件以及“VTIMEZONE”日历组件的“STANDARD”和“DAYLIGHT”子组件中指定。
Description: This property can appear along with the "RRULE" property to define an aggregate set of repeating occurrences. When they both appear in a recurring component, the recurrence
描述：此属性可以与“RRULE”属性一起出现，以定义重复出现的聚合集。当它们都出现在重复组件中时，重复
instances are defined by the union of occurrences defined by both the "RDATE" and "RRULE".
实例由“RDATE”和“RRULE”定义的事件的并集定义。
The recurrence dates, if specified, are used in computing the recurrence set. The recurrence set is the complete set of recurrence instances for a calendar component. The recurrence set is generated by considering the initial "DTSTART" property along with the "RRULE", "RDATE", and "EXDATE" properties contained within the recurring component. The "DTSTART" property defines the first instance in the recurrence set. The "DTSTART" property value SHOULD match the pattern of the recurrence rule, if specified. The recurrence set generated with a "DTSTART" property value that doesn't match the pattern of the rule is undefined. The final recurrence set is generated by gathering all of the start DATE-TIME values generated by any of the specified "RRULE" and "RDATE" properties, and then excluding any start DATE-TIME values specified by "EXDATE" properties. This implies that start DATE-TIME values specified by "EXDATE" properties take precedence over those specified by inclusion properties (i.e., "RDATE" and "RRULE"). Where duplicate instances are generated by the "RRULE" and "RDATE" properties, only one recurrence is considered. Duplicate instances are ignored.
重复日期（如果指定）用于计算重复集。重复集是日历组件的完整重复实例集。通过考虑初始“DTSTART”属性以及周期组件中包含的“RRULE”、“RDATE”和“EXDATE”属性，可以生成周期集。“DTSTART”属性定义重复集合中的第一个实例。如果指定，“DTSTART”属性值应与定期规则的模式匹配。未定义使用与规则模式不匹配的“DTSTART”属性值生成的重复集。通过收集由任何指定的“RRULE”和“RDATE”属性生成的所有开始日期时间值，然后排除由“EXDATE”属性指定的任何开始日期时间值，生成最终的定期集。这意味着“EXDATE”属性指定的开始日期时间值优先于包含属性（即“RDATE”和“RRULE”）指定的开始日期时间值。如果“RRULE”和“RDATE”属性生成重复实例，则只考虑一次重复。重复的实例将被忽略。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
rdate = "RDATE" rdtparam ":" rdtval *("," rdtval) CRLF
rdate = "RDATE" rdtparam ":" rdtval *("," rdtval) CRLF
rdtparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" "VALUE" "=" ("DATE-TIME" / "DATE" / "PERIOD")) /
(";" tzidparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
rdtparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" "VALUE" "=" ("DATE-TIME" / "DATE" / "PERIOD")) /
(";" tzidparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
rdtval = date-time / date / period
;Value MUST match value type
rdtval = date-time / date / period
;Value MUST match value type
Example: The following are examples of this property:
示例：以下是此属性的示例：
RDATE:19970714T123000Z
RDATE;TZID=America/New_York:19970714T083000
RDATE:19970714T123000Z
RDATE;TZID=America/New_York:19970714T083000
RDATE;VALUE=PERIOD:19960403T020000Z/19960403T040000Z,
19960404T010000Z/PT3H
RDATE;VALUE=PERIOD:19960403T020000Z/19960403T040000Z,
19960404T010000Z/PT3H
RDATE;VALUE=DATE:19970101,19970120,19970217,19970421 19970526,19970704,19970901,19971014,19971128,19971129,19971225
硬脂酸盐；值=日期：1997010119970120199702171997042119705261997041997090119971014199711281997112919971225
Property Name: RRULE
物业名称：RRULE
Purpose: This property defines a rule or repeating pattern for recurring events, to-dos, journal entries, or time zone definitions.
用途：此属性定义定期事件、待办事项、日记条目或时区定义的规则或重复模式。
Value Type: RECUR
值类型：重现
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property can be specified in recurring "VEVENT", "VTODO", and "VJOURNAL" calendar components as well as in the "STANDARD" and "DAYLIGHT" sub-components of the "VTIMEZONE" calendar component, but it SHOULD NOT be specified more than once. The recurrence set generated with multiple "RRULE" properties is undefined.
一致性：此属性可以在“VEVENT”、“VTODO”和“VJOURNAL”日历组件以及“VTIMEZONE”日历组件的“STANDARD”和“DAYLIGHT”子组件中指定，但不应指定多次。使用多个“RRULE”属性生成的重复集未定义。
Description: The recurrence rule, if specified, is used in computing the recurrence set. The recurrence set is the complete set of recurrence instances for a calendar component. The recurrence set is generated by considering the initial "DTSTART" property along with the "RRULE", "RDATE", and "EXDATE" properties contained within the recurring component. The "DTSTART" property defines the first instance in the recurrence set. The "DTSTART" property value SHOULD be synchronized with the recurrence rule, if specified. The recurrence set generated with a "DTSTART" property value not synchronized with the recurrence rule is undefined. The final recurrence set is generated by gathering all of the start DATE-TIME values generated by any of the specified "RRULE" and "RDATE" properties, and then excluding any start DATE-TIME values specified by "EXDATE" properties. This implies that start DATE-TIME values specified by "EXDATE" properties take precedence over those specified by inclusion properties (i.e., "RDATE" and "RRULE"). Where duplicate instances are generated by the "RRULE"
描述：递归规则（如果指定）用于计算递归集。重复集是日历组件的完整重复实例集。通过考虑初始“DTSTART”属性以及周期组件中包含的“RRULE”、“RDATE”和“EXDATE”属性，可以生成周期集。“DTSTART”属性定义重复集合中的第一个实例。如果指定，“DTSTART”属性值应与定期规则同步。未定义使用与定期规则不同步的“DTSTART”属性值生成的定期集。通过收集由任何指定的“RRULE”和“RDATE”属性生成的所有开始日期时间值，然后排除由“EXDATE”属性指定的任何开始日期时间值，生成最终的定期集。这意味着“EXDATE”属性指定的开始日期时间值优先于包含属性（即“RDATE”和“RRULE”）指定的开始日期时间值。其中“RRULE”生成重复实例
and "RDATE" properties, only one recurrence is considered. Duplicate instances are ignored.
和“RDATE”属性，只考虑一次重复。重复的实例将被忽略。
The "DTSTART" property specified within the iCalendar object defines the first instance of the recurrence. In most cases, a "DTSTART" property of DATE-TIME value type used with a recurrence rule, should be specified as a date with local time and time zone reference to make sure all the recurrence instances start at the same local time regardless of time zone changes.
在iCalendar对象中指定的“DTSTART”属性定义了循环的第一个实例。在大多数情况下，应将与定期规则一起使用的日期-时间值类型的“DTSTART”属性指定为具有本地时间和时区引用的日期，以确保所有定期实例在同一本地时间开始，而不考虑时区的更改。
If the duration of the recurring component is specified with the "DTEND" or "DUE" property, then the same exact duration will apply to all the members of the generated recurrence set. Else, if the duration of the recurring component is specified with the "DURATION" property, then the same nominal duration will apply to all the members of the generated recurrence set and the exact duration of each recurrence instance will depend on its specific start time. For example, recurrence instances of a nominal duration of one day will have an exact duration of more or less than 24 hours on a day where a time zone shift occurs. The duration of a specific recurrence may be modified in an exception component or simply by using an "RDATE" property of PERIOD value type.
如果使用“DTEND”或“DUE”属性指定定期组件的持续时间，则相同的精确持续时间将应用于生成的定期集的所有成员。否则，如果使用“duration”属性指定定期组件的持续时间，则相同的标称持续时间将应用于生成的定期集的所有成员，并且每个定期实例的确切持续时间将取决于其特定的开始时间。例如，标称持续时间为一天的重复实例在发生时区转换的一天的确切持续时间将大于或小于24小时。可以在异常组件中修改特定重复周期的持续时间，或者只需使用周期值类型的“RDATE”属性。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
rrule = "RRULE" rrulparam ":" recur CRLF
rrule=“rrule”rrulparam:“重现CRLF”
rrulparam = *(";" other-param)
rrulparam = *(";" other-param)
Example: All examples assume the Eastern United States time zone.
示例：所有示例均假定美国东部时区。
Daily for 10 occurrences:
每天发生10次：
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=DAILY;COUNT=10
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=DAILY;COUNT=10
==> (1997 9:00 AM EDT) September 2-11
==> (1997 9:00 AM EDT) September 2-11
Daily until December 24, 1997:
直至1997年12月24日每日：
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=DAILY;UNTIL=19971224T000000Z
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=DAILY;UNTIL=19971224T000000Z
==> (1997 9:00 AM EDT) September 2-30;October 1-25
(1997 9:00 AM EST) October 26-31;November 1-30;December 1-23
==> (1997 9:00 AM EDT) September 2-30;October 1-25
(1997 9:00 AM EST) October 26-31;November 1-30;December 1-23
Every other day - forever:
每隔一天-永远：
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=DAILY;INTERVAL=2
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=DAILY;INTERVAL=2
==> (1997 9:00 AM EDT) September 2,4,6,8...24,26,28,30;
October 2,4,6...20,22,24
(1997 9:00 AM EST) October 26,28,30;
November 1,3,5,7...25,27,29;
December 1,3,...
==> (1997 9:00 AM EDT) September 2,4,6,8...24,26,28,30;
October 2,4,6...20,22,24
(1997 9:00 AM EST) October 26,28,30;
November 1,3,5,7...25,27,29;
December 1,3,...
Every 10 days, 5 occurrences:
每10天发生5次：
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=DAILY;INTERVAL=10;COUNT=5
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=DAILY;INTERVAL=10;COUNT=5
==> (1997 9:00 AM EDT) September 2,12,22;
October 2,12
==> (1997 9:00 AM EDT) September 2,12,22;
October 2,12
Every day in January, for 3 years:
1月的每一天，持续3年：
DTSTART;TZID=America/New_York:19980101T090000
DTSTART;TZID=America/New_York:19980101T090000
RRULE:FREQ=YEARLY;UNTIL=20000131T140000Z;
BYMONTH=1;BYDAY=SU,MO,TU,WE,TH,FR,SA
or
RRULE:FREQ=DAILY;UNTIL=20000131T140000Z;BYMONTH=1
RRULE:FREQ=YEARLY;UNTIL=20000131T140000Z;
BYMONTH=1;BYDAY=SU,MO,TU,WE,TH,FR,SA
or
RRULE:FREQ=DAILY;UNTIL=20000131T140000Z;BYMONTH=1
==> (1998 9:00 AM EST)January 1-31
(1999 9:00 AM EST)January 1-31
(2000 9:00 AM EST)January 1-31
==> (1998 9:00 AM EST)January 1-31
(1999 9:00 AM EST)January 1-31
(2000 9:00 AM EST)January 1-31
Weekly for 10 occurrences:
每周发生10次：
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=WEEKLY;COUNT=10
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=WEEKLY;COUNT=10
==> (1997 9:00 AM EDT) September 2,9,16,23,30;October 7,14,21
(1997 9:00 AM EST) October 28;November 4
==> (1997 9:00 AM EDT) September 2,9,16,23,30;October 7,14,21
(1997 9:00 AM EST) October 28;November 4
Weekly until December 24, 1997:
至1997年12月24日，每周：
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=WEEKLY;UNTIL=19971224T000000Z
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=WEEKLY;UNTIL=19971224T000000Z
==> (1997 9:00 AM EDT) September 2,9,16,23,30;
October 7,14,21
(1997 9:00 AM EST) October 28;
November 4,11,18,25;
December 2,9,16,23
==> (1997 9:00 AM EDT) September 2,9,16,23,30;
October 7,14,21
(1997 9:00 AM EST) October 28;
November 4,11,18,25;
December 2,9,16,23
Every other week - forever:
每隔一周-永远：
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=WEEKLY;INTERVAL=2;WKST=SU
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=WEEKLY;INTERVAL=2;WKST=SU
==> (1997 9:00 AM EDT) September 2,16,30;
October 14
(1997 9:00 AM EST) October 28;
November 11,25;
December 9,23
(1998 9:00 AM EST) January 6,20;
February 3, 17
...
==> (1997 9:00 AM EDT) September 2,16,30;
October 14
(1997 9:00 AM EST) October 28;
November 11,25;
December 9,23
(1998 9:00 AM EST) January 6,20;
February 3, 17
...
Weekly on Tuesday and Thursday for five weeks:
每周星期二和星期四，为期五周：
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=WEEKLY;UNTIL=19971007T000000Z;WKST=SU;BYDAY=TU,TH
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=WEEKLY;UNTIL=19971007T000000Z;WKST=SU;BYDAY=TU,TH
or
或
RRULE:FREQ=WEEKLY;COUNT=10;WKST=SU;BYDAY=TU,TH
RRULE:FREQ=WEEKLY;COUNT=10;WKST=SU;BYDAY=TU,TH
==> (1997 9:00 AM EDT) September 2,4,9,11,16,18,23,25,30;
October 2
==> (1997 9:00 AM EDT) September 2,4,9,11,16,18,23,25,30;
October 2
Every other week on Monday, Wednesday, and Friday until December 24, 1997, starting on Monday, September 1, 1997:
从1997年9月1日星期一开始，至1997年12月24日，每隔一周的星期一、星期三和星期五：
DTSTART;TZID=America/New_York:19970901T090000
RRULE:FREQ=WEEKLY;INTERVAL=2;UNTIL=19971224T000000Z;WKST=SU;
BYDAY=MO,WE,FR
DTSTART;TZID=America/New_York:19970901T090000
RRULE:FREQ=WEEKLY;INTERVAL=2;UNTIL=19971224T000000Z;WKST=SU;
BYDAY=MO,WE,FR
==> (1997 9:00 AM EDT) September 1,3,5,15,17,19,29;
October 1,3,13,15,17
(1997 9:00 AM EST) October 27,29,31;
November 10,12,14,24,26,28;
==> (1997 9:00 AM EDT) September 1,3,5,15,17,19,29;
October 1,3,13,15,17
(1997 9:00 AM EST) October 27,29,31;
November 10,12,14,24,26,28;
December 8,10,12,22
十二月八日、十日、十二日、二十二日
Every other week on Tuesday and Thursday, for 8 occurrences:
每隔一周在星期二和星期四发生8次：
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=WEEKLY;INTERVAL=2;COUNT=8;WKST=SU;BYDAY=TU,TH
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=WEEKLY;INTERVAL=2;COUNT=8;WKST=SU;BYDAY=TU,TH
==> (1997 9:00 AM EDT) September 2,4,16,18,30;
October 2,14,16
==> (1997 9:00 AM EDT) September 2,4,16,18,30;
October 2,14,16
Monthly on the first Friday for 10 occurrences:
每月在第一个星期五发生10次：
DTSTART;TZID=America/New_York:19970905T090000
RRULE:FREQ=MONTHLY;COUNT=10;BYDAY=1FR
DTSTART;TZID=America/New_York:19970905T090000
RRULE:FREQ=MONTHLY;COUNT=10;BYDAY=1FR
==> (1997 9:00 AM EDT) September 5;October 3
(1997 9:00 AM EST) November 7;December 5
(1998 9:00 AM EST) January 2;February 6;March 6;April 3
(1998 9:00 AM EDT) May 1;June 5
==> (1997 9:00 AM EDT) September 5;October 3
(1997 9:00 AM EST) November 7;December 5
(1998 9:00 AM EST) January 2;February 6;March 6;April 3
(1998 9:00 AM EDT) May 1;June 5
Monthly on the first Friday until December 24, 1997:
1997年12月24日前的第一个星期五每月：
DTSTART;TZID=America/New_York:19970905T090000
RRULE:FREQ=MONTHLY;UNTIL=19971224T000000Z;BYDAY=1FR
DTSTART;TZID=America/New_York:19970905T090000
RRULE:FREQ=MONTHLY;UNTIL=19971224T000000Z;BYDAY=1FR
==> (1997 9:00 AM EDT) September 5; October 3
(1997 9:00 AM EST) November 7; December 5
==> (1997 9:00 AM EDT) September 5; October 3
(1997 9:00 AM EST) November 7; December 5
Every other month on the first and last Sunday of the month for 10 occurrences:
每隔一个月在该月的第一个星期日和最后一个星期日发生10次：
DTSTART;TZID=America/New_York:19970907T090000
RRULE:FREQ=MONTHLY;INTERVAL=2;COUNT=10;BYDAY=1SU,-1SU
DTSTART;TZID=America/New_York:19970907T090000
RRULE:FREQ=MONTHLY;INTERVAL=2;COUNT=10;BYDAY=1SU,-1SU
==> (1997 9:00 AM EDT) September 7,28
(1997 9:00 AM EST) November 2,30
(1998 9:00 AM EST) January 4,25;March 1,29
(1998 9:00 AM EDT) May 3,31
==> (1997 9:00 AM EDT) September 7,28
(1997 9:00 AM EST) November 2,30
(1998 9:00 AM EST) January 4,25;March 1,29
(1998 9:00 AM EDT) May 3,31
Monthly on the second-to-last Monday of the month for 6 months:
每月第二至最后一个星期一，为期6个月：
DTSTART;TZID=America/New_York:19970922T090000
RRULE:FREQ=MONTHLY;COUNT=6;BYDAY=-2MO
DTSTART;TZID=America/New_York:19970922T090000
RRULE:FREQ=MONTHLY;COUNT=6;BYDAY=-2MO
==> (1997 9:00 AM EDT) September 22;October 20
(1997 9:00 AM EST) November 17;December 22
(1998 9:00 AM EST) January 19;February 16
==> (1997 9:00 AM EDT) September 22;October 20
(1997 9:00 AM EST) November 17;December 22
(1998 9:00 AM EST) January 19;February 16
Monthly on the third-to-the-last day of the month, forever:
每月第三至最后一天，永远：
DTSTART;TZID=America/New_York:19970928T090000
RRULE:FREQ=MONTHLY;BYMONTHDAY=-3
DTSTART;TZID=America/New_York:19970928T090000
RRULE:FREQ=MONTHLY;BYMONTHDAY=-3
==> (1997 9:00 AM EDT) September 28 (1997 9:00 AM EST) October 29;November 28;December 29 (1998 9:00 AM EST) January 29;February 26 ...
==>（1997年美国东部时间上午9:00）9月28日（1997年美国东部时间上午9:00）10月29日；11月28日；12月29日（1998年美国东部时间上午9:00）1月29日；二月二十六日。。。
Monthly on the 2nd and 15th of the month for 10 occurrences:
每月2日和15日发生10次：
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=MONTHLY;COUNT=10;BYMONTHDAY=2,15
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=MONTHLY;COUNT=10;BYMONTHDAY=2,15
==> (1997 9:00 AM EDT) September 2,15;October 2,15
(1997 9:00 AM EST) November 2,15;December 2,15
(1998 9:00 AM EST) January 2,15
==> (1997 9:00 AM EDT) September 2,15;October 2,15
(1997 9:00 AM EST) November 2,15;December 2,15
(1998 9:00 AM EST) January 2,15
Monthly on the first and last day of the month for 10 occurrences:
每月的第一天和最后一天发生10次：
DTSTART;TZID=America/New_York:19970930T090000
RRULE:FREQ=MONTHLY;COUNT=10;BYMONTHDAY=1,-1
DTSTART;TZID=America/New_York:19970930T090000
RRULE:FREQ=MONTHLY;COUNT=10;BYMONTHDAY=1,-1
==> (1997 9:00 AM EDT) September 30;October 1
(1997 9:00 AM EST) October 31;November 1,30;December 1,31
(1998 9:00 AM EST) January 1,31;February 1
==> (1997 9:00 AM EDT) September 30;October 1
(1997 9:00 AM EST) October 31;November 1,30;December 1,31
(1998 9:00 AM EST) January 1,31;February 1
Every 18 months on the 10th thru 15th of the month for 10 occurrences:
每18个月10日至15日发生10次：
DTSTART;TZID=America/New_York:19970910T090000
RRULE:FREQ=MONTHLY;INTERVAL=18;COUNT=10;BYMONTHDAY=10,11,12,
13,14,15
DTSTART;TZID=America/New_York:19970910T090000
RRULE:FREQ=MONTHLY;INTERVAL=18;COUNT=10;BYMONTHDAY=10,11,12,
13,14,15
==> (1997 9:00 AM EDT) September 10,11,12,13,14,15
(1999 9:00 AM EST) March 10,11,12,13
==> (1997 9:00 AM EDT) September 10,11,12,13,14,15
(1999 9:00 AM EST) March 10,11,12,13
Every Tuesday, every other month:
每周二、每隔一个月：
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=MONTHLY;INTERVAL=2;BYDAY=TU
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=MONTHLY;INTERVAL=2;BYDAY=TU
==> (1997 9:00 AM EDT) September 2,9,16,23,30 (1997 9:00 AM EST) November 4,11,18,25 (1998 9:00 AM EST) January 6,13,20,27;March 3,10,17,24,31 ...
==>（1997年美国东部时间上午9:00）9月2、9、16、23、30日（1997年美国东部时间上午9:00）11月4、11、18、25日（1998年美国东部时间上午9:00）1月6、13、20、27日；3月3日，10日，17日，24日，31日。。。
Yearly in June and July for 10 occurrences:
每年6月和7月发生10次：
DTSTART;TZID=America/New_York:19970610T090000
RRULE:FREQ=YEARLY;COUNT=10;BYMONTH=6,7
DTSTART;TZID=America/New_York:19970610T090000
RRULE:FREQ=YEARLY;COUNT=10;BYMONTH=6,7
==> (1997 9:00 AM EDT) June 10;July 10
(1998 9:00 AM EDT) June 10;July 10
(1999 9:00 AM EDT) June 10;July 10
(2000 9:00 AM EDT) June 10;July 10
(2001 9:00 AM EDT) June 10;July 10
==> (1997 9:00 AM EDT) June 10;July 10
(1998 9:00 AM EDT) June 10;July 10
(1999 9:00 AM EDT) June 10;July 10
(2000 9:00 AM EDT) June 10;July 10
(2001 9:00 AM EDT) June 10;July 10
Note: Since none of the BYDAY, BYMONTHDAY, or BYYEARDAY components are specified, the day is gotten from "DTSTART".
注意：由于未指定BYDAY、BYMONTHDAY或BYYEARDAY组件，因此日期从“DTSTART”获取。
Every other year on January, February, and March for 10 occurrences:
每隔一年在1月、2月和3月发生10次：
DTSTART;TZID=America/New_York:19970310T090000
RRULE:FREQ=YEARLY;INTERVAL=2;COUNT=10;BYMONTH=1,2,3
DTSTART;TZID=America/New_York:19970310T090000
RRULE:FREQ=YEARLY;INTERVAL=2;COUNT=10;BYMONTH=1,2,3
==> (1997 9:00 AM EST) March 10
(1999 9:00 AM EST) January 10;February 10;March 10
(2001 9:00 AM EST) January 10;February 10;March 10
(2003 9:00 AM EST) January 10;February 10;March 10
==> (1997 9:00 AM EST) March 10
(1999 9:00 AM EST) January 10;February 10;March 10
(2001 9:00 AM EST) January 10;February 10;March 10
(2003 9:00 AM EST) January 10;February 10;March 10
Every third year on the 1st, 100th, and 200th day for 10 occurrences:
每三年的第1天、第100天和第200天发生10次：
DTSTART;TZID=America/New_York:19970101T090000
RRULE:FREQ=YEARLY;INTERVAL=3;COUNT=10;BYYEARDAY=1,100,200
DTSTART;TZID=America/New_York:19970101T090000
RRULE:FREQ=YEARLY;INTERVAL=3;COUNT=10;BYYEARDAY=1,100,200
==> (1997 9:00 AM EST) January 1
(1997 9:00 AM EDT) April 10;July 19
(2000 9:00 AM EST) January 1
(2000 9:00 AM EDT) April 9;July 18
(2003 9:00 AM EST) January 1
(2003 9:00 AM EDT) April 10;July 19
(2006 9:00 AM EST) January 1
==> (1997 9:00 AM EST) January 1
(1997 9:00 AM EDT) April 10;July 19
(2000 9:00 AM EST) January 1
(2000 9:00 AM EDT) April 9;July 18
(2003 9:00 AM EST) January 1
(2003 9:00 AM EDT) April 10;July 19
(2006 9:00 AM EST) January 1
Every 20th Monday of the year, forever:
每年的每20个星期一，永远：
DTSTART;TZID=America/New_York:19970519T090000
RRULE:FREQ=YEARLY;BYDAY=20MO
DTSTART;TZID=America/New_York:19970519T090000
RRULE:FREQ=YEARLY;BYDAY=20MO
==> (1997 9:00 AM EDT) May 19 (1998 9:00 AM EDT) May 18 (1999 9:00 AM EDT) May 17 ...
==>（1997年美国东部时间上午9:00）5月19日（1998年美国东部时间上午9:00）5月18日（1999年美国东部时间上午9:00）5月17日。。。
Monday of week number 20 (where the default start of the week is Monday), forever:
第20周的星期一（本周的默认开始时间为星期一），永久：
DTSTART;TZID=America/New_York:19970512T090000
RRULE:FREQ=YEARLY;BYWEEKNO=20;BYDAY=MO
DTSTART;TZID=America/New_York:19970512T090000
RRULE:FREQ=YEARLY;BYWEEKNO=20;BYDAY=MO
==> (1997 9:00 AM EDT) May 12 (1998 9:00 AM EDT) May 11 (1999 9:00 AM EDT) May 17 ...
==>（1997年美国东部时间上午9:00）5月12日（1998年美国东部时间上午9:00）5月11日（1999年美国东部时间上午9:00）5月17日。。。
Every Thursday in March, forever:
3月的每个星期四，永远：
DTSTART;TZID=America/New_York:19970313T090000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=TH
DTSTART;TZID=America/New_York:19970313T090000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=TH
==> (1997 9:00 AM EST) March 13,20,27 (1998 9:00 AM EST) March 5,12,19,26 (1999 9:00 AM EST) March 4,11,18,25 ...
==>（1997年东部时间上午9:00）3月13、20、27日（1998年东部时间上午9:00）3月5、12、19、26日（1999年东部时间上午9:00）3月4、11、18、25。。。
Every Thursday, but only during June, July, and August, forever:
每周四，但仅在6月、7月和8月期间，永远：
DTSTART;TZID=America/New_York:19970605T090000
RRULE:FREQ=YEARLY;BYDAY=TH;BYMONTH=6,7,8
DTSTART;TZID=America/New_York:19970605T090000
RRULE:FREQ=YEARLY;BYDAY=TH;BYMONTH=6,7,8
==> (1997 9:00 AM EDT) June 5,12,19,26;July 3,10,17,24,31;
August 7,14,21,28
(1998 9:00 AM EDT) June 4,11,18,25;July 2,9,16,23,30;
August 6,13,20,27
(1999 9:00 AM EDT) June 3,10,17,24;July 1,8,15,22,29;
August 5,12,19,26
...
==> (1997 9:00 AM EDT) June 5,12,19,26;July 3,10,17,24,31;
August 7,14,21,28
(1998 9:00 AM EDT) June 4,11,18,25;July 2,9,16,23,30;
August 6,13,20,27
(1999 9:00 AM EDT) June 3,10,17,24;July 1,8,15,22,29;
August 5,12,19,26
...
Every Friday the 13th, forever:
每周五13号，永远：
DTSTART;TZID=America/New_York:19970902T090000
EXDATE;TZID=America/New_York:19970902T090000
RRULE:FREQ=MONTHLY;BYDAY=FR;BYMONTHDAY=13
DTSTART;TZID=America/New_York:19970902T090000
EXDATE;TZID=America/New_York:19970902T090000
RRULE:FREQ=MONTHLY;BYDAY=FR;BYMONTHDAY=13
==> (1998 9:00 AM EST) February 13;March 13;November 13 (1999 9:00 AM EDT) August 13 (2000 9:00 AM EDT) October 13 ...
==>（1998年美国东部时间上午9:00）2月13日；3月13日；11月13日（1999年美国东部时间上午9:00）8月13日（2000年美国东部时间上午9:00）10月13日。。。
The first Saturday that follows the first Sunday of the month, forever:
每月第一个星期日之后的第一个星期六，永远：
DTSTART;TZID=America/New_York:19970913T090000
RRULE:FREQ=MONTHLY;BYDAY=SA;BYMONTHDAY=7,8,9,10,11,12,13
DTSTART;TZID=America/New_York:19970913T090000
RRULE:FREQ=MONTHLY;BYDAY=SA;BYMONTHDAY=7,8,9,10,11,12,13
==> (1997 9:00 AM EDT) September 13;October 11 (1997 9:00 AM EST) November 8;December 13 (1998 9:00 AM EST) January 10;February 7;March 7 (1998 9:00 AM EDT) April 11;May 9;June 13... ...
==>（1997年美国东部时间上午9:00）9月13日；10月11日（1997年美国东部时间上午9:00）11月8日；12月13日（1998年美国东部时间上午9:00）1月10日；二月七日,；3月7日（1998年美国东部夏令时上午9:00）4月11日；5月9日；六月十三日。。。
Every 4 years, the first Tuesday after a Monday in November, forever (U.S. Presidential Election day):
每4年，即11月的星期一之后的第一个星期二，永远（美国总统选举日）：
DTSTART;TZID=America/New_York:19961105T090000
RRULE:FREQ=YEARLY;INTERVAL=4;BYMONTH=11;BYDAY=TU;
BYMONTHDAY=2,3,4,5,6,7,8
DTSTART;TZID=America/New_York:19961105T090000
RRULE:FREQ=YEARLY;INTERVAL=4;BYMONTH=11;BYDAY=TU;
BYMONTHDAY=2,3,4,5,6,7,8
==> (1996 9:00 AM EST) November 5 (2000 9:00 AM EST) November 7 (2004 9:00 AM EST) November 2 ...
==>（1996年美国东部时间上午9:00）11月5日（2000年美国东部时间上午9:00）11月7日（2004年美国东部时间上午9:00）11月2日。。。
The third instance into the month of one of Tuesday, Wednesday, or Thursday, for the next 3 months:
在接下来的3个月内，第三次进入星期二、星期三或星期四的某个月：
DTSTART;TZID=America/New_York:19970904T090000
RRULE:FREQ=MONTHLY;COUNT=3;BYDAY=TU,WE,TH;BYSETPOS=3
DTSTART;TZID=America/New_York:19970904T090000
RRULE:FREQ=MONTHLY;COUNT=3;BYDAY=TU,WE,TH;BYSETPOS=3
==> (1997 9:00 AM EDT) September 4;October 7
(1997 9:00 AM EST) November 6
==> (1997 9:00 AM EDT) September 4;October 7
(1997 9:00 AM EST) November 6
The second-to-last weekday of the month:
当月第二个至最后一个工作日：
DTSTART;TZID=America/New_York:19970929T090000
RRULE:FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-2
DTSTART;TZID=America/New_York:19970929T090000
RRULE:FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-2
==> (1997 9:00 AM EDT) September 29 (1997 9:00 AM EST) October 30;November 27;December 30 (1998 9:00 AM EST) January 29;February 26;March 30 ...
==>（1997年美国东部时间上午9:00）9月29日（1997年美国东部时间上午9:00）10月30日；11月27日；12月30日（1998年美国东部时间上午9:00）1月29日；二月二十六日,；3月30日。。。
Every 3 hours from 9:00 AM to 5:00 PM on a specific day:
在特定日期，每3小时从上午9:00到下午5:00：
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=HOURLY;INTERVAL=3;UNTIL=19970902T170000Z
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=HOURLY;INTERVAL=3;UNTIL=19970902T170000Z
==> (September 2, 1997 EDT) 09:00,12:00,15:00
==> (September 2, 1997 EDT) 09:00,12:00,15:00
Every 15 minutes for 6 occurrences:
每15分钟发生6次：
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=MINUTELY;INTERVAL=15;COUNT=6
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=MINUTELY;INTERVAL=15;COUNT=6
==> (September 2, 1997 EDT) 09:00,09:15,09:30,09:45,10:00,10:15
==> (September 2, 1997 EDT) 09:00,09:15,09:30,09:45,10:00,10:15
Every hour and a half for 4 occurrences:
每一个半小时发生4次：
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=MINUTELY;INTERVAL=90;COUNT=4
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=MINUTELY;INTERVAL=90;COUNT=4
==> (September 2, 1997 EDT) 09:00,10:30;12:00;13:30
==> (September 2, 1997 EDT) 09:00,10:30;12:00;13:30
Every 20 minutes from 9:00 AM to 4:40 PM every day:
每天上午9:00至下午4:40，每20分钟：
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=DAILY;BYHOUR=9,10,11,12,13,14,15,16;BYMINUTE=0,20,40
or
RRULE:FREQ=MINUTELY;INTERVAL=20;BYHOUR=9,10,11,12,13,14,15,16
DTSTART;TZID=America/New_York:19970902T090000
RRULE:FREQ=DAILY;BYHOUR=9,10,11,12,13,14,15,16;BYMINUTE=0,20,40
or
RRULE:FREQ=MINUTELY;INTERVAL=20;BYHOUR=9,10,11,12,13,14,15,16
==> (September 2, 1997 EDT) 9:00,9:20,9:40,10:00,10:20, ... 16:00,16:20,16:40 (September 3, 1997 EDT) 9:00,9:20,9:40,10:00,10:20, ...16:00,16:20,16:40 ...
==>（1997年9月2日美国东部时间）9:00,9:20,9:40,10:00,10:20。。。16:00,16:20,16:40（1997年9月3日美国东部夏令时）9:00,9:20,9:40,10:00,10:20，…16:00,16:20,16:40。。。
An example where the days generated makes a difference because of WKST:
因WKST产生的天数产生差异的示例：
DTSTART;TZID=America/New_York:19970805T090000
RRULE:FREQ=WEEKLY;INTERVAL=2;COUNT=4;BYDAY=TU,SU;WKST=MO
DTSTART;TZID=America/New_York:19970805T090000
RRULE:FREQ=WEEKLY;INTERVAL=2;COUNT=4;BYDAY=TU,SU;WKST=MO
==> (1997 EDT) August 5,10,19,24
==> (1997 EDT) August 5,10,19,24
changing only WKST from MO to SU, yields different results...
仅将WKST从MO更改为SU，会产生不同的结果。。。
DTSTART;TZID=America/New_York:19970805T090000
RRULE:FREQ=WEEKLY;INTERVAL=2;COUNT=4;BYDAY=TU,SU;WKST=SU
DTSTART;TZID=America/New_York:19970805T090000
RRULE:FREQ=WEEKLY;INTERVAL=2;COUNT=4;BYDAY=TU,SU;WKST=SU
==> (1997 EDT) August 5,17,19,31
==> (1997 EDT) August 5,17,19,31
An example where an invalid date (i.e., February 30) is ignored.
忽略无效日期（即2月30日）的示例。
DTSTART;TZID=America/New_York:20070115T090000
RRULE:FREQ=MONTHLY;BYMONTHDAY=15,30;COUNT=5
DTSTART;TZID=America/New_York:20070115T090000
RRULE:FREQ=MONTHLY;BYMONTHDAY=15,30;COUNT=5
==> (2007 EST) January 15,30 (2007 EST) February 15 (2007 EDT) March 15,30
2007年美国东部时间1月15日，30日2007年美国东部时间2月15日2007年美国东部时间3月15日，30日
The following properties specify alarm information in calendar components.
以下属性指定日历组件中的报警信息。
Property Name: ACTION
属性名称：操作
Purpose: This property defines the action to be invoked when an alarm is triggered.
用途：此属性定义触发报警时要调用的操作。
Value Type: TEXT
值类型：文本
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property MUST be specified once in a "VALARM" calendar component.
一致性：此属性必须在“VALARM”日历组件中指定一次。
Description: Each "VALARM" calendar component has a particular type of action with which it is associated. This property specifies the type of action. Applications MUST ignore alarms with x-name and iana-token values they don't recognize.
描述：每个“VALARM”日历组件都有一个与之关联的特定类型的操作。此属性指定操作的类型。应用程序必须忽略具有无法识别的x-name和iana令牌值的报警。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
action = "ACTION" actionparam ":" actionvalue CRLF
action=“action”actionparam:“actionvalue CRLF”
actionparam = *(";" other-param)
actionparam = *(";" other-param)
actionvalue = "AUDIO" / "DISPLAY" / "EMAIL"
/ iana-token / x-name
actionvalue = "AUDIO" / "DISPLAY" / "EMAIL"
/ iana-token / x-name
Example: The following are examples of this property in a "VALARM" calendar component:
示例：以下是“VALARM”日历组件中此属性的示例：
ACTION:AUDIO
行动：音频
ACTION:DISPLAY
行动：显示
Property Name: REPEAT
属性名称：重复
Purpose: This property defines the number of times the alarm should be repeated, after the initial trigger.
用途：此属性定义初始触发后应重复报警的次数。
Value Type: INTEGER
值类型：整数
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property can be specified in a "VALARM" calendar component.
一致性：可以在“VALARM”日历组件中指定此属性。
Description: This property defines the number of times an alarm should be repeated after its initial trigger. If the alarm triggers more than once, then this property MUST be specified along with the "DURATION" property.
描述：此属性定义警报在初始触发后应重复的次数。如果报警触发多次，则必须将此属性与“DURATION”属性一起指定。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
repeat = "REPEAT" repparam ":" integer CRLF ;Default is "0", zero.
repeat=“repeat”repparam:“整数CRLF；默认值为“0”，零。
repparam = *(";" other-param)
repparam = *(";" other-param)
Example: The following is an example of this property for an alarm that repeats 4 additional times with a 5-minute delay after the initial triggering of the alarm:
示例：以下是警报初始触发后以5分钟延迟重复4次额外警报的此属性示例：
REPEAT:4 DURATION:PT5M
重复：4次持续时间：PT5M
Property Name: TRIGGER
属性名称：触发器
Purpose: This property specifies when an alarm will trigger.
用途：此属性指定何时触发报警。
Value Type: The default value type is DURATION. The value type can be set to a DATE-TIME value type, in which case the value MUST specify a UTC-formatted DATE-TIME value.
值类型：默认值类型为持续时间。值类型可以设置为日期时间值类型，在这种情况下，值必须指定UTC格式的日期时间值。
Property Parameters: IANA, non-standard, value data type, time zone identifier, or trigger relationship property parameters can be specified on this property. The trigger relationship property parameter MUST only be specified when the value type is "DURATION".
属性参数：可以在此属性上指定IANA、非标准、值数据类型、时区标识符或触发器关系属性参数。仅当值类型为“DURATION”时，才能指定触发器关系属性参数。
Conformance: This property MUST be specified in the "VALARM" calendar component.
一致性：必须在“VALARM”日历组件中指定此属性。
Description: This property defines when an alarm will trigger. The default value type is DURATION, specifying a relative time for the trigger of the alarm. The default duration is relative to the start of an event or to-do with which the alarm is associated. The duration can be explicitly set to trigger from either the end or the start of the associated event or to-do with the "RELATED" parameter. A value of START will set the alarm to trigger off the start of the associated event or to-do. A value of END will set the alarm to trigger off the end of the associated event or to-do.
描述：此属性定义何时触发报警。默认值类型为持续时间，指定报警触发的相对时间。默认持续时间与报警关联的事件或待办事项的开始时间相关。可以使用“RELATED”参数将持续时间显式设置为从关联事件或待办事项的结束或开始触发。START值将设置警报，以触发相关事件或待办事项的启动。END值将设置报警，以触发相关事件或待办事项的结束。
Either a positive or negative duration may be specified for the "TRIGGER" property. An alarm with a positive duration is triggered after the associated start or end of the event or to-do. An alarm with a negative duration is triggered before the associated start or end of the event or to-do.
可以为“触发器”属性指定正持续时间或负持续时间。事件或待办事项的相关开始或结束后，将触发持续时间为正的报警。在相关事件或待办事项的开始或结束之前触发持续时间为负的报警。
The "RELATED" property parameter is not valid if the value type of the property is set to DATE-TIME (i.e., for an absolute date and time alarm trigger). If a value type of DATE-TIME is specified, then the property value MUST be specified in the UTC time format. If an absolute trigger is specified on an alarm for a recurring event or to-do, then the alarm will only trigger for the specified absolute DATE-TIME, along with any specified repeating instances.
如果属性的值类型设置为日期-时间（即，对于绝对日期和时间报警触发器），则“相关”属性参数无效。如果指定了日期时间的值类型，则必须以UTC时间格式指定属性值。如果为周期性事件或待办事项在报警上指定了绝对触发器，则报警将仅在指定的绝对日期时间以及任何指定的重复实例中触发。
If the trigger is set relative to START, then the "DTSTART" property MUST be present in the associated "VEVENT" or "VTODO" calendar component. If an alarm is specified for an event with the trigger set relative to the END, then the "DTEND" property or the "DTSTART" and "DURATION " properties MUST be present in the associated "VEVENT" calendar component. If the alarm is specified for a to-do with a trigger set relative to the END, then either the "DUE" property or the "DTSTART" and "DURATION " properties MUST be present in the associated "VTODO" calendar component.
如果触发器是相对于START设置的，则“DTSTART”属性必须存在于相关的“VEVENT”或“VTODO”日历组件中。如果为触发器设置为相对于结束的事件指定了报警，则“DTEND”属性或“DTSTART”和“DURATION”属性必须出现在关联的“VEVENT”日历组件中。如果报警是针对与结束相关的触发器设置的待办事项指定的，则“到期”属性或“DTSTART”和“DURATION”属性必须出现在相关的“VTODO”日历组件中。
Alarms specified in an event or to-do that is defined in terms of a DATE value type will be triggered relative to 00:00:00 of the user's configured time zone on the specified date, or relative to 00:00:00 UTC on the specified date if no configured time zone can be found for the user. For example, if "DTSTART" is a DATE value
根据日期值类型定义的事件或待办事项中指定的报警将在指定日期相对于用户配置时区的00:00:00触发，如果找不到用户的配置时区，则在指定日期相对于UTC的00:00:00触发。例如，如果“DTSTART”是日期值
set to 19980205 then the duration trigger will be relative to 19980205T000000 America/New_York for a user configured with the America/New_York time zone.
设置为19980205，则对于配置了美国/纽约时区的用户，持续时间触发器将相对于19980205T000000美国/纽约。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
trigger = "TRIGGER" (trigrel / trigabs) CRLF
trigger=“trigger”（trigrel/trigabs）CRLF
trigrel = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" "VALUE" "=" "DURATION") /
(";" trigrelparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
) ":" dur-value
trigrel = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" "VALUE" "=" "DURATION") /
(";" trigrelparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
) ":" dur-value
trigabs = *(
;
; The following is REQUIRED,
; but MUST NOT occur more than once.
;
(";" "VALUE" "=" "DATE-TIME") /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
) ":" date-time
trigabs = *(
;
; The following is REQUIRED,
; but MUST NOT occur more than once.
;
(";" "VALUE" "=" "DATE-TIME") /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
) ":" date-time
Example: A trigger set 15 minutes prior to the start of the event or to-do.
示例：事件或待办事项开始前15分钟设置的触发器。
TRIGGER:-PT15M
触发器：-PT15M
A trigger set five minutes after the end of an event or the due date of a to-do.
事件结束或待办事项到期日五分钟后设置的触发器。
TRIGGER;RELATED=END:PT5M
TRIGGER;RELATED=END:PT5M
A trigger set to an absolute DATE-TIME.
设置为绝对日期时间的触发器。
TRIGGER;VALUE=DATE-TIME:19980101T050000Z
TRIGGER;VALUE=DATE-TIME:19980101T050000Z
The following properties specify change management information in calendar components.
以下属性指定日历组件中的更改管理信息。
Property Name: CREATED
属性名称：已创建
Purpose: This property specifies the date and time that the calendar information was created by the calendar user agent in the calendar store.
用途：此属性指定日历用户代理在日历存储中创建日历信息的日期和时间。
Note: This is analogous to the creation date and time for a file in the file system.
注意：这类似于文件系统中文件的创建日期和时间。
Value Type: DATE-TIME
值类型：日期时间
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: The property can be specified once in "VEVENT", "VTODO", or "VJOURNAL" calendar components. The value MUST be specified as a date with UTC time.
一致性：该属性可以在“VEVENT”、“VTODO”或“VJOURNAL”日历组件中指定一次。该值必须指定为具有UTC时间的日期。
Description: This property specifies the date and time that the calendar information was created by the calendar user agent in the calendar store.
描述：此属性指定日历用户代理在日历存储中创建日历信息的日期和时间。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
created = "CREATED" creaparam ":" date-time CRLF
created=“created”creaparam:“日期时间CRLF”
creaparam = *(";" other-param)
creaparam = *(";" other-param)
Example: The following is an example of this property:
示例：以下是此属性的示例：
CREATED:19960329T133000Z
创建日期：19960329T133000Z
Property Name: DTSTAMP
物业名称：DTSTAMP
Purpose: In the case of an iCalendar object that specifies a "METHOD" property, this property specifies the date and time that the instance of the iCalendar object was created. In the case of an iCalendar object that doesn't specify a "METHOD" property, this property specifies the date and time that the information associated with the calendar component was last revised in the calendar store.
用途：对于指定“方法”属性的iCalendar对象，此属性指定创建iCalendar对象实例的日期和时间。对于未指定“方法”属性的iCalendar对象，此属性指定与日历组件关联的信息上次在日历存储中修改的日期和时间。
Value Type: DATE-TIME
值类型：日期时间
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property MUST be included in the "VEVENT", "VTODO", "VJOURNAL", or "VFREEBUSY" calendar components.
一致性：此属性必须包含在“VEVENT”、“VTODO”、“VJOURNAL”或“VFREEBUSY”日历组件中。
Description: The value MUST be specified in the UTC time format.
说明：必须以UTC时间格式指定该值。
This property is also useful to protocols such as [2447bis] that have inherent latency issues with the delivery of content. This property will assist in the proper sequencing of messages containing iCalendar objects.
此属性对于[2447bis]等协议也很有用，这些协议在内容交付时存在固有的延迟问题。此属性将有助于对包含iCalendar对象的消息进行正确排序。
In the case of an iCalendar object that specifies a "METHOD" property, this property differs from the "CREATED" and "LAST-MODIFIED" properties. These two properties are used to specify when the particular calendar data in the calendar store was created and last modified. This is different than when the iCalendar object representation of the calendar service information was created or last modified.
对于指定“方法”属性的iCalendar对象，此属性不同于“已创建”和“上次修改”属性。这两个属性用于指定日历存储中特定日历数据的创建时间和上次修改时间。这与创建或上次修改日历服务信息的iCalendar对象表示时不同。
In the case of an iCalendar object that doesn't specify a "METHOD" property, this property is equivalent to the "LAST-MODIFIED" property.
对于未指定“方法”属性的iCalendar对象，此属性等同于“上次修改”属性。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
dtstamp = "DTSTAMP" stmparam ":" date-time CRLF
dtstamp=“dtstamp”stmparam:“日期时间CRLF”
stmparam = *(";" other-param)
stmparam = *(";" other-param)
Example:
例子：
DTSTAMP:19971210T080000Z
DTSTAMP:19971210T0800000Z
Property Name: LAST-MODIFIED
属性名称：上次修改
Purpose: This property specifies the date and time that the information associated with the calendar component was last revised in the calendar store.
用途：此属性指定上次在日历存储中修改与日历组件关联的信息的日期和时间。
Note: This is analogous to the modification date and time for a file in the file system.
注意：这类似于文件系统中文件的修改日期和时间。
Value Type: DATE-TIME
值类型：日期时间
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: This property can be specified in the "VEVENT", "VTODO", "VJOURNAL", or "VTIMEZONE" calendar components.
一致性：可以在“VEVENT”、“VTODO”、“VJOURNAL”或“VTIMEZONE”日历组件中指定此属性。
Description: The property value MUST be specified in the UTC time format.
说明：必须以UTC时间格式指定属性值。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
last-mod = "LAST-MODIFIED" lstparam ":" date-time CRLF
last mod=“last-MODIFIED”lstparam:“日期时间CRLF”
lstparam = *(";" other-param)
lstparam = *(";" other-param)
Example: The following is an example of this property:
示例：以下是此属性的示例：
LAST-MODIFIED:19960817T133000Z
最后修改：19960817T133000Z
Property Name: SEQUENCE
属性名称：序列
Purpose: This property defines the revision sequence number of the calendar component within a sequence of revisions.
用途：此属性定义修订序列中日历组件的修订序列号。
Value Type: INTEGER
值类型：整数
Property Parameters: IANA and non-standard property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA和非标准属性参数。
Conformance: The property can be specified in "VEVENT", "VTODO", or "VJOURNAL" calendar component.
一致性：该属性可以在“VEVENT”、“VTODO”或“VJOURNAL”日历组件中指定。
Description: When a calendar component is created, its sequence number is 0. It is monotonically incremented by the "Organizer's" CUA each time the "Organizer" makes a significant revision to the calendar component.
描述：创建日历组件时，其序列号为0。每次“组织者”对日历组件进行重大修改时，“组织者”的CUA都会单调递增。
The "Organizer" includes this property in an iCalendar object that it sends to an "Attendee" to specify the current version of the calendar component.
“组织者”将此属性包含在iCalendar对象中，该对象发送给“与会者”以指定日历组件的当前版本。
The "Attendee" includes this property in an iCalendar object that it sends to the "Organizer" to specify the version of the calendar component to which the "Attendee" is referring.
“与会者”将此属性包含在iCalendar对象中，该对象发送给“组织者”，以指定“与会者”所引用的日历组件的版本。
A change to the sequence number is not the mechanism that an "Organizer" uses to request a response from the "Attendees". The "RSVP" parameter on the "ATTENDEE" property is used by the "Organizer" to indicate that a response from the "Attendees" is requested.
更改序列号不是“组织者”请求“与会者”响应的机制。“组织者”使用“与会者”属性上的“RSVP”参数表示请求“与会者”的响应。
Recurrence instances of a recurring component MAY have different sequence numbers.
周期性组件的周期性实例可能具有不同的序列号。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
seq = "SEQUENCE" seqparam ":" integer CRLF ; Default is "0"
seq=“SEQUENCE”seqparam:“整数CRLF；默认值为“0”
seqparam = *(";" other-param)
seqparam = *(";" other-param)
Example: The following is an example of this property for a calendar component that was just created by the "Organizer":
示例：以下是“组织者”刚刚创建的日历组件的此属性示例：
SEQUENCE:0
序列：0
The following is an example of this property for a calendar component that has been revised two different times by the "Organizer":
以下是“组织者”已修改两次的日历组件的此属性示例：
SEQUENCE:2
顺序：2
The following properties specify information about a number of miscellaneous features of calendar components.
以下属性指定有关日历组件的许多其他功能的信息。
Property Name: An IANA-registered property name
属性名称：IANA注册的属性名称
Value Type: The default value type is TEXT. The value type can be set to any value type.
值类型：默认值类型为文本。值类型可以设置为任何值类型。
Property Parameters: Any parameter can be specified on this property.
属性参数：可以在此属性上指定任何参数。
Description: This specification allows other properties registered with IANA to be specified in any calendar components. Compliant applications are expected to be able to parse these other IANA-registered properties but can ignore them.
描述：此规范允许在任何日历组件中指定向IANA注册的其他属性。合规应用程序预计能够解析这些其他IANA注册的属性，但可以忽略它们。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
iana-prop = iana-token *(";" icalparameter) ":" value CRLF
iana-prop = iana-token *(";" icalparameter) ":" value CRLF
Example: The following are examples of properties that might be registered to IANA:
示例：以下是可能注册到IANA的属性示例：
DRESSCODE:CASUAL
着装规范：休闲
NON-SMOKING;VALUE=BOOLEAN:TRUE
NON-SMOKING;VALUE=BOOLEAN:TRUE
Property Name: Any property name with a "X-" prefix
属性名称：任何带有“X-”前缀的属性名称
Purpose: This class of property provides a framework for defining non-standard properties.
用途：此类属性提供了定义非标准属性的框架。
Value Type: The default value type is TEXT. The value type can be set to any value type.
值类型：默认值类型为文本。值类型可以设置为任何值类型。
Property Parameters: IANA, non-standard, and language property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准和语言属性参数。
Conformance: This property can be specified in any calendar component.
一致性：此属性可以在任何日历组件中指定。
Description: The MIME Calendaring and Scheduling Content Type provides a "standard mechanism for doing non-standard things". This extension support is provided for implementers to "push the envelope" on the existing version of the memo. Extension properties are specified by property and/or property parameter
说明：MIME日历和日程安排内容类型提供了“执行非标准操作的标准机制”。这种扩展支持是为实现者在现有版本的备忘录上“推动信封”而提供的。扩展属性由属性和/或属性参数指定
names that have the prefix text of "X-" (the two-character sequence: LATIN CAPITAL LETTER X character followed by the HYPHEN-MINUS character). It is recommended that vendors concatenate onto this sentinel another short prefix text to identify the vendor. This will facilitate readability of the extensions and minimize possible collision of names between different vendors. User agents that support this content type are expected to be able to parse the extension properties and property parameters but can ignore them.
前缀文本为“X-”的名称（两个字符序列：拉丁文大写字母X，后跟连字符减号）。建议供应商将另一个短前缀文本连接到此sentinel上，以标识供应商。这将促进扩展的可读性，并最大限度地减少不同供应商之间可能的名称冲突。支持此内容类型的用户代理应该能够解析扩展属性和属性参数，但可以忽略它们。
At present, there is no registration authority for names of extension properties and property parameters. The value type for this property is TEXT. Optionally, the value type can be any of the other valid value types.
目前，没有扩展属性名称和属性参数的注册机构。此属性的值类型为文本。或者，值类型可以是任何其他有效值类型。
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
x-prop = x-name *(";" icalparameter) ":" value CRLF
x-prop = x-name *(";" icalparameter) ":" value CRLF
Example: The following might be the ABC vendor's extension for an audio-clip form of subject property:
示例：以下可能是ABC供应商对主题属性的音频剪辑表单的扩展：
X-ABC-MMSUBJ;VALUE=URI;FMTTYPE=audio/basic:http://www.example.
org/mysubj.au
X-ABC-MMSUBJ;VALUE=URI;FMTTYPE=audio/basic:http://www.example.
org/mysubj.au
Property Name: REQUEST-STATUS
属性名称：请求状态
Purpose: This property defines the status code returned for a scheduling request.
用途：此属性定义为计划请求返回的状态代码。
Value Type: TEXT
值类型：文本
Property Parameters: IANA, non-standard, and language property parameters can be specified on this property.
属性参数：可以在此属性上指定IANA、非标准和语言属性参数。
Conformance: The property can be specified in the "VEVENT", "VTODO", "VJOURNAL", or "VFREEBUSY" calendar component.
一致性：可以在“VEVENT”、“VTODO”、“VJOURNAL”或“VFREEBUSY”日历组件中指定该属性。
Description: This property is used to return status code information related to the processing of an associated iCalendar object. The value type for this property is TEXT.
描述：此属性用于返回与处理关联iCalendar对象相关的状态代码信息。此属性的值类型为文本。
The value consists of a short return status component, a longer return status description component, and optionally a status-specific data component. The components of the value are separated by the SEMICOLON character.
该值由一个简短的返回状态组件、一个较长的返回状态描述组件和一个特定于状态的数据组件（可选）组成。值的组成部分由分号字符分隔。
The short return status is a PERIOD character separated pair or 3-tuple of integers. For example, "3.1" or "3.1.1". The successive levels of integers provide for a successive level of status code granularity.
短返回状态是周期字符分隔的整数对或3元组。例如，“3.1”或“3.1.1”。连续级别的整数提供了连续级别的状态代码粒度。
The following are initial classes for the return status code. Individual iCalendar object methods will define specific return status codes for these classes. In addition, other classes for the return status code may be defined using the registration process defined later in this memo.
以下是返回状态代码的初始类。个别iCalendar对象方法将为这些类定义特定的返回状态代码。此外，还可以使用本备忘录后面定义的注册流程定义退货状态代码的其他类。
+--------+----------------------------------------------------------+
| Short | Longer Return Status Description |
| Return | |
| Status | |
| Code | |
+--------+----------------------------------------------------------+
| 1.xx | Preliminary success. This class of status code |
| | indicates that the request has been initially processed |
| | but that completion is pending. |
| | |
| 2.xx | Successful. This class of status code indicates that |
| | the request was completed successfully. However, the |
| | exact status code can indicate that a fallback has been |
| | taken. |
| | |
| 3.xx | Client Error. This class of status code indicates that |
| | the request was not successful. The error is the result |
| | of either a syntax or a semantic error in the client- |
| | formatted request. Request should not be retried until |
| | the condition in the request is corrected. |
| | |
| 4.xx | Scheduling Error. This class of status code indicates |
| | that the request was not successful. Some sort of error |
| | occurred within the calendaring and scheduling service, |
| | not directly related to the request itself. |
+--------+----------------------------------------------------------+
+--------+----------------------------------------------------------+
| Short | Longer Return Status Description |
| Return | |
| Status | |
| Code | |
+--------+----------------------------------------------------------+
| 1.xx | Preliminary success. This class of status code |
| | indicates that the request has been initially processed |
| | but that completion is pending. |
| | |
| 2.xx | Successful. This class of status code indicates that |
| | the request was completed successfully. However, the |
| | exact status code can indicate that a fallback has been |
| | taken. |
| | |
| 3.xx | Client Error. This class of status code indicates that |
| | the request was not successful. The error is the result |
| | of either a syntax or a semantic error in the client- |
| | formatted request. Request should not be retried until |
| | the condition in the request is corrected. |
| | |
| 4.xx | Scheduling Error. This class of status code indicates |
| | that the request was not successful. Some sort of error |
| | occurred within the calendaring and scheduling service, |
| | not directly related to the request itself. |
+--------+----------------------------------------------------------+
Format Definition: This property is defined by the following notation:
格式定义：此属性由以下符号定义：
rstatus = "REQUEST-STATUS" rstatparam ":"
statcode ";" statdesc [";" extdata]
rstatus = "REQUEST-STATUS" rstatparam ":"
statcode ";" statdesc [";" extdata]
rstatparam = *(
;
; The following is OPTIONAL,
; but MUST NOT occur more than once.
;
(";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
rstatparam = *(
;
; The following is OPTIONAL,
; but MUST NOT occur more than once.
;
(";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
statcode = 1*DIGIT 1*2("." 1*DIGIT)
;Hierarchical, numeric return status code
statcode = 1*DIGIT 1*2("." 1*DIGIT)
;Hierarchical, numeric return status code
statdesc = text ;Textual status description
statdesc=文本；文本状态描述
extdata = text ;Textual exception data. For example, the offending property ;name and value or complete property line.
extdata=文本；文本异常数据。例如，违规财产；名称和值或完整的建筑红线。
Example: The following are some possible examples of this property.
示例：以下是此属性的一些可能示例。
The COMMA and SEMICOLON separator characters in the property value are BACKSLASH character escaped because they appear in a text value.
属性值中的逗号和分号分隔符是反斜杠字符转义的，因为它们出现在文本值中。
REQUEST-STATUS:2.0;Success
请求状态：2.0；成功
REQUEST-STATUS:3.1;Invalid property value;DTSTART:96-Apr-01
REQUEST-STATUS:3.1;Invalid property value;DTSTART:96-Apr-01
REQUEST-STATUS:2.8; Success\, repeating event ignored. Scheduled
as a single event.;RRULE:FREQ=WEEKLY\;INTERVAL=2
REQUEST-STATUS:2.8; Success\, repeating event ignored. Scheduled
as a single event.;RRULE:FREQ=WEEKLY\;INTERVAL=2
REQUEST-STATUS:4.1;Event conflict. Date-time is busy.
请求状态：4.1；事件冲突。日期时间很忙。
REQUEST-STATUS:3.7;Invalid calendar user;ATTENDEE:
mailto:jsmith@example.com
REQUEST-STATUS:3.7;Invalid calendar user;ATTENDEE:
mailto:jsmith@example.com
The following examples are provided as an informational source of illustrative iCalendar objects consistent with this content type.
以下示例作为与此内容类型一致的说明性iCalendar对象的信息源提供。
The following example specifies a three-day conference that begins at 2:30 P.M. UTC, September 18, 1996 and ends at 10:00 P.M. UTC, September 20, 1996.
以下示例指定了一个为期三天的会议，从1996年9月18日UTC下午2:30开始，到1996年9月20日UTC下午10:00结束。
BEGIN:VCALENDAR
PRODID:-//xyz Corp//NONSGML PDA Calendar Version 1.0//EN
VERSION:2.0
BEGIN:VEVENT
DTSTAMP:19960704T120000Z
UID:uid1@example.com
ORGANIZER:mailto:jsmith@example.com
DTSTART:19960918T143000Z
DTEND:19960920T220000Z
STATUS:CONFIRMED
CATEGORIES:CONFERENCE
SUMMARY:Networld+Interop Conference
DESCRIPTION:Networld+Interop Conference
and Exhibit\nAtlanta World Congress Center\n
Atlanta\, Georgia
END:VEVENT
END:VCALENDAR
BEGIN:VCALENDAR
PRODID:-//xyz Corp//NONSGML PDA Calendar Version 1.0//EN
VERSION:2.0
BEGIN:VEVENT
DTSTAMP:19960704T120000Z
UID:uid1@example.com
ORGANIZER:mailto:jsmith@example.com
DTSTART:19960918T143000Z
DTEND:19960920T220000Z
STATUS:CONFIRMED
CATEGORIES:CONFERENCE
SUMMARY:Networld+Interop Conference
DESCRIPTION:Networld+Interop Conference
and Exhibit\nAtlanta World Congress Center\n
Atlanta\, Georgia
END:VEVENT
END:VCALENDAR
The following example specifies a group-scheduled meeting that begins at 8:30 AM EST on March 12, 1998 and ends at 9:30 AM EST on March 12, 1998. The "Organizer" has scheduled the meeting with one or more calendar users in a group. A time zone specification for Eastern United States has been specified.
以下示例指定了在1998年3月12日美国东部时间上午8:30开始并在1998年3月12日美国东部时间上午9:30结束的小组计划会议。“组织者”已与组中的一个或多个日历用户安排了会议。已指定美国东部的时区规范。
BEGIN:VCALENDAR
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:STANDARD
DTSTART:19981025T020000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19990404T020000
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
BEGIN:VCALENDAR
PRODID:-//RDU Software//NONSGML HandCal//EN
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:STANDARD
DTSTART:19981025T020000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19990404T020000
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:19980309T231000Z
UID:guid-1.example.com
ORGANIZER:mailto:mrbig@example.com
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT;CUTYPE=GROUP:
mailto:employee-A@example.com
DESCRIPTION:Project XYZ Review Meeting
CATEGORIES:MEETING
CLASS:PUBLIC
CREATED:19980309T130000Z
SUMMARY:XYZ Project Review
DTSTART;TZID=America/New_York:19980312T083000
DTEND;TZID=America/New_York:19980312T093000
LOCATION:1CP Conference Room 4350
END:VEVENT
END:VCALENDAR
TZNAME:EDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:19980309T231000Z
UID:guid-1.example.com
ORGANIZER:mailto:mrbig@example.com
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT;CUTYPE=GROUP:
mailto:employee-A@example.com
DESCRIPTION:Project XYZ Review Meeting
CATEGORIES:MEETING
CLASS:PUBLIC
CREATED:19980309T130000Z
SUMMARY:XYZ Project Review
DTSTART;TZID=America/New_York:19980312T083000
DTEND;TZID=America/New_York:19980312T093000
LOCATION:1CP Conference Room 4350
END:VEVENT
END:VCALENDAR
The following is an example of an iCalendar object passed in a MIME message with a single body part consisting of a "text/calendar" Content Type.
下面是一个在MIME消息中传递的iCalendar对象的示例，其单个正文部分由“文本/日历”内容类型组成。
TO:jsmith@example.com
FROM:jdoe@example.com
MIME-VERSION:1.0
MESSAGE-ID:<id3@example.com>
CONTENT-TYPE:text/calendar; method="xyz"; component="VEVENT"
TO:jsmith@example.com
FROM:jdoe@example.com
MIME-VERSION:1.0
MESSAGE-ID:<id3@example.com>
CONTENT-TYPE:text/calendar; method="xyz"; component="VEVENT"
BEGIN:VCALENDAR
METHOD:xyz
VERSION:2.0
PRODID:-//ABC Corporation//NONSGML My Product//EN
BEGIN:VEVENT
DTSTAMP:19970324T120000Z
SEQUENCE:0
UID:uid3@example.com
ORGANIZER:mailto:jdoe@example.com
ATTENDEE;RSVP=TRUE:mailto:jsmith@example.com
DTSTART:19970324T123000Z
DTEND:19970324T210000Z
CATEGORIES:MEETING,PROJECT
CLASS:PUBLIC
SUMMARY:Calendaring Interoperability Planning Meeting
DESCRIPTION:Discuss how we can test c&s interoperability\n
using iCalendar and other IETF standards.
LOCATION:LDB Lobby
BEGIN:VCALENDAR
METHOD:xyz
VERSION:2.0
PRODID:-//ABC Corporation//NONSGML My Product//EN
BEGIN:VEVENT
DTSTAMP:19970324T120000Z
SEQUENCE:0
UID:uid3@example.com
ORGANIZER:mailto:jdoe@example.com
ATTENDEE;RSVP=TRUE:mailto:jsmith@example.com
DTSTART:19970324T123000Z
DTEND:19970324T210000Z
CATEGORIES:MEETING,PROJECT
CLASS:PUBLIC
SUMMARY:Calendaring Interoperability Planning Meeting
DESCRIPTION:Discuss how we can test c&s interoperability\n
using iCalendar and other IETF standards.
LOCATION:LDB Lobby
ATTACH;FMTTYPE=application/postscript:ftp://example.com/pub/
conf/bkgrnd.ps
END:VEVENT
END:VCALENDAR
ATTACH;FMTTYPE=application/postscript:ftp://example.com/pub/
conf/bkgrnd.ps
END:VEVENT
END:VCALENDAR
The following is an example of a to-do due on April 15, 1998. An audio alarm has been specified to remind the calendar user at noon, the day before the to-do is expected to be completed and repeat hourly, four additional times. The to-do definition has been modified twice since it was initially created.
以下是1998年4月15日到期的待办事项示例。已指定一个音频警报，提醒日历用户在中午，即预计完成待办事项的前一天，每小时重复四次。待办事项定义自最初创建以来已修改过两次。
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//ABC Corporation//NONSGML My Product//EN
BEGIN:VTODO
DTSTAMP:19980130T134500Z
SEQUENCE:2
UID:uid4@example.com
ORGANIZER:mailto:unclesam@example.com
ATTENDEE;PARTSTAT=ACCEPTED:mailto:jqpublic@example.com
DUE:19980415T000000
STATUS:NEEDS-ACTION
SUMMARY:Submit Income Taxes
BEGIN:VALARM
ACTION:AUDIO
TRIGGER:19980403T120000Z
ATTACH;FMTTYPE=audio/basic:http://example.com/pub/audio-
files/ssbanner.aud
REPEAT:4
DURATION:PT1H
END:VALARM
END:VTODO
END:VCALENDAR
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//ABC Corporation//NONSGML My Product//EN
BEGIN:VTODO
DTSTAMP:19980130T134500Z
SEQUENCE:2
UID:uid4@example.com
ORGANIZER:mailto:unclesam@example.com
ATTENDEE;PARTSTAT=ACCEPTED:mailto:jqpublic@example.com
DUE:19980415T000000
STATUS:NEEDS-ACTION
SUMMARY:Submit Income Taxes
BEGIN:VALARM
ACTION:AUDIO
TRIGGER:19980403T120000Z
ATTACH;FMTTYPE=audio/basic:http://example.com/pub/audio-
files/ssbanner.aud
REPEAT:4
DURATION:PT1H
END:VALARM
END:VTODO
END:VCALENDAR
The following is an example of a journal entry:
以下是日记账分录的示例：
BEGIN:VCALENDAR VERSION:2.0 PRODID:-//ABC Corporation//NONSGML My Product//EN BEGIN:VJOURNAL DTSTAMP:19970324T120000Z UID:uid5@example.com ORGANIZER:mailto:jsmith@example.com STATUS:DRAFT CLASS:PUBLIC CATEGORIES:Project Report,XYZ,Weekly Meeting DESCRIPTION:Project xyz Review Meeting Minutes\n Agenda\n1. Review of project version 1.0 requirements.\n2.
BEGIN:VCALENDAR版本：2.0 PRODID:-//ABC公司//非GML我的产品//EN BEGIN:VJOURNAL DTSTAMP:19970324T120000Z UID:uid5@example.com组织者：邮寄至：jsmith@example.com状态：草稿类：公共类别：项目报告、XYZ、周会说明：项目XYZ审核会议纪要\n议程\n1。审查项目版本1.0要求。\n2。
Definition of project processes.\n3. Review of project schedule.\n Participants: John Smith\, Jane Doe\, Jim Dandy\n-It was decided that the requirements need to be signed off by product marketing.\n-Project processes were accepted.\n -Project schedule needs to account for scheduled holidays and employee vacation time. Check with HR for specific dates.\n-New schedule will be distributed by Friday.\n-Next weeks meeting is cancelled. No meeting until 3/23. END:VJOURNAL END:VCALENDAR
Definition of project processes.\n3. Review of project schedule.\n Participants: John Smith\, Jane Doe\, Jim Dandy\n-It was decided that the requirements need to be signed off by product marketing.\n-Project processes were accepted.\n -Project schedule needs to account for scheduled holidays and employee vacation time. Check with HR for specific dates.\n-New schedule will be distributed by Friday.\n-Next weeks meeting is cancelled. No meeting until 3/23. END:VJOURNAL END:VCALENDARtranslate error, please retry
The following is an example of published busy time information. The iCalendar object might be placed in the network resource http://www.example.com/calendar/busytime/jsmith.ifb.
以下是已发布繁忙时间信息的示例。iCalendar对象可能放置在网络资源中http://www.example.com/calendar/busytime/jsmith.ifb.
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//RDU Software//NONSGML HandCal//EN
BEGIN:VFREEBUSY
ORGANIZER:mailto:jsmith@example.com
DTSTART:19980313T141711Z
DTEND:19980410T141711Z
FREEBUSY:19980314T233000Z/19980315T003000Z
FREEBUSY:19980316T153000Z/19980316T163000Z
FREEBUSY:19980318T030000Z/19980318T040000Z
URL:http://www.example.com/calendar/busytime/jsmith.ifb
END:VFREEBUSY
END:VCALENDAR
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//RDU Software//NONSGML HandCal//EN
BEGIN:VFREEBUSY
ORGANIZER:mailto:jsmith@example.com
DTSTART:19980313T141711Z
DTEND:19980410T141711Z
FREEBUSY:19980314T233000Z/19980315T003000Z
FREEBUSY:19980316T153000Z/19980316T163000Z
FREEBUSY:19980318T030000Z/19980318T040000Z
URL:http://www.example.com/calendar/busytime/jsmith.ifb
END:VFREEBUSY
END:VCALENDAR
These recommended practices should be followed in order to assure consistent handling of the following cases for an iCalendar object.
应遵循这些推荐做法，以确保对iCalendar对象的以下情况进行一致处理。
1. Content lines longer than 75 octets SHOULD be folded.
1. 长度超过75个八位字节的内容行应折叠。
2. When the combination of the "RRULE" and "RDATE" properties in a recurring component produces multiple instances having the same start DATE-TIME value, they should be collapsed to, and considered as, a single instance. If the "RDATE" property is specified as a PERIOD value the duration of the recurrence instance will be the one specified by the "RDATE" property, and not the duration of the recurrence instance defined by the "DTSTART" property.
2. 当周期性组件中的“RRULE”和“RDATE”属性组合产生具有相同开始日期时间值的多个实例时，它们应折叠为单个实例，并视为单个实例。如果将“RDATE”属性指定为期间值，则重复实例的持续时间将是由“RDATE”属性指定的持续时间，而不是由“DTSTART”属性定义的重复实例的持续时间。
3. When a calendar user receives multiple requests for the same calendar component (e.g., REQUEST for a "VEVENT" calendar
3. 当日历用户收到对同一日历组件的多个请求时（例如，对“VEVENT”日历的请求
component) as a result of being on multiple mailing lists specified by "ATTENDEE" properties in the request, they SHOULD respond to only one of the requests. The calendar user SHOULD also specify (using the "MEMBER" parameter of the "ATTENDEE" property) of which mailing list they are a member.
组件）由于在请求中的“ATTENDEE”属性指定的多个邮件列表中，他们应该只响应其中一个请求。日历用户还应指定（使用“ATTENDEE”属性的“MEMBER”参数）他们是哪个邮件列表的成员。
4. An implementation can truncate a "SUMMARY" property value to 255 octets, but it MUST NOT truncate the value in the middle of a UTF-8 multi-octet sequence.
4. 实现可以将“摘要”属性值截断到255个八位字节，但是它不能截断UTF-8多八位字节序列中间的值。
5. If seconds of the minute are not supported by an implementation, then a value of "00" SHOULD be specified for the seconds component in a time value.
5. 如果实现不支持每分钟秒数，则应在时间值中为秒组件指定值“00”。
6. "TZURL" values SHOULD NOT be specified as a file URI type. This URI form can be useful within an organization, but is problematic in the Internet.
6. “TZURL”值不应指定为文件URI类型。此URI表单在组织中可能很有用，但在Internet中存在问题。
7. Some possible English values for "CATEGORIES" property include: "ANNIVERSARY", "APPOINTMENT", "BUSINESS", "EDUCATION", "HOLIDAY", "MEETING", "MISCELLANEOUS", "NON-WORKING HOURS", "NOT IN OFFICE", "PERSONAL", "PHONE CALL", "SICK DAY", "SPECIAL OCCASION", "TRAVEL", "VACATION". Categories can be specified in any registered language.
7. “类别”物业的一些可能英文值包括：“周年”、“约会”、“商务”、“教育”、“假日”、“会议”、“杂项”、“非工作时间”、“不在办公室”、“私人”、“电话”、“病假”、“特殊场合”、“旅行”、“度假”。类别可以用任何注册语言指定。
8. Some possible English values for the "RESOURCES" property include: "CATERING", "CHAIRS", "COMPUTER PROJECTOR", "EASEL", "OVERHEAD PROJECTOR", "SPEAKER PHONE", "TABLE", "TV", "VCR", "VIDEO PHONE", "VEHICLE". Resources can be specified in any registered language.
8. “资源”物业可能的英文价值包括：“餐饮”、“椅子”、“电脑投影仪”、“画架”、“投影仪”、“扬声器电话”、“桌子”、“电视”、“录像机”、“视频电话”、“车辆”。可以用任何注册语言指定资源。
Applications MUST generate iCalendar streams in the UTF-8 charset and MUST accept an iCalendar stream in the UTF-8 or US-ASCII charset.
应用程序必须在UTF-8字符集中生成iCalendar流，并且必须接受UTF-8或US-ASCII字符集中的iCalendar流。
Because calendaring and scheduling information is very privacy-sensitive, the protocol used for the transmission of calendaring and scheduling information should have capabilities to protect the information from possible threats, such as eavesdropping, replay, message insertion, deletion, modification, and man-in-the-middle attacks.
由于日历和日程安排信息对隐私非常敏感，因此用于传输日历和日程安排信息的协议应该能够保护信息免受可能的威胁，如窃听、重播、消息插入、删除、修改和中间人攻击。
As this document only defines the data format and media type of text/ calendar that is independent of any calendar service or protocol, it is up to the actual protocol specifications such as iTIP [2446bis],
由于本文件仅定义独立于任何日历服务或协议的文本/日历的数据格式和媒体类型，因此它取决于实际的协议规范，如iTIP[2446bis]，
iMIP [2447bis], and "Calendaring Extensions to WebDAV (CalDAV)" [RFC4791] to describe the threats that the above attacks present, as well as ways in which to mitigate them.
iMIP[2447bis]和“WebDAV日历扩展（CalDAV）”[RFC4791]描述了上述攻击所带来的威胁，以及缓解这些威胁的方法。
The Calendaring and Scheduling Core Object Specification is intended for use as a MIME content type.
日历和调度核心对象规范旨在用作MIME内容类型。
To: ietf-types@iana.org
致：ietf-types@iana.org
Subject: Registration of media type text/calendar
主题：媒体类型文本/日历的注册
Type name: text
类型名称：text
Subtype name: calendar
子类型名称：日历
Required parameters: none
所需参数：无
Optional parameters: charset, method, component, and optinfo
可选参数：字符集、方法、组件和optinfo
The "charset" parameter is defined in [RFC2046] for subtypes of the "text" media type. It is used to indicate the charset used in the body part. The charset supported by this revision of iCalendar is UTF-8. The use of any other charset is deprecated by this revision of iCalendar; however, note that this revision requires that compliant applications MUST accept iCalendar streams using either the UTF-8 or US-ASCII charset.
[RFC2046]中为“文本”媒体类型的子类型定义了“字符集”参数。它用于指示身体部位中使用的字符集。此版本iCalendar支持的字符集为UTF-8。此版本的iCalendar不推荐使用任何其他字符集；但是，请注意，此版本要求兼容应用程序必须接受使用UTF-8或US-ASCII字符集的iCalendar流。
The "method" parameter is used to convey the iCalendar object method or transaction semantics for the calendaring and scheduling information. It also is an identifier for the restricted set of properties and values of which the iCalendar object consists. The parameter is to be used as a guide for applications interpreting the information contained within the body part. It SHOULD NOT be used to exclude or require particular pieces of information unless the identified method definition specifically calls for this behavior. Unless specifically forbidden by a particular method definition, a text/calendar content type can contain any set of properties permitted by the Calendaring and Scheduling Core Object Specification. The "method" parameter MUST be specified and MUST be set to the same value as the "METHOD" component property of the iCalendar objects of the iCalendar stream if and only if the iCalendar objects in the iCalendar stream all have a "METHOD" component property set to the same value.
“method”参数用于传递日历和调度信息的iCalendar对象方法或事务语义。它也是iCalendar对象所包含的一组受限属性和值的标识符。该参数将用作应用程序解释身体部位中包含的信息的指南。除非已标识的方法定义专门调用此行为，否则不应使用它来排除或要求特定的信息。除非特定方法定义明确禁止，否则文本/日历内容类型可以包含日历和调度核心对象规范允许的任何属性集。当且仅当iCalendar流中的iCalendar对象都具有设置为相同值的“方法”组件属性时，必须指定“方法”参数，并将其设置为与iCalendar流的iCalendar对象的“方法”组件属性相同的值。
The value for the "method" parameter is defined as follows:
“方法”参数的值定义如下：
method = 1*(ALPHA / DIGIT / "-")
; IANA-registered iCalendar object method
method = 1*(ALPHA / DIGIT / "-")
; IANA-registered iCalendar object method
The "component" parameter conveys the type of iCalendar calendar component within the body part. If the iCalendar object contains more than one calendar component type, then multiple component parameters MUST be specified.
“component”参数表示身体部位内iCalendar日历组件的类型。如果iCalendar对象包含多个日历组件类型，则必须指定多个组件参数。
The value for the "component" parameter is defined as follows:
“组件”参数的值定义如下：
component = "VEVENT"
/ "VTODO"
/ "VJOURNAL"
/ "VFREEBUSY"
/ "VTIMEZONE"
/ iana-token
/ x-name
component = "VEVENT"
/ "VTODO"
/ "VJOURNAL"
/ "VFREEBUSY"
/ "VTIMEZONE"
/ iana-token
/ x-name
The "optinfo" parameter conveys optional information about the iCalendar object within the body part. This parameter can only specify semantics already specified by the iCalendar object and that can be otherwise determined by parsing the body part. In addition, the optional information specified by this parameter MUST be consistent with that information specified by the iCalendar object. For example, it can be used to convey the "Attendee" response status to a meeting request. The parameter value consists of a string value.
“optinfo”参数传递身体部位内iCalendar对象的可选信息。此参数只能指定iCalendar对象已经指定的语义，并且可以通过解析身体部位来确定语义。此外，此参数指定的可选信息必须与iCalendar对象指定的信息一致。例如，它可用于向会议请求传达“与会者”响应状态。参数值由字符串值组成。
The parameter can be specified multiple times.
可以多次指定该参数。
The value for the "optinfo" parameter is defined as follows:
“optinfo”参数的值定义如下：
optinfo = infovalue / qinfovalue
optinfo = infovalue / qinfovalue
infovalue = iana-token / x-name
infovalue = iana-token / x-name
qinfovalue = DQUOTE (infovalue) DQUOTE
qinfovalue=DQUOTE（信息值）DQUOTE
Encoding considerations: This media type can contain 8bit characters, so the use of quoted-printable or base64 MIME Content-Transfer-Encodings might be necessary when iCalendar objects are transferred across protocols restricted to the 7bit repertoire. Note that a text valued property in the content entity can also have content encoding of special characters using a BACKSLASH character escapement technique. This means that content values can end up being encoded twice.
编码注意事项：此媒体类型可以包含8位字符，因此，当iCalendar对象通过仅限于7位指令集的协议传输时，可能需要使用带引号的可打印或base64 MIME内容传输编码。请注意，内容实体中的文本值属性还可以使用反斜杠字符转义技术对特殊字符进行内容编码。这意味着内容值最终可能会被编码两次。
Security considerations: See Section 7.
安全注意事项：见第7节。
Interoperability considerations: This media type is intended to define a common format for conveying calendaring and scheduling information between different systems. It is heavily based on the earlier [VCAL] industry specification.
互操作性注意事项：此媒体类型旨在定义用于在不同系统之间传输日历和日程安排信息的通用格式。它主要基于早期的[VCAL]行业规范。
Published specification: This specification.
已发布规范：本规范。
Applications that use this media type: This media type is designed for widespread use by Internet calendaring and scheduling applications. In addition, applications in the workflow and document management area might find this content-type applicable. The iTIP [2446bis], iMIP [2447bis], and CalDAV [RFC4791] Internet protocols directly use this media type also.
使用此媒体类型的应用程序：此媒体类型是为Internet日历和日程安排应用程序广泛使用而设计的。此外，工作流和文档管理区域中的应用程序可能会发现此内容类型适用。iTIP[2446bis]、iMIP[2447bis]和CalDAV[RFC4791]互联网协议也直接使用这种媒体类型。
Additional information:
其他信息：
Magic number(s): None.
幻数：无。
File extension(s): The file extension of "ics" is to be used to designate a file containing (an arbitrary set of) calendaring and scheduling information consistent with this MIME content type.
文件扩展名：“ics”的文件扩展名用于指定包含与此MIME内容类型一致的（任意一组）日历和日程安排信息的文件。
The file extension of "ifb" is to be used to designate a file containing free or busy time information consistent with this MIME content type.
“ifb”的文件扩展名用于指定包含与此MIME内容类型一致的忙/闲时间信息的文件。
Macintosh file type code(s): The file type code of "iCal" is to be used in Apple MacIntosh operating system environments to designate a file containing calendaring and scheduling information consistent with this MIME media type.
Macintosh文件类型代码：“iCal”的文件类型代码将在Apple Macintosh操作系统环境中用于指定包含与此MIME媒体类型一致的日历和日程安排信息的文件。
The file type code of "iFBf" is to be used in Apple MacIntosh operating system environments to designate a file containing free or busy time information consistent with this MIME media type.
文件类型代码“iFBf”将在Apple MacIntosh操作系统环境中使用，以指定包含与此MIME媒体类型一致的忙/闲时间信息的文件。
Person & email address to contact for further information: See the "Author's Address" section of this document.
联系人和电子邮件地址以了解更多信息：请参阅本文档的“作者地址”部分。
Intended usage: COMMON
预期用途：普通
Restrictions on usage: There are no restrictions on where this media type can be used.
使用限制：此媒体类型的使用位置没有限制。
Author: See the "Author's Address" section of this document.
作者：请参阅本文件的“作者地址”部分。
Change controller: IETF
更改控制器：IETF
This section defines the process to register new or modified iCalendar elements, that is, components, properties, parameters, value data types, and values, with IANA.
本节定义了使用IANA注册新的或修改的iCalendar元素（即组件、属性、参数、值数据类型和值）的过程。
The IETF will create a mailing list, icalendar@ietf.org, which can be used for public discussion of iCalendar elements proposals prior to registration. Use of the mailing list is strongly encouraged. The IESG will appoint a designated expert who will monitor the icalendar@ietf.org mailing list and review registrations.
IETF将创建一个邮件列表，icalendar@ietf.org，可用于在注册前公开讨论iCalendar元素提案。强烈鼓励使用邮件列表。IESG将任命一名指定专家，负责监督icalendar@ietf.org邮件列表和审查注册。
Registration of new iCalendar 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, as well as for the registration of participation status values to be used in "VEVENT" calendar components. A Standards Track RFC is also REQUIRED for registration of iCalendar elements that modify iCalendar elements previously documented in a Standards Track RFC.
新iCalendar元件的注册必须由指定专家审查，并在RFC中公布。注册修改现有属性的新值数据类型以及注册要在“VEVENT”日历组件中使用的参与状态值需要标准跟踪RFC。对于修改先前记录在标准跟踪RFC中的iCalendar元素的iCalendar元素的注册，还需要标准跟踪RFC。
The registration procedure begins when a completed registration template, defined in the sections below, is sent to icalendar@ietf.org and iana@iana.org. The designated expert is expected to tell IANA and the submitter of the registration within two weeks 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.
当以下各节中定义的已完成注册模板发送到时，注册过程开始icalendar@ietf.org和iana@iana.org. 指定专家应在两周内告知IANA和注册提交人注册是否被批准、批准时有微小变更还是有理由拒绝。当有理由拒绝注册时，如果原因中列出的问题得到解决，则可以重新提交注册。指定专家做出的决定可向IESG应用领域总监提出上诉，然后再向IESG提出上诉。他们遵循IESG裁决的正常上诉程序。
A component is defined by completing the following template.
通过完成以下模板来定义组件。
Component name: The name of the component.
组件名称：组件的名称。
Purpose: The purpose of the component. Give a short but clear description.
目的：组件的目的。给出一个简短但清晰的描述。
Format definition: The ABNF for the component definition needs to be specified.
格式定义：需要指定组件定义的ABNF。
Description: Any special notes about the component, how it is to be used, etc.
说明：有关组件、如何使用组件等的任何特殊说明。
Example(s): One or more examples of instances of the component need to be specified.
示例：需要指定组件实例的一个或多个示例。
A property is defined by completing the following template.
属性是通过完成以下模板定义的。
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 need to be specified. The default value type also needs to be specified.
值类型：需要指定属性值的任何有效值类型。还需要指定默认值类型。
Property parameters: Any of the valid property parameters for the property MUST be specified.
属性参数：必须指定属性的任何有效属性参数。
Conformance: The calendar components in which the property can appear 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.
通过完成以下模板定义参数。
Parameter name: The name of the parameter.
参数名称：参数的名称。
Purpose: The purpose of the parameter. Give a short but clear description.
用途：参数的用途。给出一个简短但清晰的描述。
Format definition: The ABNF for the parameter definition needs to be specified.
格式定义：需要指定参数定义的ABNF。
Description: Any special notes about the parameter, how it is to be used, etc.
描述：有关参数、如何使用参数等的任何特殊说明。
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.
目的：值类型的目的。给出一个简短但清晰的描述。
Format definition: The ABNF for the value type definition needs to be specified.
格式定义：需要指定值类型定义的ABNF。
Description: Any special notes about the value type, how it is to be used, etc.
说明：有关值类型、如何使用等的任何特殊说明。
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 calendar properties and/or parameters that can take this value need to be specified.
一致性：需要指定可以接受此值的日历属性和/或参数。
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 an iCalendar value:
以下是iCalendar值注册的虚构示例：
Value: TOP-SECRET
价值：绝密
Purpose: This value is used to specify the access classification of top-secret calendar components.
用途：此值用于指定绝密日历组件的访问分类。
Conformance: This value can be used with the "CLASS" property.
一致性：该值可与“CLASS”属性一起使用。
Example(s): The following is an example of this value used with the "CLASS" property:
示例：以下是与“类”属性一起使用的此值的示例：
CLASS:TOP-SECRET
类别：绝密
The IANA created and maintains the following registries for iCalendar elements with pointers to appropriate reference documents.
IANA为iCalendar元素创建并维护以下注册表，其中包含指向适当参考文档的指针。
The following table has been used to initialize the components registry.
下表已用于初始化组件注册表。
+-----------+---------+-------------------------+
| Component | Status | Reference |
+-----------+---------+-------------------------+
| VCALENDAR | Current | RFC 5545, Section 3.4 |
| | | |
| VEVENT | Current | RFC 5545, Section 3.6.1 |
| | | |
| VTODO | Current | RFC 5545, Section 3.6.2 |
| | | |
| VJOURNAL | Current | RFC 5545, Section 3.6.3 |
| | | |
| VFREEBUSY | Current | RFC 5545, Section 3.6.4 |
| | | |
| VTIMEZONE | Current | RFC 5545, Section 3.6.5 |
| | | |
| VALARM | Current | RFC 5545, Section 3.6.6 |
| | | |
| STANDARD | Current | RFC 5545, Section 3.6.5 |
| | | |
| DAYLIGHT | Current | RFC 5545, Section 3.6.5 |
+-----------+---------+-------------------------+
+-----------+---------+-------------------------+
| Component | Status | Reference |
+-----------+---------+-------------------------+
| VCALENDAR | Current | RFC 5545, Section 3.4 |
| | | |
| VEVENT | Current | RFC 5545, Section 3.6.1 |
| | | |
| VTODO | Current | RFC 5545, Section 3.6.2 |
| | | |
| VJOURNAL | Current | RFC 5545, Section 3.6.3 |
| | | |
| VFREEBUSY | Current | RFC 5545, Section 3.6.4 |
| | | |
| VTIMEZONE | Current | RFC 5545, Section 3.6.5 |
| | | |
| VALARM | Current | RFC 5545, Section 3.6.6 |
| | | |
| STANDARD | Current | RFC 5545, Section 3.6.5 |
| | | |
| DAYLIGHT | Current | RFC 5545, Section 3.6.5 |
+-----------+---------+-------------------------+
The following table is has been used to initialize the properties registry.
下表用于初始化属性注册表。
+------------------+------------+----------------------------+
| Property | Status | Reference |
+------------------+------------+----------------------------+
| CALSCALE | Current | RFC 5545, Section 3.7.1 |
| METHOD | Current | RFC 5545, Section 3.7.2 |
| | | |
| PRODID | Current | RFC 5545, Section 3.7.3 |
| | | |
| VERSION | Current | RFC 5545, Section 3.7.4 |
| | | |
| ATTACH | Current | RFC 5545, Section 3.8.1.1 |
| | | |
| CATEGORIES | Current | RFC 5545, Section 3.8.1.2 |
| | | |
| CLASS | Current | RFC 5545, Section 3.8.1.3 |
| | | |
| COMMENT | Current | RFC 5545, Section 3.8.1.4 |
| | | |
| DESCRIPTION | Current | RFC 5545, Section 3.8.1.5 |
| | | |
| GEO | Current | RFC 5545, Section 3.8.1.6 |
| | | |
| LOCATION | Current | RFC 5545, Section 3.8.1.7 |
| | | |
| PERCENT-COMPLETE | Current | RFC 5545, Section 3.8.1.8 |
| | | |
| PRIORITY | Current | RFC 5545, Section 3.8.1.9 |
| | | |
| RESOURCES | Current | RFC 5545, Section 3.8.1.10 |
| | | |
| STATUS | Current | RFC 5545, Section 3.8.1.11 |
| | | |
| SUMMARY | Current | RFC 5545, Section 3.8.1.12 |
| | | |
| COMPLETED | Current | RFC 5545, Section 3.8.2.1 |
| | | |
| DTEND | Current | RFC 5545, Section 3.8.2.2 |
| | | |
| DUE | Current | RFC 5545, Section 3.8.2.3 |
| | | |
| DTSTART | Current | RFC 5545, Section 3.8.2.4 |
| | | |
| DURATION | Current | RFC 5545, Section 3.8.2.5 |
+------------------+------------+----------------------------+
| Property | Status | Reference |
+------------------+------------+----------------------------+
| CALSCALE | Current | RFC 5545, Section 3.7.1 |
| METHOD | Current | RFC 5545, Section 3.7.2 |
| | | |
| PRODID | Current | RFC 5545, Section 3.7.3 |
| | | |
| VERSION | Current | RFC 5545, Section 3.7.4 |
| | | |
| ATTACH | Current | RFC 5545, Section 3.8.1.1 |
| | | |
| CATEGORIES | Current | RFC 5545, Section 3.8.1.2 |
| | | |
| CLASS | Current | RFC 5545, Section 3.8.1.3 |
| | | |
| COMMENT | Current | RFC 5545, Section 3.8.1.4 |
| | | |
| DESCRIPTION | Current | RFC 5545, Section 3.8.1.5 |
| | | |
| GEO | Current | RFC 5545, Section 3.8.1.6 |
| | | |
| LOCATION | Current | RFC 5545, Section 3.8.1.7 |
| | | |
| PERCENT-COMPLETE | Current | RFC 5545, Section 3.8.1.8 |
| | | |
| PRIORITY | Current | RFC 5545, Section 3.8.1.9 |
| | | |
| RESOURCES | Current | RFC 5545, Section 3.8.1.10 |
| | | |
| STATUS | Current | RFC 5545, Section 3.8.1.11 |
| | | |
| SUMMARY | Current | RFC 5545, Section 3.8.1.12 |
| | | |
| COMPLETED | Current | RFC 5545, Section 3.8.2.1 |
| | | |
| DTEND | Current | RFC 5545, Section 3.8.2.2 |
| | | |
| DUE | Current | RFC 5545, Section 3.8.2.3 |
| | | |
| DTSTART | Current | RFC 5545, Section 3.8.2.4 |
| | | |
| DURATION | Current | RFC 5545, Section 3.8.2.5 |
| | | |
| FREEBUSY | Current | RFC 5545, Section 3.8.2.6 |
| | | |
| TRANSP | Current | RFC 5545, Section 3.8.2.7 |
| | | |
| TZID | Current | RFC 5545, Section 3.8.3.1 |
| | | |
| TZNAME | Current | RFC 5545, Section 3.8.3.2 |
| | | |
| TZOFFSETFROM | Current | RFC 5545, Section 3.8.3.3 |
| | | |
| TZOFFSETTO | Current | RFC 5545, Section 3.8.3.4 |
| | | |
| TZURL | Current | RFC 5545, Section 3.8.3.5 |
| | | |
| ATTENDEE | Current | RFC 5545, Section 3.8.4.1 |
| | | |
| CONTACT | Current | RFC 5545, Section 3.8.4.2 |
| | | |
| ORGANIZER | Current | RFC 5545, Section 3.8.4.3 |
| | | |
| RECURRENCE-ID | Current | RFC 5545, Section 3.8.4.4 |
| | | |
| RELATED-TO | Current | RFC 5545, Section 3.8.4.5 |
| | | |
| URL | Current | RFC 5545, Section 3.8.4.6 |
| | | |
| UID | Current | RFC 5545, Section 3.8.4.7 |
| | | |
| EXDATE | Current | RFC 5545, Section 3.8.5.1 |
| | | |
| EXRULE | Deprecated | [RFC2445], Section 4.8.5.2 |
| | | |
| RDATE | Current | RFC 5545, Section 3.8.5.2 |
| | | |
| RRULE | Current | RFC 5545, Section 3.8.5.3 |
| | | |
| ACTION | Current | RFC 5545, Section 3.8.6.1 |
| | | |
| REPEAT | Current | RFC 5545, Section 3.8.6.2 |
| | | |
| TRIGGER | Current | RFC 5545, Section 3.8.6.3 |
| | | |
| CREATED | Current | RFC 5545, Section 3.8.7.1 |
| | | |
| DTSTAMP | Current | RFC 5545, Section 3.8.7.2 |
| | | |
| LAST-MODIFIED | Current | RFC 5545, Section 3.8.7.3 |
| | | |
| FREEBUSY | Current | RFC 5545, Section 3.8.2.6 |
| | | |
| TRANSP | Current | RFC 5545, Section 3.8.2.7 |
| | | |
| TZID | Current | RFC 5545, Section 3.8.3.1 |
| | | |
| TZNAME | Current | RFC 5545, Section 3.8.3.2 |
| | | |
| TZOFFSETFROM | Current | RFC 5545, Section 3.8.3.3 |
| | | |
| TZOFFSETTO | Current | RFC 5545, Section 3.8.3.4 |
| | | |
| TZURL | Current | RFC 5545, Section 3.8.3.5 |
| | | |
| ATTENDEE | Current | RFC 5545, Section 3.8.4.1 |
| | | |
| CONTACT | Current | RFC 5545, Section 3.8.4.2 |
| | | |
| ORGANIZER | Current | RFC 5545, Section 3.8.4.3 |
| | | |
| RECURRENCE-ID | Current | RFC 5545, Section 3.8.4.4 |
| | | |
| RELATED-TO | Current | RFC 5545, Section 3.8.4.5 |
| | | |
| URL | Current | RFC 5545, Section 3.8.4.6 |
| | | |
| UID | Current | RFC 5545, Section 3.8.4.7 |
| | | |
| EXDATE | Current | RFC 5545, Section 3.8.5.1 |
| | | |
| EXRULE | Deprecated | [RFC2445], Section 4.8.5.2 |
| | | |
| RDATE | Current | RFC 5545, Section 3.8.5.2 |
| | | |
| RRULE | Current | RFC 5545, Section 3.8.5.3 |
| | | |
| ACTION | Current | RFC 5545, Section 3.8.6.1 |
| | | |
| REPEAT | Current | RFC 5545, Section 3.8.6.2 |
| | | |
| TRIGGER | Current | RFC 5545, Section 3.8.6.3 |
| | | |
| CREATED | Current | RFC 5545, Section 3.8.7.1 |
| | | |
| DTSTAMP | Current | RFC 5545, Section 3.8.7.2 |
| | | |
| LAST-MODIFIED | Current | RFC 5545, Section 3.8.7.3 |
| | | |
| SEQUENCE | Current | RFC 5545, Section 3.8.7.4 |
| | | |
| REQUEST-STATUS | Current | RFC 5545, Section 3.8.8.3 |
+------------------+------------+----------------------------+
| | | |
| SEQUENCE | Current | RFC 5545, Section 3.8.7.4 |
| | | |
| REQUEST-STATUS | Current | RFC 5545, Section 3.8.8.3 |
+------------------+------------+----------------------------+
The following table has been used to initialize the parameters registry.
下表已用于初始化参数注册表。
+----------------+---------+--------------------------+
| Parameter | Status | Reference |
+----------------+---------+--------------------------+
| ALTREP | Current | RFC 5545, Section 3.2.1 |
| | | |
| CN | Current | RFC 5545, Section 3.2.2 |
| | | |
| CUTYPE | Current | RFC 5545, Section 3.2.3 |
| | | |
| DELEGATED-FROM | Current | RFC 5545, Section 3.2.4 |
| | | |
| DELEGATED-TO | Current | RFC 5545, Section 3.2.5 |
| | | |
| DIR | Current | RFC 5545, Section 3.2.6 |
| | | |
| ENCODING | Current | RFC 5545, Section 3.2.7 |
| | | |
| FMTTYPE | Current | RFC 5545, Section 3.2.8 |
| | | |
| FBTYPE | Current | RFC 5545, Section 3.2.9 |
| | | |
| LANGUAGE | Current | RFC 5545, Section 3.2.10 |
| | | |
| MEMBER | Current | RFC 5545, Section 3.2.11 |
| | | |
| PARTSTAT | Current | RFC 5545, Section 3.2.12 |
| | | |
| RANGE | Current | RFC 5545, Section 3.2.13 |
| | | |
| RELATED | Current | RFC 5545, Section 3.2.14 |
| | | |
| RELTYPE | Current | RFC 5545, Section 3.2.15 |
| | | |
| ROLE | Current | RFC 5545, Section 3.2.16 |
| | | |
| RSVP | Current | RFC 5545, Section 3.2.17 |
| | | |
+----------------+---------+--------------------------+
| Parameter | Status | Reference |
+----------------+---------+--------------------------+
| ALTREP | Current | RFC 5545, Section 3.2.1 |
| | | |
| CN | Current | RFC 5545, Section 3.2.2 |
| | | |
| CUTYPE | Current | RFC 5545, Section 3.2.3 |
| | | |
| DELEGATED-FROM | Current | RFC 5545, Section 3.2.4 |
| | | |
| DELEGATED-TO | Current | RFC 5545, Section 3.2.5 |
| | | |
| DIR | Current | RFC 5545, Section 3.2.6 |
| | | |
| ENCODING | Current | RFC 5545, Section 3.2.7 |
| | | |
| FMTTYPE | Current | RFC 5545, Section 3.2.8 |
| | | |
| FBTYPE | Current | RFC 5545, Section 3.2.9 |
| | | |
| LANGUAGE | Current | RFC 5545, Section 3.2.10 |
| | | |
| MEMBER | Current | RFC 5545, Section 3.2.11 |
| | | |
| PARTSTAT | Current | RFC 5545, Section 3.2.12 |
| | | |
| RANGE | Current | RFC 5545, Section 3.2.13 |
| | | |
| RELATED | Current | RFC 5545, Section 3.2.14 |
| | | |
| RELTYPE | Current | RFC 5545, Section 3.2.15 |
| | | |
| ROLE | Current | RFC 5545, Section 3.2.16 |
| | | |
| RSVP | Current | RFC 5545, Section 3.2.17 |
| | | |
| SENT-BY | Current | RFC 5545, Section 3.2.18 |
| | | |
| TZID | Current | RFC 5545, Section 3.2.19 |
| | | |
| VALUE | Current | RFC 5545, Section 3.2.20 |
+----------------+---------+--------------------------+
| SENT-BY | Current | RFC 5545, Section 3.2.18 |
| | | |
| TZID | Current | RFC 5545, Section 3.2.19 |
| | | |
| VALUE | Current | RFC 5545, Section 3.2.20 |
+----------------+---------+--------------------------+
The following table has been used to initialize the value data types registry.
下表用于初始化值数据类型注册表。
+-----------------+---------+--------------------------+
| Value Data Type | Status | Reference |
+-----------------+---------+--------------------------+
| BINARY | Current | RFC 5545, Section 3.3.1 |
| | | |
| BOOLEAN | Current | RFC 5545, Section 3.3.2 |
| | | |
| CAL-ADDRESS | Current | RFC 5545, Section 3.3.3 |
| | | |
| DATE | Current | RFC 5545, Section 3.3.4 |
| | | |
| DATE-TIME | Current | RFC 5545, Section 3.3.5 |
| | | |
| DURATION | Current | RFC 5545, Section 3.3.6 |
| | | |
| FLOAT | Current | RFC 5545, Section 3.3.7 |
| | | |
| INTEGER | Current | RFC 5545, Section 3.3.8 |
| | | |
| PERIOD | Current | RFC 5545, Section 3.3.9 |
| | | |
| RECUR | Current | RFC 5545, Section 3.3.10 |
| | | |
| TEXT | Current | RFC 5545, Section 3.3.11 |
| | | |
| TIME | Current | RFC 5545, Section 3.3.12 |
| | | |
| URI | Current | RFC 5545, Section 3.3.13 |
| | | |
| UTC-OFFSET | Current | RFC 5545, Section 3.3.14 |
+-----------------+---------+--------------------------+
+-----------------+---------+--------------------------+
| Value Data Type | Status | Reference |
+-----------------+---------+--------------------------+
| BINARY | Current | RFC 5545, Section 3.3.1 |
| | | |
| BOOLEAN | Current | RFC 5545, Section 3.3.2 |
| | | |
| CAL-ADDRESS | Current | RFC 5545, Section 3.3.3 |
| | | |
| DATE | Current | RFC 5545, Section 3.3.4 |
| | | |
| DATE-TIME | Current | RFC 5545, Section 3.3.5 |
| | | |
| DURATION | Current | RFC 5545, Section 3.3.6 |
| | | |
| FLOAT | Current | RFC 5545, Section 3.3.7 |
| | | |
| INTEGER | Current | RFC 5545, Section 3.3.8 |
| | | |
| PERIOD | Current | RFC 5545, Section 3.3.9 |
| | | |
| RECUR | Current | RFC 5545, Section 3.3.10 |
| | | |
| TEXT | Current | RFC 5545, Section 3.3.11 |
| | | |
| TIME | Current | RFC 5545, Section 3.3.12 |
| | | |
| URI | Current | RFC 5545, Section 3.3.13 |
| | | |
| UTC-OFFSET | Current | RFC 5545, Section 3.3.14 |
+-----------------+---------+--------------------------+
The following table has been used to initialize the calendar user types registry.
下表已用于初始化日历用户类型注册表。
+--------------------+---------+-------------------------+
| Calendar User Type | Status | Reference |
+--------------------+---------+-------------------------+
| INDIVIDUAL | Current | RFC 5545, Section 3.2.3 |
| | | |
| GROUP | Current | RFC 5545, Section 3.2.3 |
| | | |
| RESOURCE | Current | RFC 5545, Section 3.2.3 |
| | | |
| ROOM | Current | RFC 5545, Section 3.2.3 |
| | | |
| UNKNOWN | Current | RFC 5545, Section 3.2.3 |
+--------------------+---------+-------------------------+
+--------------------+---------+-------------------------+
| Calendar User Type | Status | Reference |
+--------------------+---------+-------------------------+
| INDIVIDUAL | Current | RFC 5545, Section 3.2.3 |
| | | |
| GROUP | Current | RFC 5545, Section 3.2.3 |
| | | |
| RESOURCE | Current | RFC 5545, Section 3.2.3 |
| | | |
| ROOM | Current | RFC 5545, Section 3.2.3 |
| | | |
| UNKNOWN | Current | RFC 5545, Section 3.2.3 |
+--------------------+---------+-------------------------+
The following table has been used to initialize the free/busy time types registry.
下表已用于初始化忙/闲时间类型注册表。
+---------------------+---------+-------------------------+
| Free/Busy Time Type | Status | Reference |
+---------------------+---------+-------------------------+
| FREE | Current | RFC 5545, Section 3.2.9 |
| | | |
| BUSY | Current | RFC 5545, Section 3.2.9 |
| | | |
| BUSY-UNAVAILABLE | Current | RFC 5545, Section 3.2.9 |
| | | |
| BUSY-TENTATIVE | Current | RFC 5545, Section 3.2.9 |
+---------------------+---------+-------------------------+
+---------------------+---------+-------------------------+
| Free/Busy Time Type | Status | Reference |
+---------------------+---------+-------------------------+
| FREE | Current | RFC 5545, Section 3.2.9 |
| | | |
| BUSY | Current | RFC 5545, Section 3.2.9 |
| | | |
| BUSY-UNAVAILABLE | Current | RFC 5545, Section 3.2.9 |
| | | |
| BUSY-TENTATIVE | Current | RFC 5545, Section 3.2.9 |
+---------------------+---------+-------------------------+
The following table has been used to initialize the participation statuses registry.
下表用于初始化参与状态注册表。
+--------------------+---------+--------------------------+
| Participant Status | Status | Reference |
+--------------------+---------+--------------------------+
| NEEDS-ACTION | Current | RFC 5545, Section 3.2.12 |
| | | |
| ACCEPTED | Current | RFC 5545, Section 3.2.12 |
| | | |
| DECLINED | Current | RFC 5545, Section 3.2.12 |
| | | |
| TENTATIVE | Current | RFC 5545, Section 3.2.12 |
| | | |
| DELEGATED | Current | RFC 5545, Section 3.2.12 |
| | | |
| COMPLETED | Current | RFC 5545, Section 3.2.12 |
| | | |
| IN-PROCESS | Current | RFC 5545, Section 3.2.12 |
+--------------------+---------+--------------------------+
+--------------------+---------+--------------------------+
| Participant Status | Status | Reference |
+--------------------+---------+--------------------------+
| NEEDS-ACTION | Current | RFC 5545, Section 3.2.12 |
| | | |
| ACCEPTED | Current | RFC 5545, Section 3.2.12 |
| | | |
| DECLINED | Current | RFC 5545, Section 3.2.12 |
| | | |
| TENTATIVE | Current | RFC 5545, Section 3.2.12 |
| | | |
| DELEGATED | Current | RFC 5545, Section 3.2.12 |
| | | |
| COMPLETED | Current | RFC 5545, Section 3.2.12 |
| | | |
| IN-PROCESS | Current | RFC 5545, Section 3.2.12 |
+--------------------+---------+--------------------------+
The following table has been used to initialize the relationship types registry.
下表已用于初始化关系类型注册表。
+-------------------+---------+--------------------------+
| Relationship Type | Status | Reference |
+-------------------+---------+--------------------------+
| CHILD | Current | RFC 5545, Section 3.2.15 |
| | | |
| PARENT | Current | RFC 5545, Section 3.2.15 |
| | | |
| SIBLING | Current | RFC 5545, Section 3.2.15 |
+-------------------+---------+--------------------------+
+-------------------+---------+--------------------------+
| Relationship Type | Status | Reference |
+-------------------+---------+--------------------------+
| CHILD | Current | RFC 5545, Section 3.2.15 |
| | | |
| PARENT | Current | RFC 5545, Section 3.2.15 |
| | | |
| SIBLING | Current | RFC 5545, Section 3.2.15 |
+-------------------+---------+--------------------------+
The following table has been used to initialize the participation roles registry.
下表用于初始化参与角色注册表。
+-----------------+---------+--------------------------+
| Role Type | Status | Reference |
+-----------------+---------+--------------------------+
| CHAIR | Current | RFC 5545, Section 3.2.16 |
| | | |
| REQ-PARTICIPANT | Current | RFC 5545, Section 3.2.16 |
| | | |
| OPT-PARTICIPANT | Current | RFC 5545, Section 3.2.16 |
| | | |
| NON-PARTICIPANT | Current | RFC 5545, Section 3.2.16 |
+-----------------+---------+--------------------------+
+-----------------+---------+--------------------------+
| Role Type | Status | Reference |
+-----------------+---------+--------------------------+
| CHAIR | Current | RFC 5545, Section 3.2.16 |
| | | |
| REQ-PARTICIPANT | Current | RFC 5545, Section 3.2.16 |
| | | |
| OPT-PARTICIPANT | Current | RFC 5545, Section 3.2.16 |
| | | |
| NON-PARTICIPANT | Current | RFC 5545, Section 3.2.16 |
+-----------------+---------+--------------------------+
The following table has been used to initialize the actions registry.
下表已用于初始化操作注册表。
+-----------+------------+----------------------------+
| Action | Status | Reference |
+-----------+------------+----------------------------+
| AUDIO | Current | RFC 5545, Section 3.8.6.1 |
| | | |
| DISPLAY | Current | RFC 5545, Section 3.8.6.1 |
| | | |
| EMAIL | Current | RFC 5545, Section 3.8.6.1 |
| | | |
| PROCEDURE | Deprecated | [RFC2445], Section 4.8.6.1 |
+-----------+------------+----------------------------+
+-----------+------------+----------------------------+
| Action | Status | Reference |
+-----------+------------+----------------------------+
| AUDIO | Current | RFC 5545, Section 3.8.6.1 |
| | | |
| DISPLAY | Current | RFC 5545, Section 3.8.6.1 |
| | | |
| EMAIL | Current | RFC 5545, Section 3.8.6.1 |
| | | |
| PROCEDURE | Deprecated | [RFC2445], Section 4.8.6.1 |
+-----------+------------+----------------------------+
The following table has been used to initialize the classifications registry.
下表已用于初始化分类注册表。
+----------------+---------+---------------------------+
| Classification | Status | Reference |
+----------------+---------+---------------------------+
| PUBLIC | Current | RFC 5545, Section 3.8.1.3 |
| | | |
| PRIVATE | Current | RFC 5545, Section 3.8.1.3 |
| | | |
| CONFIDENTIAL | Current | RFC 5545, Section 3.8.1.3 |
+----------------+---------+---------------------------+
+----------------+---------+---------------------------+
| Classification | Status | Reference |
+----------------+---------+---------------------------+
| PUBLIC | Current | RFC 5545, Section 3.8.1.3 |
| | | |
| PRIVATE | Current | RFC 5545, Section 3.8.1.3 |
| | | |
| CONFIDENTIAL | Current | RFC 5545, Section 3.8.1.3 |
+----------------+---------+---------------------------+
No values are defined in this document for the "METHOD" property.
本文档中未定义“方法”属性的值。
The editor of this document wishes to thank Frank Dawson and Derik Stenerson, the original authors of RFC 2445, as well as the following individuals who have participated in the drafting, review, and discussion of this memo:
本文件编辑感谢RFC 2445的原始作者Frank Dawson和Derik Stenerson，以及参与本备忘录起草、审查和讨论的以下个人：
Joe Abley, Hervey Allen, Steve Allen, Jay Batson, Oliver Block, Stephane Bortzmeyer, Chris Bryant, Tantek Celik, Mark Crispin, Cyrus Daboo, Mike Douglass, Andrew N. Dowden, Lisa Dusseault, Lars Eggert, Gren Eliot, Pasi Eronen, Ben Fortuna, Ned Freed, Neal Gafter, Ted Hardie, Tim Hare, Jeffrey Harris, Helge Hess, Paul B. Hill, Thomas Hnetila, Russ Housley, Leif Johansson, Ciny Joy, Bruce Kahn, Reinhold Kainhofer, Martin Kiff, Patrice Lapierre, Michiel van Leeuwen, Jonathan Lennox, Jeff McCullough, Bill McQuillan, Alexey Melnikov, John W. Noerenberg II, Chuck Norris, Mark Paterson, Simon Pilette, Arnaud Quillaud, Robert Ransdell, Julian F. Reschke, Caleb Richardson, Sam Roberts, Dan Romascanu, Mike Samuel, George Sexton, Nigel Swinson, Clint Talbert, Simon Vaillancourt, Magnus Westerlund, and Sandy Wills.
Joe Abley，Hervey Allen，Steve Allen，Jay Batson，Oliver Block，Stephane Bortzmeyer，Chris Bryant，Tantek Celik，Mark Crispin，Cyrus Daboo，Mike Douglass，Andrew N.Dowden，Lisa Dusseault，Lars Eggert，Gren Eliot，Pasi Eren，Ben Fortuna，Ned Freed，Neal Gafter，Ted Hardie，Tim Hare，Jeffrey Harris，Helge Hess，Paul B.Hill，Thomas Hnetila，Russ Housley、Leif Johansson、Ciny Joy、Bruce Kahn、Reinhold Kainhofer、Martin Kiff、Patrice Lapierre、Michiel van Leeuwen、Jonathan Lennox、Jeff McCullough、Bill McQuillan、Alexey Melnikov、John W.Noerenberg II、Chuck Norris、Mark Paterson、Simon Pilette、Arnaud Quillaud、Robert Randell、Julian F.Reschke、Caleb Richardson、Sam Roberts、，Dan Romascanu、Mike Samuel、George Sexton、Nigel Swinson、Clint Talbert、Simon Vaillancourt、Magnus Westerlund和Sandy Wills。
A special thanks to the working group chairs Aki Niemi and Eliot Lear for their support and guidance.
特别感谢工作组主席Aki Niemi和Eliot Lear的支持和指导。
The editor would also like to thank the Calendaring and Scheduling Consortium for advice with this specification, and for organizing interoperability testing events to help refine it.
编辑还想感谢日历和日程安排联合会对本规范的建议，以及组织互操作性测试活动以帮助完善本规范。
[ISO.8601.2004] International Organization for Standardization, "Data elements and interchange formats -- Information interchange -- Representation of dates and times", 2004.
[ISO.8601.2004]国际标准化组织，“数据元素和交换格式——信息交换——日期和时间的表示”，2004年。
[ISO.9070.1991] International Organization for Standardization, "Information Technology_SGML Support Facilities -- Registration Procedures for Public Text Owner Identifiers, Second Edition", April 1991.
[ISO.9070.1991]国际标准化组织，“信息技术支持设施——公共文本所有者标识符的注册程序，第二版”，1991年4月。
[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月。
[RFC2368] Hoffman, P., Masinter, L., and J. Zawinski, "The mailto URL scheme", RFC 2368, July 1998.
[RFC2368]Hoffman，P.，Masinter，L.，和J.Zawinski，“邮件URL方案”，RFC 2368，1998年7月。
[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月。
[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月。
[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月。
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data Encodings", RFC 4648, October 2006.
[RFC4648]Josefsson，S.，“Base16、Base32和Base64数据编码”，RFC4648，2006年10月。
[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月。
[RFC5646] Phillips, A., Ed., and M. Davis, Ed., "Tags for Identifying Languages", BCP 47, RFC 5646, September 2009.
[RFC5646]Phillips，A.，Ed.，和M.Davis，Ed.，“识别语言的标签”，BCP 47，RFC 5646，2009年9月。
[US-ASCII] American National Standards Institute, "Coded Character Set - 7-bit American Standard Code for Information Interchange", ANSI X3.4, 1986.
[US-ASCII]美国国家标准协会，“编码字符集-信息交换用7位美国标准代码”，ANSI X3.41986。
[2446bis] Daboo, C., "iCalendar Transport-Independent Interoperability Protocol (iTIP)", Work in Progress, April 2009.
[2446bis]Daboo，C.，“iCalendar传输独立互操作性协议（iTIP）”，正在进行的工作，2009年4月。
[2447bis] Melnikov, A., "iCalendar Message-Based Interoperability Protocol (iMIP)", Work in Progress, June 2008.
[2447bis]Melnikov，A.，“iCalendar基于消息的互操作性协议（iMIP）”，正在进行的工作，2008年6月。
[ANSI INCITS 61-1986] International Committee for Information Technology, "Representation of Geographic Point Locations for Information Interchange (formerly ANSI X3.61-1986 (R1997))", ANSI INCITS 61-1986 (R2007), 2007.
[ANSI INCITS 61-1986]国际信息技术委员会，“信息交换用地理点位置的表示（原ANSI X3.61-1986（R1997）），ANSI INCITS 61-1986（R2007），2007年。
[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月。
[RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource Locators", RFC 2392, August 1998.
[RFC2392]Levinson，E.“内容ID和消息ID统一资源定位器”，RFC 2392，1998年8月。
[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月。
[RFC2445] Dawson, F. and Stenerson, D., "Internet Calendaring and Scheduling Core Object Specification (iCalendar)", RFC 2445, November 1998.
[RFC2445]Dawson，F.和Stenerson，D.，“互联网日历和调度核心对象规范（iCalendar）”，RFC 24451998年11月。
[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月。
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000.
[RFC2818]Rescorla，E.，“TLS上的HTTP”，RFC2818，2000年5月。
[RFC4516] Smith, M. and T. Howes, "Lightweight Directory Access Protocol (LDAP): Uniform Resource Locator", RFC 4516, June 2006.
[RFC4516]Smith，M.和T.Howes，“轻量级目录访问协议（LDAP）：统一资源定位器”，RFC4516，2006年6月。
[RFC4791] Daboo, C., Desruisseaux, B., and L. Dusseault, "Calendaring Extensions to WebDAV (CalDAV)", RFC 4791, March 2007.
[RFC4791]Daboo，C.，Desruisseaux，B.，和L.Dusseault，“WebDAV（CalDAV）的日历扩展”，RFC 47912007年3月。
[TZDB] Eggert, P. and A.D. Olson, "Sources for Time Zone and Daylight Saving Time Data", July 2009, <http://www.twinsun.com/tz/tz-link.htm>.
[TZDB]Eggert，P.和A.D.Olson，“时区和夏令时数据来源”，2009年7月<http://www.twinsun.com/tz/tz-link.htm>.
[VCAL] Internet Mail Consortium, "vCalendar: The Electronic Calendaring and Scheduling Exchange Format", September 1996, <http://www.imc.org/pdi/vcal-10.txt>.
[VCAL]互联网邮件联盟，“vCalendar：电子日历和日程安排交换格式”，1996年9月<http://www.imc.org/pdi/vcal-10.txt>.
This appendix contains a list of changes that have been made in the Internet Calendaring and Scheduling Core Object Specification from RFC 2445.
本附录包含RFC 2445中Internet日历和调度核心对象规范中所做更改的列表。
1. The "DTSTART" property SHOULD be synchronized with the recurrence rule, if specified.
1. 如果指定，“DTSTART”属性应与定期规则同步。
2. The "RRULE" property SHOULD NOT occur more than once in a component.
2. “RRULE”属性在组件中不应出现多次。
3. The BYHOUR, BYMINUTE, and BYSECOND rule parts MUST NOT be specified in the "RRULE" property when the "DTSTART" property is specified as a DATE value.
3. 当“DTSTART”属性指定为日期值时，不得在“RRULE”属性中指定BYHOUR、BYMINUTE和BYSECOND规则部分。
4. The value type of the "DTEND" or "DUE" properties MUST match the value type of "DTSTART" property.
4. “DTEND”或“DUE”属性的值类型必须与“DTSTART”属性的值类型匹配。
5. The "DURATION" property can no longer appear in "VFREEBUSY" components.
5. “DURATION”属性不能再出现在“VFREEBUSY”组件中。
1. The "DTSTART" and "DTEND" properties are no longer required to be specified as date with local time and time zone reference when used with a recurrence rule.
1. 与定期规则一起使用时，“DTSTART”和“DTEND”属性不再需要指定为具有本地时间和时区引用的日期。
1. The "EXRULE" property can no longer be specified in a component.
1. 无法再在组件中指定“EXRULE”属性。
2. The "THISANDPRIOR" value can no longer be used with the "RANGE" parameter.
2. “ThisandPrevior”值不能再与“RANGE”参数一起使用。
3. The "PROCEDURE" value can no longer be used with the "ACTION" property.
3. “过程”值不能再与“操作”属性一起使用。
4. The value type RECUR no longer allows multiple values to be specified by a COMMA-separated list of values.
4. 值类型RECUR不再允许由逗号分隔的值列表指定多个值。
5. x-name rule parts can no longer be specified in properties of RECUR value type (e.g., "RRULE"). x-param can be used on RECUR value type properties instead.
5. 不能再在重复值类型的属性（例如，“RRULE”）中指定x名称规则部分。x-param可以改为用于重现值类型属性。
Author's Address
作者地址
Bernard Desruisseaux (editor) Oracle Corporation 600 blvd. de Maisonneuve West Suite 1900 Montreal, QC H3A 3J2 CANADA
伯纳德·德斯鲁索（编辑）甲骨文公司600大道。de Maisonneuve West套房1900加拿大蒙特利尔QC H3A 3J2
EMail: bernard.desruisseaux@oracle.com
URI: http://www.oracle.com/
EMail: bernard.desruisseaux@oracle.com
URI: http://www.oracle.com/