Improved Support for Icalendar Relationships
draft-douglass-ical-relations-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Author Mike Douglass 
Last updated 2013-07-02
Replaced by draft-ietf-calext-ical-relations
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        M. Douglass
Internet-Draft                                                       RPI
Intended status: Standards Track                           July 02, 2013
Expires: January 03, 2014

              Improved Support for Icalendar Relationships
                    draft-douglass-ical-relations-00

Abstract

   This specification updates RELATED-TO and introduces new iCalendar
   properties LINK and RELATED-ID 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 January 03, 2014.

Copyright Notice

   Copyright (c) 2013 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 January 03, 2014                [Page 1]
Internet-Draft           Icalendar Relationships               July 2013

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Structured iCalendar relationships  . . . . . . . . . . .   3
     1.2.  Grouped iCalendar relationships . . . . . . . . . . . . .   3
     1.3.  Linked relationships  . . . . . . . . . . . . . . . . . .   3
     1.4.  Conventions Used in This Document . . . . . . . . . . . .   4
   2.  Reference Types . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Link Relation Types . . . . . . . . . . . . . . . . . . . . .   4
   4.  Redefined Relation Type Value . . . . . . . . . . . . . . . .   4
   5.  New Property Parameters . . . . . . . . . . . . . . . . . . .   7
     5.1.  Rel . . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     5.2.  Gap . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.3.  Title . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   6.  New Parameter Values  . . . . . . . . . . . . . . . . . . . .   8
   7.  New Properties  . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Link  . . . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.2.  Related-id  . . . . . . . . . . . . . . . . . . . . . . .  10
   8.  Redefined RELATED-TO Property . . . . . . . . . . . . . . . .  12
     8.1.  RELATED-TO  . . . . . . . . . . . . . . . . . . . . . . .  12
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   12. Normative References  . . . . . . . . . . . . . . . . . . . .  14
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  15

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
      group.  CATEGORIES are often used for this purpose but are
      problematic for application developers.

   Linked:  Icalendar entities and non-iCalendar entities are linked to
      each other.

Douglass                Expires January 03, 2014                [Page 2]
Internet-Draft           Icalendar Relationships               July 2013

1.1.  Structured iCalendar relationships

   The currently existing iCalendar [RFC5545] RELATED-TO property has no
   support for temporal relationships as used by standard project
   management tools.

   The RELTYPE parameter is extended to take new values defining
   temporal relationships, a GAP parameter is defined to provide lead
   and lag values and RELATED-TO is extended to allow URI values.  These
   changes allows the RELATED-TO property to define a richer set of
Show full document text