draft-ietf-calext-ical-relations-01.txt   draft-ietf-calext-ical-relations-02.txt 
Network Working Group M. Douglass Network Working Group M. Douglass
Internet-Draft Spherical Cow Group Internet-Draft Spherical Cow Group
Updates: 5545 (if approved) February 3, 2017 Updates: 5545 (if approved) February 10, 2017
Intended status: Standards Track Intended status: Standards Track
Expires: August 7, 2017 Expires: August 14, 2017
Support for iCalendar Relationships Support for iCalendar Relationships
draft-ietf-calext-ical-relations-01 draft-ietf-calext-ical-relations-02
Abstract Abstract
This specification updates RELATED-TO and introduces new iCalendar This specification updates RELATED-TO defined in [RFC5545] and
properties LINK, STRUCTURED-CATEGORY and REFID to allow better introduces new iCalendar properties LINK, STRUCTURED-CATEGORY and
linking and grouping of iCalendar components and related data. REFID to allow better linking and grouping of iCalendar components
and related data.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 7, 2017. This Internet-Draft will expire on August 14, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 11 skipping to change at page 2, line 11
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Structured iCalendar relationships . . . . . . . . . . . 3 1.1. Structured iCalendar relationships . . . . . . . . . . . 3
1.2. Grouped iCalendar relationships . . . . . . . . . . . . . 3 1.2. Grouped iCalendar relationships . . . . . . . . . . . . . 3
1.3. Structured category relationships . . . . . . . . . . . . 3 1.3. Structured category relationships . . . . . . . . . . . . 3
1.4. Linked relationships . . . . . . . . . . . . . . . . . . 3 1.4. Linked relationships . . . . . . . . . . . . . . . . . . 4
1.5. Caching and offline use . . . . . . . . . . . . . . . . . 4 1.5. Caching and offline use . . . . . . . . . . . . . . . . . 4
1.6. Conventions Used in This Document . . . . . . . . . . . . 4 1.6. Conventions Used in This Document . . . . . . . . . . . . 5
2. Reference Types . . . . . . . . . . . . . . . . . . . . . . . 5 2. Reference Types . . . . . . . . . . . . . . . . . . . . . . . 5
3. Link Relation Types . . . . . . . . . . . . . . . . . . . . . 5 3. Link Relation Types . . . . . . . . . . . . . . . . . . . . . 5
4. Redefined Relation Type Value . . . . . . . . . . . . . . . . 5 4. Redefined Relation Type Value . . . . . . . . . . . . . . . . 5
5. New Property Parameters . . . . . . . . . . . . . . . . . . . 8 5. New Property Parameters . . . . . . . . . . . . . . . . . . . 8
5.1. Rel . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 5.1. Rel . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.2. Gap . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.2. Gap . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
6. New Value Data Types . . . . . . . . . . . . . . . . . . . . 9 6. New Value Data Types . . . . . . . . . . . . . . . . . . . . 9
7. New Properties . . . . . . . . . . . . . . . . . . . . . . . 10 7. New Properties . . . . . . . . . . . . . . . . . . . . . . . 10
7.1. Structured-Category . . . . . . . . . . . . . . . . . . . 10 7.1. Structured-Category . . . . . . . . . . . . . . . . . . . 10
7.2. Link . . . . . . . . . . . . . . . . . . . . . . . . . . 11 7.2. Link . . . . . . . . . . . . . . . . . . . . . . . . . . 11
skipping to change at page 3, line 23 skipping to change at page 3, line 23
The RELTYPE parameter is extended to take new values defining The RELTYPE parameter is extended to take new values defining
temporal relationships, a GAP parameter is defined to provide lead temporal relationships, a GAP parameter is defined to provide lead
and lag values and RELATED-TO is extended to allow URI values. These and lag values and RELATED-TO is extended to allow URI values. These
changes allow the RELATED-TO property to define a richer set of changes allow the RELATED-TO property to define a richer set of
relationships useful for project management. relationships useful for project management.
1.2. Grouped iCalendar relationships 1.2. Grouped iCalendar relationships
This specification defines a new REFID property which allows This specification defines a new REFID property which allows
arbitrary groups of entities to be associated with the same key arbitrary groups of entities to be associated with the same key
value. The presence of a REFID property imparts no meaning to the value.
event. It is merely a key to allow retrieval.
REFID is used to identify a key allowing the association of tasks
that are related to the same object and retrieval of a task based on
this key. This may be, for example, to identify the tasks associated
with a given project without having to communicate the task structure
of the project, or, for example, in a package delivery system all
tasks associated to a specific package.
As such, the presence of a REFID property imparts no meaning to the
event. It is merely a key to allow retrieval. This is distinct from
categorisation which, while allowing grouping also adds meaning to
the entity to which it is attached.
1.3. Structured category relationships 1.3. Structured category relationships
The introduction of STRUCTURED-CATEGORY allows a more structured The introduction of STRUCTURED-CATEGORY allows a more structured
approach to categorization, with the possibility of namespaced and approach to categorization, with the possibility of namespaced and
path-like values. Unlike REFID the category imparts some meaning. path-like values. Unlike REFID the category imparts some meaning.
It is assumed that the value of this property will reference a well It is assumed that the value of this property will reference a well
defined category. defined category.
The current [RFC5545] CATEGORY property is used as a free form The current [RFC5545] CATEGORY property is used as a free form
skipping to change at page 6, line 7 skipping to change at page 6, line 7
[RFC5545]. This specification redefines that type to include the new [RFC5545]. This specification redefines that type to include the new
temporal relationship values FINISHTOSTART, FINISHTOFINISH, temporal relationship values FINISHTOSTART, FINISHTOFINISH,
STARTTOFINISH and STARTTOSTART. It also adds the DEPENDS-ON value to STARTTOFINISH and STARTTOSTART. It also adds the DEPENDS-ON value to
provide a link to a component upon which the current component provide a link to a component upon which the current component
depends. depends.
Format Definition: Format Definition:
This property parameter is defined by the following notation: This property parameter is defined by the following notation:
reltypeparam = "RELTYPE" "=" reltypeparam = "RELTYPE" "="
("PARENT" ; Parent relationship - Default ("PARENT" ; Parent relationship - Default
/ "CHILD" ; Child relationship / "CHILD" ; Child relationship
/ "SIBLING" ; Sibling relationship / "SIBLING" ; Sibling relationship
/ "DEPENDS-ON" ; refers to previous task / "DEPENDS-ON" ; refers to previous task
/ "REFID" ; Relationship based on REFID / "REFID" ; Relationship based on REFID
/ "STRUCTURED-CATEGORY" / "STRUCTURED-CATEGORY"
; Relationship based on STRUCTURED-CATEGORY ; Relationship based on STRUCTURED-CATEGORY
/ "FINISHTOSTART" ; Temporal relationship / "FINISHTOSTART" ; Temporal relationship
/ "FINISHTOFINISH" ; Temporal relationship / "FINISHTOFINISH" ; Temporal relationship
/ "STARTTOFINISH" ; Temporal relationship / "STARTTOFINISH" ; Temporal relationship
/ "STARTTOSTART" ; Temporal relationship / "STARTTOSTART" ; Temporal relationship
/ iana-token ; Some other IANA-registered / iana-token ; Some other IANA-registered
; iCalendar relationship type ; iCalendar relationship type
/ x-name) ; A non-standard, experimental / x-name) ; A non-standard, experimental
; relationship type ; relationship type
Description: This parameter can be specified on a property that Description: This parameter can be specified on a property that
references another related calendar component. The parameter may references another related calendar component. The parameter may
specify the hierarchical relationship type of the calendar specify the hierarchical relationship type of the calendar
component referenced by the property when the value is PARENT, component referenced by the property when the value is PARENT,
CHILD or SIBLING. If this parameter is not specified on an CHILD or SIBLING. If this parameter is not specified on an
allowable property, the default relationship type is PARENT. allowable property, the default relationship type is PARENT.
Applications MUST treat x-name and iana-token values they don't Applications MUST treat x-name and iana-token values they don't
recognize the same way as they would the PARENT value. recognize the same way as they would the PARENT value.
skipping to change at page 8, line 41 skipping to change at page 8, line 41
Parameter name: REL Parameter name: REL
Purpose: To specify the relationship of data referenced by a LINK Purpose: To specify the relationship of data referenced by a LINK
property. property.
Format Definition: Format Definition:
This parameter is defined by the following notation: This parameter is defined by the following notation:
relparam = "REL" "=" relparam = "REL" "="
("SOURCE" ; Link to source of this component ("SOURCE" ; Link to source of this component
/ DQUOTE uri DQUOTE / DQUOTE uri DQUOTE
/ x-name ; Experimental reference type / x-name ; Experimental reference type
/ iana-token) ; Other IANA registered type / iana-token) ; Other IANA registered type
Description: This parameter MUST be specified on all LINK Description: This parameter MUST be specified on all LINK
properties, and defines the type of reference. This allows properties, and defines the type of reference. This allows
programs consuming this data to automatically scan for references programs consuming this data to automatically scan for references
they support. In addition to the values defined here any value they support. In addition to the values defined here any value
defined in [RFC5988] may be used. There is no default relation defined in [RFC5988] may be used. There is no default relation
type. type.
skipping to change at page 11, line 7 skipping to change at page 11, line 7
for example Library of Congress, or an open source such as for example Library of Congress, or an open source such as
dmoz.org. dmoz.org.
In addition, a structured URI value allows for hierarchical In addition, a structured URI value allows for hierarchical
categorization of events. categorization of events.
Format Definition: Format Definition:
This property is defined by the following notation: This property is defined by the following notation:
structured-category = "STRUCTURED-CATEGORY" structcatparam ":" uri CRLF structured-category = "STRUCTURED-CATEGORY" structcatparam ":"
uri CRLF
structcatparam = *( structcatparam = *(
; ;
; The following is OPTIONAL, ; The following is OPTIONAL,
; and MAY occur more than once. ; and MAY occur more than once.
; ;
(";" other-param) (";" other-param)
; ;
) )
Example: Example:
The following is an example of this property. It points to a server The following is an example of this property. It points to a server
acting as the source for the calendar object. acting as the source for the calendar object.
STRUCTURED-CATEGORY:http://example.com/event-types/sports STRUCTURED-CATEGORY:http://example.com/event-types/sports
STRUCTURED-CATEGORY:http://example.com/event-types/arts/music STRUCTURED-CATEGORY:http://example.com/event-types/arts/music
STRUCTURED-CATEGORY:http://example.com/task-types/delivery STRUCTURED-CATEGORY:http://example.com/task-types/delivery
skipping to change at page 14, line 15 skipping to change at page 14, line 15
Property name: RELATED-TO Property name: RELATED-TO
Purpose: This property is used to represent a relationship or Purpose: This property is used to represent a relationship or
reference between one calendar component and another. The reference between one calendar component and another. The
definition here extends the definition in Section 3.8.4.5. of definition here extends the definition in Section 3.8.4.5. of
[RFC5545] by allowing URI or UID values and a GAP parameter. [RFC5545] by allowing URI or UID values and a GAP parameter.
Value type: URI, UID or TEXT Value type: URI, UID or TEXT
Property Parameters: Non-standard, reference type, gap, value or Property Parameters: Relationship type, IANA and non-standard
format type parameters can be specified on this property. property parameters can be specified on this property.
Conformance: This property MAY be specified in any iCalendar Conformance: This property MAY be specified in any iCalendar
component. component.
Description: By default or when VALUE=UID is specified, the property Description: By default or when VALUE=UID is specified, the property
value consists of the persistent, globally unique identifier of value consists of the persistent, globally unique identifier of
another calendar component. This value would be represented in a another calendar component. This value would be represented in a
calendar component by the "UID" property. calendar component by the "UID" property.
By default, the property value points to another calendar By default, the property value points to another calendar
skipping to change at page 18, line 17 skipping to change at page 18, line 17
[I-D.daboo-caldav-attachments] [I-D.daboo-caldav-attachments]
Daboo, C. and A. Quillaud, "CalDAV Managed Attachments", Daboo, C. and A. Quillaud, "CalDAV Managed Attachments",
draft-daboo-caldav-attachments-03 (work in progress), draft-daboo-caldav-attachments-03 (work in progress),
February 2014. February 2014.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005, RFC 3986, DOI 10.17487/RFC3986, January 2005,
<http://www.rfc-editor.org/info/rfc3986>. <http://www.rfc-editor.org/info/rfc3986>.
[RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and [RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and
Scheduling Core Object Specification (iCalendar)", Scheduling Core Object Specification (iCalendar)",
RFC 5545, DOI 10.17487/RFC5545, September 2009, RFC 5545, DOI 10.17487/RFC5545, September 2009,
<http://www.rfc-editor.org/info/rfc5545>. <http://www.rfc-editor.org/info/rfc5545>.
 End of changes. 14 change blocks. 
44 lines changed or deleted 53 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/