Support for iCalendar Relationships
draft-ietf-calext-ical-relations-02
|
| Document |
Type |
|
Active Internet-Draft (calext WG)
|
|
Last updated |
|
2017-02-10
|
|
Replaces |
|
draft-douglass-ical-relations
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
xml
html
bibtex
|
| Stream |
WG state
|
|
WG Document
(wg milestone:
Jul 2017 - Send iCal relation d...
)
|
|
Document shepherd |
|
Philipp Kewisch
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
"Philipp Kewisch" <mozilla@kewis.ch>
|
Network Working Group M. Douglass
Internet-Draft Spherical Cow Group
Updates: 5545 (if approved) February 10, 2017
Intended status: Standards Track
Expires: August 14, 2017
Support for iCalendar Relationships
draft-ietf-calext-ical-relations-02
Abstract
This specification updates RELATED-TO defined in [RFC5545] and
introduces new iCalendar properties LINK, STRUCTURED-CATEGORY and
REFID to allow better linking and grouping of iCalendar components
and related data.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 14, 2017.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Douglass Expires August 14, 2017 [Page 1]
Internet-Draft iCalendar Relationships February 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Structured iCalendar relationships . . . . . . . . . . . 3
1.2. Grouped iCalendar relationships . . . . . . . . . . . . . 3
1.3. Structured category relationships . . . . . . . . . . . . 3
1.4. Linked relationships . . . . . . . . . . . . . . . . . . 4
1.5. Caching and offline use . . . . . . . . . . . . . . . . . 4
1.6. Conventions Used in This Document . . . . . . . . . . . . 5
2. Reference Types . . . . . . . . . . . . . . . . . . . . . . . 5
3. Link Relation Types . . . . . . . . . . . . . . . . . . . . . 5
4. Redefined Relation Type Value . . . . . . . . . . . . . . . . 5
5. New Property Parameters . . . . . . . . . . . . . . . . . . . 8
5.1. Rel . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.2. Gap . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
6. New Value Data Types . . . . . . . . . . . . . . . . . . . . 9
7. New Properties . . . . . . . . . . . . . . . . . . . . . . . 10
7.1. Structured-Category . . . . . . . . . . . . . . . . . . . 10
7.2. Link . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.3. Refid . . . . . . . . . . . . . . . . . . . . . . . . . . 13
8. Redefined RELATED-TO Property . . . . . . . . . . . . . . . . 13
8.1. RELATED-TO . . . . . . . . . . . . . . . . . . . . . . . 14
9. Security Considerations . . . . . . . . . . . . . . . . . . . 16
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
10.1. iCalendar Property Registrations . . . . . . . . . . . . 16
10.2. iCalendar Property Parameter Registrations . . . . . . . 16
10.3. iCalendar Value Data Type Registrations . . . . . . . . 16
10.4. iCalendar RELTYPE Value Registrations . . . . . . . . . 17
10.5. New Reference Type Registration . . . . . . . . . . . . 17
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17
12. Normative References . . . . . . . . . . . . . . . . . . . . 18
Appendix A. Change log . . . . . . . . . . . . . . . . . . . . . 18
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction
iCalendar entities often need to be related to each other or to
associated meta-data. These relationships can take the following
forms
Structured iCalendar: iCalendar entities are related to each other
in some structured way, for example as parent, sibling, before,
after.
Grouped iCalendar: iCalendar entities are related to each other as a
Show full document text