© 2018 The Calendaring and Scheduling Consortium, Inc.
This document is not a CalConnect Standard. It is distributed for review and comment, and is subject to change without notice and may not be referred to as a Standard. Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from the address below.
The Calendaring and Scheduling Consortium, Inc.
4390 Chaffin Lane
McKinleyville
California 95519
United States of America
www.calconnect.org
This document updates RELATED-TO defined in
The Calendaring and Scheduling Consortium (“CalConnect”) is a global non-profit organization with the aim to facilitate interoperability of collaborative technologies and tools through open standards.
CalConnect works closely with international and regional partners, of which the full list is available on our website ().
The procedures used to develop this document and those intended for its further maintenance are described in the CalConnect Directives.
In particular the different approval criteria needed for the different types of CalConnect documents should be noted. This document was drafted in accordance with the editorial rules of the CalConnect Directives.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CalConnect shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be provided in the Introduction.
Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.
This document was prepared by Technical Committee CALENDAR.
iCalendar entities often need to be related to each other or to associated meta-data. These relationships can take the following forms
iCalendar entities are related to each other in some structured way, for example as parent, sibling, before, after.
iCalendar entities are related to each other as a group. CATEGORIES are often used for this purpose but are problematic for application developers.
Entities are linked to each other through typed references.
The currently existing iCalendar
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 allow the RELATED-TO property to define a richer set of relationships useful for project management.
This specification defines a new REFID property which allows arbitrary groups of entities to be associated with the same key value.
REFID is used to identify a key allowing the association of components that are related to the same object and retrieval of a component 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 component. It is merely a key to allow retrieval. This is distinct from categorisation which, while allowing grouping also adds meaning to the component to which it is attached.
The name CONCEPT is used by the Simple Knowledge Organization System defined in
The introduction of CONCEPT allows a more structured approach to categorization, with the possibility of namespaced and path-like values. Unlike REFID the CONCEPT property imparts some meaning. It is assumed that the value of this property will reference a well defined category.
The current
Rather than attempt to add semantics to the current property it seeems best to continue its usage as an informal tag and establish a new property with more constraints.
The currently existing iCalendar standard
This document proposes a method for referencing typed external information that can provide additional information about an iCalendar component. This new LINK property is closely aligned to the LINK header defined in
The LINK property defines a typed reference or relation to external meta-data or related resources. By providing type and format information as parameters, clients and servers are able to discover interesting references and make use of them, perhaps for indexing or the presentation of interesting links for the user.
It is often necessary to relate calendar components. The current RELATED-TO property only allows for a UID which is inadequate for many purposes. Allowing other value types for that property may help but might raise a number of backward compatibility issues. The link property can link components in different collections or even on different servers.
When publishing events it is useful to be able to refer back to the source of that information. The actual event may have been consumed from a feed or an ics file on a web site. A LINK property can provide a reference to the originator of the event.
Beyond the need to relate elements temporally, project management tools often need to be able to specify the relationships between the various events and tasks which make up a project. The LINK property provides such a mechanism.
The LINK property SHOULD NOT be treated as just another attachment. The ATTACH property is being extended to handle server-side management and stripping of inline data. Clients may choose to handle attachments differently as they are often an integral part of the message — for example, the agenda. See
To facilitate offline display the link type may identify important pieces of data which should be downloaded in advance.
In general, the calendar entity should be self explanatory without the need to download referenced meta-data such as a web page.
This specification updates RELATED-TO defined in
No terms and definitions are listed in this document.
The actual reference value can take three forms specified by the type parameter
The default type. This is a URI referring to the target.
This allows for linking within a single collection and the value is assumed to be another component within that collection.
An xpointer. In an XML environment it may be necessary to refer to an external XML artifact. The XPointer is defined in
The relation types defined here will be registered with IANA in accordance with the specifications in
Relationship parameter type values are defined in
This property parameter is defined by the following notation:
This parameter can be specified on a property that references another related calendar component. The parameter may specify the hierarchical relationship type of the calendar component referenced by the property when the value is PARENT, CHILD or SIBLING. 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.
This parameter defines the temporal relationship when the value is one of the project management standard relationships FINISHTOSTART, FINISHTOFINISH, STARTTOFINISH or STARTTOSTART. This property will be present in the predecessor entity and will refer to the successor entity. The GAP parameter specifies the lead or lag time between the predecessor and the successor. In the description of each temporal relationship below we refer to Task-A which contains and controls the relationship and Task-B the target of the relationship.
See
See
See
Indicates that the current calendar component depends on the referenced calendar component in some manner. For example a task may be blocked waiting on the other, referenced, task.
Establishes a reference from the current component to components with a REFID property which matches the value given in the associated RELATED-TO property.
Establishes a reference from the current component to components with a CONCEPT property which matches the value given in the associated RELATED-TO property.
Task-B cannot start until Task-A finishes. For example, when sanding is complete, painting can begin.
============
| Task-A |--+
============ |
|
V
============
| Task-B |
============Task-B cannot finish before Task-A is finished, that is the end of Task-A defines the end of Task-B. For example, we start the potatoes, then the meat then the peas but they should all be cooked at the same time.
============
| Task-A |--+
============ |
|
============ |
| Task-B |<-+
============The start of Task-A (which occurs after Task- B) controls the finish of Task-B. For example, ticket sales (Task-B) end when the game starts (Task-A).
============
+--| Task-A |
| ============
|
============ |
| Task-B |<-+
============The start of Task-A triggers the start of Task-B, that is Task-B can start anytime after Task-A starts.
============
+--| Task-A |
| ============
|
| ============
+->| Task-B |
============REL
To specify the relationship of data referenced by a LINK property.
This parameter is defined by the following notation:
This parameter MUST be specified on all LINK properties, and defines the type of reference. This allows programs consuming this data to automatically scan for references they support. In addition to the values defined here any value defined in
identifies the source of the event information.
These relation types are registered in
GAP
To specify the length of the gap, positive or negative between two temporaly related components.
This parameter is defined by the following notation:
This parameter MAY be specified on the RELATED-TO property, and defines the duration of time between the predecessor and successor in an interval. When positive it defines the lag time between a task and its logical successor. When negative it defines the lead time.
An example of lag time might be if task A is “paint the room” and task B is “hang the drapes” then task A may be related to task B with RELTYPE=FINISHTOSTART with a gap long enough for the paint to dry.
An example of lead time might be to relate a 1 week task A to the end of task B with RELTYPE=STARTTOFINISH and a negative gap of 1 week so they finish at the same time.
This specification defines the following new value types to be used with the VALUE property parameter:
VALUE=UID indicates that the associated value is the UID for a component.
VALUE=REFERENCE indicates that the associated value is an xpointer referencing an associated XML artifact.
CONCEPT
This property defines the formal categories for a calendar component.
URI
IANA, and non-standard parameters can be specified on this property.
This property can be specified zero or more times in any iCalendar component.
This property is used to specify formal categories or classifications of the calendar component. The values 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 formal category can be specified by using multiple CONCEPT properties.
This categorization is distinct from the more informal “tagging” of components provided by the existing CATEGORIES property. It is expected that the value of the CONCEPT property will reference an external resource which provides information about the categorization.
In addition, a structured URI value allows for hierarchical categorization of events.
Possible category resources are the various proprietary systems, for example Library of Congress, or an open source derived from something like the dmoz.org data.
This property is defined by the following notation:
The following is an example of this property. It points to a server acting as the source for the calendar object.
LINK
This property provides a reference to external information about a component.
URI, TEXT or REFERENCE
Non-standard, reference type or format type parameters can be specified on this property.
This property MAY be specified in any iCalendar component.
When used in a component the value of this property points to additional information related to the component. For example, it may reference the originating web server.
This property is defined by the following notation:
The following is an example of this property. It points to a server acting as the source for the calendar object.
REFID
This property value acts as a key for associated iCalendar entities.
TEXT
Non-standard parameters can be specified on this property.
This property MAY be specified multiple times in any iCalendar component.
The value of this property is a text identifier that allows associated components to be located or retrieved as a whole. For example all of the events in a travel itinerary would have the same REFID value.
This property is defined by the following notation:
The following is an example of this property.
RELATED-TO
This property is used to represent a relationship or reference between one calendar component and another. The definition here extends the definition in
URI, UID or TEXT
Relationship type, IANA and non-standard property parameters can be specified on this property.
This property MAY be specified in any iCalendar component.
By default or when VALUE=UID is specified, 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.
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 or a temporal 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.
The FINISHTOSTART, FINISHTOFINISH, STARTTOFINISH or STARTTOSTART relationships define temporal relationships as specified in the reltype parameter definition.
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.
This property is defined by the following notation:
The following are examples of this property.
Applications using the LINK property need to be aware of the risks entailed in using the URIs provided as values. See
The CONCEPT and redefined RELATED-TO property have the same issues in that values may be URIs.
The following iCalendar property names have been added to the iCalendar Properties Registry defined in
| Property | Status | Reference |
|---|---|---|
CONCEPT |
Current |
|
LINK |
Current |
|
REFID |
Current |
The following iCalendar property parameter names have been added to the iCalendar Parameters Registry defined in
| Parameter | Status | Reference |
|---|---|---|
REL |
Current |
|
GAP |
Current |
The following iCalendar property parameter names have been added to the iCalendar Value Data Types Registry defined in
| Value Data Type | Status | Reference |
|---|---|---|
UID |
Current |
|
REFERENCE |
Current |
The following iCalendar “RELTYPE” values have been added to the iCalendar Relationship Types Registry defined in
| Relationship Type | Status | Reference |
|---|---|---|
DEPENDS-ON |
Current |
|
REFID |
Current |
|
CONCEPT |
Current |
|
FINISHTOSTART |
Current |
|
FINISHTOFINISH |
Current |
|
STARTTOFINISH |
Current |
|
STARTTOSTART |
Current |
The following link relation values have been added to the Reference Types Registry defined in
| Name | Status | Reference |
|---|---|---|
SOURCE |
Current |
The author would like to thank the members of the Calendaring and Scheduling Consortium technical committees and the following individuals for contributing their ideas, support and comments:
Adrian Apthorp, Cyrus Daboo, Marten Gajda, Ken Murchison
The author would also like to thank CalConnect, the Calendaring and Scheduling Consortium for advice with this specification.
The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
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. [STANDARDS-TRACK]
This document specifies relation types for Web links, and defines a registry for them. It also defines the use of such links in HTTP headers with the Link header field. [STANDARDS-TRACK]
This document defines extensions to the Calendaring Extensions to WebDAV (CalDAV) “calendar-access” feature to specify a standard way of performing scheduling operations with iCalendar-based calendar components. This document defines the “calendar-auto-schedule” feature of CalDAV. [STANDARDS-TRACK]
In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. [STANDARDS-TRACK]