iCalendar Format Extension for JSCalendar

Preface This document is a work in progress. The list of new or updated properties and parameters is likely to be incomplete. This section is removed from the document before publication.

Introduction The JSCalendar format aims to be an alternative to the iCalendar format for representation of calendar data. As such, it introduces new semantics that are not covered in the current definition of iCalendar and its extensions. Converting calendar data between the two formats is defined in with the goal of not loosing any semantics during conversion. In order to do so, this document defines a new set of properties for iCalendar and extends existing definitions.

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

New Properties

COMP-ID Property

Property name:: COMP-ID
Purpose:: This property uniquely identifies a component among all its siblings of the same type.
Value type:: TEXT, also see Format Definition for value restrictions.
Conformance:: The property can be specified once in a calendar component.
Property parameters:: IANA and non-standard property parameters can be specified on this property.
Description:: A calendar component may embed multiple components of the same type. For example, a VEVENT component may embed multiple VALARM components. To distinguish these VALARMs among all global instances of VALARM calendar components, an application may choose to assign a uniquely global UID to each of them. However, some applications or formats such as JSCalendar, do not require globally uniqueness. Instead, they only require uniqueness among all instances of calendar components within one parent component. This is what the COMP-ID property is for. The COMP-ID property identifies a component among all of its siblings of the same type. A valid COMP-ID value must be of 1 and a maximum of 255 octets in size, and it MUST only contain the ASCII alphanumeric characters (A-Za-z0-9), hyphen (-), and underscore (_). The identifier only has the purpose to uniquely identify siblings, its value has no other meaning. If an application makes use of COMP-ID it SHOULD assign a unique identifier to each sibling component of the same type within their parent component. The same identifier MAY be used for components of a different type, and it MAY also be assigned to a same-typed component that is not a sibling. Resolving duplicate identifier conflicts is specific to the application. Similarly, handling components where some but not all siblings have a COMP-ID is assigned, is application-specific.
Format definition:: This property is defined by the following notation:
Example(s):

SHOW-WITHOUT-TIME Property

Property name:: SHOW-WITHOUT-TIME
Purpose:: This property indicates if an event or task should be displayed with time information.
Value type:: BOOLEAN
Conformance:: The property can be specified once in the VEVENT, VTODO or VJOURNAL calendar components.
Property parameters:: IANA and non-standard property parameters can be specified on this property.
Description:: This indicates that the time is not important to display to the user when rendering this calendar object. An example of this is an event that conceptually occurs all day or across multiple days, such as "New Year's Day" or "Italy Vacation". While the time component is important for free-busy calculations and checking for scheduling clashes, calendars may choose to omit displaying it and/or display the object separately to other objects to enhance the user's view of their schedule.
Format definition:: This property is defined by the following notation:
Example(s):

Updated Properties

GEO Property This specification modifies the definition of the GEO property to allow storing spatial positions in form of URIs using the geo: scheme . The following additions are made to the definition of this property, original specified in .

Value type:: The default value type is FLOAT, where the value MUST be two SEMICOLON-separated FLOAT values. The value type can also be set to URI to indicate geo: encoded coordinates.
Property parameters:: VALUE
Description:: When the property value is a URI in the geo: scheme, then the VALUE property parameter MUST be set to URI.
Format definition:: This property is defined by the following notation:
Example(s):

New Parameters

CONTENT-ID Parameter

Parameter name:: CONTENT-ID
Purpose:: This parameter identifies an attachment contents for use with styled descriptions.
Format definition:
Description:: This parameter MAY be set on an "ATTACH" or "IMAGE" property. It assigns the property an identifier that MUST be unique within the calendar component. A calendar component MAY include a STYLED-DESCRIPTION property as specified in , and MAY contain HTML text. URLs in the "cid:" scheme referred to by images and other data within that HTML description can be resolved to calendar component attachments having that content-id.
Example(s):: ]]>

INVITED-BY Parameter

Parameter name:: INVITED-BY
Purpose:: This parameter specifies which calendar address user invited another.
Format definition:
Description:: This parameter MAY be set on an "ATTENDEE" property, specified in . If set, it identifies the participant that invited the calendar user represented by the ATTENDEE property to the calendar component.
Example(s):

LINK-REL Parameter

Parameter name:: LINK-REL
Purpose:: This parameter defines how an attachment relates to calendar component.
Format definition:
Description:: This parameter MAY be set on an "ATTACH" or "IMAGE" property. It indicates how the contents of the attachment or image relate to the calendar component this property is part of. For the list of available relations, see the Link Relation Types in the IANA Link Relations Registry .
Example(s):

PROP-ID Parameter

Parameter name:: PROP-ID
Purpose:: This parameter identifies a property among all its siblings of the same type.
Format definition:
Description:: This parameter uniquely identifies a property among all of its siblings with the same name within a calendar component. A valid PROP-ID value must be of 1 and a maximum of 255 octets in size, and it MUST only contain the ASCII alphanumeric characters (A-Za-z0-9), hyphen (-), and underscore (_). The identifier only has the purpose to uniquely identify siblings, its value has no other meaning. If an application makes use of PROP-ID it SHOULD assign a unique identifier to each sibling property of the same name within their embedding component. The same identifier MAY be used for properties of a different name, and it MAY also be assigned to a same-named property that is not a sibling. Resolving duplicate identifier conflicts is specific to the application. Similarly, handling properties where some but not all siblings have a PROP-ID is assigned, is application-specific.
Example(s):

IANA Considerations This section will be filled at a later stage.

Security Considerations This section will be filled at a later stage.