Support for iCalendar Relationships
draft-ietf-calext-ical-relations-06

Document Type Active Internet-Draft (calext WG)
Author Michael Douglass 
Last updated 2020-12-31
Replaces draft-douglass-ical-relations
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream WG state In WG Last Call (wg milestones: Jun 2019 - Send iCal relation d..., Dec 2020 - Submit icalendar rel... )
Document shepherd Bron Gondwana
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Bron Gondwana <brong@fastmailteam.com>
Network Working Group                                        M. Douglass
Internet-Draft                                                  Bedework
Updates: 5545 (if approved)                            December 31, 2020
Intended status: Standards Track
Expires: July 4, 2021

                  Support for iCalendar Relationships
                  draft-ietf-calext-ical-relations-06

Abstract

   This specification updates RELATED-TO defined in [RFC5545] and
   introduces new iCalendar properties LINK, CONCEPT 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 https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 4, 2021.

Copyright Notice

   Copyright (c) 2020 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
   (https://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 July 4, 2021                  [Page 1]
Internet-Draft           iCalendar Relationships           December 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Structured iCalendar relationships  . . . . . . . . . . .   3
     1.2.  Grouped iCalendar relationships . . . . . . . . . . . . .   3
     1.3.  Concept relationships . . . . . . . . . . . . . . . . . .   3
     1.4.  Linked relationships  . . . . . . . . . . . . . . . . . .   4
     1.5.  Caching and offline use . . . . . . . . . . . . . . . . .   5
     1.6.  Conventions Used in This Document . . . . . . . . . . . .   5
   2.  Reference Types . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Link Relation Types . . . . . . . . . . . . . . . . . . . . .   5
   4.  New temporal RELTYPE Parameter values . . . . . . . . . . . .   6
   5.  Additional New RELTYPE Parameter Values . . . . . . . . . . .   7
   6.  New Property Parameters . . . . . . . . . . . . . . . . . . .   8
     6.1.  Link Relation . . . . . . . . . . . . . . . . . . . . . .   8
     6.2.  Gap . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  New Value Data Types  . . . . . . . . . . . . . . . . . . . .   9
   8.  New Properties  . . . . . . . . . . . . . . . . . . . . . . .   9
     8.1.  Concept . . . . . . . . . . . . . . . . . . . . . . . . .   9
     8.2.  Link  . . . . . . . . . . . . . . . . . . . . . . . . . .  10
     8.3.  Refid . . . . . . . . . . . . . . . . . . . . . . . . . .  11
   9.  Redefined RELATED-TO Property . . . . . . . . . . . . . . . .  12
     9.1.  RELATED-TO  . . . . . . . . . . . . . . . . . . . . . . .  12
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  14
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
     11.1.  iCalendar Property Registrations . . . . . . . . . . . .  14
     11.2.  iCalendar Property Parameter Registrations . . . . . . .  15
     11.3.  iCalendar Value Data Type Registrations  . . . . . . . .  15
     11.4.  iCalendar RELTYPE Value Registrations  . . . . . . . . .  15
     11.5.  New Reference Type Registration  . . . . . . . . . . . .  16
   12. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  16
   13. Normative References  . . . . . . . . . . . . . . . . . . . .  16
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   iCalendar entities often need to be related to each other or to
   associated meta-data.  The specifications below support relationships
   of the following forms:

   Structured iCalendar:  iCalendar entities can be related to each
      other in some structured way, for example as parent, sibling,
      before, after.

   Grouped iCalendar:  iCalendar entities can be related to each other
      as a group.  CATEGORIES are often used for this purpose but are
      problematic for application developers due to their lack of
Show full document text