<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd"> "rfc2629-xhtml.ent">

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902"     docName="draft-ietf-calext-jscalendar-32" number="8984" obsoletes="" updates=""
submissionType="IETF" category="std" docName="draft-ietf-calext-jscalendar-32">
  <?rfc toc="yes"?>
  <?rfc symrefs="yes"?>
  <?rfc sortrefs="yes"?>
  <?rfc compact="no"?>
  <?rfc subcompact="no"?>
  <?rfc private=""?>
  <?rfc topblock="yes"?>
  <?rfc comments="no"?> consensus="true" xml:lang="en" tocInclude="true"
symRefs="true" sortRefs="true" version="3">

  <!-- xml2rfc v2v3 conversion 3.5.0 -->
  <front>
    <title abbrev="JSCalendar">JSCalendar: A JSON representation Representation of calendar data</title> Calendar Data</title>
    <seriesInfo name="RFC" value="8984"/>
    <author initials="N.M." initials="N." surname="Jenkins" fullname="Neil Jenkins">
      <organization>Fastmail</organization>
      <address>
        <postal>
          <street>PO
          <street>P.O. Box 234</street>
          <street>Collins St West</street>
          <extaddr>Collins St. West</extaddr>
          <city>Melbourne</city>
          <code>VIC 8007</code>
          <country>Australia</country>
          <region />
          <region/>
        </postal>
        <phone />
        <phone/>
        <email>neilj@fastmailteam.com</email>
        <uri>https://www.fastmail.com</uri>
      </address>
    </author>
    <author initials="R." surname="Stepanek" fullname="Robert Stepanek">
      <organization>Fastmail</organization>
      <address>
        <postal>
          <street>PO
          <street>P.O. Box 234</street>
          <street>Collins St West</street>
          <extaddr>Collins St. West</extaddr>
          <city>Melbourne</city>
          <code>VIC 8007</code>
          <country>Australia</country>
          <region />
          <region/>
        </postal>
        <email>rsto@fastmailteam.com</email>
        <uri>https://www.fastmail.com</uri>
      </address>
    </author>
    <date year="2020" month="October" day="16" /> year="2021" month="July"/>
    <area>Applications</area>
    <workgroup>Calendaring extensions</workgroup>
    <keyword>JSON</keyword>
    <keyword>iCalendar</keyword>
    <keyword>calendar</keyword>
    <keyword>events</keyword>
    <keyword>date</keyword>
    <keyword>time</keyword>

    <abstract>
      <t>This specification defines a data model and JSON representation of calendar data that can be used for storage and data exchange in a calendaring and scheduling environment. It aims to be an alternative and, over time, successor to the widely deployed iCalendar data format, and format. It also aims to be unambiguous, extendable, and simple to process. In contrast to the jCal format, which is also JSON-based, based on JSON, JSCalendar is not a direct mapping from iCalendar, iCalendar but defines the data model independently and expands semantics where appropriate.</t>
    </abstract>
  </front>
  <middle>
    <section anchor="introduction" title="Introduction"> numbered="true" toc="default">
      <name>Introduction</name>
      <t>This document defines a data model for calendar event and task objects, or groups of such objects, in electronic calendar applications and systems. The format aims to be unambiguous, extendable extendable, and simple to process.</t>
      <t>The key design considerations for this data model are as follows:
        <list style="symbols">
          <t>The
      </t>
      <ul spacing="normal">
        <li>The attributes of the calendar entry represented must be described as simple key-value pairs. Simple events are simple to represent; complex events can be modelled accurately.</t>
          <t>Wherever modeled accurately.</li>
        <li>Wherever possible, there should be only one way to express the desired semantics, reducing complexity.</t>
          <t>The complexity.</li>
        <li>The data model should avoid ambiguities, which often lead to interoperability issues between implementations.</t>
          <t>The implementations.</li>

        <li>The data model should be generally compatible with the iCalendar data format <xref target="RFC5545" /> format="default"/> <xref target="RFC7986" /> format="default"/> and extensions, but the specification should add new attributes where the iCalendar format currently lacks expressivity, and drop seldom-used, obsolete, or redundant properties. This means translation with no loss of semantics should be easy with most common iCalendar files.</t>
          <t>Extensions, files.</li>
        <li>Extensions, such as new properties and components, should not require updates to this document.</t>
        </list>
      </t> document.</li>
      </ul>
      <t>The representation of this data model is defined in the I-JSON Internet JSON (I-JSON) format <xref target="RFC7493" />, format="default"/>, which is a strict subset of the JavaScript Object Notation (JSON) Data Interchange Format JSON data interchange format <xref target="RFC8259" />. format="default"/>. Using JSON is mostly a pragmatic choice: its widespread use makes JSCalendar easier to adopt, adopt and the ready availability of production-ready JSON implementations eliminates a whole category of parser-related interoperability issues, which iCalendar has often suffered from.</t>
      <section anchor="relation-to-icalendar" title="Motivation numbered="true" toc="default">
        <name>Motivation and Relation to iCalendar and jCal"> jCal</name>
        <t>The iCalendar data format <xref target="RFC5545" />, format="default"/>, a widely deployed interchange format for calendaring and scheduling data, has served calendaring vendors for a long while, time but contains some ambiguities and pitfalls that can not cannot be overcome without backward-incompatible changes.</t>
        <t>Sources of implementation errors include the following:
          <list style="symbols">
            <t>iCalendar
        </t>
        <ul spacing="normal">
          <li>iCalendar defines various formats for local times, UTC time, UTC, and dates.</t>
            <t>iCalendar dates.</li>
          <li>iCalendar requires custom time zone definitions within a single calendar component.</t>
            <t>iCalendar's component.</li>
          <li>iCalendar's definition of recurrence rules is ambiguous and has resulted in differing understandings interpretations, even between experienced calendar developers.</t>
            <t>The developers.</li>
          <li>The iCalendar format itself causes interoperability issues due to misuse of CRLF-terminated strings, line continuations, and subtle differences among iCalendar parsers.</t>
          </list>
        </t> parsers.</li>
        </ul>
        <t>In recent years, many new products and services have appeared that wish to use a JSON representation of calendar data within their APIs. The JSON format for iCalendar data, <xref target="RFC7265">jCal</xref>, target="RFC7265" format="default">jCal</xref>, is a direct mapping between iCalendar and JSON. In its effort to represent full iCalendar semantics, it inherits all the same pitfalls and uses a complicated JSON structure.</t>
        <t>As a consequence, since the standardization of jCal, the majority of implementations and service providers either kept using iCalendar, iCalendar or came up with their own proprietary JSON representations, which are incompatible with each other and often suffer from common pitfalls, such as storing event start times in UTC (which become incorrect if the timezone's time zone's rules change in the future). JSCalendar meets the demand for JSON-formatted calendar data that is free of such known problems and provides a standard representation as an alternative to the proprietary formats.</t>
      </section>
      <section anchor="notational-conventions" title="Notational Conventions">
        <t>The numbered="true" toc="default">
        <name>Notational Conventions</name>
        <t>
    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
    NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
    "<bcp14>MAY</bcp14>", and "OPTIONAL" "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
    described in BCP 14 BCP&nbsp;14 <xref target="RFC2119" /> target="RFC2119"/> <xref target="RFC8174" /> target="RFC8174"/>
    when, and only when, they appear in all capitals, as shown here.</t> here.
        </t>
        <t>The underlying format used for this specification is JSON. Consequently, the terms "object" and "array" as well as the four primitive types (strings, numbers, booleans, and null) are to be interpreted as described in Section 1 of <xref target="RFC8259" sectionFormat="of" section="1" />.</t>
        <t>Some examples in this document contain "partial" JSON documents used for illustrative purposes. In these examples, three periods an ellipsis "..." are is used to indicate a portion of the document that has been removed for compactness.</t>
      </section>
      <section anchor="type-signatures" title="Type Signatures"> numbered="true" toc="default">
        <name>Type Signatures</name>
        <t>Type signatures are given for all JSON values in this document. The following conventions are
	used:</t>

        <t><list style="symbols">
          <t><spanx style="verb">*</spanx> - The
        <dl newline="false">
          <dt><tt>*</tt>:</dt>
	    <dd>The type is undefined (the value could be any type, although permitted values may be constrained
	      by the context of this value).</t>
          <t><spanx style="verb">String</spanx> - The value).</dd>
          <dt><tt>String</tt>:</dt>
	    <dd>This is the JSON string type.</t>
          <t><spanx style="verb">Number</spanx> - The type.</dd>
          <dt><tt>Number</tt>:</dt>
	    <dd>This is the JSON number type.</t>
          <t><spanx style="verb">Boolean</spanx> - The type.</dd>
          <dt><tt>Boolean</tt>:</dt>
	    <dd>This is the JSON boolean type.</t>
          <t><spanx style="verb">A[B]</spanx> - A JSON object where the type.</dd>
          <dt><tt>A[B]</tt>:</dt>
	    <dd>The keys are all of type <spanx style="verb">A</spanx>, <tt>A</tt> and the values are all of type <spanx style="verb">B</spanx>.</t>
          <t><spanx style="verb">A[]</spanx> - An
	      <tt>B</tt> for a JSON object.</dd>
          <dt><tt>A[]</tt>:</dt>
	    <dd>There is an array of values of type
            <spanx style="verb">A</spanx>.</t>
          <t><spanx style="verb">A|B</spanx> - The <tt>A</tt></dd>
          <dt><tt>A|B</tt>:</dt>
	    <dd>The value is either of type
            <spanx style="verb">A</spanx> <tt>A</tt> or of type
            <spanx style="verb">B</spanx>.</t>
        </list></t> <tt>B</tt>.</dd>
        </dl>
        <t>Other types may also be given, with given; their representations are defined elsewhere in this document.</t>
      </section>
      <section anchor="data-types" title="Data Types"> numbered="true" toc="default">
        <name>Data Types</name>
        <t>In addition to the standard JSON data types, the following data types are used in this specification:</t>
        <section anchor="type-Id" title="Id"> numbered="true" toc="default">
          <name>Id</name>
          <t>Where <spanx style="verb">Id</spanx> <tt>Id</tt> is given as a data type, it means a <spanx style="verb">String</spanx> <tt>String</tt> of at least 1 and a maximum of 255 octets in size, and it MUST <bcp14>MUST</bcp14> only contain characters from the "URL and Filename Safe" base64url alphabet, as defined in Section 5 of <xref target="RFC4648" />, sectionFormat="of" section="5"/>, excluding the pad character (<spanx style="verb">=</spanx>). (<tt>=</tt>). This means the allowed characters are the ASCII alphanumeric characters (<spanx style="verb">A-Za-z0-9</spanx>), (<tt>A-Za-z0-9</tt>), hyphen (<spanx style="verb">-</spanx>), (<tt>-</tt>), and underscore (<spanx style="verb">_</spanx>).</t> (<tt>_</tt>).</t>
          <t>In many places in JSCalendar JSCalendar, a JSON map is used where the map keys are of type Id and the map values are all the same type of object. This construction represents an unordered set of objects, with the added advantage that each entry has a name (the corresponding map key). This allows for more concise patching of objects, and, when applicable, for the objects in question to be referenced from other objects within the JSCalendar object.</t>
          <t>Unless otherwise specified for a particular property, there are no uniqueness constraints on an Id value (other than, of course, the requirement that you cannot have two values with the same key within a single JSON map). For example, two JSEvent Event objects might use the same Ids in their respective <spanx style="verb">links</spanx> properties. Or <tt>links</tt> properties or, within the same JSEvent object Event object, the same Id could appear in the <spanx style="verb">participants</spanx> <tt>participants</tt> and <spanx style="verb">alerts</spanx> <tt>alerts</tt> properties. These situations do not imply any semantic connections among the objects. <vspace blankLines="1" /> Nevertheless, a UUID <xref target="RFC4122" /> is typically a good choice.</t> objects.</t>
        </section>
        <section anchor="type-Int" title="Int"> numbered="true" toc="default">
          <name>Int</name>
          <t>Where <spanx style="verb">Int</spanx> <tt>Int</tt> is given as a data type, it means an integer in the range -2^53+1 -2<sup>53</sup>+1 &lt;= value &lt;= 2^53-1, 2<sup>53</sup>-1, the safe range for integers stored in a floating-point double, represented as a JSON <spanx style="verb">Number</spanx>.</t> <tt>Number</tt>.</t>
        </section>
        <section anchor="type-UnsignedInt" title="UnsignedInt"> numbered="true" toc="default">
          <name>UnsignedInt</name>
          <t>Where <spanx style="verb">UnsignedInt</spanx> <tt>UnsignedInt</tt> is given as a data type, it means an integer in the range 0 &lt;= value &lt;= 2^53-1, 2<sup>53</sup>-1, represented as a JSON <spanx style="verb">Number</spanx>.</t> <tt>Number</tt>.</t>
        </section>
        <section anchor="type-UTCDateTime" title="UTCDateTime"> numbered="true" toc="default">
          <name>UTCDateTime</name>
          <t>This is a string in the <tt>date-time</tt> <xref target="RFC3339" /> <spanx style="verb">date-time</spanx> format="default"/> format, with
	    the
	      further restrictions that any letters MUST <bcp14>MUST</bcp14> be in uppercase, and the time offset MUST
	        <bcp14>MUST</bcp14> be the character <spanx style="verb">Z</spanx>. <tt>Z</tt>. Fractional second values MUST NOT <bcp14>MUST NOT</bcp14> be
		  included unless non-zero and MUST NOT <bcp14>MUST NOT</bcp14> have trailing zeros, to ensure there is only a
		    single representation for each date-time. </t>
          <t>For example <spanx style="verb">2010-10-10T10:10:10.003Z</spanx> example, <tt>2010-10-10T10:10:10.003Z</tt> is conformant, but <spanx style="verb">2010-10-10T10:10:10.000Z</spanx> <tt>2010-10-10T10:10:10.000Z</tt>
	    is invalid and is correctly encoded as <spanx style="verb">2010-10-10T10:10:10Z</spanx>.</t> <tt>2010-10-10T10:10:10Z</tt>.</t>
        </section>
        <section anchor="type-LocalDateTime" title="LocalDateTime"> numbered="true" toc="default">
          <name>LocalDateTime</name>
          <t>This is a date-time string with no time zone/offset information. It is otherwise in the same
	    format as UTCDateTime, including fractional seconds. For example <spanx style="verb">2006-01-02T15:04:05</spanx> example, <tt>2006-01-02T15:04:05</tt> and <spanx style="verb">2006-01-02T15:04:05.003</spanx>
	      <tt>2006-01-02T15:04:05.003</tt> are both valid. The time zone to associate with the LocalDateTime
	        comes from the <spanx style="verb">timeZone</spanx> <tt>timeZone</tt> property of the JSCalendar object (see <xref target="prop-timeZone" />).
		  format="default"/>). If no time zone is specified, the LocalDateTime is <spanx style="verb">floating</spanx>. <tt>floating</tt>. Floating
		  date-times are not tied to any specific time zone. Instead, they occur in each time zone at the given
		    wall-clock time (as opposed to the same instant point in time).</t>
          <t>A time zone may have a period of discontinuity, for example example, a change from standard time to daylight-savings
	    daylight savings time. When converting local date-times that fall in the discontinuity to UTC, the
	      offset before the transition MUST <bcp14>MUST</bcp14> be used.</t>
          <t>For example, in the America/Los_Angeles time zone, the date-time 2020-11-01T01:30:00 occurs twice:
	    before the DST daylight savings time (DST) transition with a UTC offset of -07:00, -07:00 and again after the
	      transition with an offset of -08:00. When converting to UTC, we therefore use the offset before the
	        transition (-07:00) and (-07:00), so it becomes 2020-11-01T08:30:00Z.</t>
          <t>Similarly, in the Australia/Melbourne time zone, the date-time 2020-10-04T02:30:00 does not exist: exist;
	    the clocks are moved forward one hour for DST on that day at 02:00. However, such a value may appear
	      during calculations (see duration semantics in <xref target="type-Duration" />), format="default"/>) or
	        due to a change in time zone rules (so it was valid when the event was first created). Again, it is
		  interpreted as though the offset before the transition is in effect (+10:00), therefore (+10:00); therefore, when
		    converted to UTC UTC, we get 2020-10-03T16:30:00Z.</t>
        </section>
        <section anchor="type-Duration" title="Duration"> numbered="true" toc="default">
          <name>Duration</name>
          <t>Where Duration is given as a type, it means a length of time represented by a subset of ISO8601 the ISO 8601 duration format, as specified by the following ABNF <xref target="RFC5234" />:</t>

          <figure>
            <artwork><![CDATA[ format="default"/>:</t>
          <sourcecode name="" type="abnf"><![CDATA[
    dur-secfrac = "." 1*DIGIT
    dur-second  = 1*DIGIT [dur-secfrac] "S"
    dur-minute  = 1*DIGIT "M" [dur-second]
    dur-hour    = 1*DIGIT "H" [dur-minute]
    dur-time    = "T" (dur-hour / dur-minute / dur-second)
    dur-day     = 1*DIGIT "D"
    dur-week    = 1*DIGIT "W"
    dur-cal     = (dur-week [dur-day] / dur-day)

    duration    = "P" (dur-cal [dur-time] / dur-time)]]></artwork>
          </figure> dur-time)
]]></sourcecode>
          <t>In addition, the duration MUST NOT <bcp14>MUST NOT</bcp14> include fractional second values unless the fraction is non-zero. Fractional second values MUST NOT <bcp14>MUST NOT</bcp14> have trailing zeros, zeros to ensure there is only a single representation for each duration.</t>
          <t>A duration specifies an abstract number of weeks, days, hours, minutes, and/or seconds. A duration specified using weeks or days does not always correspond to an exact multiple of 24 hours. The number of hours/minutes/seconds may vary if it overlaps a period of discontinuity in the event's time zone, for example example, a change from standard time to daylight-savings daylight savings time. Leap seconds MUST NOT <bcp14>MUST NOT</bcp14> be considered when adding or subtracting a duration to/from a LocalDateTime.</t>
          <t>To add a duration to a LocalDateTime:
          <list style="numbers">
              <t>Add
          </t>
          <ol spacing="normal" type="1"><li>Add any week or day components of the duration to the date. A week is always the same as 7 days.</t>
              <t>If seven days.</li>
            <li>If a time zone applies to the LocalDateTime, convert it to a UTCDateTime following the semantics in <xref target="type-LocalDateTime" />.</t>
              <t>Add format="default"/>.</li>
            <li>Add any hour, minute minute, or second components of the duration (in absolute time).</t>
              <t>Convert time).</li>
            <li>Convert the resulting UTCDateTime back to a LocalDateTime in the time zone that applies.</t>
          </list></t> applies.</li>
          </ol>
          <t>To subtract a duration from a LocalDateTime, the steps apply in reverse:
          <list style="numbers">
              <t>If
          </t>
          <ol spacing="normal" type="1"><li>If a time zone applies to the LocalDateTime, convert it to UTC following the semantics in <xref target="type-LocalDateTime" />.</t>
              <t>Subtract format="default"/>.</li>
            <li>Subtract any hour, minute minute, or second components of the duration (in absolute time).</t>
              <t>Convert time).</li>
            <li>Convert the resulting UTCDateTime back to LocalDateTime in the time zone that applies.</t>
              <t>Subtract applies.</li>
            <li>Subtract any week or day components of the duration from the date.</t>
              <t>If date.</li>
            <li>If the resulting time does not exist on the date due to a discontinuity in the time zone, use the semantics in <xref target="type-LocalDateTime" /> format="default"/> to convert to UTC and back to get a valid LocalDateTime.</t>
          </list></t> LocalDateTime.</li>
          </ol>
          <t>These semantics match the iCalendar DURATION value type (<xref target="RFC5545" />, Section 3.3.6).</t> sectionFormat="comma" section="3.3.6"/>).</t>
        </section>
        <section anchor="type-SignedDuration" title="SignedDuration"> numbered="true" toc="default">
          <name>SignedDuration</name>
          <t>A SignedDuration represents a length of time that may be positive or negative and is typically used to express the offset of a point in time relative to an associated time. It is represented as a Duration, optionally preceded by a sign character. It is specified by the following ABNF:</t>

          <figure>
            <artwork><![CDATA[
          <sourcecode name="" type="abnf"><![CDATA[
signed-duration = ["+" / "-"] duration]]></artwork>
          </figure> duration
]]></sourcecode>
          <t>A negative sign indicates a point in time at or before the associated time, time; a positive or no sign
	    indicates a time at or after the associated time.</t>
        </section>
        <section anchor="type-timeZoneId" title="TimeZoneId"> numbered="true" toc="default">
          <name>TimeZoneId</name>
          <t>Where <spanx style="verb">TimeZoneId</spanx> <tt>TimeZoneId</tt> is given as a data type, it means a <spanx style="verb">String</spanx> <tt>String</tt> that is either a
	    time zone name in the IANA Time Zone Database <xref target="TZDB" /> format="default"/> or a custom time
	      zone identifier defined in the <spanx style="verb">timeZones</spanx> <tt>timeZones</tt> property (see <xref target="prop-timeZones" />).</t>
	        format="default"/>).</t>
          <t>Where an IANA time zone is specified, the zone rules of the respective zone records apply. Custom
	    time zones are interpreted as described in <xref target="prop-timeZones" />.</t> format="default"/>.</t>
        </section>
        <section anchor="type-PatchObject" title="PatchObject"> numbered="true" toc="default">
          <name>PatchObject</name>
          <t>A PatchObject is of type <spanx style="verb">String[*]</spanx>, <tt>String[*]</tt> and represents an unordered set of patches on a JSON
	    object. Each key is a path represented in a subset of the JSON pointer Pointer format <xref target="RFC6901" />.
	      format="default"/>. The paths have an implicit leading <spanx style="verb">/</spanx>, <tt>/</tt>, so each key is prefixed with <spanx style="verb">/</spanx>
	      <tt>/</tt> before applying the JSON pointer Pointer evaluation algorithm.</t>
          <t>A patch within a PatchObject is only valid if all of the following conditions apply:</t>

          <t><list style="numbers">
            <t>The
          <ol spacing="normal" type="1">
	        <li>The pointer MUST NOT <bcp14>MUST NOT</bcp14> reference inside an array (i.e., you MUST NOT <bcp14>MUST
		    NOT</bcp14> insert/delete from an array; the array MUST <bcp14>MUST</bcp14> be replaced in its entirety instead).</t>
            <t>All
		        instead).</li>
            <li>All parts prior to the last (i.e., the value after the final slash) MUST <bcp14>MUST</bcp14> already
	        exist on the object being patched.</t>
            <t>There MUST NOT patched.</li>
            <li>There <bcp14>MUST NOT</bcp14> be two patches in the PatchObject where the pointer of one is the
	        prefix of the pointer of the other, e.g., <spanx style="verb">alerts/1/offset</spanx> <tt>alerts/1/offset</tt> and <spanx style="verb">alerts</spanx>.</t>
            <t>The <tt>alerts</tt>.</li>
            <li>The value for the patch MUST <bcp14>MUST</bcp14> be valid for the property being set (of the correct
	        type and obeying any other applicable restrictions), or or, if null null, the property MUST <bcp14>MUST</bcp14> be optional.</t>
          </list></t>
		    optional.</li>
          </ol>
          <t>The value associated with each pointer determines how to apply that patch:
            <list style="symbols">
              <t>If patch:</t>
          <ul spacing="normal">
            <li>If null, remove the property from the patched object. If the key is not present in the parent, this a no-op.</t>
              <t>Anything else: The value to no-op.</li>
            <li>If non-null, set the value given as the value for this property
            (this may be a replacement or addition to the object being patched).</t>
            </list>
          </t> patched).</li>
          </ul>
          <t>A PatchObject does not define its own <spanx style="verb">@type</spanx> <tt>@type</tt> property (see <xref target="prop-type" />). A <spanx style="verb">@type</spanx>
	    format="default"/>). An <tt>@type</tt> property in a patch MUST <bcp14>MUST</bcp14> be handled as any other
	    patched property value.</t>
          <t>Implementations MUST <bcp14>MUST</bcp14> reject a PatchObject in its entirety a PatchObject if any of its patches is are
	    invalid.  Implementations MUST NOT <bcp14>MUST NOT</bcp14> apply partial patches.</t>
          <t>The PatchObject format is used to significantly reduce file size and duplicated content when
	    specifying variations to a common object, such as with recurring events or when translating the data
	      into multiple languages. It can also better preserve semantic intent if only the properties that
	        should differ between the two objects are patched. For example, if one person is not going to a
		  particular instance of a regularly scheduled event, in iCalendar iCalendar, you would have to duplicate the
		    entire event in the override. In JSCalendar JSCalendar, this is a small patch to show the difference. As only
		      this property is patched, if the location of the event is changed, the occurrence will automatically
		        still inherit this.</t>
        </section>
        <section anchor="type-Relation" title="Relation"> numbered="true" toc="default">
          <name>Relation</name>
          <t>A Relation object defines the relation to other objects, using a possibly empty set of relation
	    types. The object that defines this relation is the linking object, while the other object is the
	      linked object. A Relation object has the following properties:</t>
          <t><list style="symbols">
            <t>@type: <spanx style="verb">String</spanx> (mandatory)
               <vspace blankLines="1" />
               Specifies
          <dl newline="true">
              <dt>@type: <tt>String</tt> (mandatory)</dt>
              <dd>This specifies the type of this object. This MUST <bcp14>MUST</bcp14> be <spanx style="verb">Relation</spanx>.
            </t>
            <t>relation: <spanx style="verb">String[Boolean]</spanx> <tt>Relation</tt>.</dd>
              <dt>relation: <tt>String[Boolean]</tt> (optional, default: empty Object)
            <vspace blankLines="1" />
            Describes Object)</dt>
              <dd><t>This describes how the linked object is related to the linking object. The relation is defined
	            as a set of relation types. If empty, the relationship between the two objects is unspecified.
            <vspace blankLines="1" />
            Keys unspecified.</t>
		          <t>Keys in the set MUST <bcp14>MUST</bcp14> be one of the following values, or specified in the
			        property definition where the Relation object is used, or a value registered in the IANA JSCalendar
				      &quot;JSCalendar Enum Values Values&quot; registry, or a vendor-specific value (see <xref target="custom-properties" />):
            <list style="symbols">
              <t><spanx style="verb">first</spanx>: The
				            format="default"/>):</t>
              <dl newline="false">
                <dt><tt>first</tt>:</dt>
		<dd>The linked object is the first in a series the linking object is part of.</t>
              <t><spanx style="verb">next</spanx>: The of.</dd>
                <dt><tt>next</tt>:</dt>
		<dd>The linked object is the next in a series the linking object is part of.</t>
              <t><spanx style="verb">child</spanx>: The of.</dd>
                <dt><tt>child</tt>:</dt>
		<dd>The linked object is a subpart of the linking object.</t>
              <t><spanx style="verb">parent</spanx>: The object.</dd>
                <dt><tt>parent</tt>:</dt>
		<dd>The linking object is a subpart of the linked object.</t>
            </list> object.</dd>
              </dl>
              <t>
          The value for each key in the map MUST <bcp14>MUST</bcp14> be true.</t>
          </list></t>
              </dd></dl>
        </section>
        <section anchor="type-Link" title="Link"> numbered="true" toc="default">
          <name>Link</name>
          <t>A Link object represents an external resource associated with the linking object. It has the
	    following properties:</t>

          <t><list style="symbols">
            <t>@type: <spanx style="verb">String</spanx> (mandatory)
            <vspace blankLines="1" />
            Specifies
          <dl newline="true">
	        <dt>@type: <tt>String</tt> (mandatory)</dt>
              <dd>This specifies the type of this object. This MUST <bcp14>MUST</bcp14> be <spanx style="verb">Link</spanx>.</t>
            <t>href: <spanx style="verb">String</spanx> (mandatory)
            <vspace blankLines="1" />
            A <tt>Link</tt>.</dd>
              <dt>href: <tt>String</tt> (mandatory)</dt>
              <dd><t>This is a URI <xref target="RFC3986" /> format="default"/> from which the resource may be fetched.
            <vspace blankLines="1" />
            This MAY
	            fetched.</t>
              <t>This <bcp14>MAY</bcp14> be a <spanx style="verb">data:</spanx> <tt>data:</tt> URL <xref target="RFC2397" />, format="default"/>, but
	            it is recommended that the file be hosted on a server to avoid embedding arbitrarily large data
		          in JSCalendar object instances.</t>

            <t>cid: <spanx style="verb">String</spanx> instances.</t></dd>
              <dt>cid: <tt>String</tt> (optional)
            <vspace blankLines="1" />
            This MUST
              </dt>
              <dd><t>This <bcp14>MUST</bcp14> be a valid <spanx style="verb">content-id</spanx> <tt>content-id</tt> value according to the definition
	            of Section 2 in <xref target="RFC2392" />. sectionFormat="of" section="2"/>. The value MUST <bcp14>MUST</bcp14> be
		          unique within this Link object but has no meaning beyond that. It MAY <bcp14>MAY</bcp14> be different
			        from the link id for this Link object.</t>

            <t>contentType: <spanx style="verb">String</spanx> (optional)
            <vspace blankLines="1" />
            The object.</t></dd>
              <dt>contentType: <tt>String</tt> (optional)</dt>
              <dd>This is the media type <xref target="RFC6838" /> format="default"/> of the resource, if known.</t>

            <t>size: <spanx style="verb">UnsignedInt</spanx> (optional)
            <vspace blankLines="1" />
            The
	            known.</dd>
              <dt>size: <tt>UnsignedInt</tt> (optional)</dt>
              <dd>This is the size, in octets, of the resource when fully decoded (i.e., the number of octets
	            in the
		          file the user would download), if known. Note that this is an informational estimate, and
			        implementations must be prepared to handle the actual size being quite different when the
				      resource is fetched.</t>

            <t>rel: <spanx style="verb">String</spanx> (optional)
            <vspace blankLines="1" />
            Identifies fetched.</dd>
              <dt>rel: <tt>String</tt> (optional)</dt>
              <dd>This identifies the relation of the linked resource to the object. If set, the value MUST
	            <bcp14>MUST</bcp14> be a relation type from the IANA &quot;Link Relations&quot; registry <xref target="LINKRELS" />,
		          format="default"/>, as established in <xref target="RFC8288" />.</t>

            <t>display: <spanx style="verb">String</spanx> (optional)
            <vspace blankLines="1" />
            Describes format="default"/>.</dd>
              <dt>display: <tt>String</tt> (optional)</dt>
              <dd><t>This describes the intended purpose of a link to an image. If set, the <spanx style="verb">rel</spanx> <tt>rel</tt>
	            property MUST <bcp14>MUST</bcp14> be set to <spanx style="verb">icon</spanx>. <tt>icon</tt>. The value MUST <bcp14>MUST</bcp14> be one of the
		          following values, another value registered in the IANA JSCalendar &quot;JSCalendar Enum Values Values&quot; registry, or a
			        vendor-specific value (see <xref target="custom-properties" />):

            <list style="symbols">
              <t><spanx style="verb">badge</spanx>: an format="default"/>):</t>
              <dl newline="false">
                <dt><tt>badge</tt>:</dt>
		<dd>an image meant to be displayed alongside the title of the object.</t>

              <t><spanx style="verb">graphic</spanx>: a object</dd>
                <dt><tt>graphic</tt>:</dt>
		<dd>a full image replacement for the object itself.</t>

              <t><spanx style="verb">fullsize</spanx>: an itself</dd>
                <dt><tt>fullsize</tt>:</dt>
		<dd>an image that is used to enhance the object.</t>

              <t><spanx style="verb">thumbnail</spanx>: a object</dd>
                <dt><tt>thumbnail</tt>:</dt>
		<dd>a smaller variant of <spanx style="verb">fullsize</spanx> <tt>fullsize</tt> to be used when space for the image is constrained.</t>
            </list></t>

            <t>title: <spanx style="verb">String</spanx> (optional)
            <vspace blankLines="1" />
            A human-readable
		constrained</dd>
              </dl>
	      </dd>
            <dt>title: <tt>String</tt> (optional)</dt>
              <dd>This is a human-readable, plain-text description of the resource.</t>
          </list></t> resource.</dd>
          </dl>
        </section>
      </section>
    </section>
    <section anchor="jscalendar-objects" title="JSCalendar Objects"> numbered="true" toc="default">
      <name>JSCalendar Objects</name>
      <t>This section describes the calendar object types specified by JSCalendar.</t>
      <section anchor="jsevent" title="JSEvent"> numbered="true" toc="default">
        <name>Event</name>
        <t>Media type: <spanx style="verb">application/jscalendar+json;type=jsevent</spanx></t>

        <t>A JSEvent <tt>application/jscalendar+json;type=event</tt></t>
        <t>An Event represents a scheduled amount of time on a calendar, typically a meeting, appointment, reminder
	reminder, or anniversary. It is required to start at a certain point in time and typically has a
	non-zero duration. Multiple participants may partake in the event at multiple locations.</t>
        <t>The <xref target="prop-type">@type</xref> target="prop-type" format="default">@type</xref> property value MUST <bcp14>MUST</bcp14> be <spanx style="verb">jsevent</spanx>.</t>
	<tt>Event</tt>.</t>
      </section>
      <section anchor="jstask" title="JSTask"> numbered="true" toc="default">
        <name>Task</name>
        <t>Media type: <spanx style="verb">application/jscalendar+json;type=jstask</spanx></t> <tt>application/jscalendar+json;type=task</tt></t>
        <t>A JSTask Task represents an action-item, action item, assignment, to-do item, or work item. It may start and be due at
	certain points in time, may take some estimated time to complete, and may recur, none of which is
	required.</t>
        <t>The <xref target="prop-type">@type</xref> target="prop-type" format="default">@type</xref> property value MUST <bcp14>MUST</bcp14> be <spanx style="verb">jstask</spanx>.</t>
	<tt>Task</tt>.</t>
      </section>
      <section anchor="jsgroup" title="JSGroup"> numbered="true" toc="default">
        <name>Group</name>
        <t>Media type: <spanx style="verb">application/jscalendar+json;type=jsgroup</spanx></t> <tt>application/jscalendar+json;type=group</tt></t>
        <t>A JSGroup Group is a collection of <xref target="jsevent">JSEvent</xref> target="jsevent" format="default">Event</xref> and/or <xref target="jstask">JSTask</xref>
	target="jstask" format="default">Task</xref> objects. Typically, objects are grouped by topic (e.g.,
	by keywords) or calendar membership.</t>
        <t>The <xref target="prop-type">@type</xref> target="prop-type" format="default">@type</xref> property value MUST <bcp14>MUST</bcp14> be <spanx style="verb">jsgroup</spanx>.</t>
	<tt>Group</tt>.</t>
      </section>
    </section>
    <section anchor="structure-of-jscalendar-objects" title="Structure numbered="true" toc="default">
      <name>Structure of JSCalendar Objects"> Objects</name>
      <t>A JSCalendar object is a JSON object <xref target="RFC8259" />, format="default"/>, which MUST
      <bcp14>MUST</bcp14> be valid I-JSON (a stricter subset of JSON) <xref target="RFC7493" />.
      format="default"/>. Property names and values are case-sensitive.</t> case sensitive.</t>
      <t>The object has a collection of properties, as specified in the following sections. Properties are
      specified as being either mandatory or optional. Optional properties may have a default value, value if
      explicitly specified in the property definition.</t>
      <section anchor="objecttype" title="Object Type"> numbered="true" toc="default">
        <name>Object Type</name>
        <t>JSCalendar objects MUST <bcp14>MUST</bcp14> name their type in the <spanx style="verb">@type</spanx> property, <tt>@type</tt> property if not
	explicitly specified otherwise for the respective object type. A notable exception to this rule is the
	<xref target="type-PatchObject">PatchObject</xref>.</t> target="type-PatchObject" format="default">PatchObject</xref>.</t>
      </section>
      <section anchor="normalization" title="Normalization numbered="true" toc="default">
        <name>Normalization and Equivalence"> Equivalence</name>
        <t>JSCalendar aims to provide unambiguous definitions for value types and properties, properties but does not
	define a general normalization or equivalence method for JSCalendar objects and types. This is because
	the notion of equivalence might range from byte-level equivalence to semantic equivalence, depending on
	the respective use case.

        <vspace blankLines="1" /> Normalization of JSCalendar objects is hindered because of the following reasons:

        <list style="symbols">
          <t>Custom
	reasons:</t>
        <ul spacing="normal">
          <li>Custom JSCalendar properties may contain arbitrary JSON values, including arrays. However,
	    equivalence of arrays might or might not depend on the order of elements, depending on the respective
	      property definition.</t>
          <t>Several definition.</li>
          <li>Several JSCalendar property values are defined as URIs and media types, but normalization of
	    these types is inherently protocol- protocol and scheme-specific, scheme specific, depending on the use-case use case of the equivalence
	      definition (see Section 6 of <xref target="RFC3986" />).</t>
        </list>

        Considering sectionFormat="of" section="6" />).</li>
        </ul>
        <t>Considering this, the definition of equivalence and normalization is left to client and server
	implementations and to be negotiated by a calendar exchange protocol or defined elsewhere.</t>
      </section>
      <section anchor="custom-properties" title="Vendor-specific numbered="true" toc="default">
        <name>Vendor-Specific Property Extensions, Values Values, and Types"> Types</name>
        <t>Vendors MAY <bcp14>MAY</bcp14> add additional properties to the calendar object to support their custom features. To avoid conflict, the names of these properties MUST <bcp14>MUST</bcp14> be prefixed by a domain name controlled by the vendor followed by a colon, e.g., <spanx style="verb">example.com:customprop</spanx>. <tt>example.com:customprop</tt>. If the value is a new JSCalendar object, it either MUST <bcp14>MUST</bcp14> include a <spanx style="verb">@type</spanx> property an <tt>@type</tt> property, or it MUST <bcp14>MUST</bcp14> explicitly be specified to not require a type designator. The type name MUST <bcp14>MUST</bcp14> be prefixed with a domain name controlled by the vendor.</t>
        <t>Some JSCalendar properties allow vendor-specific value extensions. Such vendor-specific values MUST <bcp14>MUST</bcp14> be prefixed by a domain name controlled by the vendor followed by a colon, e.g., <spanx style="verb">example.com:customrel</spanx>.</t> <tt>example.com:customrel</tt>.</t>
        <t>Vendors are strongly encouraged to register any new property values or extensions that are useful to other systems as well, rather than use a vendor-specific prefix.</t>
      </section>
    </section>
    <section anchor="jscalendar-props" title="Common numbered="true" toc="default">
      <name>Common JSCalendar Properties"> Properties</name>
      <t>This section describes the properties that are common to the various JSCalendar object types. Specific JSCalendar object types may only support a subset of these properties. The object type definitions in <xref target="jscalendar-object-props" /> format="default"/> describe the set of supported properties per type.</t>
      <section anchor="metadata-properties" title="Metadata Properties"> numbered="true" toc="default">
        <name>Metadata Properties</name>
        <section anchor="prop-type" title="@type"> numbered="true" toc="default">
          <name>@type</name>
          <t>Type: <spanx style="verb">String</spanx> (mandatory).</t>
          <t>Specifies <tt>String</tt> (mandatory)</t>
          <t>This specifies the type which that this object represents. This MUST be one of the following values:
            <list style="symbols">
              <t><spanx style="verb">jsevent</spanx>: a JSCalendar event (<xref The allowed value differs by object type and is defined in Sections <xref target="jsevent" />).</t>
              <t><spanx style="verb">jstask</spanx>: a JSCalendar task (<xref format="counter"/>, <xref target="jstask" />).</t>
              <t><spanx style="verb">jsgroup</spanx>: a JSCalendar group (<xref format="counter"/>, and <xref target="jsgroup" />).</t>
            </list>
          </t> format="counter"/>.</t>
        </section>
        <section anchor="prop-uid" title="uid"> numbered="true" toc="default">
          <name>uid</name>
          <t>Type: <spanx style="verb">String</spanx> (mandatory).</t>
          <t>A <tt>String</tt> (mandatory)</t>
          <t>This is a globally unique identifier, identifier used to associate the object as objects representing the same event, task, group, or other object across different systems, calendars calendars, and views. The value of this property MUST be unique across For recurring events and tasks, the UID is associated with the base object and therefore is the same for all JSCalendar objects, even if they are occurrences; the combination of different type. the UID with a <tt>recurrenceId</tt> identifies a particular instance.</t>
          <t>The generator of the identifier <bcp14>MUST</bcp14> guarantee that the identifier is unique. <xref target="RFC4122" /> format="default"/> describes a range of established algorithms to generate universally unique identifiers (UUID). (UUIDs). UUID version 4, described in Section 4.4 of <xref target="RFC4122" />, sectionFormat="of" section="4.4"/>, is RECOMMENDED.</t> <bcp14>RECOMMENDED</bcp14>.</t>
          <t>For compatibility with  UIDs <xref target="RFC5545" /> UIDs, format="default"/>, implementations MUST <bcp14>MUST</bcp14> be able to receive and persist values of at least 255 octets for this property, but they MUST NOT <bcp14>MUST NOT</bcp14> truncate values in the middle of a UTF-8 multi-octet sequence.</t>
        </section>
        <section anchor="prop-relatedTo" title="relatedTo"> numbered="true" toc="default">
          <name>relatedTo</name>
          <t>Type: <spanx style="verb">String[Relation]</spanx> (optional).</t>

          <t>Relates <tt>String[Relation]</tt> (optional)</t>
          <t>This relates the object to other JSCalendar objects. This is represented as a map of the UIDs of
	    the related objects to information about the relation.</t>
          <t>If an object is split to make a "this and future" change to a recurrence, the original object MUST <bcp14>MUST</bcp14> be truncated to end at the previous occurrence before this split, and a new object is created to represent all the occurrences after the split. A <spanx style="verb">next</spanx> <tt>next</tt> relation MUST <bcp14>MUST</bcp14> be set on the original object's relatedTo <tt>relatedTo</tt> property for the UID of the new object. A <spanx style="verb">first</spanx> <tt>first</tt> relation for the UID of the first object in the series MUST <bcp14>MUST</bcp14> be set on the new object. Clients can then follow these UIDs to get the complete set of objects if the user wishes to modify them all at once.</t>
        </section>
        <section anchor="prop-prodId" title="prodId"> numbered="true" toc="default">
          <name>prodId</name>
          <t>Type: <spanx style="verb">String</spanx> (optional).</t>

          <t>The <tt>String</tt> (optional)</t>
          <t>This is the identifier for the product that last updated the JSCalendar object. This should be set whenever the data in the object is modified (i.e., whenever the "updated" <tt>updated</tt> property is set).</t>
          <t>The vendor of the implementation MUST <bcp14>MUST</bcp14> ensure that this is a globally unique identifier, using some technique such as an FPI a Formal Public Identifier (FPI) value, as defined in [ISO.9070.1991].</t> <xref target="ISO.9070.1991"/>.</t>
          <t>This property SHOULD NOT <bcp14>SHOULD NOT</bcp14> be used to alter the interpretation of a JSCalendar object beyond the semantics specified in this document. For example, it is not to be used to further the understanding of non-standard nonstandard properties, a practice that is known to cause long-term interoperability problems.</t>
        </section>
        <section anchor="prop-created" title="created"> numbered="true" toc="default">
          <name>created</name>
          <t>Type: <spanx style="verb">UTCDateTime</spanx> (optional).</t>

          <t>The <tt>UTCDateTime</tt> (optional)</t>
          <t>This is the date and time this object was initially created.</t>
        </section>
        <section anchor="prop-updated" title="updated"> numbered="true" toc="default">
          <name>updated</name>
          <t>Type: <spanx style="verb">UTCDateTime</spanx> (mandatory).</t>

          <t>The <tt>UTCDateTime</tt> (mandatory)</t>
          <t>This is the date and time the data in this object was last modified (or its creation date/time if
	    not modified since).</t>
        </section>
        <section anchor="prop-sequence" title="sequence"> numbered="true" toc="default">
          <name>sequence</name>
          <t>Type: <spanx style="verb">UnsignedInt</spanx> <tt>UnsignedInt</tt> (optional, default: 0).</t> 0)</t>
          <t>Initially zero, this MUST <bcp14>MUST</bcp14> be incremented by one every time a change is made to the
	    object, except if the change only modifies the <spanx style="verb">participants</spanx> <tt>participants</tt> property (see <xref
	      target="prop-participants" />).</t> format="default"/>).</t>
          <t>This is used as part of iTIP the iCalendar Transport-independent Interoperability Protocol (iTIP) <xref
	    target="RFC5546" /> format="default"/> to know which version of the object a scheduling message relates
	    to.</t>
        </section>
        <section anchor="prop-method" title="method"> numbered="true" toc="default">
          <name>method</name>
          <t>Type: <spanx style="verb">String</spanx> (optional).</t>

          <t>The <tt>String</tt> (optional)</t>
          <t>This is the iTIP <xref target="RFC5546" /> format="default"/> method, in lowercase. This MUST <bcp14>MUST</bcp14>
	    only be present if the JSCalendar object represents an iTIP scheduling message.</t>
        </section>
      </section>
      <section anchor="whatwhere-properties" title="What numbered="true" toc="default">
        <name>What and Where Properties"> Properties</name>
        <section anchor="prop-title" title="title"> numbered="true" toc="default">
          <name>title</name>
          <t>Type: <spanx style="verb">String</spanx> <tt>String</tt> (optional, default: empty String).</t>

          <t>A String)</t>
          <t>This is a short summary of the object.</t>
        </section>
        <section anchor="prop-description" title="description"> numbered="true" toc="default">
          <name>description</name>
          <t>Type: <spanx style="verb">String</spanx> <tt>String</tt> (optional, default: empty String).</t>

          <t>A String)</t>
          <t>This is a longer-form text description of the object. The content is formatted according to the <spanx style="verb">descriptionContentType</spanx>
	    <tt>descriptionContentType</tt> property.</t>
        </section>
        <section anchor="prop-descriptionContentType" title="descriptionContentType"> numbered="true" toc="default">
          <name>descriptionContentType</name>
          <t>Type: <spanx style="verb">String</spanx> <tt>String</tt> (optional, default: <spanx style="verb">text/plain</spanx>).</t>

          <t>Describes <tt>text/plain</tt>)</t>
          <t>This describes the media type <xref target="RFC6838" /> format="default"/> of the contents of the <spanx style="verb">description</spanx>
	    <tt>description</tt> property. Media types MUST <bcp14>MUST</bcp14> be sub-types subtypes of type <spanx style="verb">text</spanx>, <tt>text</tt> and SHOULD
	      <bcp14>SHOULD</bcp14> be <spanx style="verb">text/plain</spanx> <tt>text/plain</tt> or <spanx style="verb">text/html</spanx> <tt>text/html</tt> <xref target="MEDIATYPES" />.
	        format="default"/>. They MAY <bcp14>MAY</bcp14> include parameters parameters, and the <spanx style="verb">charset</spanx> <tt>charset</tt> parameter
	        value MUST <bcp14>MUST</bcp14> be <spanx style="verb">utf-8</spanx>, <tt>utf-8</tt>, if specified. Descriptions of type <spanx style="verb">text/html</spanx> MAY <tt>text/html</tt>
		  <bcp14>MAY</bcp14> contain <spanx style="verb">cid</spanx> <tt>cid</tt> URLs <xref target="RFC2392" /> format="default"/> to reference
		    links in the calendar object by use of the <spanx style="verb">cid</spanx> <tt>cid</tt> property of the Link object.</t>
        </section>
        <section anchor="prop-showWithoutTime" title="showWithoutTime"> numbered="true" toc="default">
          <name>showWithoutTime</name>
          <t>Type: <spanx style="verb">Boolean</spanx> <tt>Boolean</tt> (optional, default: false).</t>

          <t>Indicates false)</t>
          <t>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.</t>
          <t>Such events are also commonly known as "all-day" events.</t>
        </section>
        <section anchor="prop-locations" title="locations"> numbered="true" toc="default">
          <name>locations</name>
          <t>Type: <spanx style="verb">Id[Location]</spanx> (optional).</t>

          <t>A <tt>Id[Location]</tt> (optional)</t>
          <t>This is a map of location ids to Location objects, representing locations associated with the
	    object.</t>
          <t>A Location object has the following properties. It MUST <bcp14>MUST</bcp14> have at least one property
	    other than the <spanx style="verb">relativeTo</spanx> <tt>relativeTo</tt> property.</t>

          <t><list style="symbols">
            <t>@type: <spanx style="verb">String</spanx> (mandatory)
            <vspace blankLines="1" />
            Specifies
          <dl newline="true">
              <dt>@type: <tt>String</tt> (mandatory)</dt>
              <dd>This specifies the type of this object. This MUST <bcp14>MUST</bcp14> be <spanx style="verb">Location</spanx>.
            </t>
            <t>name: <spanx style="verb">String</spanx> (optional)
            <vspace blankLines="1" />
            The human-readable <tt>Location</tt>.</dd>
              <dt>name: <tt>String</tt> (optional)</dt>
              <dd>This is the human-readable name of the location.</t>

            <t>description: <spanx style="verb">String</spanx> (optional)
            <vspace blankLines="1" />
            Human-readable, location.</dd>
              <dt>description: <tt>String</tt> (optional)</dt>
              <dd>This is the human-readable, plain-text instructions for accessing this location. This may be
	            an address, set of directions, door access code, etc.</t>

            <t>locationTypes: <spanx style="verb">String[Boolean]</spanx> (optional)
            <vspace blankLines="1" />
            A etc.</dd>
              <dt>locationTypes: <tt>String[Boolean]</tt> (optional)</dt>
              <dd>This is a set of one or more location types that describe this location. All types MUST
	            <bcp14>MUST</bcp14> be from the Location &quot;Location Types Registry Registry&quot; <xref target="LOCATIONTYPES" />
		          format="default"/>, as defined in <xref target="RFC4589" />. format="default"/>. The set is
		          represented as a map, with the keys being the location types. The value for each key in the map MUST
			        <bcp14>MUST</bcp14> be true.
            </t>

            <t>relativeTo: <spanx style="verb">String</spanx> (optional)
            <vspace blankLines="1" />
            Specifies true.</dd>
              <dt>relativeTo: <tt>String</tt> (optional)</dt>
              <dd><t>This specifies the relation between this location and the time of the JSCalendar object.
	            This
		          is primarily to allow events representing travel to specify the location of departure (at the
			        start of the event) and location of arrival (at the end); this is particularly important if these
				      locations are in different time zones, as a client may wish to highlight this information for the user.
            <vspace blankLines="1" />
            This MUST
				            user.</t>
              <t>This <bcp14>MUST</bcp14> be one of the following values, another value registered in the IANA JSCalendar
	            &quot;JSCalendar Enum Values Values&quot; registry, or a vendor-specific value (see <xref target="custom-properties" />).
		          format="default"/>). Any value the client or server doesn't understand should be treated the same
		          as if this property is omitted.
            <list style="symbols">
              <t><spanx style="verb">start</spanx>: The omitted.</t>
              <dl>
                <dt><tt>start</tt>:</dt>
		<dd>The event/task described by this JSCalendar object occurs at this location at the time the
		event/task starts.</t>
              <t><spanx style="verb">end</spanx>: The starts.</dd>
                <dt><tt>end</tt>:</dt>
		<dd>The event/task described by this JSCalendar object occurs at this location at the time the
		event/task ends.</t>
            </list></t>

            <t>timeZone: <spanx style="verb">TimeZoneId</spanx> (optional)
            <vspace blankLines="1" />
            A ends.</dd>
              </dl></dd>
              <dt>timeZone: <tt>TimeZoneId</tt> (optional)</dt>
              <dd>This is a time zone for this location.</t>

            <t>coordinates: <spanx style="verb">String</spanx> (optional)
            <vspace blankLines="1" />
            A <spanx style="verb">geo:</spanx> location.</dd>
            <dt>coordinates: <tt>String</tt> (optional)</dt>
              <dd>This is a <tt>geo:</tt> URI <xref target="RFC5870" /> format="default"/> for the location.</t>

            <t>links: <spanx style="verb">Id[Link]</spanx> (optional)
            <vspace blankLines="1" />
            A location.</dd>
              <dt>links: <tt>Id[Link]</tt> (optional)</dt>
              <dd>This is a map of link ids to Link objects, representing external resources associated with
	            this location, for example example, a vCard or image. If there are no links, this MUST
		          <bcp14>MUST</bcp14> be omitted (rather than specified as an empty set).</t>
          </list></t> set).</dd>
          </dl>
        </section>
        <section anchor="prop-virtualLocations" title="virtualLocations"> numbered="true" toc="default">
          <name>virtualLocations</name>
          <t>Type: <spanx style="verb">Id[VirtualLocation]</spanx> (optional).</t>

          <t>A <tt>Id[VirtualLocation]</tt> (optional)</t>
          <t>This is a map of virtual location ids to VirtualLocation objects, representing virtual locations,
	    such as video conferences or chat rooms, associated with the object.</t>
          <t>A VirtualLocation object has the following properties.</t>
          <t><list style="symbols">
            <t>@type: <spanx style="verb">String</spanx> (mandatory)
            <vspace blankLines="1" />
            Specifies
          <dl newline="true">
              <dt>@type: <tt>String</tt> (mandatory)</dt>
              <dd>This specifies the type of this object. This MUST <bcp14>MUST</bcp14> be <spanx style="verb">VirtualLocation</spanx>.</t>
            <t>name: <spanx style="verb">String</spanx>
	            <tt>VirtualLocation</tt>.</dd>
              <dt>name: <tt>String</tt> (optional, default: empty String)
            <vspace blankLines="1" />
            The String)</dt>
              <dd>This is the human-readable name of the virtual location.</t>

            <t>description: <spanx style="verb">String</spanx> (optional)
            <vspace blankLines="1" />
            Human-readable location.</dd>
              <dt>description: <tt>String</tt> (optional)</dt>
              <dd>These are human-readable plain-text instructions for accessing this virtual location. This
	            may be a conference access code, etc.</t>

            <t>uri: <spanx style="verb">String</spanx> (mandatory)
            <vspace blankLines="1" />
            A etc.</dd>
              <dt>uri: <tt>String</tt> (mandatory)</dt>
              <dd><t>This is a URI <xref target="RFC3986" /> format="default"/> that represents how to connect to
	            this virtual location.
            <vspace blankLines="1" />
            This location.</t>
              <t>This may be a telephone number (represented using the <spanx style="verb">tel:</spanx> <tt>tel:</tt> scheme, e.g., <spanx style="verb">tel:+1-555-555-5555</spanx>)
	            <tt>tel:+1-555-555-5555</tt>) for a teleconference, a web address for online chat, or any custom URI.</t>
          </list></t>
		          URI.</t></dd>
              <dt>features: <tt>String[Boolean]</tt> (optional)</dt>
              <dd><t>A set of features supported by this virtual location. The set is represented as a map, with the keys being the feature. The value for each key in the map <bcp14>MUST</bcp14> be true.</t>
              <t>The feature <bcp14>MUST</bcp14> be one of the following values, another value registered in the IANA &quot;JSCalendar Enum Values&quot; registry, or a vendor-specific value (see <xref target="custom-properties" />). Any value the client or server doesn't understand should be treated the same as if this feature is omitted.</t>
              <dl>
                <dt>audio:</dt>
                  <dd>Audio conferencing</dd>
                <dt>chat:</dt>
                  <dd>Chat or instant messaging</dd>
                <dt>feed:</dt>
                  <dd>Blog or atom feed</dd>
                <dt>moderator:</dt>
                  <dd>Provides moderator-specific features</dd>
                <dt>phone:</dt>
                  <dd>Phone conferencing</dd>
                <dt>screen:</dt>
                  <dd>Screen sharing</dd>
                <dt>video:</dt>
                  <dd>Video conferencing</dd>
              </dl></dd>
          </dl>
        </section>
        <section anchor="prop-links" title="links"> numbered="true" toc="default">
          <name>links</name>
          <t>Type: <spanx style="verb">Id[Link]</spanx> (optional).</t>

          <t>A <tt>Id[Link]</tt> (optional)</t>
          <t>This is a map of link ids to Link objects, representing external resources associated with the
	    object.</t>
          <t>Links with a rel of <spanx style="verb">enclosure</spanx> MUST <tt>enclosure</tt> <bcp14>MUST</bcp14> be considered by the client as to be
	    attachments for download.
          <vspace blankLines="1" />
          Links download.</t>
	      <t>Links with a rel of <spanx style="verb">describedby</spanx> MUST <tt>describedby</tt> <bcp14>MUST</bcp14> be considered by the client to be an
	        alternative representation representations of the description.
          <vspace blankLines="1" />
          Links description.</t>
          <t>Links with a rel of <spanx style="verb">icon</spanx> MUST <tt>icon</tt> <bcp14>MUST</bcp14> be considered by the client to be an image images
	    that it may use when presenting the calendar data to a user. The <spanx style="verb">display</spanx> <tt>display</tt> property may be set
	      to indicate the purpose of this image.</t>
        </section>
        <section anchor="prop-locale" title="locale"> numbered="true" toc="default">
          <name>locale</name>
          <t>Type: <spanx style="verb">String</spanx> (optional).</t>

          <t>The <tt>String</tt> (optional)</t>
          <t>This is the language tag tag, as defined in <xref target="RFC5646" /> target="BCP47" format="default"/>, that best
	    describes the locale used for the text in the calendar object, if known.</t>
        </section>
        <section anchor="prop-keywords" title="keywords"> numbered="true" toc="default">
          <name>keywords</name>
          <t>Type: <spanx style="verb">String[Boolean]</spanx> (optional).</t>

          <t>A <tt>String[Boolean]</tt> (optional)</t>
          <t>This is a set of keywords or tags that relate to the object. The set is represented as a map, with
	    the keys being the keywords. The value for each key in the map MUST <bcp14>MUST</bcp14> be true.</t>
        </section>
        <section anchor="prop-categories" title="categories"> numbered="true" toc="default">
          <name>categories</name>
          <t>Type: <spanx style="verb">String[Boolean]</spanx> (optional).</t>

          <t>A <tt>String[Boolean]</tt> (optional)</t>
          <t>This is a set of categories that relate to the calendar object. The set is represented as a map,
	    with the
	      keys being the categories specified as URIs. The value for each key in the map MUST <bcp14>MUST</bcp14> be
	        true.</t>
          <t>In contrast to keywords, categories typically are typically structured. For example, a vendor owning the
	    domain <spanx style="verb">example.com</spanx> <tt>example.com</tt> might define the categories <spanx style="verb">http://example.com/categories/sports/american-football</spanx>
	      <tt>http://example.com/categories/sports/american-football</tt> and <spanx style="verb">http://example.com/categories/music/r-b</spanx>.</t>
	        <tt>http://example.com/categories/music/r-b</tt>.</t>
        </section>
        <section anchor="prop-color" title="color"> numbered="true" toc="default">
          <name>color</name>
          <t>Type: <spanx style="verb">String</spanx> (optional).</t>

          <t>A <tt>String</tt> (optional)</t>
          <t>This is a color clients MAY <bcp14>MAY</bcp14> use when displaying this calendar object. The value is
	    a color name taken from the set of names defined in Section 4.3 of CSS Color Module Level 3 <xref
	      target="COLORS" />, format="default"/> or an RGB value in hexadecimal notation, as defined in Section
	      4.2.1 of CSS Color Module Level 3.</t>
        </section>
      </section>
      <section anchor="recurrence-props" title="Recurrence Properties"> numbered="true" toc="default">
        <name>Recurrence Properties</name>
        <t>Some events and tasks occur at regular or irregular intervals. Rather than having to copy the data for every occurrence occurrence, there can be a master base event with rules to generate recurrences, recurrences and/or overrides that add extra dates or exceptions to the rules.</t>
        <t>The recurrence set is the complete set of instances for an object. It is generated by considering the following properties in order, all of which are optional:
          <list style="numbers">
            <t>The recurrenceRules
        </t>
        <ol spacing="normal" type="1">
	    <li>The <tt>recurrenceRules</tt> property (<xref target="prop-recurrenceRules" />)
	    format="default"/>) generates a set of extra date-times on which the object occurs.</t>
            <t>The excludedRecurrenceRules occurs.</li>
          <li>The <tt>excludedRecurrenceRules</tt> property (<xref target="prop-excludedRecurrenceRules" />)
	    format="default"/>) generates a set of date-times that are to be removed from the previously
	    generated set of date-times on which the object occurs.</t>
            <t>The recurrenceOverrides occurs.</li>
          <li>The <tt>recurrenceOverrides</tt> property (<xref target="prop-recurrenceOverrides" />) format="default"/>)
	    defines date-times which that are added or excluded to form the final set. (This property may also contain
	      changes to the object to apply to particular instances.)</t>
          </list>
        </t> instances.)</li>
        </ol>
        <section anchor="prop-recurrenceId" title="recurrenceId"> numbered="true" toc="default">
          <name>recurrenceId</name>
          <t>Type: <spanx style="verb">LocalDateTime</spanx> (optional).</t> <tt>LocalDateTime</tt> (optional)</t>
          <t>If present, this JSCalendar object represents one occurrence of a recurring JSCalendar object. If present
	    present, the <spanx style="verb">recurrenceRules</spanx> <tt>recurrenceRules</tt> and <spanx style="verb">recurrenceOverrides</spanx> <tt>recurrenceOverrides</tt> properties MUST NOT <bcp14>MUST
	      NOT</bcp14> be present.</t>
          <t>The value is a date-time either produced by the <spanx style="verb">recurrenceRules</spanx> <tt>recurrenceRules</tt> of the master event, base event or
	    added as a key to the <spanx style="verb">recurrenceOverrides</spanx> <tt>recurrenceOverrides</tt> property of the master base event.</t>
        </section>
        <section anchor="prop-recurrenceIdTimeZone" numbered="true" toc="default">
          <name>recurrenceIdTimeZone</name>
          <t>Type: <tt>TimeZoneId|null</tt> (optional, default: null)</t>
          <t> Identifies the time zone of the main JSCalendar object, of which this JSCalendar object is a recurrence instance. This property <bcp14>MUST</bcp14> be set if the <tt>recurrenceId</tt> property is set. It <bcp14>MUST NOT</bcp14> be set if the <tt>recurrenceId</tt> property is not set.</t>
        </section>
        <section anchor="prop-recurrenceRules" title="recurrenceRules"> numbered="true" toc="default">
          <name>recurrenceRules</name>
          <t>Type: <spanx style="verb">RecurrenceRule[]</spanx> (optional).</t>

          <t>Defines <tt>RecurrenceRule[]</tt> (optional)</t>
          <t>This defines a set of recurrence rules (repeating patterns) for recurring calendar objects.</t>

          <t>A JSEvent
          <t>An Event recurs by applying the recurrence rules to the <spanx style="verb">start</spanx> <tt>start</tt> date-time.</t>
          <t>A JSTask Task recurs by applying the recurrence rules to the <spanx style="verb">start</spanx> <tt>start</tt> date-time, if defined, otherwise defined;
	    otherwise, it recurs by the <spanx style="verb">due</spanx> <tt>due</tt> date-time, if defined. If the task defines neither a <spanx style="verb">start</spanx>
	      <tt>start</tt> nor <spanx style="verb">due</spanx> <tt>due</tt> date-time, it MUST NOT <bcp14>MUST NOT</bcp14> define a <spanx style="verb">recurrenceRules</spanx>
	        <tt>recurrenceRules</tt> property.</t>
          <t>If multiple recurrence rules are given, each rule is to be applied applied, and then the union of the
	    results are used, ignoring any duplicates.</t>
          <t>A RecurrenceRule object is a JSON object mapping of a RECUR value type in iCalendar <xref
	    target="RFC5545" /> format="default"/> <xref target="RFC7529" /> format="default"/> and has the same
	    semantics. It has the following properties:

              <list style="symbols">
            <t>@type: <spanx style="verb">String</spanx> (mandatory)
            <vspace blankLines="1" />
            Specifies properties:</t>
          <dl newline="true">
              <dt>@type: <tt>String</tt> (mandatory)</dt>
              <dd>This specifies the type of this object. This MUST <bcp14>MUST</bcp14> be <spanx style="verb">RecurrenceRule</spanx>.</t>
            <t>frequency: <spanx style="verb">String</spanx> (mandatory)
            <vspace blankLines="1" />
            The
	            <tt>RecurrenceRule</tt>.</dd>
              <dt>frequency: <tt>String</tt> (mandatory)</dt>
              <dd><t>This is the time span covered by each iteration of this recurrence rule (see <xref
	            target="recurrence-semantics" /> format="default"/> for full semantics). This MUST <bcp14>MUST</bcp14> be
	            one of the following values:

            <list style="symbols">
              <t><spanx style="verb">yearly</spanx></t>
              <t><spanx style="verb">monthly</spanx></t>
              <t><spanx style="verb">weekly</spanx></t>
              <t><spanx style="verb">daily</spanx></t>
              <t><spanx style="verb">hourly</spanx></t>
              <t><spanx style="verb">minutely</spanx></t>
              <t><spanx style="verb">secondly</spanx></t>
            </list>

            This values:</t>
              <ul spacing="normal">
                <li><tt>yearly</tt></li>
                <li><tt>monthly</tt></li>
                <li><tt>weekly</tt></li>
                <li><tt>daily</tt></li>
                <li><tt>hourly</tt></li>
                <li><tt>minutely</tt></li>
                <li><tt>secondly</tt></li>
              </ul>
              <t>This is the FREQ part from iCalendar, converted to lowercase.</t>

            <t>interval: <spanx style="verb">UnsignedInt</spanx>
              </dd>
              <dt>interval: <tt>UnsignedInt</tt> (optional, default: 1)
            <vspace blankLines="1" />
            The 1)</dt>
              <dd><t>This is the interval of iteration periods at which the recurrence repeats. If included, it MUST
	            <bcp14>MUST</bcp14> be an integer &gt;= 1.
            <vspace blankLines="1" />
            This 1.</t>
              <t>This is the INTERVAL part from iCalendar.</t>

            <t>rscale: <spanx style="verb">String</spanx> iCalendar.</t></dd>
              <dt>rscale: <tt>String</tt> (optional, default: "gregorian")
            <vspace blankLines="1" />
            The "gregorian")</dt>
              <dd><t>This is the calendar system in which this recurrence rule operates, in lowercase. This MUST
	            <bcp14>MUST</bcp14> be either a CLDR-registered calendar system name <xref target="CLDR" />,
		          format="default"/> or a vendor-specific value (see <xref target="custom-properties" />).
            <vspace blankLines="1" />
            This
			        format="default"/>).</t>
              <t>This is the RSCALE part from iCalendar <xref target="RFC7529">RSCALE</xref>, target="RFC7529" format="default">RSCALE</xref>,
	            converted to lowercase.</t>

            <t>skip: <spanx style="verb">String</spanx>
              </dd>
              <dt>skip: <tt>String</tt> (optional, default: "omit")
            <vspace blankLines="1" />
            The behaviour "omit")</dt>
              <dd><t>This is the behavior to use when the expansion of the recurrence produces invalid dates.
	            This
		          property only has an effect if the frequency is "yearly" or "monthly". It MUST <bcp14>MUST</bcp14> be
			        one of the following values:

            <list style="symbols">
              <t><spanx style="verb">omit</spanx></t>
              <t><spanx style="verb">backward</spanx></t>
              <t><spanx style="verb">forward</spanx></t>
            </list>

            This values:</t>
              <ul spacing="normal">
                <li><tt>omit</tt></li>
                <li><tt>backward</tt></li>
                <li><tt>forward</tt></li>
              </ul>
              <t>This is the SKIP part from iCalendar <xref target="RFC7529">RSCALE</xref>, target="RFC7529" format="default">RSCALE</xref>,
	            converted to lowercase.</t>

            <t>firstDayOfWeek: <spanx style="verb">String</spanx>
              </dd>
              <dt>firstDayOfWeek: <tt>String</tt> (optional, default: "mo")
            <vspace blankLines="1" />
            The "mo")</dt>
              <dd><t>This is the day on which the week is considered to start, represented as a lowercase abbreviated lowercase,
	            abbreviated, and two-letter English day of the week. If included, it MUST <bcp14>MUST</bcp14> be one
		          of the following values:

            <list style="symbols">
              <t><spanx style="verb">mo</spanx></t>
              <t><spanx style="verb">tu</spanx></t>
              <t><spanx style="verb">we</spanx></t>
              <t><spanx style="verb">th</spanx></t>
              <t><spanx style="verb">fr</spanx></t>
              <t><spanx style="verb">sa</spanx></t>
              <t><spanx style="verb">su</spanx></t>
            </list>

            This values:</t>
              <ul spacing="normal">
                <li><tt>mo</tt></li>
                <li><tt>tu</tt></li>
                <li><tt>we</tt></li>
                <li><tt>th</tt></li>
                <li><tt>fr</tt></li>
                <li><tt>sa</tt></li>
                <li><tt>su</tt></li>
              </ul>
              <t>This is the WKST part from iCalendar.</t>

            <t>byDay: <spanx style="verb">NDay[]</spanx> (optional)
            <vspace blankLines="1" />
            Days
              </dd>
              <dt>byDay: <tt>NDay[]</tt> (optional)</dt>
              <dd><t>These are days of the week on which to repeat. An <spanx style="verb">NDay</spanx> <tt>NDay</tt> object has the following properties:

            <list style="symbols">
              <t>@type: <spanx style="verb">String</spanx> (mandatory)
              <vspace blankLines="1" />
              Specifies
	            properties:</t>
              <dl newline="true">
                  <dt>@type: <tt>String</tt> (mandatory)</dt>
                  <dd>This specifies the type of this object. This MUST <bcp14>MUST</bcp14> be <spanx style="verb">NDay</spanx>.</t>
              <t>day: <spanx style="verb">String</spanx> (mandatory)
              <vspace blankLines="1" />
              A <tt>NDay</tt>.</dd>
                  <dt>day: <tt>String</tt> (mandatory)</dt>
                  <dd><t>This is a day of the week on which to repeat; the allowed values are the same as for
		    the <spanx style="verb">firstDayOfWeek</spanx> RecurrenceRule property.
              <vspace blankLines="1" />
              This <tt>firstDayOfWeek</tt> recurrenceRule property.</t>
                  <t>This is the day-of-the-week day of the week of the BYDAY part in iCalendar, converted to lowercase.</t>
              <t>nthOfPeriod: <spanx style="verb">Int</spanx> (optional)
              <vspace blankLines="1" />
              If
                  </dd>
                  <dt>nthOfPeriod: <tt>Int</tt> (optional)</dt>
                  <dd><t>If present, rather than representing every occurrence of the weekday defined in the <spanx style="verb">day</spanx>
		    <tt>day</tt> property, it represents only a specific instance within the recurrence period.
		      The value can be positive or negative, negative but MUST NOT <bcp14>MUST NOT</bcp14> be zero. A negative integer means the nth-last of period.
              <vspace blankLines="1" />
              This occurrence within that period (i.e., -1 is the last occurrence, -2 the one before that, etc.).</t>
                  <t>This is the ordinal part of the BYDAY value in iCalendar (e.g., 1 or -3).</t>
            </list></t>

            <t>byMonthDay: <spanx style="verb">Int[]</spanx>
                  </dd>
              </dl>
              </dd>
              <dt>byMonthDay: <tt>Int[]</tt> (optional)
            <vspace blankLines="1" />
            Days
              </dt>
              <dd><t>These are the days of the month on which to repeat. Valid values are between 1 and the
	            maximum number of
		          days any month may have in the calendar given by the "rscale" property, <tt>rscale</tt> property and the negative values
			        of these numbers. For example, in the Gregorian calendar calendar, valid values are 1 to 31 and -31 to -1.
				      Negative values offset from the end of the month. The array MUST <bcp14>MUST</bcp14> have at least one
				            entry if included.
            <vspace blankLines="1" />
            This included.</t>
              <t>This is the BYMONTHDAY part in iCalendar.</t>

            <t>byMonth: <spanx style="verb">String[]</spanx> (optional)
            <vspace blankLines="1" />
            The
              </dd>
              <dt>byMonth: <tt>String[]</tt> (optional)</dt>
              <dd><t>These are the months in which to repeat. Each entry is a string representation of a
	            number, starting
		          from "1" for the first month in the calendar (e.g., "1" means January with the Gregorian
			        calendar), with an optional "L" suffix (see <xref target="RFC7529" />) format="default"/>) for leap
				      months (this MUST <bcp14>MUST</bcp14> be uppercase, e.g., "3L"). The array MUST <bcp14>MUST</bcp14> have at
				            least one entry if included.
            <vspace blankLines="1" />
            This included.</t>
              <t>This is the BYMONTH part from iCalendar.</t>

            <t>byYearDay: <spanx style="verb">Int[]</spanx> (optional)
            <vspace blankLines="1" />
            The
              </dd>
              <dt>byYearDay: <tt>Int[]</tt> (optional)</dt>
              <dd><t>These are the days of the year on which to repeat. Valid values are between 1 and the
	            maximum number
		          of days any year may have in the calendar given by the "rscale" property, <tt>rscale</tt> property and the negative values
			        of these numbers. For example, in the Gregorian calendar calendar, valid values are 1 to 366 and -366 to
				      -1. Negative values offset from the end of the year. The array MUST <bcp14>MUST</bcp14> have at least
				            one entry if included.
            <vspace blankLines="1" />
            This included.</t>
              <t>This is the BYYEARDAY part from iCalendar.</t>

            <t>byWeekNo: <spanx style="verb">Int[]</spanx> (optional)
            <vspace blankLines="1" />
            Weeks
              </dd>
              <dt>byWeekNo: <tt>Int[]</tt> (optional)</dt>
              <dd><t>These are the weeks of the year in which to repeat. Valid values are between 1 and the
	            maximum number of
		          weeks any year may have in the calendar given by the "rscale" property, <tt>rscale</tt> property and the negative values
			        of these numbers. For example, in the Gregorian calendar calendar, valid values are 1 to 53 and -53 to -1.
				      The array MUST <bcp14>MUST</bcp14> have at least one entry if included.
            <vspace blankLines="1" />
            This included.</t>
              <t>This is the BYWEEKNO part from iCalendar.</t>

            <t>byHour: <spanx style="verb">UnsignedInt[]</spanx> (optional)
            <vspace blankLines="1" />
            The
              </dd>
              <dt>byHour: <tt>UnsignedInt[]</tt> (optional)</dt>
              <dd><t>These are the hours of the day in which to repeat. Valid values are 0 to 23. The array MUST
	            <bcp14>MUST</bcp14> have at least one entry if included. This is the BYHOUR part from
		          iCalendar.</t>

            <t>byMinute: <spanx style="verb">UnsignedInt[]</spanx>
              </dd>
              <dt>byMinute: <tt>UnsignedInt[]</tt> (optional)
            <vspace blankLines="1" />
            The
              </dt>
              <dd><t>These are the minutes of the hour in which to repeat. Valid values are 0 to 59. The array MUST
	            <bcp14>MUST</bcp14> have at least one entry if included.
            <vspace blankLines="1" />
            This included.</t>
              <t>This is the BYMINUTE part from iCalendar.</t>

            <t>bySecond: <spanx style="verb">UnsignedInt[]</spanx> (optional)
            <vspace blankLines="1" />
            The
              </dd>
              <dt>bySecond: <tt>UnsignedInt[]</tt> (optional)</dt>
              <dd><t>These are the seconds of the minute in which to repeat. Valid values are 0 to 60. The
	            array MUST <bcp14>MUST</bcp14> have at least one entry if included.
            <vspace blankLines="1" />
            This included.</t>
              <t>This is the BYSECOND part from iCalendar.</t>

            <t>bySetPosition: <spanx style="verb">Int[]</spanx> (optional)
            <vspace blankLines="1" />
            The
              </dd>
              <dt>bySetPosition: <tt>Int[]</tt> (optional)</dt>
              <dd>These are the occurrences within the recurrence interval to include in the final results.
	            Negative values offset from the end of the list of occurrences. The array MUST <bcp14>MUST</bcp14>
		          have at least one entry if included. This is the BYSETPOS part from iCalendar.</t>

            <t>count: <spanx style="verb">UnsignedInt</spanx> (optional)
            <vspace blankLines="1" />
            The iCalendar.</dd>
              <dt>count: <tt>UnsignedInt</tt> (optional)</dt>
              <dd><t>These are the number of occurrences at which to range-bound the recurrence. This MUST NOT
	            <bcp14>MUST
		          NOT</bcp14> be included if an <spanx style="verb">until</spanx> <tt>until</tt> property is specified.
            <vspace blankLines="1" />
            This specified.</t>
              <t>This is the COUNT part from iCalendar.</t>
            <t>until: <spanx style="verb">LocalDateTime</spanx> (optional)
            <vspace blankLines="1" />
            The
              </dd>
              <dt>until: <tt>LocalDateTime</tt> (optional)</dt>
              <dd><t>These are the date-time at which to finish recurring. The last occurrence is on or before
	            this
		          date-time. This MUST NOT <bcp14>MUST NOT</bcp14> be included if a <spanx style="verb">count</spanx> <tt>count</tt> property is specified. Note:
			        Note that if not specified otherwise for a specific JSCalendar object, this date is to be
				      interpreted
				            in the time zone specified in the JSCalendar object's <spanx style="verb">timeZone</spanx> property.
            <vspace blankLines="1" />
            This <tt>timeZone</tt> property.</t>
              <t>This is the UNTIL part from iCalendar.</t>
          </list></t>
              </dd>
            </dl>
          <section anchor="recurrence-semantics" title="Interpreting recurrence rules"> numbered="true" toc="default">
            <name>Interpreting Recurrence Rules</name>
            <t>A recurrence rule specifies a set of date-times for recurring calendar objects. A recurrence
	        rule has the following semantics. Note, Note that wherever "year", "month" "month", or "day of month" is used,
		    this is
		        within the calendar system given by the "rscale" <tt>rscale</tt> property, which defaults to "gregorian" if omitted.

            <list style="numbers">
			    omitted.</t>
            <ol spacing="normal" type="1"><li>
                <t>A set of candidates is generated. This is every second within a period defined by the frequency
		<tt>frequency</tt> property value:

              <list style="symbols">
                <t><spanx style="verb">yearly</spanx>: every value:</t>
                <dl>
                    <dt><tt>yearly</tt>:</dt>
		        <dd><t>every second from midnight on the 1st first day of a year (inclusive) to midnight the 1st first
			    day of the following year (exclusive).
                <vspace blankLines="1" />
                If (exclusive).</t>
			        <t>If skip is not "omit", the calendar system has leap months months, and there is a byMonth <tt>byMonth</tt>
				    property, generate candidates for the leap months months, even if they don't occur in this year.
                <vspace blankLines="1" />
				        year.</t>
                    <t>
                If skip is not "omit" and there is a byMonthDay <tt>byMonthDay</tt> property, presume each month has the maximum number of days any month may have in this calendar system when generating candidates, even if it's more than this month actually has.</t>

                <t><spanx style="verb">monthly</spanx>: every
			</dd>
                    <dt><tt>monthly</tt>:</dt><dd><t>every second from midnight on the 1st first day of a month (inclusive) to midnight on the 1st first of the following month (exclusive).
                <vspace blankLines="1" />
                  </t>
                    <t>
                If skip is not "omit" and there is a byMonthDay <tt>byMonthDay</tt> property, presume the month has the maximum number of days any month may have in this calendar system when generating candidates, even if it's more than this month actually has.</t>

                <t><spanx style="verb">weekly</spanx>: every has.</t></dd>
                   <dt><tt>weekly</tt>:</dt><dd>every second from midnight (inclusive) on the first day of the week (as defined by the firstDayOfWeek property, <tt>firstDayOfWeek</tt> property or Monday if omitted), omitted) to midnight 7 seven days later (exclusive).</t>

                <t><spanx style="verb">daily</spanx>: every (exclusive).</dd>
                    <dt><tt>daily</tt>:</dt><dd>every second from midnight at the start of the day (inclusive) to midnight at the end of the day (exclusive).</t>

                <t><spanx style="verb">hourly</spanx>: (exclusive).</dd>
                    <dt><tt>hourly</tt>:</dt><dd> every second from the beginning of the hour (inclusive) to the beginning of the next hour (exclusive).</t>

                <t><spanx style="verb">minutely</spanx>: (exclusive).</dd>
                    <dt><tt>minutely</tt>:</dt><dd> every second from the beginning of the minute (inclusive) to the beginning of the next minute (exclusive).</t>

                <t><spanx style="verb">secondly</spanx>: (exclusive).</dd>
                    <dt><tt>secondly</tt>:</dt><dd>only the second itself, only.</t>
              </list></t> itself.</dd>
                </dl>
	      </li>
              <li>
                <t>Each date-time candidate is compared against all of the byX properties of the rule except bySetPosition. If any property in the rule does not match the date-time, the date-time is eliminated. Each byX property is an array; the date-time matches the property if it matches any of the values in the array. The properties have the following semantics:

              <list style="symbols">
                <t>byMonth: the

                </t>
                <dl>
                  <dt>byMonth:</dt>
		    <dd>The date-time is in the given month.</t>

                <t>byWeekNo: the month.</dd>
                    <dt>byWeekNo:</dt>
		        <dd><t>The date-time is in the nth week of the year. Negative numbers mean the nth last week of the year. This corresponds to weeks according to week numbering numbering, as defined in ISO.8601.2004, with a week defined as a seven day seven-day period, starting on the firstDayOfWeek <tt>firstDayOfWeek</tt> property value or Monday if omitted. Week number one of the calendar year is the first week that contains at least four days in that calendar year.
                <vspace blankLines="1" /> year.</t>
                    <t>
                If the date-time is not valid (this may happen when generating candidates with a skip <tt>skip</tt> property in effect), it is always eliminated by this property.</t>

                <t>byYearDay: the property.</t></dd>
                    <dt>byYearDay:</dt>
		        <dd><t>The date-time is on the nth day of year. Negative numbers mean the nth last day of
			    the year.
                <vspace blankLines="1" />
                If year.</t>
                    <t>If the date-time is not valid (this may happen when generating candidates with a skip <tt>skip</tt>
		        property in effect), it is always eliminated by this property.</t>

                <t>byMonthDay: the property.</t></dd>
                  <dt>byMonthDay:</dt>
		    <dd>The date-time is on the given day of the month. Negative numbers mean the nth last day of
		      the month.</t>

                <t>byDay: the month.</dd>
                  <dt>byDay:</dt>
		    <dd>The date-time is on the given day of the week. If the day is prefixed by a number, it is the nth occurrence of that day of the week within the month (if frequency is monthly) or year (if frequency is yearly). Negative numbers means mean the nth last occurrence within that period.</t>

                <t>byHour: the period.</dd>
                  <dt>byHour:</dt>
		    <dd>The date-time has the given hour value.</t>

                <t>byMinute: the value.</dd>
                  <dt>byMinute:</dt>
		    <dd>The date-time has the given minute value.</t>

                <t>bySecond: the value.</dd>
                  <dt>bySecond:</dt>
		    <dd>The date-time has the given second value.</t>
              </list>

              If value.</dd>
                </dl>
                <t>If a skip <tt>skip</tt> property is defined and is not "omit", there may be candidates that do not
		correspond to valid dates (e.g., 31st February 31st in the Gregorian calendar). In this case, the
		properties MUST <bcp14>MUST</bcp14> be considered in the order above and:

              <list style="numbers">
                <t>After above, and:</t>
                <ol spacing="normal" type="1">
		    <li>After applying the byMonth filter, if the candidate's month is invalid for the given year, increment it (if skip is "forward") or decrement it (if skip is "backward") until a valid month is found, incrementing/decrementing the year as well if passing through the beginning/end of the year. This only applies to calendar systems with leap months.</t>
                <t>After months.</li>
                  <li>After applying the byMonthDay filter, if the day of the month is invalid for the given month and year, change the date to the first day of the next month (if skip is "forward") or the last day of the current month (if skip is "backward").</t>
                <t>If "backward").</li>
                  <li>If any valid date produced after applying the skip is already a candidate, eliminate the duplicate. (For example example, after adjusting, 30th February 30th and 31st February 31st would both become the same "real" date, so one is eliminated as a duplicate.)</t>
              </list>
            </t>
              <t>If duplicate.)</li>
                </ol>
              </li>
              <li>If a bySetPosition <tt>bySetPosition</tt> property is included, this is now applied to the ordered list of remaining dates. This property specifies the indexes of date-times to keep; all others should be eliminated. Negative numbers are indexes indexed from the end of the list, with -1 being the last item.</t>

              <t>Any item, -2 the second from last, etc.</li>
              <li>Any date-times before the start date of the event are eliminated (see below for why this might be needed).</t>

              <t>If needed).</li>
              <li>If a skip <tt>skip</tt> property is included and is not "omit", eliminate any date-times that have already been produced by previous iterations of the algorithm. (This is not possible if skip is "omit".)</t>

              <t>If "omit".)</li>
              <li>If further dates are required (we have not reached the until date, date or count limit) limit), skip the next (interval - 1) sets of candidates, then continue from step 1.</t>
            </list>

            When 1.</li>
            </ol>
            <t>When determining the set of occurrence dates for an event or task, the following extra rules
	        must be applied:

            <list style="numbers">
              <t>The applied:</t>
            <ol spacing="normal" type="1">
	            <li>The initial date-time to which the rule is applied (the <spanx style="verb">start</spanx> <tt>start</tt> date-time for events; events
		          or the <spanx style="verb">start</spanx> <tt>start</tt> or <spanx style="verb">due</spanx> <tt>due</tt> date-time for tasks) is always the first occurrence in the
			        expansion (and is counted if the recurrence is limited by a "count" <tt>count</tt> property), even if it would
				      normally not match the rule.</t>

              <t>The rule.</li>
              <li>The first set of candidates to consider is that which would contain the initial date-time.

	            This means the first set may include candidates before the initial date-time; such candidates are
		          eliminated from the results in step (4) as outlined before.</t>

              <t>The 4 of the list above.</li>
              <li><t>The following properties MUST <bcp14>MUST</bcp14> be implicitly added to the rule under the
	            given conditions:

              <list style="symbols">
                <t>If conditions:</t>
                <ul spacing="normal">
                  <li>If frequency is not <spanx style="verb">secondly</spanx> <tt>secondly</tt> and there is no bySecond property: Add <tt>bySecond</tt> property, add a bySecond <tt>bySecond</tt>
		    property with the sole value being the seconds value of the initial date-time.</t>

                <t>If date-time.</li>
                  <li>If frequency is not <spanx style="verb">secondly</spanx> <tt>secondly</tt> or <spanx style="verb">minutely</spanx>, <tt>minutely</tt> and there is no byMinute property: Add <tt>byMinute</tt>
		    property, add a byMinute <tt>byMinute</tt> property with the sole value being the minutes value of the initial date-time.</t>

                <t>If
		      date-time.</li>
                  <li>If frequency is not <spanx style="verb">secondly</spanx>, <spanx style="verb">minutely</spanx> <tt>secondly</tt>, <tt>minutely</tt>, or <spanx style="verb">hourly</spanx> <tt>hourly</tt> and there is
		    no byHour property: Add <tt>byHour</tt> property, add a byHour <tt>byHour</tt> property with the sole value being the hours value of the
		      initial date-time.</t>

                <t>If date-time.</li>
                  <li>If frequency is <spanx style="verb">weekly</spanx> <tt>weekly</tt> and there is no byDay property: Add <tt>byDay</tt> property, add a byDay <tt>byDay</tt> property with
		    the sole value being the day-of-the-week day of the week of the initial date-time.</t>

                <t>If date-time.</li>
                  <li>If frequency is <spanx style="verb">monthly</spanx> <tt>monthly</tt> and there is no byDay <tt>byDay</tt> property and no byMonthDay property: Add <tt>byMonthDay</tt>
		    property, add a byMonthDay <tt>byMonthDay</tt> property with the sole value being the day-of-the-month day of the month of the
		      initial date-time.</t>

                <t>If date-time.</li>
                  <li><t>If frequency is <spanx style="verb">yearly</spanx> <tt>yearly</tt> and there is no byYearDay property:

                <list style="symbols">
                  <t>If <tt>byYearDay</tt> property:</t>
                    <ul spacing="normal">
                      <li>If there are no byMonth <tt>byMonth</tt> or byWeekNo <tt>byWeekNo</tt> properties, and either there is a byMonthDay <tt>byMonthDay</tt> property or there is no byDay property: Add <tt>byDay</tt> property, add a byMonth <tt>byMonth</tt> property with the sole value being the month of the initial date-time.</t>

                  <t>If date-time.</li>
                      <li>If there is are no byMonthDay, byWeekNo <tt>byMonthDay</tt>, <tt>byWeekNo</tt>, or byDay properties: Add <tt>byDay</tt> properties, add a byMonthDay <tt>byMonthDay</tt> property with the sole value being the day-of-the-month day of the month of the initial date-time.</t>

                  <t>If date-time.</li>
                      <li>If there is a byWeekNo <tt>byWeekNo</tt> property and no byMonthDay <tt>byMonthDay</tt> or byDay properties: Add <tt>byDay</tt> properties, add a byDay <tt>byDay</tt> property with the sole value being the day-of-the-week day of the week of the initial date-time.</t>
                </list></t>
              </list></t>
            </list></t> date-time.</li>
                    </ul>
                  </li>
                </ul>
              </li>
            </ol>
          </section>
        </section>
        <section anchor="prop-excludedRecurrenceRules" title="excludedRecurrenceRules"> numbered="true" toc="default">
          <name>excludedRecurrenceRules</name>
          <t>Type: <spanx style="verb">RecurrenceRule[]</spanx> (optional).</t>

          <t>Defines <tt>RecurrenceRule[]</tt> (optional)</t>
          <t>This defines a set of recurrence rules (repeating patterns) for date-times on which the object will not occur. The rules are interpreted the same as for the "recurrenceRules" <tt>recurrenceRules</tt> property (see <xref target="prop-recurrenceRules" />), format="default"/>), with the exception that the initial date-time to which the rule is applied (the "start" date-time for events; events or the "start" or "due" date-time for tasks) is only considered part of the expansion if it matches the rule. The resulting set of date-times are is then removed from those generated by the recurrenceRules <tt>recurrenceRules</tt> property, as described in <xref target="recurrence-props" />. format="default"/>. </t>
        </section>
        <section anchor="prop-recurrenceOverrides" title="recurrenceOverrides"> numbered="true" toc="default">
          <name>recurrenceOverrides</name>
          <t>Type: <spanx style="verb">LocalDateTime[PatchObject]</spanx> (optional).</t>

          <t>A map of the <tt>LocalDateTime[PatchObject]</tt> (optional)</t>
          <t>Maps recurrence ids (the date-time produced by the recurrence rule) to an object the overridden properties of patches to apply to the generated occurrence object.</t> recurrence instance.</t>
          <t>If the recurrence id does not match a date-time from the recurrence rule (or no rule is specified), it is to be treated as an additional occurrence (like an RDATE from iCalendar). The patch object may often be empty in this case.</t>
          <t>If the patch object defines the <spanx style="verb">excluded</spanx> <tt>excluded</tt> property of an occurrence to be true, this occurrence is omitted from the final set of recurrences for the calendar object (like an EXDATE from iCalendar). Such a patch object MUST NOT <bcp14>MUST NOT</bcp14> patch any other property.</t>
          <t>By default, an occurrence inherits all properties from the main object except the start (or due) date-time, which is shifted to match the recurrence id LocalDateTime. However, individual properties of the occurrence can be modified by a patch, patch or multiple patches. It is valid to patch the <spanx style="verb">start</spanx> <tt>start</tt> property value, and this patch takes precedence over the value generated from the recurrence id. Both the recurrence id as well as the patched <spanx style="verb">start</spanx> <tt>start</tt> date-time may occur before the original JSCalendar object's <spanx style="verb">start</spanx> <tt>start</tt> or <spanx style="verb">due</spanx> <tt>due</tt> date.</t>
          <t>A pointer in the PatchObject MUST <bcp14>MUST</bcp14> be ignored if it starts with one of the following prefixes:

          <list style="symbols">
            <t>@type</t>
            <t>excludedRecurrenceRules</t>
            <t>method</t>
            <t>privacy</t>
            <t>prodId</t>
            <t>recurrenceId</t>
            <t>recurrenceOverrides</t>
            <t>recurrenceRules</t>
            <t>relatedTo</t>
            <t>replyTo</t>
            <t>uid</t>
          </list></t>
	    prefixes:</t>
          <ul spacing="normal">
            <li>@type</li>
            <li>excludedRecurrenceRules</li>
            <li>method</li>
            <li>privacy</li>
            <li>prodId</li>
            <li>recurrenceId</li>
            <li>recurrenceIdTimeZone</li>
            <li>recurrenceOverrides</li>
            <li>recurrenceRules</li>
            <li>relatedTo</li>
            <li>replyTo</li>
            <li>sentBy</li>
            <li>timeZones</li>
            <li>uid</li>
          </ul>
        </section>
        <section anchor="prop-excluded" title="excluded"> numbered="true" toc="default">
          <name>excluded</name>
          <t>Type: <spanx style="verb">Boolean</spanx> <tt>Boolean</tt> (optional, default: false).</t>

          <t>Defines false)</t>
          <t>This defines if this object is an overridden, excluded instance of a recurring JSCalendar object (see <xref target="prop-recurrenceOverrides" />). format="default"/>). If this property value is true, this calendar object instance MUST <bcp14>MUST</bcp14> be removed from the occurrence expansion. The absence of this property, or the presence of its default value as false, indicates that this instance MUST <bcp14>MUST</bcp14> be included in the occurrence expansion.</t>
        </section>
      </section>
      <section anchor="sharing-scheduling-properties" title="Sharing numbered="true" toc="default">
        <name>Sharing and Scheduling Properties"> Properties</name>
        <section anchor="prop-priority" title="priority"> numbered="true" toc="default">
          <name>priority</name>
          <t>Type: <spanx style="verb">Int</spanx> <tt>Int</tt> (optional, default: 0).</t>

          <t>Specifies 0)</t>
          <t>This specifies a priority for the calendar object. This may be used as part of scheduling systems to help resolve conflicts for a time period.</t>
          <t>The priority is specified as an integer in the range 0 to 9. A value of 0 specifies an undefined priority, for which the treatment will vary by situation. A value of 1 is the highest priority. A value of 2 is the second highest priority. Subsequent numbers specify a decreasing ordinal priority. A value of 9 is the lowest priority. Other integer values are reserved for future use.</t>
        </section>
        <section anchor="prop-freeBusyStatus" title="freeBusyStatus"> numbered="true" toc="default">
          <name>freeBusyStatus</name>
          <t>Type: <spanx style="verb">String</spanx> <tt>String</tt> (optional, default: <spanx style="verb">busy</spanx>).</t>
          <t>Specifies <tt>busy</tt>)</t>
          <t>This specifies how this calendar object should be treated when calculating free-busy state. This MUST <bcp14>MUST</bcp14> be one of the following values, another value registered in the IANA JSCalendar &quot;JSCalendar Enum Values Values&quot; registry, or a vendor-specific value (see <xref target="custom-properties" />):

          <list style="symbols">
            <t><spanx style="verb">free</spanx>: The format="default"/>):
          </t>
          <dl newline="false">
            <dt><tt>free</tt>:</dt>
	        <dd>The object should be ignored when calculating whether the user is busy.</t>

            <t><spanx style="verb">busy</spanx>: The busy.</dd>
            <dt><tt>busy</tt>:</dt>
	        <dd>The object should be included when calculating whether the user is busy.</t>
          </list></t> busy.</dd>
          </dl>
        </section>
        <section anchor="prop-privacy" title="privacy"> numbered="true" toc="default">
          <name>privacy</name>
          <t>Type: <spanx style="verb">String</spanx> <tt>String</tt> (optional, default: <spanx style="verb">public</spanx>).</t> <tt>public</tt>)</t>
          <t>Calendar objects are normally collected together and may be shared with other users. The privacy property allows the object owner to indicate that it should not be shared, shared or should only have the time information shared but the details withheld. Enforcement of the restrictions indicated by this property are is up to the API via which this object is accessed.</t>
          <t>This property MUST NOT <bcp14>MUST NOT</bcp14> affect the information sent to scheduled participants; it is only interpreted by protocols that share the calendar objects belonging to one user with other users.</t>
          <t>The value MUST <bcp14>MUST</bcp14> be one of the following values, another value registered in the IANA JSCalendar &quot;JSCalendar Enum Values Values&quot; registry, or a vendor-specific value (see <xref target="custom-properties" />). format="default"/>). Any value the client or server doesn't understand should be preserved but treated as equivalent to <spanx style="verb">private</spanx>.

          <list style="symbols">
            <t><spanx style="verb">public</spanx>: The <tt>private</tt>.</t>
          <dl newline="false" spacing="normal">
            <dt><tt>public</tt>:</dt>
	        <dd>The full details of the object are visible to those whom the object's calendar is shared with.</t>

            <t><spanx style="verb">private</spanx>: The
		    with.</dd>
            <dt><tt>private</tt>:</dt>
	        <dd><t>The details of the object are hidden; only the basic time and metadata is are shared. The
		    following properties MAY <bcp14>MAY</bcp14> be shared, shared; any other properties MUST NOT <bcp14>MUST NOT</bcp14> be shared:

            <list style="symbols">
              <t>@type</t>
              <t>created</t>
              <t>due</t>
              <t>duration</t>
              <t>estimatedDuration</t>
              <t>freeBusyStatus</t>
              <t>privacy</t>
              <t>recurrenceOverrides. Only
		        shared:</t>
              <ul spacing="normal">
                <li>@type</li>
                <li>created</li>
                <li>due</li>
                <li>duration</li>
                <li>estimatedDuration</li>
                <li>freeBusyStatus</li>
                <li>privacy</li>
                <li>recurrenceOverrides (Only patches which that apply to another permissible property are allowed to be shared.</t>
              <t>sequence</t>
              <t>showWithoutTime</t>
              <t>start</t>
              <t>timeZone</t>
              <t>timeZones</t>
              <t>uid</t>
              <t>updated</t>
            </list></t>

            <t><spanx style="verb">secret</spanx>: The shared.)</li>
                <li>sequence</li>
                <li>showWithoutTime</li>
                <li>start</li>
                <li>timeZone</li>
                <li>timeZones</li>
                <li>uid</li>
                <li>updated</li>
              </ul></dd>
            <dt><tt>secret</tt>:</dt>
	        <dd>The object is hidden completely (as though it did not exist) when the calendar this object is
		    in is shared.</t>
          </list></t> shared.</dd>
          </dl>
        </section>
        <section anchor="prop-replyTo" title="replyTo"> numbered="true" toc="default">
          <name>replyTo</name>
          <t>Type: <spanx style="verb">String[String]</spanx> (optional).</t>

          <t>Represents <tt>String[String]</tt> (optional)</t>
          <t>This represents methods by which participants may submit their response to the organizer of the calendar object. The keys in the property value are the available methods and MUST <bcp14>MUST</bcp14> only contain ASCII alphanumeric characters (A-Za-z0-9). The value is a URI for the method specified in the key. Future methods may be defined in future specifications and registered with IANA; a calendar client MUST <bcp14>MUST</bcp14> ignore any method it does not understand, understand but MUST <bcp14>MUST</bcp14> preserve the method key and URI. This property MUST <bcp14>MUST</bcp14> be omitted if no method is defined (rather than being specified as an empty object).</t>
          <t>The following methods are defined:

          <list style="symbols">
            <t><spanx style="verb">imip</spanx>: The defined:</t>
          <dl newline="false">
            <dt><tt>imip</tt>:</dt>
	        <dd>The organizer accepts an iMIP iCalendar Message-Based Interoperability Protocol (iMIP) <xref
		    target="RFC6047" /> format="default"/> response at this email address. The value MUST <bcp14>MUST</bcp14>
            be a <spanx style="verb">mailto:</spanx> URI.</t>

            <t><spanx style="verb">web</spanx>: <tt>mailto:</tt> URI.</dd>
            <dt><tt>web</tt>:</dt>
	        <dd> Opening this URI in a web browser will provide the user with a page where they can submit a
		    reply to the organizer. The value MUST <bcp14>MUST</bcp14> be a URL using the <spanx style="verb">https:</spanx> scheme.</t>

            <t><spanx style="verb">other</spanx>: <tt>https:</tt>
            scheme.</dd>
            <dt><tt>other</tt>:</dt>
	        <dd> The organizer is identified by this URI URI, but the method for submitting the response is undefined.</t>
            </list></t>
		    undefined.</dd>
          </dl>
        </section>
        <section anchor="prop-participants" title="participants"> anchor="prop-sentBy" numbered="true" toc="default">
          <name>sentBy</name>
          <t>Type: <spanx style="verb">Id[Participant]</spanx> (optional).</t>

          <t>A map of participant ids to participants, describing their participation <tt>String</tt> (optional)</t>
          <t>This is the email address in the calendar object.</t>

          <t>If "From" header of the email in which this property calendar object was received. This is set and any participant has a sendTo property, then only relevant if the <spanx style="verb">replyTo</spanx> property of this calendar object MUST define at least one reply method.</t>

          <t>A Participant is received via iMIP or as an attachment to a message.  If set, the value <bcp14>MUST</bcp14> be a valid <tt>addr-spec</tt> value as defined in Section 3.4.1 of <xref target="RFC5322" format="default"/>.</t>
        </section>
        <section anchor="prop-participants" numbered="true" toc="default">
          <name>participants</name>
          <t>Type: <tt>Id[Participant]</tt> (optional)</t>
          <t>This is a map of participant ids to participants, describing their participation in the calendar
	    object.</t>
          <t>If this property is set and any participant has a <tt>sendTo</tt> property, then the <tt>replyTo</tt>
	    property of this calendar object <bcp14>MUST</bcp14> define at least one reply method.</t>
          <t>A Participant object has the following properties:

          <list style="symbols">
            <t>@type: <spanx style="verb">String</spanx> (mandatory)
            <vspace blankLines="1" />
            Specifies
          </t>
          <dl newline="true">
	        <dt>@type: <tt>String</tt> (mandatory)</dt>
              <dd>This specifies the type of this object. This MUST <bcp14>MUST</bcp14> be <spanx style="verb">Participant</spanx>.</t>

            <t>name: <spanx style="verb">String</spanx> (optional)
            <vspace blankLines="1" />
            The <tt>Participant</tt>.</dd>
            <dt>name: <tt>String</tt> (optional)</dt>
              <dd>This is the display name of the participant (e.g., "Joe Bloggs").</t>

            <t>email: <spanx style="verb">String</spanx> (optional)
            <vspace blankLines="1" />
            The Bloggs").</dd>
              <dt>email: <tt>String</tt> (optional)</dt>
              <dd>This is the email address to use to contact the participant or, for example, match with an address book entry. If set, the participant.</t>

            <t>description: <spanx style="verb">String</spanx> (optional).
            <vspace blankLines="1" />
            A plain text value <bcp14>MUST</bcp14> be a valid <tt>addr-spec</tt> value as defined in Section 3.4.1 of <xref target="RFC5322" format="default"/>.</dd>
              <dt>description: <tt>String</tt> (optional)</dt>
              <dd>This is a plain-text description of this participant. For example, this may include more
	             information about their role in the event or how best to contact them.</t>

            <t>sendTo: <spanx style="verb">String[String]</spanx> (optional)
            <vspace blankLines="1" />
            Represents them.</dd>
              <dt>sendTo: <tt>String[String]</tt> (optional)</dt>
              <dd><t>This represents methods by which the participant may receive the invitation and updates to
	            the calendar object.
            <vspace blankLines="1" />
            The object.</t>
              <t>The keys in the property value are the available methods and MUST <bcp14>MUST</bcp14> only contain
	            ASCII alphanumeric characters (A-Za-z0-9). The value is a URI for the method specified in the
		          key. Future methods may be defined in future specifications and registered with IANA; a calendar
			        client MUST <bcp14>MUST</bcp14> ignore any method it does not understand, understand but MUST <bcp14>MUST</bcp14>
				      preserve the method key and URI. This property MUST <bcp14>MUST</bcp14> be omitted if no method is
				            defined (rather than being specified as an empty object).
            <vspace blankLines="1" />
            The object).</t>
              <t>The following methods are defined:
            <list style="symbols">
              <t><spanx style="verb">imip</spanx>: The defined:</t>
              <dl>
                <dt><tt>imip</tt>:</dt>
		<dd>The participant accepts an iMIP <xref target="RFC6047" />
		format="default"/> request at this email address. The value MUST <bcp14>MUST</bcp14> be a <spanx style="verb">mailto:</spanx>
		<tt>mailto:</tt> URI. It MAY <bcp14>MAY</bcp14> be different from the value of the participant's <spanx style="verb">email</spanx> property.</t>

              <t><spanx style="verb">other</spanx>: The
		<tt>email</tt> property.</dd>
                <dt><tt>other</tt>:</dt>
		<dd>The participant is identified by this URI URI, but the method for submitting the invitation is undefined.</t>
            </list></t>

            <t>kind: <spanx style="verb">String</spanx> (optional)
            <vspace blankLines="1" />
            What
		undefined.</dd>
              </dl></dd>
              <dt>kind: <tt>String</tt> (optional)</dt>
              <dd><t>This is what kind of entity this participant is, if known.
            <vspace blankLines="1" />
            This MUST known.</t>
              <t>This <bcp14>MUST</bcp14> be one of the following values, another value registered in the IANA JSCalendar
	            &quot;JSCalendar Enum Values Values&quot; registry, or a vendor-specific value (see <xref target="custom-properties" />).
		          format="default"/>). Any value the client or server doesn't understand should be treated the same
		          as if this property is omitted.

            <list style="symbols">
              <t><spanx style="verb">individual</spanx>: omitted.</t>
   <dl newline="false">
                <dt><tt>individual</tt>:</dt>
		<dd> a single person</t>

              <t><spanx style="verb">group</spanx>: a person</dd>
                <dt><tt>group</tt>:</dt>
		<dd>a collection of people invited as a whole</t>

              <t><spanx style="verb">location</spanx>: whole</dd>
                <dt><tt>location</tt>:</dt>
		<dd> a physical location that needs to be scheduled, e.g., a conference room</t>

              <t><spanx style="verb">resource</spanx>: a room</dd>
                <dt><tt>resource</tt>:</dt>
		<dd>a non-human resource other than a location, such as a projector</t>
            </list></t>

            <t>roles: <spanx style="verb">String[Boolean]</spanx> (mandatory)
            <vspace blankLines="1" />
            A projector</dd>
   </dl></dd>
            <dt>roles: <tt>String[Boolean]</tt> (mandatory)</dt>
	        <dd><t>This is a set of roles that this participant fulfills.
            <vspace blankLines="1" />
            At fulfills.</t>
              <t>At least one role MUST <bcp14>MUST</bcp14> be specified for the participant. The keys in the set MUST
	            <bcp14>MUST</bcp14> be one of the following values, another value registered in the IANA JSCalendar
		          &quot;JSCalendar Enum Values Values&quot; registry, or a vendor-specific value (see <xref target="custom-properties" />):

            <list style="symbols">
              <t><spanx style="verb">owner</spanx>:
			        format="default"/>):</t>
              <dl>
                <dt><tt>owner</tt>:</dt>
		<dd> The participant is an owner of the object. This signifies they have permission to make
		changes to it that affect the other participants. Non-owner Nonowner participants may only change
		properties that just affect only themselves (for example example, setting their own alerts or changing their rsvp status).</t>
              <t><spanx style="verb">attendee</spanx>: The
		RSVP status).</dd>
                <dt><tt>attendee</tt>:</dt>
		<dd>The participant is expected to be present at the event.</t>
              <t><spanx style="verb">optional</spanx>: The event.</dd>
                <dt><tt>optional</tt>:</dt>
		<dd>The participant's involvement with the event is optional. This is expected to be primarily
		combined with the "attendee" role.</t>
              <t><spanx style="verb">informational</spanx>: role.</dd>
                <dt><tt>informational</tt>:</dt>
		<dd> The participant is copied for informational reasons, reasons and is not expected to attend.</t>
              <t><spanx style="verb">chair</spanx>: attend.</dd>
                <dt><tt>chair</tt>:</dt>
		<dd> The participant is in charge of the event/task when it occurs.</t>
              <t><spanx style="verb">contact</spanx>: occurs.</dd>
                <dt><tt>contact</tt>:</dt>
		<dd> The participant is someone that may be contacted for information about the event.</t>
            </list>

            The event.</dd>
              </dl>
              <t>The value for each key in the map MUST <bcp14>MUST</bcp14> be true. It is expected that no more
	          than one of the roles "attendee" and "informational" be present; if more than one are given,
		      "attendee" takes precedence over "informational". Roles that are unknown to the implementation MUST
		          <bcp14>MUST</bcp14> be preserved.</t>

            <t>locationId: <spanx style="verb">String</spanx> (optional)
            <vspace blankLines="1" />
            The preserved.</t></dd>
              <dt>locationId: <tt>Id</tt> (optional)</dt>
              <dd><t>This is the location at which this participant is expected to be attending.
            <vspace blankLines="1" />
            If attending.</t>
              <t>If the value does not correspond to any location id in the
            <spanx style="verb">locations</spanx> <tt>locations</tt> property of the
	            JSCalendar object, this MUST <bcp14>MUST</bcp14> be treated the same as if the participant's
		          locationId were omitted.</t>

            <t>language: <spanx style="verb">String</spanx> (optional)
            <vspace blankLines="1" />
            The omitted.</t></dd>
              <dt>language: <tt>String</tt> (optional)</dt>
              <dd>This is the language tag tag, as defined in <xref target="RFC5646" /> target="BCP47" format="default"/>, that best
	            describes
		          the participant's preferred language, if known.</t>

            <t>participationStatus: <spanx style="verb">String</spanx> known.</dd>
              <dt>participationStatus: <tt>String</tt> (optional, default: <spanx style="verb">needs-action</spanx>)
            <vspace blankLines="1" />
            The <tt>needs-action</tt>)</dt>
	            <dd><t>This is the participation status, if any, of this participant.
            <vspace blankLines="1" />
            The participant.</t>
              <t>The value MUST <bcp14>MUST</bcp14> be one of the following values, another value registered in the
	            IANA JSCalendar &quot;JSCalendar Enum Values Values&quot; registry, or a vendor-specific value (see <xref
		          target="custom-properties" />):

            <list style="symbols">
              <t><spanx style="verb">needs-action</spanx>: format="default"/>):</t>
              <dl newline="false">
                <dt><tt>needs-action</tt>:</dt>
		<dd> No status has yet been set by the participant.</t>

              <t><spanx style="verb">accepted</spanx>: participant.</dd>
                <dt><tt>accepted</tt>:</dt>
		<dd> The invited participant will participate.</t>

              <t><spanx style="verb">declined</spanx>: The participate.</dd>
                <dt><tt>declined</tt>:</dt>
		<dd>The invited participant will not participate.</t>

              <t><spanx style="verb">tentative</spanx>: participate.</dd>
                <dt><tt>tentative</tt>:</dt>
		<dd> The invited participant may participate.</t>

              <t><spanx style="verb">delegated</spanx>: participate.</dd>
                <dt><tt>delegated</tt>:</dt>
		<dd> The invited participant has delegated their attendance to another participant, as
		specified in the delegatedTo property.</t>
            </list></t>

            <t>participationComment: <spanx style="verb">String</spanx> (optional)
            <vspace blankLines="1" />
            A <tt>delegatedTo</tt> property.</dd>
              </dl></dd>
              <dt>participationComment: <tt>String</tt> (optional)</dt>
              <dd>This is a  note from the participant to explain their participation status.</t>

            <t>expectReply: <spanx style="verb">Boolean</spanx> status.</dd>
              <dt>expectReply: <tt>Boolean</tt> (optional, default: false)
            <vspace blankLines="1" />
            If false)</dt>
              <dd>If true, the organizer is expecting the participant to notify them of their participation status.</t>

            <t>scheduleAgent: <spanx style="verb">String</spanx>
	            status.</dd>
              <dt>scheduleAgent: <tt>String</tt> (optional, default: <spanx style="verb">server</spanx>)
            <vspace blankLines="1" />
            Who <tt>server</tt>)</dt><dd>
              <t>This is who is responsible for sending scheduling messages with this calendar object to the participant.
            <vspace blankLines="1" />
            The
	            participant.</t>
              <t>The value MUST <bcp14>MUST</bcp14> be one of the following values, another value registered in the
	            IANA JSCalendar &quot;JSCalendar Enum Values Values&quot; registry, or a vendor-specific value (see <xref
		          target="custom-properties" />):

            <list style="symbols">
              <t><spanx style="verb">server</spanx>: format="default"/>):</t>
              <dl spacing="normal">
                <dt><tt>server</tt>:</dt>
		<dd> The calendar server will send the scheduling messages.</t>

              <t><spanx style="verb">client</spanx>: messages.</dd>
                <dt><tt>client</tt>:</dt>
		<dd> The calendar client will send the scheduling messages.</t>

              <t><spanx style="verb">none</spanx>: messages.</dd>
                <dt><tt>none</tt>:</dt>
		<dd> No scheduling messages are to be sent to this participant.</t>
            </list></t>

            <t>scheduleForceSend: <spanx style="verb">Boolean</spanx> participant.</dd>
              </dl></dd>
              <dt>scheduleForceSend: <tt>Boolean</tt> (optional, default: false)
            <vspace blankLines="1" />
            A false)</dt>
              <dd>A client may set the property on a participant to true to request that the server send a
	            scheduling message to the participant when it would not normally do so (e.g. (e.g., if no significant
		          change is made the object or the scheduleAgent is set to client). The property MUST NOT <bcp14>MUST
			        NOT</bcp14> be stored in the JSCalendar object on the server or appear in a scheduling message.</t>

            <t>scheduleSequence: <spanx style="verb">UnsignedInt</spanx>
				      message.</dd>
              <dt>scheduleSequence: <tt>UnsignedInt</tt> (optional, default: 0)
            <vspace blankLines="1" />
            The 0)</dt>
              <dd><t>This is the sequence number of the last response from the participant. If defined, this MUST
	            <bcp14>MUST</bcp14> be a non-negative integer.
            <vspace blankLines="1" />
            This nonnegative integer.</t>
              <t>This can be used to determine whether the participant has sent a new response following
	            significant changes to the calendar object, object and to determine if future responses are responding
		          to a current or older view of the data.</t>

            <t>scheduleStatus: <spanx style="verb">String[]</spanx> (optional)
            <vspace blankLines="1" />
            A data.</t></dd>
              <dt>scheduleStatus: <tt>String[]</tt> (optional)</dt>
              <dd><t>This is a list of status codes, as defined in Section 3.8.8.3 of <xref target="RFC5545" />, returned from the processing of the most recent scheduling message sent to this participant.
            <vspace blankLines="1" />
            Servers The status codes MUST be valid <tt>statcode</tt> values as defined in the ABNF in <xref target="RFC5545" sectionFormat="of" section="3.8.8.3"/>.</t>
              <t>Servers <bcp14>MUST</bcp14> only add or change this property when they send a scheduling
	            message to the participant. Clients SHOULD NOT <bcp14>SHOULD NOT</bcp14> change or remove this property if
		          it was provided by the server. Clients MAY <bcp14>MAY</bcp14> add, change, or remove the property for
			        participants where the client is handling the scheduling.
            <vspace blankLines="1" />
            This scheduling.</t>
              <t>This property MUST NOT <bcp14>MUST NOT</bcp14> be included in scheduling messages.</t>

            <t>scheduleUpdated: <spanx style="verb">UTCDateTime</spanx> (optional)
            <vspace blankLines="1" />
            The
              </dd>
              <dt>scheduleUpdated: <tt>UTCDateTime</tt> (optional)</dt>
              <dd><t>This is the timestamp for the most recent response from this participant.
            <vspace blankLines="1" />
            This participant.</t>
              <t>This is the <spanx style="verb">updated</spanx> <tt>updated</tt> property of the last response when using iTIP. It can be compared
	            to the <spanx style="verb">updated</spanx> <tt>updated</tt> property in future responses to detect and discard older responses
		          delivered out of order.</t>

            <t>invitedBy: <spanx style="verb">String</spanx> (optional)
            <vspace blankLines="1" />
            The order.</t></dd>
              <dt>sentBy: <tt>String</tt> (optional)</dt>
              <dd><t>This is the email address in the "From" header of the email that last updated this participant via iMIP. This SHOULD only be set if the email address is different to that in the mailto URI of this participant's <tt>imip</tt> method in the <tt>sendTo</tt> property (i.e., the response was received from a different address to that which the invitation was sent to). If set, the value <bcp14>MUST</bcp14> be a valid <tt>addr-spec</tt> value as defined in Section 3.4.1 of <xref target="RFC5322" format="default"/>.</t>
              </dd>
              <dt>invitedBy: <tt>Id</tt> (optional)</dt>
	            <dd>This is the id of the participant who invited added this one, participant to the event/task, if known.</t>

            <t>delegatedTo: <spanx style="verb">String[Boolean]</spanx> (optional)
            <vspace blankLines="1" />
            A known.</dd>
              <dt>delegatedTo: <tt>Id[Boolean]</tt> (optional)</dt>
	            <dd>This is set of participant ids that this participant has delegated their participation to.
		          Each key
			        in the set MUST <bcp14>MUST</bcp14> be the id of a participant. The value for each key in the map MUST
				      <bcp14>MUST</bcp14> be true. If there are no delegates, this MUST <bcp14>MUST</bcp14> be omitted
				            (rather than specified as an empty set).</t>

            <t>delegatedFrom: <spanx style="verb">String[Boolean]</spanx> (optional)
            <vspace blankLines="1" />
            A set).</dd>
              <dt>delegatedFrom: <tt>Id[Boolean]</tt> (optional)</dt>
              <dd>This is a set of participant ids that this participant is acting as a delegate for. Each key
	            in the set MUST <bcp14>MUST</bcp14> be the id of a participant. The value for each key in the map MUST
		          <bcp14>MUST</bcp14> be true. If there are no delegators, this MUST <bcp14>MUST</bcp14> be omitted
			        (rather than specified as an empty set).</t>

            <t>memberOf: <spanx style="verb">String[Boolean]</spanx> (optional)
            <vspace blankLines="1" />
            A set).</dd>
              <dt>memberOf: <tt>Id[Boolean]</tt> (optional)</dt>
              <dd>This is a set of group participants that were invited to this calendar object, which caused
	            this
		          participant to be invited due to their membership in the group(s). Each key in the set MUST
			        <bcp14>MUST</bcp14> be the id of a participant. The value for each key in the map MUST
				      <bcp14>MUST</bcp14> be true. If there are no groups, this MUST <bcp14>MUST</bcp14> be omitted (rather
				            than specified as an empty set).</t>

            <t>links: <spanx style="verb">Id[Link]</spanx> (optional)
            <vspace blankLines="1" />
            A set).</dd>
              <dt>links: <tt>Id[Link]</tt> (optional)</dt>
              <dd>This is a map of link ids to Link objects, representing external resources associated with
	            this participant, for example example, a vCard or image. If there are no links, this MUST <bcp14>MUST</bcp14>
		          be omitted (rather than specified as an empty set).</t>

             <t>progress: <spanx style="verb">String</spanx> set).</dd>
            <dt>progress: <tt>String</tt> (optional; only allowed for participants of a JSTask). Represents Task)</dt>
	        <dd>This represents the progress of the participant for this task. It MUST NOT <bcp14>MUST NOT</bcp14> be
		    set if
		        the <spanx style="verb">participationStatus</spanx> <tt>participationStatus</tt> of this participant is any value other than <spanx style="verb">accepted</spanx>. <tt>accepted</tt>. See
			    <xref target="prop-progress" /> format="default"/> for allowed values and semantics.</t>

            <t>progressUpdated: <spanx style="verb">UTCDateTime</spanx> semantics.</dd>
            <dt>progressUpdated: <tt>UTCDateTime</tt> (optional; only allowed for participants of a JSTask). Specifies
	        Task)</dt>
		    <dd>This specifies the date-time the progress <tt>progress</tt> property was last set on this participant. See <xref target="prop-progressUpdated" /> format="default"/> for allowed values and semantics.</t>

            <t>percentComplete: <spanx style="verb">UnsignedInt</spanx> semantics.</dd>
            <dt>percentComplete: <tt>UnsignedInt</tt> (optional; only allowed for participants of a JSTask). Represents Task)</dt>
	        <dd>This represents the percent completion of the participant for this task. The property value MUST <bcp14>MUST</bcp14> be a positive integer between 0 and 100.</t>
          </list></t> 100.</dd>
              </dl>
            </section>
        <section anchor="prop-requestStatus" numbered="true" toc="default">
          <name>requestStatus</name>
          <t>Type: <tt>String</tt> (optional)</t>
          <t>A request status as returned from processing the most recent scheduling request for this JSCalendar object. The allowed values are defined by the ABNF definitions of <tt>statcode</tt>, <tt>statdesc</tt> and <tt>extdata</tt> in <xref target="RFC5545" sectionFormat="of" section="3.8.8.3"/> and the following ABNF <xref target="RFC5234" />:</t>
          <sourcecode name="" type="abnf"><![CDATA[
reqstatus = statcode ";" statdesc [";" extdata]
]]></sourcecode>
          <t>Servers <bcp14>MUST</bcp14> only add or change this property when they performe a scheduling action. Clients <bcp14>SHOULD NOT</bcp14> change or remove this property if it was provided by the server. Clients <bcp14>MAY</bcp14> add, change, or remove the property when the client is handling the scheduling.</t>
          <t>This property <bcp14>MUST</bcp14> only be included in scheduling messages according to the rules defined for the REQUEST-STATUS iCalendar property in <xref target="RFC5546" format="default"/>.</t>
        </section>
      </section>
      <section anchor="alerts-properties" title="Alerts Properties"> numbered="true" toc="default">
        <name>Alerts Properties</name>
        <section anchor="useDefaultAlerts" title="useDefaultAlerts"> numbered="true" toc="default">
          <name>useDefaultAlerts</name>
          <t>Type: <spanx style="verb">Boolean</spanx> <tt>Boolean</tt> (optional, default: false).</t> false)</t>
          <t>If true, use the user's default alerts and ignore the value of the <spanx style="verb">alerts</spanx> <tt>alerts</tt> property. Fetching user defaults is dependent on the API from which this JSCalendar object is being fetched, fetched and is not defined in this specification. If an implementation cannot determine the user's default alerts, or none are set, it MUST <bcp14>MUST</bcp14> process the alerts <tt>alerts</tt> property as if <spanx style="verb">useDefaultAlerts</spanx> <tt>useDefaultAlerts</tt> is set to false.</t>
        </section>
        <section anchor="prop-alerts" title="alerts"> numbered="true" toc="default">
          <name>alerts</name>
          <t>Type: <spanx style="verb">Id[Alert]</spanx> (optional).</t>

          <t>A <tt>Id[Alert]</tt> (optional)</t>
          <t>This is a map of alert ids to Alert objects, representing alerts/reminders to display or send to the user for this calendar object.</t>
          <t>An Alert Object object has the following properties:

          <list style="symbols">
            <t>@type: <spanx style="verb">String</spanx> (mandatory)
            <vspace blankLines="1" />
            Specifies properties:</t>
          <dl newline="true">
              <dt>@type: <tt>String</tt> (mandatory)</dt>
              <dd>This specifies the type of this object. This MUST <bcp14>MUST</bcp14> be <spanx style="verb">Alert</spanx>.
            </t>
            <t>trigger: <spanx style="verb">OffsetTrigger|AbsoluteTrigger|UnknownTrigger</spanx> (mandatory)
            <vspace blankLines="1" />
            Defines <tt>Alert</tt>.</dd>
              <dt>trigger: <tt>OffsetTrigger|AbsoluteTrigger|UnknownTrigger</tt> (mandatory)</dt>
              <dd><t>This defines when to trigger the alert. New types may be defined in future documents.
            <vspace blankLines="1" />
            An <spanx style="verb">OffsetTrigger</spanx> documents.</t>
              <t>An <tt>OffsetTrigger</tt> object has the following properties:
            <list style="symbols">
              <t>@type: <spanx style="verb">String</spanx> (mandatory)
              <vspace blankLines="1" />
              Specifies properties:</t>
              <dl newline="true">
                  <dt>@type: <tt>String</tt> (mandatory)</dt>
                  <dd>This specifies the type of this object. This MUST <bcp14>MUST</bcp14> be <spanx style="verb">OffsetTrigger</spanx>.
              </t>
              <t>offset: <spanx style="verb">SignedDuration</spanx> (mandatory).
              <vspace blankLines="1" />
              Defines
		    <tt>OffsetTrigger</tt>.</dd>
                  <dt>offset: <tt>SignedDuration</tt> (mandatory)</dt>
                  <dd>This defines the offset at which to trigger the alert relative to the time property
		    defined in the <spanx style="verb">relativeTo</spanx> <tt>relativeTo</tt> property of the alert. Negative durations signify alerts
		      before the time property, property; positive durations signify alerts after.</t>

              <t>relativeTo: <spanx style="verb">String</spanx> after the time property.</dd>
                  <dt>relativeTo: <tt>String</tt> (optional, default: <spanx style="verb">start</spanx>)
              <vspace blankLines="1" />
              Specifies <tt>start</tt>)</dt>
                  <dd><t>This specifies the time property that the alert offset is relative to. The value MUST
		    <bcp14>MUST</bcp14> be one of:

              <list style="symbols">
                <t><spanx style="verb">start</spanx>: of the following:</t>
                  <dl newline="false">
                    <dt><tt>start</tt>:</dt>
		        <dd> triggers the alert relative to the start of the calendar object</t>
                <t><spanx style="verb">end</spanx>: object</dd>
                    <dt><tt>end</tt>:</dt>
		        <dd> triggers the alert relative to the end/due time of the calendar object</t>
              </list></t>
            </list>

            An <spanx style="verb">AbsoluteTrigger</spanx> object</dd>
                  </dl></dd></dl>
              <t>An <tt>AbsoluteTrigger</tt> object has the following properties:
            <list style="symbols">
              <t>@type: <spanx style="verb">String</spanx> (mandatory)
              <vspace blankLines="1" />
              Specifies properties:</t>
              <dl newline="true">
                  <dt>@type: <tt>String</tt> (mandatory)</dt>
                  <dd>This specifies the type of this object. This MUST <bcp14>MUST</bcp14> be <spanx style="verb">AbsoluteTrigger</spanx>.
              </t>
              <t>when: <spanx style="verb">UTCDateTime</spanx> (mandatory).
              <vspace blankLines="1" />
              Defines
		    <tt>AbsoluteTrigger</tt>.</dd>
                  <dt>when: <tt>UTCDateTime</tt> (mandatory)</dt>
                  <dd>This defines a specific UTC date-time when the alert is triggered.</t>
            </list>

            An <spanx style="verb">UnknownTrigger</spanx> triggered.</dd>
              </dl>
              <t>An <tt>UnknownTrigger</tt> object is an object that contains a <spanx style="verb">@type</spanx> an <tt>@type</tt> property whose
	            value is not recognized (i.e., not <spanx style="verb">OffsetTrigger</spanx> <tt>OffsetTrigger</tt> or <spanx style="verb">AbsoluteTrigger</spanx>), <tt>AbsoluteTrigger</tt>) plus zero
		          or more other properties. This is for compatibility with client extensions and future
			        specifications. Implementations SHOULD NOT <bcp14>SHOULD NOT</bcp14> trigger for trigger types they do not understand,
				      understand but MUST <bcp14>MUST</bcp14> preserve them.</t>

            <t>acknowledged: <spanx style="verb">UTCDateTime</spanx> (optional)
            <vspace blankLines="1" />
            This
              </dd>
              <dt>acknowledged: <tt>UTCDateTime</tt> (optional)</dt>
              <dd><t>This records when an alert was last acknowledged. This is set when the user has dismissed
	            the alert; other clients that sync this property SHOULD <bcp14>SHOULD</bcp14> automatically dismiss or
		          suppress duplicate alerts (alerts with the same alert id that triggered on or before this date-time).
            <vspace blankLines="1" />
            For
			        date-time).</t>
              <t>For a recurring calendar object, setting the <spanx style="verb">acknowledged</spanx> <tt>acknowledged</tt> property MUST NOT <bcp14>MUST
	            NOT</bcp14> add a new override to the <spanx style="verb">recurrenceOverrides</spanx> <tt>recurrenceOverrides</tt> property. If the alert is not
		          already overridden, the acknowledged <tt>acknowledged</tt> property MUST <bcp14>MUST</bcp14> be set on the alert in the master event/task.
            <vspace blankLines="1" />
            Certain
			        base event/task.</t>
              <t>Certain kinds of alert action may not provide feedback as to when the user sees them, for example email based
	            example, email-based alerts. For those kinds of alerts, this property MUST <bcp14>MUST</bcp14> be set
		          immediately when the alert is triggered and the action is successfully carried out.</t>

            <t>relatedTo: <spanx style="verb">String[Relation]</spanx> (optional)
            <vspace blankLines="1" />
            Relates
              </dd>
              <dt>relatedTo: <tt>String[Relation]</tt> (optional)</dt>
	            <dd>This relates this alert to other alerts in the same JSCalendar object. If the user wishes to
		          snooze an alert, the application MUST <bcp14>MUST</bcp14> create an alert to trigger after snoozing.
			        This new snooze alert MUST <bcp14>MUST</bcp14> set a parent relation to the identifier of the original alert.</t>

            <t>action: <spanx style="verb">String</spanx>
				      alert.</dd>
              <dt>action: <tt>String</tt> (optional, default: <spanx style="verb">display</spanx>)
            <vspace blankLines="1" />
            Describes <tt>display</tt>)</dt>
	            <dd><t>This describes how to alert the user.
            <vspace blankLines="1" />
            The user.</t>
              <t>The value MUST <bcp14>MUST</bcp14> be at most one of the following values, a value registered in
	            the IANA JSCalendar &quot;JSCalendar Enum Values Values&quot; registry, or a vendor-specific value (see <xref
		          target="custom-properties" />):

            <list style="symbols">
              <t><spanx style="verb">display</spanx>: The format="default"/>):</t>
              <dl spacing="normal">
                <dt><tt>display</tt>:</dt>
		<dd>The alert should be displayed as appropriate for the current device and user context.</t>

              <t><spanx style="verb">email</spanx>: The context.</dd>
                <dt><tt>email</tt>:</dt>
		<dd>The alert should trigger an email sent out to the user, notifying about them of the alert. This
		action is typically only appropriate for server implementations.</t>
            </list></t>
          </list></t> implementations.</dd>
              </dl></dd>
            </dl>
          </section>
	</section>
      <section anchor="localized-props" title="Multilingual Properties"> numbered="true" toc="default">
        <name>Multilingual Properties</name>
        <section anchor="prop-localizations" title="localizations"> numbered="true" toc="default">
          <name>localizations</name>
          <t>Type: <spanx style="verb">String[PatchObject]</spanx> (optional).</t> <tt>String[PatchObject]</tt> (optional)</t>
          <t>A map of where each key is a language tags tag <xref target="RFC5646" /> target="BCP47" format="default"/>, and the corresponding value is a set of patches to apply to patch objects, which localize the calendar object in order to localize it into the locale of the respective language tag.</t> that locale.</t>
          <t>See the description of <xref target="type-PatchObject">PatchObject</xref> target="type-PatchObject" format="default">PatchObject</xref> for the structure of the PatchObject. The patches are applied to the top-level calendar object. In addition, the <spanx style="verb">locale</spanx> <tt>locale</tt> property of the patched object is set to the language tag. All pointers for patches MUST <bcp14>MUST</bcp14> end with one of the following suffixes; any patch that does not follow this MUST <bcp14>MUST</bcp14> be ignored unless otherwise specified in a future RFC:

          <list style="symbols">
            <t>title</t>
            <t>description</t>
            <t>name</t>
          </list>

          A

          </t>
          <ul spacing="normal">
            <li>title</li>
            <li>description</li>
            <li>name</li>
          </ul>
          <t>A patch MUST NOT <bcp14>MUST NOT</bcp14> have the prefix <spanx style="verb">recurrenceOverrides</spanx>; <tt>recurrenceOverrides</tt>; any localization of
	    the override MUST <bcp14>MUST</bcp14> be a patch to the localizations <tt>localizations</tt> property inside the override
	      instead. For example, a patch to <spanx style="verb">locations/abcd1234/title</spanx> <tt>locations/abcd1234/title</tt> is permissible, but a patch to <spanx style="verb">uid</spanx>
	        <tt>uid</tt> or <spanx style="verb">recurrenceOverrides/2020-01-05T14:00:00/title</spanx> <tt>recurrenceOverrides/2020-01-05T14:00:00/title</tt> is not.</t>
          <t>Note that this specification does not define how to maintain validity of localized content. For example, a client application changing a JSCalendar object's title <tt>title</tt> property might also need to update any localizations of this property. Client implementations SHOULD <bcp14>SHOULD</bcp14> provide the means to manage localizations, but how to achieve this is specific to the application's workflow and requirements.</t>
        </section>
      </section>
      <section anchor="timezone-props" title="Time numbered="true" toc="default">
        <name>Time Zone Properties"> Properties</name>
        <section anchor="prop-timeZone" title="timeZone"> numbered="true" toc="default">
          <name>timeZone</name>
          <t>Type: <spanx style="verb">TimeZoneId|null</spanx> <tt>TimeZoneId|null</tt> (optional, default: null).</t>

          <t>Identifies null)</t>
          <t>This identifies the time zone the object is scheduled in, in or is null for floating time. This is
	    either a name from the IANA Time Zone Database <xref target="TZDB" /> format="default"/> or the
	      TimeZoneId of a custom time zone from the <spanx style="verb">timeZones</spanx> <tt>timeZones</tt> property (<xref target="prop-timeZones" />).
	        format="default"/>). If omitted, this MUST <bcp14>MUST</bcp14> be presumed to be null (i.e., floating
	        time).</t>
        </section>
        <section anchor="prop-timeZones" title="timeZones"> numbered="true" toc="default">
          <name>timeZones</name>
          <t>Type: <spanx style="verb">TimeZoneId[TimeZone]</spanx> (optional).</t>

          <t>Maps <tt>TimeZoneId[TimeZone]</tt> (optional)</t>
          <t>This maps identifiers of custom time zones to their time zone definitions. The following
	    restrictions apply for each key in the map:

          <list style="symbols">
            <t>To map:</t>
          <ul spacing="normal">
            <li>To avoid conflict with names in the IANA Time Zone Database <xref target="TZDB" />, format="default"/>, it MUST <bcp14>MUST</bcp14> start with the <spanx style="verb">/</spanx> character.</t>

            <t>It MUST <tt>/</tt> character.</li>
            <li>It <bcp14>MUST</bcp14> be a valid <spanx style="verb">paramtext</spanx> value <tt>paramtext</tt> value, as specified in Section 3.1. of <xref target="RFC5545" />.</t>

            <t>At sectionFormat="of" section="3.1"/>.</li>
            <li>At least one other property in the same JSCalendar object MUST <bcp14>MUST</bcp14> reference a time zone using this identifier (i.e., orphaned time zones are not allowed).</t>
          </list>

          An allowed).</li>
          </ul>
          <t>An identifier need only be unique to this JSCalendar object. A It <bcp14>MAY</bcp14> differ from the
        <tt>tzId</tt> property value of the TimeZone object it maps to.</t>
        <t>A JSCalendar object may be part in of a hierarchy of other JSCalendar objects (say, a JSEvent an Event is an entry in a JSGroup). Group). In this case, the set of time zones is the sum of the time zone definitions of this object and its parent objects. If multiple time zones with the same identifier exist, then the definition closest to the calendar object in relation to its parents MUST <bcp14>MUST</bcp14> be used. (In context of JSEvent, Event, a time zone definition in its timeZones <tt>timeZones</tt> property has precedence over a definition of the same id in the JSGroup). Group). Time zone definitions in any children of the calendar object MUST <bcp14>MUST</bcp14> be ignored. </t> ignored.</t>
          <t>A TimeZone object maps a VTIMEZONE component from iCalendar <xref target="RFC5545" /> iCalendar, and the semantics are as defined there. in
	     <xref target="RFC5545" format="default"/>. A valid time zone MUST <bcp14>MUST</bcp14>
	       define at least one transition rule in the <spanx style="verb">standard</spanx> <tt>standard</tt> or <spanx style="verb">daylight</spanx> <tt>daylight</tt> property. Its
	         properties are:

          <list style="symbols">
            <t>@type: <spanx style="verb">String</spanx> (mandatory)
            <vspace blankLines="1" />
            Specifies are:</t>
          <dl newline="true">
              <dt>@type: <tt>String</tt> (mandatory)</dt>
              <dd>This specifies the type of this object. This MUST <bcp14>MUST</bcp14> be <spanx style="verb">TimeZone</spanx>.
            </t>
            <t>tzId: <spanx style="verb">String</spanx> (mandatory).
            <vspace blankLines="1" />
            The <tt>TimeZone</tt>.</dd>
              <dt>tzId: <tt>String</tt> (mandatory)</dt>
              <dd>This is the TZID property from iCalendar.</t>

            <t>updated: <spanx style="verb">UTCDateTime</spanx> (optional)
            <vspace blankLines="1" />
            The iCalendar. Note that this implies that the value <bcp14>MUST</bcp14> be a valid <tt>paramtext</tt> value as specified in Section 3.1. of <xref target="RFC5545" format="default"/>.</dd>
              <dt>updated: <tt>UTCDateTime</tt> (optional)</dt>
              <dd>This is the LAST-MODIFIED property from iCalendar.</t>

            <t>url: <spanx style="verb">String</spanx> (optional)
            <vspace blankLines="1" />
            The iCalendar.</dd>
              <dt>url: <tt>String</tt> (optional)</dt>
              <dd>This is the TZURL property from iCalendar.</t>

            <t>validUntil: <spanx style="verb">UTCDateTime</spanx> (optional)
            <vspace blankLines="1" />
            The iCalendar.</dd>
              <dt>validUntil: <tt>UTCDateTime</tt> (optional)</dt>
              <dd>This is the TZUNTIL property from iCalendar iCalendar, specified in <xref target="RFC7808" />.</t>

            <t>aliases: <spanx style="verb">String[Boolean]</spanx> (optional)
            <vspace blankLines="1" />
            Maps
	            format="default"/>.</dd>
              <dt>aliases: <tt>String[Boolean]</tt> (optional)</dt>
              <dd>This maps the TZID-ALIAS-OF properties from iCalendar iCalendar, specified in <xref target="RFC7808" />
	            format="default"/>, to a JSON set of aliases. The set is represented as an object, with the keys
	            being the aliases. The value for each key in the map MUST <bcp14>MUST</bcp14> be true.</t>

            <t>standard: <spanx style="verb">TimeZoneRule[]</spanx> (optional)
            <vspace blankLines="1" />
            The true.</dd>
              <dt>standard: <tt>TimeZoneRule[]</tt> (optional)</dt>
              <dd>This the STANDARD sub-components from iCalendar. The order MUST <bcp14>MUST</bcp14> be preserved
	            during conversion.</t>

            <t>daylight: <spanx style="verb">TimeZoneRule[]</spanx> (optional).
            <vspace blankLines="1" />
            The conversion.</dd>
              <dt>daylight: <tt>TimeZoneRule[]</tt> (optional)</dt>
              <dd>This the DAYLIGHT sub-components from iCalendar. The order MUST <bcp14>MUST</bcp14> be preserved
	            during conversion.</t>
          </list></t> conversion.</dd>
          </dl>

          <t>A TimeZoneRule object maps a STANDARD or DAYLIGHT sub-component from iCalendar, with the
	    restriction that that, at most most, one recurrence rule is allowed per rule. It has the following properties:

          <list style="symbols">
            <t>@type: <spanx style="verb">String</spanx> (mandatory)
            <vspace blankLines="1" />
            Specifies the
	      properties:</t>
          <dl newline="true">
              <dt>@type: <tt>String</tt> (mandatory)</dt>
              <dd>This specifies the type of this object. This MUST <bcp14>MUST</bcp14> be <spanx style="verb">TimeZoneRule</spanx>.
            </t>
            <t>start: <spanx style="verb">LocalDateTime</spanx> (mandatory)
            <vspace blankLines="1" />
            The
	            <tt>TimeZoneRule</tt>.</dd>
              <dt>start: <tt>LocalDateTime</tt> (mandatory)</dt>
              <dd>This is the DTSTART property from iCalendar.</t>

            <t>offsetFrom: <spanx style="verb">String</spanx> (mandatory)
            <vspace blankLines="1" />
            The iCalendar.</dd>
              <dt>offsetFrom: <tt>String</tt> (mandatory)</dt>
              <dd>This is the TZOFFSETFROM property from iCalendar.</t>

            <t>offsetTo: <spanx style="verb">String</spanx> (mandatory)
            <vspace blankLines="1" />
            The iCalendar.</dd>
              <dt>offsetTo: <tt>String</tt> (mandatory)</dt>
              <dd>This is the TZOFFSETTO property from iCalendar.</t>

            <t>recurrenceRules: <spanx style="verb">RecurrenceRule[]</spanx> (optional)
            <vspace blankLines="1" />
            The iCalendar.</dd>
              <dt>recurrenceRules: <tt>RecurrenceRule[]</tt> (optional)</dt>
              <dd>This is the RRULE property mapped mapped, as specified in <xref target="prop-recurrenceRules" />.
	            format="default"/>. During recurrence rule evaluation, the <spanx style="verb">until</spanx> <tt>until</tt> property value MUST
	            <bcp14>MUST</bcp14> be interpreted as a local time in the UTC time zone.</t>

            <t>recurrenceOverrides: <spanx style="verb">LocalDateTime[PatchObject]</spanx> (optional)
            <vspace blankLines="1" />
            Maps zone.</dd>
              <dt>recurrenceOverrides: <tt>LocalDateTime[PatchObject]</tt> (optional)</dt>
              <dd>This maps the RDATE properties from iCalendar. The set is represented as an object, with the
	            keys being the recurrence dates. The patch object MUST <bcp14>MUST</bcp14> be the empty JSON object ({}).</t>

            <t>names: <spanx style="verb">String[Boolean]</spanx> (optional)
            <vspace blankLines="1" />
            Maps
		          ({}).</dd>
              <dt>names: <tt>String[Boolean]</tt> optional)</dt>
              <dd>This maps the TZNAME properties from iCalendar to a JSON set. The set is represented as an
	            object, with the keys being the names, excluding any <spanx style="verb">tznparam</spanx> <tt>tznparam</tt> component from iCalendar.
		          The value for each key in the map MUST <bcp14>MUST</bcp14> be true.</t>

            <t>comments: <spanx style="verb">String[]</spanx> (optional). Maps true.</dd>
            <dt>comments: <tt>String[]</tt> (optional)</dt>
	        <dd> This maps the COMMENT properties from iCalendar. The order MUST <bcp14>MUST</bcp14> be preserved
		    during conversion.</t>
          </list></t> conversion.</dd>
          </dl>
        </section>
      </section>
    </section>
    <section anchor="jscalendar-object-props" title="Type-specific numbered="true" toc="default">
      <name>Type-Specific JSCalendar Properties"> Properties</name>
      <section anchor="jsevent-props" title="JSEvent Properties"> numbered="true" toc="default">
        <name>Event Properties</name>
        <t>In addition to the common JSCalendar object <xref target="jscalendar-props">properties</xref> a JSEvent target="jscalendar-props" format="default">properties</xref>, an Event has the following properties:</t>
        <section anchor="prop-start-jsevent" title="start"> numbered="true" toc="default">
          <name>start</name>
          <t>Type: <spanx style="verb">LocalDateTime</spanx> (mandatory).</t>

          <t>The <tt>LocalDateTime</tt> (mandatory)</t>
          <t>This is the date/time the event starts in the event's time zone (as specified in the <spanx style="verb">timeZone</spanx>
	    <tt>timeZone</tt>
	      property, see <xref target="prop-timeZone" />).</t> format="default"/>).</t>
        </section>
        <section anchor="prop-duration" title="duration"> numbered="true" toc="default">
          <name>duration</name>
          <t>Type: <spanx style="verb">Duration</spanx> <tt>Duration</tt> (optional, default: <spanx style="verb">PT0S</spanx>).</t>

          <t>The <tt>PT0S</tt>)</t>
          <t>This is the zero or positive duration of the event in the event's start time zone. The end time of an event can be found by adding the duration to the event's start time.</t>

          <t>A JSEvent MAY
          <t>An Event <bcp14>MAY</bcp14> involve start and end locations that are in different time zones (e.g., a trans-continental transcontinental flight). This can be expressed using the <spanx style="verb">relativeTo</spanx> <tt>relativeTo</tt> and <spanx style="verb">timeZone</spanx> <tt>timeZone</tt> properties of the JSEvent's Event's Location objects (see <xref target="prop-locations" />).</t> format="default"/>).</t>
        </section>
        <section anchor="prop-status-jsevent" title="status"> numbered="true" toc="default">
          <name>status</name>
          <t>Type: <spanx style="verb">String</spanx> <tt>String</tt> (optional, default: <spanx style="verb">confirmed</spanx>).</t>

          <t>The <tt>confirmed</tt>)</t>
          <t>This is the scheduling status (<xref target="sharing-scheduling-properties" />) format="default"/>) of a JSEvent. an Event. If set, it MUST <bcp14>MUST</bcp14> be one of the following values, another value registered in the IANA JSCalendar &quot;JSCalendar Enum Values Values&quot; registry, or a vendor-specific value (see <xref target="custom-properties" />):

          <list style="symbols">
            <t><spanx style="verb">confirmed</spanx>: Indicates format="default"/>):</t>
          <dl newline="false">
            <dt><tt>confirmed</tt>:</dt><dd>indicates the event is definitely happening.</t>
            <t><spanx style="verb">cancelled</spanx>: Indicates happening</dd>
            <dt><tt>cancelled</tt>:</dt><dd>indicates the event has been cancelled.</t>
            <t><spanx style="verb">tentative</spanx>: Indicates cancelled</dd>
            <dt><tt>tentative</tt>:</dt><dd>indicates the event may happen.</t>
          </list></t> happen</dd>
          </dl>
        </section>
      </section>
      <section anchor="jstask-props" title="JSTask Properties"> numbered="true" toc="default">
        <name>Task Properties</name>
        <t>In addition to the common JSCalendar object <xref target="jscalendar-props">properties</xref> target="jscalendar-props" format="default">properties</xref>, a JSTask Task has the following properties:</t>
        <section anchor="prop-due" title="due"> numbered="true" toc="default">
          <name>due</name>
          <t>Type: <spanx style="verb">LocalDateTime</spanx> (optional).</t>

          <t>The <tt>LocalDateTime</tt> (optional)</t>
          <t>This is the date/time the task is due in the task's time zone.</t>
        </section>
        <section anchor="prop-start-jstask" title="start"> numbered="true" toc="default">
          <name>start</name>
          <t>Type: <spanx style="verb">LocalDateTime</spanx> (optional).</t>

          <t>The <tt>LocalDateTime</tt> (optional)</t>
          <t>This the date/time the task should start in the task's time zone.</t>
        </section>
        <section anchor="prop-estimatedDuration" title="estimatedDuration"> numbered="true" toc="default">
          <name>estimatedDuration</name>
          <t>Type: <spanx style="verb">Duration</spanx> (optional).</t>

          <t>Specifies <tt>Duration</tt> (optional)</t>
          <t>This specifies the estimated positive duration of time the task takes to complete.</t>
        </section>
        <section anchor="prop-percentComplete" title="percentComplete"> numbered="true" toc="default">
          <name>percentComplete</name>
          <t>Type: <spanx style="verb">UnsignedInt</spanx> (optional).</t>

          <t>Represents <tt>UnsignedInt</tt> (optional)</t>
          <t>This represents the percent completion of the task overall. The property value MUST <bcp14>MUST</bcp14>
	    be a positive integer between 0 and 100.</t>
        </section>
        <section anchor="prop-progress" title="progress"> numbered="true" toc="default">
          <name>progress</name>
          <t>Type: <spanx style="verb">String</spanx> (optional).</t>

          <t>Defines <tt>String</tt> (optional)</t>
          <t>This defines the progress of this task. If omitted, the default progress (<xref
	    target="sharing-scheduling-properties" />) format="default"/>) of a JSTask Task is defined as follows (in
	    order of evaluation):

          <list style="symbols">
            <t><spanx style="verb">completed</spanx>: if evaluation):</t>
          <dl newline="false">
            <dt><tt>completed</tt>:</dt>
	        <dd>if the <spanx style="verb">progress</spanx> <tt>progress</tt> property value of all participants is
              <spanx style="verb">completed</spanx>.</t>
            <t><spanx style="verb">failed</spanx>: <tt>completed</tt></dd>
            <dt><tt>failed</tt>:</dt>
	        <dd> if at least one <spanx style="verb">progress</spanx> <tt>progress</tt> property value of a participant is <spanx style="verb">failed</spanx>.</t>
            <t><spanx style="verb">in-process</spanx>: <tt>failed</tt></dd>
            <dt><tt>in-process</tt>:</dt>
	        <dd> if at least one <spanx style="verb">progress</spanx> <tt>progress</tt> property value of a participant is <spanx style="verb">in-process</spanx>.</t>
            <t><spanx style="verb">needs-action</spanx>: If <tt>in-process</tt></dd>
            <dt><tt>needs-action</tt>:</dt>
	        <dd>if none of the other criteria match.</t>
          </list></t> match</dd>
          </dl>
          <t>If set, it MUST <bcp14>MUST</bcp14> be one of the following values, another value registered in the IANA JSCalendar &quot;JSCalendar Enum Values Values&quot; registry, or a vendor-specific value (see <xref target="custom-properties" />):

          <list style="symbols">
            <t><spanx style="verb">needs-action</spanx>: Indicates format="default"/>):

          </t>
          <dl newline="false">
            <dt><tt>needs-action</tt>:</dt><dd>indicates the task needs action.</t>
            <t><spanx style="verb">in-process</spanx>: Indicates action</dd>
            <dt><tt>in-process</tt>:</dt><dd>indicates the task is in process.</t>
            <t><spanx style="verb">completed</spanx>: Indicates process</dd>
            <dt><tt>completed</tt>:</dt><dd>indicates the task is completed.</t>
            <t><spanx style="verb">failed</spanx>: Indicates completed</dd>
            <dt><tt>failed</tt>:</dt><dd>indicates the task failed.</t>
            <t><spanx style="verb">cancelled</spanx>: Indicates failed</dd>
            <dt><tt>cancelled</tt>:</dt><dd>indicates the task was cancelled.</t>
          </list></t> cancelled</dd>
          </dl>
        </section>
        <section anchor="prop-progressUpdated" title="progressUpdated"> numbered="true" toc="default">
          <name>progressUpdated</name>
          <t>Type: <spanx style="verb">UTCDateTime</spanx> (optional).</t>

          <t>Specifies <tt>UTCDateTime</tt> (optional)</t>
          <t>This specifies the date/time the <spanx style="verb">progress</spanx> <tt>progress</tt> property of either the task overall (<xref target="prop-progress" />) format="default"/>) or a specific participant (<xref target="prop-participants" />) format="default"/>) was last updated.</t>
          <t>If the task is recurring and has future instances, a client may want to keep track of the last progress update timestamp of a specific task recurrence, recurrence but leave other instances unchanged. One way to achieve this is by overriding the progressUpdated <tt>progressUpdated</tt> property in the task <spanx style="verb">recurrenceOverrides</spanx> <tt>recurrenceOverrides</tt> property. However, this could produce a long list of timestamps for regularly recurring tasks. An alternative approach is to split the JSTask Task into a current, single instance of JSTask Task with this instance progress update time and a future recurring instance. See also <xref target="prop-relatedTo" /> format="default"/> on splitting.</t>
        </section>
      </section>
      <section anchor="jsgroup-props" title="JSGroup Properties">
        <t>JSGroup numbered="true" toc="default">
        <name>Group Properties</name>
        <t>Group supports the following common <xref target="jscalendar-props">JSCalendar properties</xref>:
        <list style="symbols">
          <t>@type</t>
          <t>uid</t>
          <t>prodId</t>
          <t>created</t>
          <t>updated</t>
          <t>title</t>
          <t>description</t>
          <t>descriptionContentType</t>
          <t>links</t>
          <t>locale</t>
          <t>keywords</t>
          <t>categories</t>
          <t>color</t>
          <t>timeZones</t>
        </list>

        In target="jscalendar-props" format="default">JSCalendar properties</xref>:</t>
        <ul spacing="normal">
          <li>@type</li>
          <li>uid</li>
          <li>prodId</li>
          <li>created</li>
          <li>updated</li>
          <li>title</li>
          <li>description</li>
          <li>descriptionContentType</li>
          <li>links</li>
          <li>locale</li>
          <li>keywords</li>
          <li>categories</li>
          <li>color</li>
          <li>timeZones</li>
        </ul>
        <t>In addition, the following JSGroup-specific Group-specific properties are supported:</t>
        <section anchor="prop-entries" title="entries"> numbered="true" toc="default">
          <name>entries</name>
          <t>Type: <spanx style="verb">(JSTask|JSEvent)[]</spanx> (mandatory).</t>

          <t>A <tt>(Task|Event)[]</tt> (mandatory)</t>
          <t>This is a collection of group members. Implementations MUST <bcp14>MUST</bcp14> ignore entries of
	    unknown type.</t>
        </section>
        <section anchor="prop-source" title="source"> numbered="true" toc="default">
          <name>source</name>
          <t>Type: <spanx style="verb">String</spanx> (optional).</t>

          <t>The <tt>String</tt> (optional)</t>
          <t>This is the source from which updated versions of this group may be retrieved from. retrieved. The value MUST
	    <bcp14>MUST</bcp14> be a URI.</t>
        </section>
      </section>
    </section>
    <section anchor="examples" title="Examples"> numbered="true" toc="default">
      <name>Examples</name>
      <t>The following examples illustrate several aspects of the JSCalendar data model and format. The examples may omit mandatory or additional properties, which is indicated by a placeholder property with key <spanx style="verb">...</spanx>. <tt>...</tt>. While most of the examples use calendar event objects, they are also illustrative for tasks.</t>
      <!-- EXAMPLES START -->
<section anchor="example-simple-event" title="Simple event">
    <t>
    This numbered="true" toc="default">
        <name>Simple Event</name>
        <t>This example illustrates a simple one-time event. It specifies a one-time event that begins on
	January 15, 2020 at 1pm 1 pm New York local time and ends after 1 hour.
    </t>
    <figure>
          <artwork><![CDATA[ hour.</t>
<sourcecode name="" type="json"><![CDATA[
{
  "@type": "jsevent", "Event",
  "uid": "a8df6573-0474-496d-8496-033ad45d7fea",
  "updated": "2020-01-02T18:23:04Z",
  "title": "Some event",
  "start": "2020-01-15T13:00:00",
  "timeZone": "America/New_York",
  "duration": "PT1H"
}
          ]]></artwork>
    </figure>
]]></sourcecode>
</section>
      <section anchor="example-simple-task" title="Simple task">
    <t>
    This numbered="true" toc="default">
        <name>Simple Task</name>
        <t>This example illustrates a simple task for a plain to-do item.
    </t>
    <figure>
          <artwork><![CDATA[ item.</t>
<sourcecode name="" type="json"><![CDATA[
{
  "@type": "jstask", "Task",
  "uid": "2a358cee-6489-4f14-a57f-c104db4dc2f2",
  "updated": "2020-01-09T14:32:01Z",
  "title": "Do something"
}
          ]]></artwork>
    </figure>
]]></sourcecode>
      </section>
      <section anchor="example-simple-group" title="Simple group">
    <t>
    This numbered="true" toc="default">
        <name>Simple Group</name>
        <t>This example illustrates a simple calendar object group that contains an event and a task.
    </t>
    <figure>
          <artwork><![CDATA[ task.</t>
<sourcecode name="" type="json"><![CDATA[
{
  "@type": "jsgroup", "Group",
  "uid": "bf0ac22b-4989-4caf-9ebd-54301b4ee51a",
  "updated": "2020-01-15T18:00:00Z",
  "name": "A simple group",
  "entries": [{
    "@type": "jsevent", "Event",
    "uid": "a8df6573-0474-496d-8496-033ad45d7fea",
    "updated": "2020-01-02T18:23:04Z",
    "title": "Some event",
    "start": "2020-01-15T13:00:00",
    "timeZone": "America/New_York",
    "duration": "PT1H"
  },
  {
    "@type": "jstask", "Task",
    "uid": "2a358cee-6489-4f14-a57f-c104db4dc2f2",
    "updated": "2020-01-09T14:32:01Z",
    "title": "Do something"
  }]
}
          ]]></artwork>
    </figure>
]]></sourcecode>
      </section>
      <section anchor="example-all-day-event" title="All-day event"> numbered="true" toc="default">
        <name>All-Day Event</name>
        <t>
    This example illustrates an event for an international holiday. It specifies an all-day event on April 1 that occurs every year since the year 1900.
        </t>
    <figure>
          <artwork><![CDATA[
<sourcecode name="" type="json"><![CDATA[
{
  "...": "",
  "title": "April Fool's Day",
  "showWithoutTime": true,
  "start": "1900-04-01T00:00:00",
  "duration": "P1D",
  "recurrenceRules": [{
    "@type": "RecurrenceRule",
    "frequency": "yearly"
  }]
}
          ]]></artwork>
    </figure>
]]></sourcecode>
      </section>
      <section anchor="example-due-task" title="Task numbered="true" toc="default">
        <name>Task with a due date"> Due Date</name>
        <t>
    This example illustrates a task with a due date. It is a reminder to buy groceries before 6pm 6 pm Vienna local time on January 19, 2020. The calendar user expects to need 1 hour for shopping.
        </t>
    <figure>
          <artwork><![CDATA[
<sourcecode name="" type="json"><![CDATA[
{
  "...": "",
  "title": "Buy groceries",
  "due": "2020-01-19T18:00:00",
  "timeZone": "Europe/Vienna",
  "estimatedDuration": "PT1H"
}
          ]]></artwork>
    </figure>
]]></sourcecode>
      </section>
      <section anchor="example-zoned-event-endtz" title="Event numbered="true" toc="default">
        <name>Event with end time zone"> End Time Zone</name>
        <t>
    This example illustrates the use of end time zones by use of an international flight. The flight starts on April 1, 2020 at 9am 9 am in Berlin local time. The duration of the flight is scheduled at 10 hours 30 minutes. The time at the flight's destination is in the same time zone as Tokyo. Calendar clients could use the end time zone to display the arrival time in Tokyo local time and highlight the time zone difference of the flight. The location names can serve as input for navigation systems.
        </t>
    <figure>
          <artwork><![CDATA[
<sourcecode name="" type="json"><![CDATA[
{
  "...": "",
  "title": "Flight XY51 to Tokyo",
  "start": "2020-04-01T09:00:00",
  "timeZone": "Europe/Berlin",
  "duration": "PT10H30M",
  "locations": {
    "418d0b9b-b656-4b3c-909f-5b149ca779c9":
    "1": {
      "@type": "Location",
      "rel": "start",
      "name": "Frankfurt Airport (FRA)"
    },
    "c2c7ac67-dc13-411e-a7d4-0780fb61fb08":
    "2": {
      "@type": "Location",
      "rel": "end",
      "name": "Narita International Airport (NRT)",
      "timeZone": "Asia/Tokyo"
    }
  }
}
          ]]></artwork>
    </figure>
]]></sourcecode>
      </section>
      <section anchor="example-floating-event" title="Floating-time event numbered="true" toc="default">
        <name>Floating-Time Event (with recurrence)"> Recurrence)</name>
        <t>
    This example illustrates the use of floating time. Since January 1, 2020, a calendar user blocks 30 minutes every day to practice Yoga yoga at 7am 7 am local time, time in whatever time zone the user is located on that date.
        </t>
    <figure>
          <artwork><![CDATA[
<sourcecode name="" type="json"><![CDATA[
{
  "...": "",
  "title": "Yoga",
  "start": "2020-01-01T07:00:00",
  "duration": "PT30M",
  "recurrenceRules": [{
    "@type": "RecurrenceRule",
    "frequency": "daily"
  }]
}
          ]]></artwork>
    </figure>
]]></sourcecode>
      </section>
      <section anchor="example-multi-location-event" title="Event numbered="true" toc="default">
        <name>Event with multiple locations Multiple Locations and localization"> Localization</name>
        <t>
    This example illustrates an event that happens at both a physical and a virtual location. Fans can see a live concert on premises or online. The event title and descriptions are localized.
        </t>
    <figure>
          <artwork><![CDATA[
<sourcecode name="" type="json"><![CDATA[
{
  "...": "",
  "title": "Live from Music Bowl: The Band",
  "description": "Go see the biggest music event ever!",
  "locale": "en",
  "start": "2020-07-04T17:00:00",
  "timeZone": "America/New_York",
  "duration": "PT3H",
  "locations": {
    "c0503d30-8c50-4372-87b5-7657e8e0fedd": {
      "@type": "Location",
      "name": "The Music Bowl",
      "description": "Music Bowl, Central Park, New York",
      "coordinates": "geo:40.7829,-73.9654"
    }
  },
  "virtualLocations": {
    "1":
    "vloc1": {
      "@type": "VirtualLocation",
      "name": "Free live Stream from Music Bowl",
      "uri": "https://stream.example.com/the_band_2020"
    }
  },
  "localizations": {
    "de": {
      "title": "Live von der Music Bowl: The Band!",
      "description": "Schau dir das größte Musikereignis an!",
      "virtualLocations/1/name":
      "virtualLocations/vloc1/name":
        "Gratis Live-Stream aus der Music Bowl"
    }
  }
}
          ]]></artwork>
    </figure>
]]></sourcecode>
      </section>
      <section anchor="example-recurring-overrides" title="Recurring event numbered="true" toc="default">
        <name>Recurring Event with overrides"> Overrides</name>
        <t>
    This example illustrates the use of recurrence overrides. A math course at a University university is held for the first time on January 8, 2020 at 9am 9 am London time and occurs every week until June 24, 2020. Each lecture lasts for one hour and 30 minutes and is located at the Mathematics department. This event has exceptional occurrences: at the last occurrence of the course is an exam, which lasts for 2 hours and starts at 10am. 10 am. Also, the location of the exam differs from the usual location. On April 1 1, no course is held. On January 7 at 2pm 2 pm, there is an optional introduction course, that which occurs before the first regular lecture.
        </t>
    <figure>
          <artwork><![CDATA[
<sourcecode name="" type="json"><![CDATA[
{
  "...": "",
  "title": "Calculus I",
  "start": "2020-01-08T09:00:00",
  "timeZone": "Europe/London",
  "duration": "PT1H30M",
  "locations": {
    "0dfb8ace-aad1-4734-b3b4-a2fe3d6ae1c5":
    "mlab": {
      "@type": "Location",
      "title": "Math lab room 1",
      "description": "Math Lab I, Department of Mathematics"
    }
  },
  "recurrenceRules": [{
    "@type": "RecurrenceRule",
    "frequency": "weekly",
    "until": "2020-06-24T09:00:00"
  }],
  "recurrenceOverrides": {
    "2020-01-07T14:00:00": {
      "title": "Introduction to Calculus I (optional)"
    },
    "2020-04-01T09:00:00": {
      "excluded": true
    },
    "2020-06-25T09:00:00": {
      "title": "Calculus I Exam",
      "start": "2020-06-25T10:00:00",
      "duration": "PT2H",
      "locations": {
        "84d639ca-37ac-4a86-81e5-9bbba8eb4053":
        "auditorium": {
          "@type": "Location",
          "title": "Big Auditorium",
          "description": "Big Auditorium, Other Road"
        }
      }
    }
  }
}
          ]]></artwork>
    </figure>
          ]]></sourcecode>
      </section>
      <section anchor="example-recurring-participants" title="Recurring event numbered="true" toc="default">
        <name>Recurring Event with participants"> Participants</name>
        <t>
    This example illustrates scheduled events. A team meeting occurs every week since January 8, 2020 at 9am 9 am Johannesburg time. The event owner also chairs the event. Participants meet in a virtual meeting room. An attendee has accepted the invitation, but but, on March 4, 2020 2020, he is unavailable and declined participation for this occurrence.
        </t>
    <figure>
          <artwork><![CDATA[
<sourcecode name="" type="json"><![CDATA[
{
  "...": "",
  "title": "FooBar team meeting",
  "start": "2020-01-08T09:00:00",
  "timeZone": "Africa/Johannesburg",
  "duration": "PT1H",
  "virtualLocations": {
    "3f41b47b-a5eb-494f-90eb-19d279486d84":
    "0": {
      "@type": "VirtualLocation",
      "name": "ChatMe meeting room",
      "uri": "https://chatme.example.com?id=1234567&pw=a8a24627b63d396e" "https://chatme.example.com?id=1234567&pw=a8a24627b63d"
    }
  },
  "recurrenceRules": [{
    "@type": "RecurrenceRule",
    "frequency": "weekly"
  }],
  "replyTo": {
    "imip": "mailto:f245f875-7f63-4a5e-a2c8@schedule.example.com"
  },
  "participants": {
    "dG9tQGZvb2Jhci5xlLmNvbQ": {
      "@type": "Participant",
      "name": "Tom Tool",
      "email": "tom@foobar.example.com",
      "sendTo": {
        "imip": "mailto:tom@calendar.example.com"
      },
      "participationStatus": "accepted",
      "roles": {
        "attendee": true
      }
    },
    "em9lQGZvb2GFtcGxlLmNvbQ": {
      "@type": "Participant",
      "name": "Zoe Zelda",
      "email": "zoe@foobar.example.com",
      "sendTo": {
        "imip": "mailto:zoe@foobar.example.com"
      },
      "participationStatus": "accepted",
      "roles": {
        "owner": true,
        "attendee": true,
        "chair": true
      }
    }
  },
  "recurrenceOverrides": {
    "2020-03-04T09:00:00": {
      "participants/dG9tQGZvb2Jhci5xlLmNvbQ/participationStatus":
                                                          "declined"
    }
  }
}
          ]]></artwork>
    </figure>
]]></sourcecode>
      </section>
      <!-- EXAMPLES END -->
    </section>
    <section anchor="security-considerations" title="Security Considerations"> numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>Calendaring and scheduling information is very privacy-sensitive. privacy sensitive.  It can reveal the social network of a user; user, location information of this user and those in their social network; network, identity and credentials information; information, and the patterns of behavior of the user in both the physical and cyber realm. Additionally, calendar events and tasks can could influence the physical location of a user or their cyber behavior within a known time window.  Its transmission and storage must be done carefully to protect it from possible threats, such as eavesdropping, replay, message insertion, deletion, modification, and on-path attacks.</t>
      <t>The data being stored and transmitted may be used in systems with real world real-world consequences. For example, a home automation system may turn an alarm on and off. Or off  or a coworking space may charge money to the organiser organizer of an event that books one of their meeting rooms. Such systems must be careful to authenticate all data they receive to prevent them from being subverted, subverted and ensure the change comes from an authorized entity.</t>
      <t>This document just only defines the data format; such considerations are primarily the concern of the API or method of storage and transmission of such files.</t>
      <section anchor="sec-recurrences" title="Expanding Recurrences"> numbered="true" toc="default">
        <name>Expanding Recurrences</name>
        <t>A recurrence rule may produce infinite occurrences of an event. Implementations MUST <bcp14>MUST</bcp14> handle expansions carefully to prevent accidental or deliberate resource exhaustion.</t>
        <t>Conversely, a recurrence rule may be specified that does not expand to anything. It is not always possible to tell this through static analysis of the rule, so implementations MUST <bcp14>MUST</bcp14> be careful to avoid getting stuck in infinite loops, loops or otherwise exhausting resources while searching for the next occurrence.</t>
        <t>Events recur in the event's time zone. If the user is in a different time zone, daylight saving transitions may cause an event that normally occurs at, for example, 9am 9 am to suddenly shift an hour earlier. This may be used in an attempt to cause a participant to miss an important meeting. User agents must be careful to translate date-times correctly between time zones and may wish to call out unexpected changes in the time of a recurring event.</t>
      </section>
      <section anchor="json-parsing" title="JSON Parsing"> numbered="true" toc="default">
        <name>JSON Parsing</name>
        <t>The Security Considerations security considerations of <xref target="RFC8259"/> target="RFC8259" format="default"/> apply to the use of JSON as the data interchange format.
        </t>
        <t>As for any serialization format, parsers need to thoroughly check the syntax of the supplied data. JSON uses opening and closing tags for several types and structures, and it is possible that the end of the supplied data will be reached when scanning for a matching closing tag; this is an error condition, and implementations need to stop scanning at the end of the supplied data.</t>
        <t>JSON also uses a string encoding with some escape sequences to encode special characters within a string. Care is needed when processing these escape sequences to ensure that they are fully formed before the special processing is triggered, with special care taken when the escape sequences appear adjacent to other (non-escaped) special characters or adjacent to the end of data (as in the previous paragraph).</t>
        <t>If parsing JSON into a non-textual structured data format, implementations may need to allocate storage to hold JSON string elements.  Since JSON does not use explicit string lengths, the risk of denial of service due to resource exhaustion is small, but implementations may still wish to place limits on the size of allocations they are willing to make in any given context, to avoid untrusted data causing excessive memory allocation.</t>
      </section>
      <section anchor="uri-values" title="URI Values"> numbered="true" toc="default">
        <name>URI Values</name>
        <t>Several JSCalendar properties contain URIs as values, and processing these properties requires extra care. Section 7 of <xref target="RFC3986" /> sectionFormat="of" section="7"/> discusses security risks related to URIs.</t>
        <t>Fetching remote resources carries inherent risks. Connections must only be allowed on well known well-known ports, using allowed protocols (generally (generally, just HTTP/HTTPS on their default ports). The URL must be resolved externally and not allowed to access internal resources. Connecting to an external source reveals IP (and therefore generally often location) information.</t>
        <t>A maliciously constructed JSCalendar object may contain a very large number of URIs. In the case of published calendars with a large number of subscribers, such objects could be widely distributed. Implementations should be careful to limit the automatic fetching of linked resources to reduce the risk of this being an amplification vector for a denial-of-service attack.</t>
      </section>
      <section anchor="spam" title="Spam"> numbered="true" toc="default">
        <name>Spam</name>
        <t>Calendar systems may receive JSCalendar files from untrusted sources, in particular particular, as attachments to emails. This can be a vector for an attacker to inject spam into a user's calendar. This may confuse, annoy, and mislead users, users or overwhelm their calendar with bogus events, preventing them from seeing legitimate ones.</t>
        <t>Heuristic, statistical statistical, or machine-learning-based filters can be effective in filtering out spam. Authentication mechanisms mechanisms, such as DKIM DomainKeys Identified Mail (DKIM) <xref target="RFC6376" /> format="default"/>, can help establish the source of messages and associate the data with existing relationships (such as an address book contact). Misclassifications However, misclassifications are always possible, however, possible and providing a mechanism for users to quickly correct this is advised.</t>
        <t>Confusable unicode characters may be used to trick a user into trusting a JSCalendar file that appears to come from a known contact but is actually from a similar-looking source controlled by an attacker.</t>
      </section>
      <section anchor="duplication" title="Duplication"> numbered="true" toc="default">
        <name>Duplication</name>
        <t>It is important for calendar systems to maintain the UID of an event when updating it to avoid an unexpected duplication of events. Consumers of the data may not remove the previous version of the event if it has a different UID. This can lead to a confusing situation for the user, with many variations of the event and no indication of which one is correct. Care must be taken by consumers of the data to remove old events where possible to avoid an accidental denial-of-service attack due to the volume of data.</t>
      </section>
      <section anchor="timezonesec" title="Time Zones"> numbered="true" toc="default">
        <name>Time Zones</name>
        <t>Events recur in a particular time zone. When this differs from the user's current time zone, it may unexpectedly cause an occurrence to shift in time for that user due to a daylight savings change in the event's time zone. A maliciously crafted event could attempt to confuse users with such an event to ensure a meeting is missed.</t>
      </section>
    </section>
    <section anchor="iana-considerations" title="IANA Considerations"> numbered="true" toc="default">
      <name>IANA Considerations</name>
      <section anchor="iana-mime-type" title="Media numbered="true" toc="default">
        <name>Media Type Registration"> Registration</name>
        <t>This document defines a media type for use with JSCalendar data formatted in JSON.</t>

  <t><list style="hanging">
    <t hangText="Type name:">application</t>
    <t hangText="Subtype name:">jscalendar+json</t>
    <t hangText="Required parameters:">type
        <vspace blankLines="1" />
        The <spanx style="verb">type</spanx>
        <dl newline="false" spacing="normal">
          <dt>Type name:</dt>
          <dd>application</dd>
          <dt>Subtype name:</dt>
          <dd>jscalendar+json</dd>
          <dt>Required parameters:</dt>
          <dd><t>type</t>

            <t>The <tt>type</tt> parameter conveys the type of the JSCalendar data in the body part, with the value being one of <spanx style="verb">jsevent</spanx>, <spanx style="verb">jstask</spanx>, or <spanx style="verb">jsgroup</spanx>. part. The
	        allowed parameter MUST NOT occur more than once. It MUST match the value of values correspond to the <spanx style="verb">@type</spanx> <tt>@type</tt> property of the JSON-formatted
		    JSCalendar object in the body.</t>
    <t hangText="Optional parameters:">none</t>
    <t hangText="Encoding considerations:">
        Same body:</t>
            <dl newline="false" spacing="normal">
              <dt><tt>event</tt>:</dt>
	            <dd>The <tt>@type</tt> property value <bcp14>MUST</bcp14> be
		          <tt>Event</tt>.</dd>
              <dt><tt>task</tt>:</dt>
	            <dd>The <tt>@type</tt> property value <bcp14>MUST</bcp14> be <tt>Task</tt>.</dd>
              <dt><tt>group</tt>:</dt>
	            <dd>The <tt>@type</tt> property value <bcp14>MUST</bcp14> be <tt>Group</tt>.</dd>
            </dl>
            <t>No other parameter values are allowed. The parameter <bcp14>MUST NOT</bcp14> occur more than
	        once.</t>
          </dd>
          <dt>Optional parameters:</dt>
          <dd>none</dd>
          <dt>Encoding considerations:</dt>
          <dd>This is the same as the encoding considerations of application/json application/json, as specified in <xref target="RFC8259">RFC8529, Section 11</xref>.</t>
    <t hangText="Security considerations:">
	    target="RFC8259" sectionFormat="of" section="11"/>.</dd>
          <dt>Security considerations:</dt>
          <dd> See <xref target="security-considerations" /> format="default"/> of this document.</t>
    <t hangText="Interoperability considerations:">While document.</dd>
          <dt>Interoperability considerations:</dt>
          <dd>While JSCalendar is designed to avoid ambiguities as much as possible, when converting objects from other calendar formats to/from JSCalendar JSCalendar, it is possible that differing representations for the same logical data might arise, or ambiguities in interpretation. interpretation might arise. The semantic equivalence of two JSCalendar objects may be determined differently by different applications, for example example, where URL values differ in case between the two objects.</t>
    <t hangText="Published specification:">This specification.</t>
    <t hangText="Applications objects.</dd>
          <dt>Published specification:</dt>
          <dd>RFC 8984</dd>
          <dt>Applications that use this media type:">Applications type:</dt>
          <dd>Applications that currently make use of the text/calendar and application/calendar+json media types can use this as an alternative. Similarly, applications that use the application/json media type to transfer calendaring data can use this to further specify the content.</t>
    <t hangText="Fragment content.</dd>
          <dt>Fragment identifier considerations:">A considerations:</dt>
          <dd>A JSON Pointer fragment identifier may be used, as defined in <xref target="RFC6901" />, Section 6.</t>
    <t hangText="Additional information:">
        <list style="hanging">
            <t hangText="Magic number(s):">N/A</t>
            <t hangText="File extensions(s):">N/A</t>
            <t hangText="Macintosh sectionFormat="comma" section="6"/>.</dd>
          <dt>Additional information:</dt>
          <dd>
            <dl newline="false" spacing="normal">
              <dt>Magic number(s):</dt>
              <dd>N/A</dd>
              <dt>File extensions(s):</dt>
              <dd>N/A</dd>
              <dt>Macintosh file type code(s):">N/A</t>
        </list>
    </t>
    <t hangText="Person code(s):</dt>
              <dd>N/A</dd>
            </dl>
          </dd>
          <dt>Person &amp; email address to contact for further information:">calsify@ietf.org</t>
    <t hangText="Intended usage:">COMMON</t>
    <t hangText="Restrictions information:</dt>
          <dd>calsify@ietf.org</dd>
          <dt>Intended usage:</dt>
          <dd>COMMON</dd>
          <dt>Restrictions on usage:">N/A</t>
    <t hangText="Author:">See usage:</dt>
          <dd>N/A</dd>
          <dt>Author:</dt>
          <dd>See the "Author's Address" section of this document.</t>
    <t hangText="Change controller:">IETF</t>
  </list></t> document.</dd>
          <dt>Change controller:</dt>
          <dd>IETF</dd>
        </dl>
      </section>
      <section anchor="iana-property-registry" title='Creation numbered="true" toc="default">
        <name>Creation of the "JSCalendar Properties" Registry'>
  <t>The IANA will create Registry</name>
        <t>IANA has created the "JSCalendar Properties" registry to allow interoperability of extensions to JSCalendar objects.</t>
        <t>This registry follows the Expert Review process (<xref target="RFC8126"/>, Section 4.5). target="RFC8126" sectionFormat="comma" section="4.5"/>). If the &quot;intended use&quot; "Intended Usage" field is <spanx style="verb">common</spanx>, <tt>common</tt>, sufficient documentation is required to enable interoperability. Preliminary community review for this registry is optional but strongly encouraged.</t>
        <t>A registration can have an intended use usage of <spanx style="verb">common</spanx>, <spanx style="verb">reserved</spanx>, <tt>common</tt>, <tt>reserved</tt>, or <spanx style="verb">obsolete</spanx>. The <tt>obsolete</tt>. IANA will list common-use registrations with a common usage designation prominently and separately from those with other intended use usage values.</t>
        <t>A <spanx style="verb">reserved</spanx> <tt>reserved</tt> registration reserves a property name without assigning semantics to avoid name collisions with future extensions or protocol use.</t>
        <t>An <spanx style="verb">obsolete</spanx> <tt>obsolete</tt> registration denotes a property that is no longer expected to be added by up-to-date systems. A new property has probably been defined covering the obsolete property's semantics.</t>
        <t>The JSCalendar property registration procedure is not a formal standards process but rather an administrative procedure intended to allow community comment and sanity checking check it is coherent without excessive time delay. It is designed to encourage vendors to document and register new properties they add for use cases not covered by the original specification, leading to increased interoperability.</t>
        <section anchor="iana-property-registry-preliminary-community-review" title="Preliminary numbered="true" toc="default">
          <name>Preliminary Community Review"> Review</name>
          <t>Notice of a potential new registration SHOULD <bcp14>SHOULD</bcp14> be sent to the Calext mailing list
	    &lt;calsify@ietf.org&gt; for review. This mailing list is appropriate to solicit community feedback
	      on a proposed new property.</t>

    <t>Properties
          <t>Property registrations must be marked with their intended use: "common", "reserved" "reserved", or
	    "obsolete".</t>
          <t>The intent of the public posting to this list is to solicit comments and feedback on the choice of
	    the property name, the unambiguity of the specification document, and a review of any
	      interoperability or security considerations. The submitter may submit a revised registration proposal
	        or abandon the registration completely at any time.</t>
        </section>
        <section anchor="iana-property-registry-submit-request-to-iana" title="Submit numbered="true" toc="default">
          <name>Submit Request to IANA"> IANA</name>
          <t>Registration requests can be sent to &lt;iana@iana.org&gt;.</t>
        </section>
        <section anchor="iana-property-registry-designated-expert-review" title="Designated numbered="true" toc="default">
          <name>Designated Expert Review"> Review</name>
          <t>The primary concern of the designated expert (DE) is preventing name collisions and encouraging
	    the submitter to document security and privacy considerations. For a common-use registration, the DE
	      is expected to confirm that suitable documentation, as described in Section 4.6 of <xref target="RFC8126"/>, target="RFC8126"
	        sectionFormat="of" section="4.6"/>, is available to ensure interoperability. That documentation will
	        usually be in an RFC, but simple definitions are likely to use a web/wiki page, and if a sentence or
		  two is deemed sufficient sufficient, it could be described in the registry itself. The DE should also verify that
		    the property name does not conflict with work that is active or already published within the IETF. A
		      published specification is not required for reserved or obsolete registrations.</t>
          <t>The DE will either approve or deny the registration request and publish a notice of the decision
	    to the Calext WG mailing list or its successor, as well as inform IANA. A denial notice must be
	      justified by an explanation, and, in the cases where it is possible, concrete suggestions on how the
	        request can be modified so as to become acceptable should be provided.</t>
        </section>
        <section anchor="iana-property-registry-change-procedures" title="Change Procedures"> numbered="true" toc="default">
          <name>Change Procedures</name>
          <t>Once a JSCalendar property has been published by the IANA, the change controller may request a
	    change to its definition. The same procedure that would be appropriate for the original registration
	      request is used to process a change request.</t>
          <t>JSCalendar property registrations may not be deleted; properties that are no longer believed appropriate for use can be declared obsolete by a change to their &quot;intended use&quot; "intended usage" field; such properties will be clearly marked in the lists published by the IANA.</t> IANA registry.</t>
          <t>Significant changes to a JSCalendar property's definition should be requested only when there are
	    serious omissions or errors in the published specification, as such changes may cause
	      interoperability issues. When review is required, a change request may be denied if it renders
	        entities that were valid under the previous definition invalid under the new definition.</t>
          <t>The owner of a JSCalendar property may pass responsibility to another person or agency by
	    informing the IANA; this can be done without discussion or review.</t>
        </section>
        <section anchor="iana-property-registry-template" title="JSCalendar Properties numbered="true" toc="default">
          <name>&quot;JSCalendar Properties&quot; Registry Template">
    <t><list style="symbols">
      <t>Property Name: The Template</name>
          <dl newline="false">
            <dt>Property Name:</dt>
	        <dd>This is the name of the property. The property name MUST NOT <bcp14>MUST NOT</bcp14> already be
		    registered for
		        any of the object types listed in the "Property Context" field of this registration. Other object
			    types MAY <bcp14>MAY</bcp14> already have registered a different property with the same name, however name; however,
			        the same name SHOULD <bcp14>SHOULD</bcp14> only be used when the semantics are analogous.</t>
      <t>Property Type: The analogous.</dd>
            <dt>Property Type:</dt>
	        <dd> This is the type of this property, using type signatures signatures, as specified in <xref target="type-signatures"/>. target="type-signatures" format="default"/>.
		    The property type MUST <bcp14>MUST</bcp14> be registed registered in the Type Registry.</t>
      <t>Property Context: A "JSCalendar Types" registry.</dd>
            <dt>Property Context:</dt>
	        <dd>This is a comma-separated list of JSCalendar object types this property is allowed on.</t>
      <t>Reference on.</dd>
            <dt>Reference or Description: A Description:</dt>
	        <dd>This is a brief description or RFC number and section reference where the property is specified (omitted for "reserved" property names).</t>
      <t>Intended Use: Common, reserved, names).</dd>
            <dt>Intended Usage:</dt>
	        <dd>This may be "common", "reserved", or obsolete.</t>
      <t>Change Controller: Who "obsolete".</dd>
            <dt>Change Controller:</dt>
	        <dd>This is who may request a change to this entry's definition (<spanx style="verb">IETF</spanx> (<tt>IETF</tt> for IETF-stream RFCs).</t>
  </list></t> RFCs from the IETF stream).</dd>
          </dl>
        </section>
        <section anchor="iana-property-registry-contents" title="Initial numbered="true" toc="default">
          <name>Initial Contents for the JSCalendar Properties Registry"> &quot;JSCalendar Properties&quot; Registry</name>
          <t>The following table lists the initial entries of the JSCalendar Properties "JSCalendar Properties" registry. All properties are for common-use. common use. All RFC section references are for this document. The change controller for all these properties is "IETF".</t>

    <texttable anchor="table-iana-property-registry">
      <ttcol align='left'>Property Name</ttcol>
      <ttcol align='left'>Property Type</ttcol>
      <ttcol align='left'>Property Context</ttcol>
      <ttcol align='left'>Reference or Description</ttcol>

      <c>@type</c>
      <c>String</c>
      <c>JSEvent, JSTask, JSGroup,

<table anchor="tab-iana-property-registry" align="center">
  <name>Initial Contents of the &quot;JSCalendar Properties&quot; Registry</name>
            <thead>
              <tr>
                <th align="left">Property Name</th>
                <th align="left">Property Type</th>
                <th align="left">Property Context</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">@type</td>
                <td align="left">String</td>
                <td align="left">Event, Task, Group, AbsoluteTrigger, Alert, Link, Location, NDay, OffsetTrigger, Participant, RecurrenceRule, Relation, TimeZone, TimeZoneRule, VirtualLocation</c>
      <c><xref target="prop-type"/>, <xref target="prop-alerts"/>, <xref target="type-Link"/>, <xref target="prop-locations"/>, <xref target="prop-participants"/>, <xref target="prop-recurrenceRules"/>, <xref target="prop-relatedTo"/>, <xref target="prop-timeZones"/>, <xref target="prop-timeZones"/>, <xref target="prop-virtualLocations"/></c>

      <c>acknowledged</c>
      <c>UTCDateTime</c>
      <c>Alert</c>
      <c><xref target="prop-alerts"/></c>

      <c>action</c>
      <c>String</c>
      <c>Alert</c>
      <c><xref target="prop-alerts"/></c>

      <c>alerts</c>
      <c>Id[Alert]</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-alerts"/></c>

      <c>aliases</c>
      <c>String[Boolean]</c>
      <c>TimeZone</c>
      <c><xref target="prop-timeZones"/></c>

      <c>byDay</c>
      <c>NDay[]</c>
      <c>RecurrenceRule</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>byHour</c>
      <c>UnsignedInt[]</c>
      <c>RecurrenceRule</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>byMinute</c>
      <c>UnsignedInt[]</c>
      <c>RecurrenceRule</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>byMonth</c>
      <c>String[]</c>
      <c>RecurrenceRule</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>byMonthDay</c>
      <c>Int[]</c>
      <c>RecurrenceRule</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>bySecond</c>
      <c>UnsignedInt[]</c>
      <c>RecurrenceRule</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>bySetPosition</c>
      <c>Int[]</c>
      <c>RecurrenceRule</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>byWeekNo</c>
      <c>Int[]</c>
      <c>RecurrenceRule</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>byYearDay</c>
      <c>Int[]</c>
      <c>RecurrenceRule</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>categories</c>
      <c>String[Boolean]</c>
      <c>JSEvent, JSTask, JSGroup</c>
      <c><xref target="prop-categories"/></c>

      <c>cid</c>
      <c>String</c>
      <c>Link</c>
      <c><xref target="type-Link"/></c>

      <c>color</c>
      <c>String</c>
      <c>JSEvent, JSTask, JSGroup</c>
      <c><xref target="prop-color"/></c>

      <c>comments</c>
      <c>String[]</c>
      <c>TimeZoneRule</c>
      <c><xref target="prop-timeZones"/></c>

      <c>contentType</c>
      <c>String</c>
      <c>Link</c>
      <c><xref target="type-Link"/></c>

      <c>coordinates</c>
      <c>String</c>
      <c>Location</c>
      <c><xref target="prop-locations"/></c>

      <c>count</c>
      <c>UnsignedInt</c>
      <c>RecurrenceRule</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>created</c>
      <c>UTCDateTime</c>
      <c>JSEvent, JSTask, JSGroup</c>
      <c><xref target="prop-created"/></c>

      <c>day</c>
      <c>String</c>
      <c>NDay</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>daylight</c>
      <c>TimeZoneRule</c>
      <c>TimeZone</c>
      <c><xref target="prop-timeZones"/></c>

      <c>delegatedFrom</c>
      <c>String[Boolean]</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>delegatedTo</c>
      <c>String[Boolean]</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>description</c>
      <c>String</c>
      <c>JSEvent, JSTask, VirtualLocation</td>
                <td align="left">
                  <xref target="prop-type" format="default"/>, <xref target="prop-alerts" format="default"/>, <xref target="type-Link" format="default"/>, <xref target="prop-locations" format="default"/>, <xref target="prop-participants" format="default"/>, <xref target="prop-recurrenceRules" format="default"/>, <xref target="type-Relation" format="default"/>, <xref target="prop-timeZones" format="default"/>, <xref target="prop-virtualLocations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">acknowledged</td>
                <td align="left">UTCDateTime</td>
                <td align="left">Alert</td>
                <td align="left">
                  <xref target="prop-alerts" format="default"/></td>
              </tr>
              <tr>
                <td align="left">action</td>
                <td align="left">String</td>
                <td align="left">Alert</td>
                <td align="left">
                  <xref target="prop-alerts" format="default"/></td>
              </tr>
              <tr>
                <td align="left">alerts</td>
                <td align="left">Id[Alert]</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-alerts" format="default"/></td>
              </tr>
              <tr>
                <td align="left">aliases</td>
                <td align="left">String[Boolean]</td>
                <td align="left">TimeZone</td>
                <td align="left">
                  <xref target="prop-timeZones" format="default"/></td>
              </tr>
              <tr>
                <td align="left">byDay</td>
                <td align="left">NDay[]</td>
                <td align="left">RecurrenceRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">byHour</td>
                <td align="left">UnsignedInt[]</td>
                <td align="left">RecurrenceRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">byMinute</td>
                <td align="left">UnsignedInt[]</td>
                <td align="left">RecurrenceRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">byMonth</td>
                <td align="left">String[]</td>
                <td align="left">RecurrenceRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">byMonthDay</td>
                <td align="left">Int[]</td>
                <td align="left">RecurrenceRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">bySecond</td>
                <td align="left">UnsignedInt[]</td>
                <td align="left">RecurrenceRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">bySetPosition</td>
                <td align="left">Int[]</td>
                <td align="left">RecurrenceRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">byWeekNo</td>
                <td align="left">Int[]</td>
                <td align="left">RecurrenceRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">byYearDay</td>
                <td align="left">Int[]</td>
                <td align="left">RecurrenceRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">categories</td>
                <td align="left">String[Boolean]</td>
                <td align="left">Event, Task, Group</td>
                <td align="left">
                  <xref target="prop-categories" format="default"/></td>
              </tr>
              <tr>
                <td align="left">cid</td>
                <td align="left">String</td>
                <td align="left">Link</td>
                <td align="left">
                  <xref target="type-Link" format="default"/></td>
              </tr>
              <tr>
                <td align="left">color</td>
                <td align="left">String</td>
                <td align="left">Event, Task, Group</td>
                <td align="left">
                  <xref target="prop-color" format="default"/></td>
              </tr>
              <tr>
                <td align="left">comments</td>
                <td align="left">String[]</td>
                <td align="left">TimeZoneRule</td>
                <td align="left">
                  <xref target="prop-timeZones" format="default"/></td>
              </tr>
              <tr>
                <td align="left">contentType</td>
                <td align="left">String</td>
                <td align="left">Link</td>
                <td align="left">
                  <xref target="type-Link" format="default"/></td>
              </tr>
              <tr>
                <td align="left">coordinates</td>
                <td align="left">String</td>
                <td align="left">Location</td>
                <td align="left">
                  <xref target="prop-locations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">count</td>
                <td align="left">UnsignedInt</td>
                <td align="left">RecurrenceRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">created</td>
                <td align="left">UTCDateTime</td>
                <td align="left">Event, Task, Group</td>
                <td align="left">
                  <xref target="prop-created" format="default"/></td>
              </tr>
              <tr>
                <td align="left">day</td>
                <td align="left">String</td>
                <td align="left">NDay</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">daylight</td>
                <td align="left">TimeZoneRule[]</td>
                <td align="left">TimeZone</td>
                <td align="left">
                  <xref target="prop-timeZones" format="default"/></td>
              </tr>
              <tr>
                <td align="left">delegatedFrom</td>
                <td align="left">Id[Boolean]</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">delegatedTo</td>
                <td align="left">Id[Boolean]</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">description</td>
                <td align="left">String</td>
                <td align="left">Event, Task, Location, Participant, VirtualLocation</c>
      <c><xref target="prop-description"/>, <xref target="prop-locations"/>, <xref target="prop-participants"/>, <xref target="prop-virtualLocations"/></c>

      <c>descriptionContentType</c>
      <c>String</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-descriptionContentType"/></c>

      <c>display</c>
      <c>String</c>
      <c>Link</c>
      <c><xref target="type-Link"/></c>

      <c>due</c>
      <c>LocalDateTime</c>
      <c>JSTask</c>
      <c><xref target="prop-due"/></c>

      <c>duration</c>
      <c>Duration</c>
      <c>JSEvent</c>
      <c><xref target="prop-duration"/></c>

      <c>email</c>
      <c>String</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>entries</c>
      <c>(JSTask|JSEvent)[]</c>
      <c>JSGroup</c>
      <c><xref target="prop-entries"/></c>

      <c>estimatedDuration</c>
      <c>Duration</c>
      <c>JSTask</c>
      <c><xref target="prop-estimatedDuration"/></c>

      <c>excluded</c>
      <c>Boolean</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-excluded"/></c>

      <c>excludedRecurrenceRules</c>
      <c>RecurrenceRule[]</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-excludedRecurrenceRules"/></c>

      <c>expectReply</c>
      <c>Boolean</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>firstDayOfWeek</c>
      <c>String</c>
      <c>RecurrenceRule</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>freeBusyStatus</c>
      <c>String</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-freeBusyStatus"/></c>

      <c>frequency</c>
      <c>String</c>
      <c>RecurrenceRule</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>href</c>
      <c>String</c>
      <c>Link</c>
      <c><xref target="type-Link"/></c>

      <c>interval</c>
      <c>UnsignedInt</c>
      <c>RecurrenceRule</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>invitedBy</c>
      <c>String</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>keywords</c>
      <c>String[Boolean]</c>
      <c>JSEvent, JSTask, JSGroup</c>
      <c><xref target="prop-keywords"/></c>

      <c>kind</c>
      <c>String</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>language</c>
      <c>String</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>links</c>
      <c>Id[Link]</c>
      <c>JSGroup, JSEvent, JSTask, VirtualLocation</td>
                <td align="left">
                  <xref target="prop-description" format="default"/>, <xref target="prop-locations" format="default"/>, <xref target="prop-participants" format="default"/>, <xref target="prop-virtualLocations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">description&zwsp;ContentType</td>
                <td align="left">String</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-descriptionContentType" format="default"/></td>
              </tr>
              <tr>
                <td align="left">display</td>
                <td align="left">String</td>
                <td align="left">Link</td>
                <td align="left">
                  <xref target="type-Link" format="default"/></td>
              </tr>
              <tr>
                <td align="left">due</td>
                <td align="left">LocalDateTime</td>
                <td align="left">Task</td>
                <td align="left">
                  <xref target="prop-due" format="default"/></td>
              </tr>
              <tr>
                <td align="left">duration</td>
                <td align="left">Duration</td>
                <td align="left">Event</td>
                <td align="left">
                  <xref target="prop-duration" format="default"/></td>
              </tr>
              <tr>
                <td align="left">email</td>
                <td align="left">String</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">entries</td>
                <td align="left">(Task|Event)[]</td>
                <td align="left">Group</td>
                <td align="left">
                  <xref target="prop-entries" format="default"/></td>
              </tr>
              <tr>
                <td align="left">estimatedDuration</td>
                <td align="left">Duration</td>
                <td align="left">Task</td>
                <td align="left">
                  <xref target="prop-estimatedDuration" format="default"/></td>
              </tr>
              <tr>
                <td align="left">excluded</td>
                <td align="left">Boolean</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-excluded" format="default"/></td>
              </tr>
              <tr>
                <td align="left">excluded&zwsp;RecurrenceRules</td>
                <td align="left">RecurrenceRule[]</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-excludedRecurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">expectReply</td>
                <td align="left">Boolean</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">features</td>
                <td align="left">String[Boolean]</td>
                <td align="left">VirtualLocation</td>
                <td align="left">
                  <xref target="prop-virtualLocations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">firstDayOfWeek</td>
                <td align="left">String</td>
                <td align="left">RecurrenceRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">freeBusyStatus</td>
                <td align="left">String</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-freeBusyStatus" format="default"/></td>
              </tr>
              <tr>
                <td align="left">frequency</td>
                <td align="left">String</td>
                <td align="left">RecurrenceRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">href</td>
                <td align="left">String</td>
                <td align="left">Link</td>
                <td align="left">
                  <xref target="type-Link" format="default"/></td>
              </tr>
              <tr>
                <td align="left">interval</td>
                <td align="left">UnsignedInt</td>
                <td align="left">RecurrenceRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">invitedBy</td>
                <td align="left">Id</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">keywords</td>
                <td align="left">String[Boolean]</td>
                <td align="left">Event, Task, Group</td>
                <td align="left">
                  <xref target="prop-keywords" format="default"/></td>
              </tr>
              <tr>
                <td align="left">kind</td>
                <td align="left">String</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">language</td>
                <td align="left">String</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">links</td>
                <td align="left">Id[Link]</td>
                <td align="left">Group, Event, Task, Location, Participant</c>
      <c><xref target="prop-links"/>, <xref target="prop-locations"/>, <xref target="prop-participants"/></c>

      <c>locale</c>
      <c>String</c>
      <c>JSGroup, JSEvent, JSTask</c>
      <c><xref target="prop-locale"/></c>

      <c>localizations</c>
      <c>String[PatchObject]</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-localizations"/></c>

      <c>locationId</c>
      <c>String</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>locations</c>
      <c>Id[Location]</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-locations"/></c>

      <c>locationTypes</c>
      <c>String[Boolean]</c>
      <c>Location</c>
      <c><xref target="prop-locations"/></c>

      <c>memberOf</c>
      <c>String[Boolean]</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>method</c>
      <c>String</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-method"/></c>

      <c>name</c>
      <c>String</c>
      <c>Location, Participant</td>
                <td align="left">
                  <xref target="prop-links" format="default"/>, <xref target="prop-locations" format="default"/>, <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">locale</td>
                <td align="left">String</td>
                <td align="left">Group, Event, Task</td>
                <td align="left">
                  <xref target="prop-locale" format="default"/></td>
              </tr>
              <tr>
                <td align="left">localizations</td>
                <td align="left">String&zwsp;[PatchObject]</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-localizations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">locationId</td>
                <td align="left">Id</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">locations</td>
                <td align="left">Id[Location]</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-locations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">locationTypes</td>
                <td align="left">String[Boolean]</td>
                <td align="left">Location</td>
                <td align="left">
                  <xref target="prop-locations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">memberOf</td>
                <td align="left">Id[Boolean]</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">method</td>
                <td align="left">String</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-method" format="default"/></td>
              </tr>
              <tr>
                <td align="left">name</td>
                <td align="left">String</td>
                <td align="left">Location, VirtualLocation, Participant</c>
      <c><xref target="prop-locations"/>, <xref target="prop-virtualLocations"/>, <xref target="prop-participants"/></c>

      <c>names</c>
      <c>String[Boolean]</c>
      <c>TimeZoneRule</c>
      <c><xref target="prop-timeZones"/></c>

      <c>nthOfPeriod</c>
      <c>Int</c>
      <c>NDay</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>offset</c>
      <c>SignedDuration</c>
      <c>OffsetTrigger</c>
      <c><xref target="prop-alerts"/></c>

      <c>offsetFrom</c>
      <c>UTCDateTime</c>
      <c>TimeZoneRule</c>
      <c><xref target="prop-timeZones"/></c>

      <c>offsetTo</c>
      <c>UTCDateTime</c>
      <c>TimeZoneRule</c>
      <c><xref target="prop-timeZones"/></c>

      <c>participants</c>
      <c>Id[Participant]</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-participants"/></c>

      <c>participationComment</c>
      <c>String</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>participationStatus</c>
      <c>String</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>percentComplete</c>
      <c>UnsignedInt</c>
      <c>JSTask, Participant</c>
      <c><xref target="prop-percentComplete"/></c>

      <c>priority</c>
      <c>Int</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-priority"/></c>

      <c>privacy</c>
      <c>String</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-privacy"/></c>

      <c>prodId</c>
      <c>String</c>
      <c>JSEvent, JSTask, JSGroup</c>
      <c><xref target="prop-prodId"/></c>

      <c>progress</c>
      <c>String</c>
      <c>JSTask, Participant</c>
      <c><xref target="prop-progress"/></c>

      <c>progressUpdated</c>
      <c>UTCDateTime</c>
      <c>JSTask, Participant</c>
      <c><xref target="prop-progressUpdated"/></c>

      <c>recurrenceId</c>
      <c>LocalDateTime</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-recurrenceId"/></c>

      <c>recurrenceOverrides</c>
      <c>LocalDateTime[PatchObject]</c>
      <c>JSEvent, JSTask, TimeZoneRule</c>
      <c><xref target="prop-recurrenceOverrides"/>, <xref target="prop-timeZones"/></c>

      <c>recurrenceRules</c>
      <c>RecurrenceRule[]</c>
      <c>JSEvent, JSTask, TimeZoneRule</c>
      <c><xref target="prop-recurrenceRules"/>, <xref target="prop-timeZones"/></c>

      <c>rel</c>
      <c>String</c>
      <c>Link</c>
      <c><xref target="type-Link"/></c>

      <c>relatedTo</c>
      <c>String[Relation]</c>
      <c>JSEvent, JSTask, Alert</c>
      <c><xref target="prop-relatedTo"/>, <xref target="prop-alerts"/></c>

      <c>relation</c>
      <c>String[Boolean]</c>
      <c>Relation</c>
      <c><xref target="type-Relation"/></c>

      <c>relativeTo</c>
      <c>String</c>
      <c>OffsetTrigger, Location</c>
      <c><xref target="prop-alerts"/>, <xref target="prop-locations"/></c>

      <c>replyTo</c>
      <c>String[String]</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-replyTo"/></c>

      <c>roles</c>
      <c>String[Boolean]</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>rscale</c>
      <c>String</c>
      <c>RecurrenceRule</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>standard</c>
      <c>TimeZoneRule</c>
      <c>TimeZone</c>
      <c><xref target="prop-timeZones"/></c>

      <c>start</c>
      <c>LocalDateTime</c>
      <c>TimeZoneRule</c>
      <c><xref target="prop-timeZones"/></c>

      <c>scheduleAgent</c>
      <c>String</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>scheduleForceSend</c>
      <c>Boolean</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>scheduleSequence</c>
      <c>UnsignedInt</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>scheduleStatus</c>
      <c>String[]</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>scheduleUpdated</c>
      <c>UTCDateTime</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>sendTo</c>
      <c>String[String]</c>
      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>sequence</c>
      <c>UnsignedInt</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-sequence"/></c>

      <c>showWithoutTime</c>
      <c>Boolean</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-showWithoutTime"/></c>

      <c>size</c>
      <c>UnsignedInt</c>
      <c>Link</c>
      <c><xref target="type-Link"/></c>

      <c>skip</c>
      <c>String</c>
      <c>RecurrenceRule</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>source</c>
      <c>String</c>
      <c>JSGroup</c>
      <c><xref target="prop-source"/></c>

      <c>start</c>
      <c>LocalDateTime</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-start-jsevent"/>, <xref target="prop-start-jstask"/></c>

      <c>status</c>
      <c>String</c>
      <c>JSEvent</c>
      <c><xref target="prop-status-jsevent"/></c>

      <c>timeZone</c>
      <c>TimeZoneId|null</c>
      <c>JSEvent, JSTask, Location</c>
      <c><xref target="prop-timeZone"/>, <xref target="prop-locations"/></c>

      <c>timeZones</c>
      <c>TimeZoneId[TimeZone]</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-timeZones"/></c>

      <c>title</c>
      <c>String</c>
      <c>JSEvent, JSTask, JSGroup, Link</c>
      <c><xref target="prop-title"/></c>

      <c>trigger</c>
      <c>OffsetTrigger|AbsoluteTrigger|UnknownTrigger</c>
      <c>Alert</c>
      <c><xref target="prop-alerts"/></c>

      <c>tzId</c>
      <c>String</c>
      <c>TimeZone</c>
      <c><xref target="prop-timeZones"/></c>

      <c>uid</c>
      <c>String</c>
      <c>JSEvent, JSTask, JSGroup</c>
      <c><xref target="prop-uid"/></c>

      <c>until</c>
      <c>LocalDateTime</c>
      <c>RecurrenceRule</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>updated</c>
      <c>UTCDateTime</c>
      <c>JSEvent, JSTask, JSGroup</c>
      <c><xref target="prop-updated"/></c>

      <c>uri</c>
      <c>String</c>
      <c>VirtualLocation</c>
      <c><xref target="prop-virtualLocations"/></c>

      <c>url</c>
      <c>String</c>
      <c>TimeZone</c>
      <c><xref target="prop-timeZones"/></c>

      <c>useDefaultAlerts</c>
      <c>Boolean</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="useDefaultAlerts"/></c>

      <c>validUntil</c>
      <c>UTCDateTime</c>
      <c>TimeZone</c>
      <c><xref target="prop-timeZones"/></c>

      <c>virtualLocations</c>
      <c>Id[VirtualLocation]</c>
      <c>JSEvent, JSTask</c>
      <c><xref target="prop-virtualLocations"/></c>

      <c>when</c>
      <c>UTCDateTime</c>
      <c>AbsoluteTrigger</c>
      <c><xref target="prop-alerts"/></c>
    </texttable> Participant</td>
                <td align="left">
                  <xref target="prop-locations" format="default"/>, <xref target="prop-virtualLocations" format="default"/>, <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">names</td>
                <td align="left">String[Boolean]</td>
                <td align="left">TimeZoneRule</td>
                <td align="left">
                  <xref target="prop-timeZones" format="default"/></td>
              </tr>
              <tr>
                <td align="left">nthOfPeriod</td>
                <td align="left">Int</td>
                <td align="left">NDay</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">offset</td>
                <td align="left">SignedDuration</td>
                <td align="left">OffsetTrigger</td>
                <td align="left">
                  <xref target="prop-alerts" format="default"/></td>
              </tr>
              <tr>
                <td align="left">offsetFrom</td>
                <td align="left">UTCDateTime</td>
                <td align="left">TimeZoneRule</td>
                <td align="left">
                  <xref target="prop-timeZones" format="default"/></td>
              </tr>
              <tr>
                <td align="left">offsetTo</td>
                <td align="left">UTCDateTime</td>
                <td align="left">TimeZoneRule</td>
                <td align="left">
                  <xref target="prop-timeZones" format="default"/></td>
              </tr>
              <tr>
                <td align="left">participants</td>
                <td align="left">Id[Participant]</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">participation&zwsp;Comment</td>
                <td align="left">String</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">participationStatus</td>
                <td align="left">String</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">percentComplete</td>
                <td align="left">UnsignedInt</td>
                <td align="left">Task, Participant</td>
                <td align="left">
                  <xref target="prop-percentComplete" format="default"/></td>
              </tr>
              <tr>
                <td align="left">priority</td>
                <td align="left">Int</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-priority" format="default"/></td>
              </tr>
              <tr>
                <td align="left">privacy</td>
                <td align="left">String</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-privacy" format="default"/></td>
              </tr>
              <tr>
                <td align="left">prodId</td>
                <td align="left">String</td>
                <td align="left">Event, Task, Group</td>
                <td align="left">
                  <xref target="prop-prodId" format="default"/></td>
              </tr>
              <tr>
                <td align="left">progress</td>
                <td align="left">String</td>
                <td align="left">Task, Participant</td>
                <td align="left">
                  <xref target="prop-progress" format="default"/></td>
              </tr>
              <tr>
                <td align="left">progressUpdated</td>
                <td align="left">UTCDateTime</td>
                <td align="left">Task, Participant</td>
                <td align="left">
                  <xref target="prop-progressUpdated" format="default"/></td>
              </tr>
              <tr>
                <td align="left">recurrenceId</td>
                <td align="left">LocalDateTime</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-recurrenceId" format="default"/></td>
              </tr>
              <tr>
                <td align="left">recurrenceIdTimeZone</td>
                <td align="left">TimeZoneId|null</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-recurrenceIdTimeZone" format="default"/></td>
              </tr>
              <tr>
                <td align="left">recurrenceOverrides</td>
                <td align="left">LocalDateTime&zwsp;[PatchObject]</td>
                <td align="left">Event, Task, TimeZoneRule</td>
                <td align="left">
                  <xref target="prop-recurrenceOverrides" format="default"/>, <xref target="prop-timeZones" format="default"/></td>
              </tr>
              <tr>
                <td align="left">recurrenceRules</td>
                <td align="left">RecurrenceRule[]</td>
                <td align="left">Event, Task, TimeZoneRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/>, <xref target="prop-timeZones" format="default"/></td>
              </tr>
              <tr>
                <td align="left">rel</td>
                <td align="left">String</td>
                <td align="left">Link</td>
                <td align="left">
                  <xref target="type-Link" format="default"/></td>
              </tr>
              <tr>
                <td align="left">relatedTo</td>
                <td align="left">String[Relation]</td>
                <td align="left">Event, Task, Alert</td>
                <td align="left">
                  <xref target="prop-relatedTo" format="default"/>, <xref target="prop-alerts" format="default"/></td>
              </tr>
              <tr>
                <td align="left">relation</td>
                <td align="left">String[Boolean]</td>
                <td align="left">Relation</td>
                <td align="left">
                  <xref target="type-Relation" format="default"/></td>
              </tr>
              <tr>
                <td align="left">relativeTo</td>
                <td align="left">String</td>
                <td align="left">OffsetTrigger, Location</td>
                <td align="left">
                  <xref target="prop-alerts" format="default"/>, <xref target="prop-locations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">replyTo</td>
                <td align="left">String[String]</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-replyTo" format="default"/></td>
              </tr>
              <tr>
                <td align="left">requestStatus</td>
                <td align="left">String</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-requestStatus" format="default"/></td>
              </tr>
              <tr>
                <td align="left">roles</td>
                <td align="left">String[Boolean]</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">rscale</td>
                <td align="left">String</td>
                <td align="left">RecurrenceRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">sentBy</td>
                <td align="left">String</td>
                <td align="left">Event, Task, Participant</td>
                <td align="left">
                  <xref target="prop-sentBy" format="default"/>, <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">standard</td>
                <td align="left">TimeZoneRule[]</td>
                <td align="left">TimeZone</td>
                <td align="left">
                  <xref target="prop-timeZones" format="default"/></td>
              </tr>
              <tr>
                <td align="left">start</td>
                <td align="left">LocalDateTime</td>
                <td align="left">TimeZoneRule</td>
                <td align="left">
                  <xref target="prop-timeZones" format="default"/></td>
              </tr>
              <tr>
                <td align="left">scheduleAgent</td>
                <td align="left">String</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">scheduleForceSend</td>
                <td align="left">Boolean</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">scheduleSequence</td>
                <td align="left">UnsignedInt</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">scheduleStatus</td>
                <td align="left">String[]</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">scheduleUpdated</td>
                <td align="left">UTCDateTime</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">sendTo</td>
                <td align="left">String[String]</td>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">sequence</td>
                <td align="left">UnsignedInt</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-sequence" format="default"/></td>
              </tr>
              <tr>
                <td align="left">showWithoutTime</td>
                <td align="left">Boolean</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-showWithoutTime" format="default"/></td>
              </tr>
              <tr>
                <td align="left">size</td>
                <td align="left">UnsignedInt</td>
                <td align="left">Link</td>
                <td align="left">
                  <xref target="type-Link" format="default"/></td>
              </tr>
              <tr>
                <td align="left">skip</td>
                <td align="left">String</td>
                <td align="left">RecurrenceRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">source</td>
                <td align="left">String</td>
                <td align="left">Group</td>
                <td align="left">
                  <xref target="prop-source" format="default"/></td>
              </tr>
              <tr>
                <td align="left">start</td>
                <td align="left">LocalDateTime</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-start-jsevent" format="default"/>, <xref target="prop-start-jstask" format="default"/></td>
              </tr>
              <tr>
                <td align="left">status</td>
                <td align="left">String</td>
                <td align="left">Event</td>
                <td align="left">
                  <xref target="prop-status-jsevent" format="default"/></td>
              </tr>
              <tr>
                <td align="left">timeZone</td>
                <td align="left">TimeZoneId|null</td>
                <td align="left">Event, Task, Location</td>
                <td align="left">
                  <xref target="prop-timeZone" format="default"/>, <xref target="prop-locations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">timeZones</td>
                <td align="left">TimeZoneId&zwsp;[TimeZone]</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-timeZones" format="default"/></td>
              </tr>
              <tr>
                <td align="left">title</td>
                <td align="left">String</td>
                <td align="left">Event, Task, Group, Link</td>
                <td align="left">
                  <xref target="prop-title" format="default"/></td>
              </tr>
              <tr>
                <td align="left">trigger</td>
                <td align="left">OffsetTrigger|&zwsp;AbsoluteTrigger|&zwsp;UnknownTrigger</td>
                <td align="left">Alert</td>
                <td align="left">
                  <xref target="prop-alerts" format="default"/></td>
              </tr>
              <tr>
                <td align="left">tzId</td>
                <td align="left">String</td>
                <td align="left">TimeZone</td>
                <td align="left">
                  <xref target="prop-timeZones" format="default"/></td>
              </tr>
              <tr>
                <td align="left">uid</td>
                <td align="left">String</td>
                <td align="left">Event, Task, Group</td>
                <td align="left">
                  <xref target="prop-uid" format="default"/></td>
              </tr>
              <tr>
                <td align="left">until</td>
                <td align="left">LocalDateTime</td>
                <td align="left">RecurrenceRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">updated</td>
                <td align="left">UTCDateTime</td>
                <td align="left">Event, Task, Group</td>
                <td align="left">
                  <xref target="prop-updated" format="default"/></td>
              </tr>
              <tr>
                <td align="left">uri</td>
                <td align="left">String</td>
                <td align="left">VirtualLocation</td>
                <td align="left">
                  <xref target="prop-virtualLocations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">url</td>
                <td align="left">String</td>
                <td align="left">TimeZone</td>
                <td align="left">
                  <xref target="prop-timeZones" format="default"/></td>
              </tr>
              <tr>
                <td align="left">useDefaultAlerts</td>
                <td align="left">Boolean</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="useDefaultAlerts" format="default"/></td>
              </tr>
              <tr>
                <td align="left">validUntil</td>
                <td align="left">UTCDateTime</td>
                <td align="left">TimeZone</td>
                <td align="left">
                  <xref target="prop-timeZones" format="default"/></td>
              </tr>
              <tr>
                <td align="left">virtualLocations</td>
                <td align="left">Id&zwsp;[VirtualLocation]</td>
                <td align="left">Event, Task</td>
                <td align="left">
                  <xref target="prop-virtualLocations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">when</td>
                <td align="left">UTCDateTime</td>
                <td align="left">AbsoluteTrigger</td>
                <td align="left">
                  <xref target="prop-alerts" format="default"/></td>
              </tr>
            </tbody>
          </table>
        </section>
      </section>
      <section anchor="iana-type-registry" title='Creation numbered="true" toc="default">
        <name>Creation of "JSCalendar Types" Registry'>
  <t>The IANA will create the &quot;JSCalendar Types&quot; Registry</name>
        <t>IANA has created the "JSCalendar Types" registry to avoid name collisions and provide a complete reference for all data types used for JSCalendar property values. The registration process is the same as for the JSCalendar Properties "JSCalendar Properties" registry, as defined in <xref target="iana-property-registry"/>.</t> target="iana-property-registry" format="default"/>.</t>
        <section anchor="iana-type-registry-template" title="JSCalendar Types numbered="true" toc="default">
          <name>&quot;JSCalendar Types&quot; Registry Template">
    <t><list style="symbols">
      <t>Type Name: The Template</name>
          <dl newline="false">
            <dt>Type Name:</dt>
	        <dd>the name of the type.</t>
      <t>Reference type</dd>
            <dt>Reference or Description: A Description:</dt>
	        <dd>a brief description or RFC number and section reference where the Type is specified (may be omitted for "reserved" type names).</t>
      <t>Intended Use: Common, names)</dd>
            <dt>Intended Use:</dt>
	        <dd>common, reserved, or obsolete.</t>
      <t>Change Controller: Who obsolete</dd>
            <dt>Change Controller:</dt>
	        <dd>who may request a change to this entry's definition (<spanx style="verb">IETF</spanx> (<tt>IETF</tt> for IETF-stream RFCs).</t>
  </list></t> RFCs from the IETF stream)</dd>
          </dl>
        </section>
        <section anchor="iana-type-registry-contents" title="Initial numbered="true" toc="default">
          <name>Initial Contents for the JSCalendar Types Registry"> &quot;JSCalendar Types&quot; Registry</name>
          <t>The following table lists the initial entries of the JSCalendar Types registry. All properties are for common-use. common use. All RFC section references are for this document. The change controller for all these properties is "IETF".</t>

    <texttable anchor="table-iana-type-registry">
      <ttcol align='left'>Type Name</ttcol>
      <ttcol align='left'>Reference or Description</ttcol>

      <c>Alert</c>
      <c><xref target="prop-alerts"/></c>

      <c>Boolean</c>
      <c><xref target="type-signatures"/></c>

      <c>Duration</c>
      <c><xref target="type-Duration"/></c>

      <c>Id</c>
      <c><xref target="type-Id"/></c>

      <c>Int</c>
      <c><xref target="type-Int"/></c>

      <c>LocalDateTime</c>
      <c><xref target="type-LocalDateTime"/></c>

      <c>Link</c>
      <c><xref target="type-Link"/></c>

      <c>Location</c>
      <c><xref target="prop-locations"/></c>

      <c>NDay</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>Number</c>
      <c><xref target="type-signatures"/></c>

      <c>Participant</c>
      <c><xref target="prop-participants"/></c>

      <c>PatchObject</c>
      <c><xref target="type-PatchObject"/></c>

      <c>RecurrenceRule</c>
      <c><xref target="prop-recurrenceRules"/></c>

      <c>Relation</c>
      <c><xref target="type-Relation"/></c>

      <c>SignedDuration</c>
      <c><xref target="type-SignedDuration"/></c>

      <c>String</c>
      <c><xref target="type-signatures"/></c>

      <c>TimeZone</c>
      <c><xref target="prop-timeZones"/></c>

      <c>TimeZoneId</c>
      <c><xref target="type-timeZoneId"/></c>

      <c>TimeZoneRule</c>
      <c><xref target="prop-timeZones"/></c>

      <c>UnsignedInt</c>
      <c><xref target="type-UnsignedInt"/></c>

      <c>UTCDateTime</c>
      <c><xref target="type-UTCDateTime"/></c>

      <c>VirtualLocation</c>
      <c><xref target="prop-virtualLocations"/></c>
    </texttable>
          <table anchor="tab-iana-type-registry" align="left">
	        <name>Initial Contents of the &quot;JSCalendar Types&quot; Registry</name>
            <thead>
              <tr>
                <th align="left">Type Name</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">Alert</td>
                <td align="left">
                  <xref target="prop-alerts" format="default"/></td>
              </tr>
              <tr>
                <td align="left">Boolean</td>
                <td align="left">
                  <xref target="type-signatures" format="default"/></td>
              </tr>
              <tr>
                <td align="left">Duration</td>
                <td align="left">
                  <xref target="type-Duration" format="default"/></td>
              </tr>
              <tr>
                <td align="left">Id</td>
                <td align="left">
                  <xref target="type-Id" format="default"/></td>
              </tr>
              <tr>
                <td align="left">Int</td>
                <td align="left">
                  <xref target="type-Int" format="default"/></td>
              </tr>
              <tr>
                <td align="left">LocalDateTime</td>
                <td align="left">
                  <xref target="type-LocalDateTime" format="default"/></td>
              </tr>
              <tr>
                <td align="left">Link</td>
                <td align="left">
                  <xref target="type-Link" format="default"/></td>
              </tr>
              <tr>
                <td align="left">Location</td>
                <td align="left">
                  <xref target="prop-locations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">NDay</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">Number</td>
                <td align="left">
                  <xref target="type-signatures" format="default"/></td>
              </tr>
              <tr>
                <td align="left">Participant</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">PatchObject</td>
                <td align="left">
                  <xref target="type-PatchObject" format="default"/></td>
              </tr>
              <tr>
                <td align="left">RecurrenceRule</td>
                <td align="left">
                  <xref target="prop-recurrenceRules" format="default"/></td>
              </tr>
              <tr>
                <td align="left">Relation</td>
                <td align="left">
                  <xref target="type-Relation" format="default"/></td>
              </tr>
              <tr>
                <td align="left">SignedDuration</td>
                <td align="left">
                  <xref target="type-SignedDuration" format="default"/></td>
              </tr>
              <tr>
                <td align="left">String</td>
                <td align="left">
                  <xref target="type-signatures" format="default"/></td>
              </tr>
              <tr>
                <td align="left">TimeZone</td>
                <td align="left">
                  <xref target="prop-timeZones" format="default"/></td>
              </tr>
              <tr>
                <td align="left">TimeZoneId</td>
                <td align="left">
                  <xref target="type-timeZoneId" format="default"/></td>
              </tr>
              <tr>
                <td align="left">TimeZoneRule</td>
                <td align="left">
                  <xref target="prop-timeZones" format="default"/></td>
              </tr>
              <tr>
                <td align="left">UnsignedInt</td>
                <td align="left">
                  <xref target="type-UnsignedInt" format="default"/></td>
              </tr>
              <tr>
                <td align="left">UTCDateTime</td>
                <td align="left">
                  <xref target="type-UTCDateTime" format="default"/></td>
              </tr>
              <tr>
                <td align="left">VirtualLocation</td>
                <td align="left">
                  <xref target="prop-virtualLocations" format="default"/></td>
              </tr>
            </tbody>
          </table>
        </section>
      </section>
      <section anchor="iana-enum-registry" title='Creation numbered="true" toc="default">
        <name>Creation of the "JSCalendar Enum Values" Registry'>
  <t>The IANA will create Registry</name>
        <t>IANA has created the "JSCalendar Enum Values" registry to allow interoperable extension of semantics for properties with enumerable values. Each such property will have a subregistry of allowed values. The registration process for a new enum value or adding a new enumerable property is the same as for the JSCalendar Properties &quot;JSCalendar Properties&quot; registry, as defined in <xref target="iana-property-registry"/>.</t> target="iana-property-registry" format="default"/>.</t>
        <section anchor="iana-enum-registry-registry-template" title="JSCalendar numbered="true" toc="default">
          <name>&quot;JSCalendar Enum Values&quot; Registry Property Template"> Template</name>
          <t>This template is for adding a subregistry for a new enumerable property to the JSCalendar Enum &quot;JSCalendar Enum&quot; registry.</t>

    <t><list style="symbols">
      <t>Property Name:
          <dl newline="false">
            <dt>Property Name:</dt>
	        <dd>These are the name(s) of the property or properties where these values may be used. This MUST <bcp14>MUST</bcp14> be registered in the JSCalendar Properties registry.</t>
      <t>Context: &quot;JSCalendar Properties&quot; registry.</dd>
            <dt>Context:</dt>
	        <dd>This is the list of allowed object types where the property or properties may appear, as registered in the JSCalendar Properties &quot;JSCalendar Properties&quot; registry. This disambiguates where there may be two distinct properties with the same name in different contexts.</t>
      <t>Change Controller: (<spanx style="verb">IETF</spanx> contexts.</dd>
            <dt>Change Controller:</dt>
	        <dd> (<tt>IETF</tt> for properties defined in IETF-stream RFCs).</t>
      <t>Initial Contents: The RFCs from the IETF stream).</dd>
            <dt>Initial Contents:</dt>
	        <dd>This is the initial list of defined values for this enum, using the template defined in <xref target="iana-enum-registry-value-template"/>. target="iana-enum-registry-value-template" format="default"/>. A subregistry will be created with these values for this property name/context tuple.</t>
    </list></t> tuple.</dd>
          </dl>
        </section>
        <section anchor="iana-enum-registry-value-template" title="JSCalendar numbered="true" toc="default">
          <name>&quot;JSCalendar Enum Values&quot; Registry Value Template"> Template</name>
          <t>This template is for adding a new enum value to a subregistry in the JSCalendar Enum registry.</t>

    <t><list style="symbols">
      <t>Enum Value: The
          <dl newline="false">
            <dt>Enum Value:</dt>
	        <dd>the verbatim value of the enum.</t>
      <t>Reference enum</dd>
            <dt>Reference or Description: A Description:</dt>
	        <dd>a brief description or RFC number and section reference for the semantics of this value.</t>
    </list></t> value</dd>
          </dl>
        </section>
        <section anchor="iana-enum-registry-contents" title="Initial numbered="true" toc="default">
          <name>Initial Contents for the JSCalendar &quot;JSCalendar Enum Values registry"> Values&quot; Registry</name>
          <t>For each subregistry created in this section, all RFC section references are for this document.</t>

    <t>------------------------------------------------------------</t>

    <t>Property Name: action</t>
    <t>Context: Alert</t>
    <t>Change Controller: IETF</t>
    <t>Initial Contents:</t>

    <texttable anchor="table-iana-enum-alert-action">
      <ttcol align='left'>Enum Value</ttcol>
      <ttcol align='left'>Reference or Description</ttcol>
      <c>display</c>
      <c><xref target="prop-alerts"/></c>
      <c>email</c>
      <c><xref target="prop-alerts"/></c>
    </texttable>

    <t>------------------------------------------------------------</t>

    <t>Property Name: display</t>
    <t>Context: Link</t>
    <t>Change Controller: IETF</t>
    <t>Initial Contents:</t>

    <texttable anchor="table-iana-enum-link-display">
      <ttcol align='left'>Enum Value</ttcol>
      <ttcol align='left'>Reference or Description</ttcol>
      <c>badge</c>
      <c><xref target="type-Link"/></c>
      <c>graphic</c>
      <c><xref target="type-Link"/></c>
      <c>fullsize</c>
      <c><xref target="type-Link"/></c>
      <c>thumbnail</c>
      <c><xref target="type-Link"/></c>
    </texttable>

    <t>------------------------------------------------------------</t>

    <t>Property Name: freeBusyStatus</t>
    <t>Context: JSEvent, JSTask</t>
    <t>Change Controller: IETF</t>
    <t>Initial Contents:</t>

    <texttable anchor="table-iana-enum-freeBusyStatus">
      <ttcol align='left'>Enum Value</ttcol>
      <ttcol align='left'>Reference or Description</ttcol>
      <c>free</c>
      <c><xref target="prop-freeBusyStatus"/></c>
      <c>busy</c>
      <c><xref target="prop-freeBusyStatus"/></c>
    </texttable>

    <t>------------------------------------------------------------</t>

    <t>Property Name: kind</t>
    <t>Context: Participant</t>
    <t>Change Controller: IETF</t>
    <t>Initial Contents:</t>

    <texttable anchor="table-iana-enum-participant-kind">
      <ttcol align='left'>Enum Value</ttcol>
      <ttcol align='left'>Reference or Description</ttcol>
      <c>individual</c>
      <c><xref target="prop-participants"/></c>
      <c>group</c>
      <c><xref target="prop-participants"/></c>
      <c>resource</c>
      <c><xref target="prop-participants"/></c>
      <c>location</c>
      <c><xref target="prop-participants"/></c>
    </texttable>

    <t>------------------------------------------------------------</t>

    <t>Property Name: participationStatus</t>
    <t>Context: Participant</t>
    <t>Change Controller: IETF</t>
    <t>Initial Contents:</t>

    <texttable anchor="table-iana-enum-participationStatus">
      <ttcol align='left'>Enum Value</ttcol>
      <ttcol align='left'>Reference or Description</ttcol>
      <c>needs-action</c>
      <c><xref target="prop-participants"/></c>
      <c>accepted</c>
      <c><xref target="prop-participants"/></c>
      <c>declined</c>
      <c><xref target="prop-participants"/></c>
      <c>tenative</c>
      <c><xref target="prop-participants"/></c>
      <c>delegated</c>
      <c><xref target="prop-participants"/></c>
    </texttable>

    <t>------------------------------------------------------------</t>

    <t>Property Name: privacy</t>
    <t>Context: JSEvent, JSTask</t>
    <t>Change Controller: IETF</t>
    <t>Initial Contents:</t>

    <texttable anchor="table-iana-enum-privacy">
      <ttcol align='left'>Enum Value</ttcol>
      <ttcol align='left'>Reference or Description</ttcol>
      <c>public</c>
      <c><xref target="prop-privacy"/></c>
      <c>private</c>
      <c><xref target="prop-privacy"/></c>
      <c>secret</c>
      <c><xref target="prop-privacy"/></c>
    </texttable>

    <t>------------------------------------------------------------</t>

    <t>Property Name: progress</t>
    <t>Context: JSTask, Participant</t>
    <t>Change Controller: IETF</t>
    <t>Initial Contents:</t>

    <texttable anchor="table-iana-enum-status-jstask">
      <ttcol align='left'>Enum Value</ttcol>
      <ttcol align='left'>Reference or Description</ttcol>
      <c>needs-action</c>
      <c><xref target="prop-progress"/></c>
      <c>in-process</c>
      <c><xref target="prop-progress"/></c>
      <c>completed</c>
      <c><xref target="prop-progress"/></c>
      <c>failed</c>
      <c><xref target="prop-progress"/></c>
      <c>cancelled</c>
      <c><xref target="prop-progress"/></c>
    </texttable>

    <t>------------------------------------------------------------</t>

    <t>Property Name: relation</t>
    <t>Context: Relation</t>
    <t>Change Controller: IETF</t>
    <t>Initial Contents:</t>

    <texttable anchor="table-iana-enum-relation">
      <ttcol align='left'>Enum Value</ttcol>
      <ttcol align='left'>Reference or Description</ttcol>
      <c>first</c>
      <c><xref target="type-Relation"/></c>
      <c>next</c>
      <c><xref target="type-Relation"/></c>
      <c>child</c>
      <c><xref target="type-Relation"/></c>
      <c>parent</c>
      <c><xref target="type-Relation"/></c>
    </texttable>

    <t>------------------------------------------------------------</t>

    <t>Property Name: relativeTo</t>
    <t>Context:
<dl spacing="compact" newline="false" indent="20">
          <dt>Property Name:</dt><dd>action</dd>
          <dt>Context:</dt><dd>Alert</dd>
          <dt>Change Controller:</dt><dd>IETF</dd>
          <dt>Initial Contents:</dt><dd>
          <table anchor="tab-iana-enum-alert-action" align="left">
	        <name>JSCalendar Enum Values for action (Context: Alert)</name>
            <thead>
              <tr>
                <th align="left">Enum Value</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">display</td>
                <td align="left">
                  <xref target="prop-alerts" format="default"/></td>
              </tr>
              <tr>
                <td align="left">email</td>
                <td align="left">
                  <xref target="prop-alerts" format="default"/></td>
              </tr>
            </tbody>
          </table></dd>
</dl>

<dl spacing="compact" newline="false" indent="20">
          <dt>Property Name:</dt><dd>display</dd>
          <dt>Context:</dt><dd>Link</dd>
          <dt>Change Controller:</dt><dd>IETF</dd>
          <dt>Initial Contents:</dt><dd>
          <table anchor="tab-iana-enum-link-display" align="left">
	        <name>JSCalendar Enum Values for display (Context: Link)</name>
            <thead>
              <tr>
                <th align="left">Enum Value</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">badge</td>
                <td align="left">
                  <xref target="type-Link" format="default"/></td>
              </tr>
              <tr>
                <td align="left">graphic</td>
                <td align="left">
                  <xref target="type-Link" format="default"/></td>
              </tr>
              <tr>
                <td align="left">fullsize</td>
                <td align="left">
                  <xref target="type-Link" format="default"/></td>
              </tr>
              <tr>
                <td align="left">thumbnail</td>
                <td align="left">
                  <xref target="type-Link" format="default"/></td>
              </tr>
            </tbody>
          </table></dd>
</dl>
<dl spacing="compact" newline="false" indent="20">
          <dt>Property Name:</dt><dd>features</dd>
          <dt>Context:</dt><dd>VirtualLocation</dd>
          <dt>Change Controller:</dt><dd>IETF</dd>
          <dt>Initial Contents:</dt><dd>
          <table anchor="tab-iana-enum-virtualLocation-features" align="left">
      <name>JSCalendar Enum Values for features (Context: VirtualLocation)</name>
            <thead>
              <tr>
                <th align="left">Enum Value</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">audio</td>
                <td align="left">
                  <xref target="prop-virtualLocations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">chat</td>
                <td align="left">
                  <xref target="prop-virtualLocations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">feed</td>
                <td align="left">
                  <xref target="prop-virtualLocations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">moderator</td>
                <td align="left">
                  <xref target="prop-virtualLocations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">phone</td>
                <td align="left">
                  <xref target="prop-virtualLocations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">screen</td>
                <td align="left">
                  <xref target="prop-virtualLocations" format="default"/></td>
              </tr>
              <tr>
                <td align="left">video</td>
                <td align="left">
                  <xref target="prop-virtualLocations" format="default"/></td>
              </tr>
            </tbody>
          </table></dd>
</dl>
<dl spacing="compact" newline="false" indent="20">
          <dt>Property Name:</dt><dd>freeBusyStatus</dd>
          <dt>Context:</dt><dd>Event, Task</dd>
          <dt>Change Controller:</dt><dd>IETF</dd>
          <dt>Initial Contents:</dt><dd>
          <table anchor="tab-iana-enum-freeBusyStatus" align="left">
	        <name>JSCalendar Enum Values for freeBusyStatus (Context: Event, Task)</name>
            <thead>
              <tr>
                <th align="left">Enum Value</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">free</td>
                <td align="left">
                  <xref target="prop-freeBusyStatus" format="default"/></td>
              </tr>
              <tr>
                <td align="left">busy</td>
                <td align="left">
                  <xref target="prop-freeBusyStatus" format="default"/></td>
              </tr>
            </tbody>
          </table></dd>
</dl>
<dl spacing="compact" newline="false" indent="20">
          <dt>Property Name:</dt><dd>kind</dd>
          <dt>Context:</dt><dd>Participant</dd>
          <dt>Change Controller:</dt><dd>IETF</dd>
          <dt>Initial Contents:</dt><dd>
          <table anchor="tab-iana-enum-participant-kind" align="left">
	        <name>JSCalendar Enum Values for kind (Context: Participant)</name>
            <thead>
              <tr>
                <th align="left">Enum Value</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">individual</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">group</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">resource</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">location</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
            </tbody>
          </table></dd>
</dl>
<dl spacing="compact" newline="false" indent="20">
          <dt>Property Name:</dt><dd>participationStatus</dd>
          <dt>Context:</dt><dd>Participant</dd>
          <dt>Change Controller:</dt><dd>IETF</dd>
          <dt>Initial Contents:</dt><dd>
          <table anchor="tab-iana-enum-participationStatus" align="left">
	        <name>JSCalendar Enum Values for participationStatus (Context: Participant)</name>
            <thead>
              <tr>
                <th align="left">Enum Value</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">needs-action</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">accepted</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">declined</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">tentative</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">delegated</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
            </tbody>
          </table></dd>
</dl>
<dl spacing="compact" newline="false" indent="20">
          <dt>Property Name:</dt><dd>privacy</dd>
          <dt>Context:</dt><dd>Event, Task</dd>
          <dt>Change Controller:</dt><dd>IETF</dd>
          <dt>Initial Contents:</dt><dd>
          <table anchor="tab-iana-enum-privacy" align="left">
	        <name>JSCalendar Enum Values for privacy (Context: Event, Task)</name>
            <thead>
              <tr>
                <th align="left">Enum Value</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">public</td>
                <td align="left">
                  <xref target="prop-privacy" format="default"/></td>
              </tr>
              <tr>
                <td align="left">private</td>
                <td align="left">
                  <xref target="prop-privacy" format="default"/></td>
              </tr>
              <tr>
                <td align="left">secret</td>
                <td align="left">
                  <xref target="prop-privacy" format="default"/></td>
              </tr>
            </tbody>
          </table></dd>
</dl>
<dl spacing="compact" newline="false" indent="20">
          <dt>Property Name:</dt><dd>progress</dd>
          <dt>Context:</dt><dd>Task, Participant</dd>
          <dt>Change Controller:</dt><dd>IETF</dd>
          <dt>Initial Contents:</dt><dd>
          <table anchor="tab-iana-enum-status-jstask" align="left">
	        <name>JSCalendar Enum Values for progress (Context: Task, Participant)</name>
            <thead>
              <tr>
                <th align="left">Enum Value</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">needs-action</td>
                <td align="left">
                  <xref target="prop-progress" format="default"/></td>
              </tr>
              <tr>
                <td align="left">in-process</td>
                <td align="left">
                  <xref target="prop-progress" format="default"/></td>
              </tr>
              <tr>
                <td align="left">completed</td>
                <td align="left">
                  <xref target="prop-progress" format="default"/></td>
              </tr>
              <tr>
                <td align="left">failed</td>
                <td align="left">
                  <xref target="prop-progress" format="default"/></td>
              </tr>
              <tr>
                <td align="left">cancelled</td>
                <td align="left">
                  <xref target="prop-progress" format="default"/></td>
              </tr>
            </tbody>
          </table></dd>
</dl>
<dl spacing="compact" newline="false" indent="20">
          <dt>Property Name:</dt><dd>relation</dd>
          <dt>Context:</dt><dd>Relation</dd>
          <dt>Change Controller:</dt><dd>IETF</dd>
          <dt>Initial Contents:</dt><dd>
          <table anchor="tab-iana-enum-relation" align="left">
	        <name>JSCalendar Enum Values for relation (Context: Relation)</name>
            <thead>
              <tr>
                <th align="left">Enum Value</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">first</td>
                <td align="left">
                  <xref target="type-Relation" format="default"/></td>
              </tr>
              <tr>
                <td align="left">next</td>
                <td align="left">
                  <xref target="type-Relation" format="default"/></td>
              </tr>
              <tr>
                <td align="left">child</td>
                <td align="left">
                  <xref target="type-Relation" format="default"/></td>
              </tr>
              <tr>
                <td align="left">parent</td>
                <td align="left">
                  <xref target="type-Relation" format="default"/></td>
              </tr>
            </tbody>
          </table></dd>
</dl>
<dl spacing="compact" newline="false" indent="20">
          <dt>Property Name:</dt><dd>relativeTo</dd>
          <dt>Context:</dt><dd>OffsetTrigger, Location</dd>
          <dt>Change Controller:</dt><dd>IETF</dd>
          <dt>Initial Contents:</dt><dd>
          <table anchor="tab-iana-enum-offsetTrigger-relativeTo" align="left">
	        <name>JSCalendar Enum Values for relativeTo (Context: OffsetTrigger, Location</t>
    <t>Change Controller: IETF</t>
    <t>Initial Contents:</t>

    <texttable anchor="table-iana-enum-offsetTrigger-relativeTo">
      <ttcol align='left'>Enum Value</ttcol>
      <ttcol align='left'>Reference or Description</ttcol>
      <c>start</c>
      <c><xref target="prop-alerts"/></c>
      <c>end</c>
      <c><xref target="prop-alerts"/></c>
    </texttable>

    <t>------------------------------------------------------------</t>

    <t>Property Name: roles</t>
    <t>Context: Participant</t>
    <t>Change Controller: IETF</t>
    <t>Initial Contents:</t>

    <texttable anchor="table-iana-enum-participant-role">
      <ttcol align='left'>Enum Value</ttcol>
      <ttcol align='left'>Reference or Description</ttcol>
      <c>owner</c>
      <c><xref target="prop-participants"/></c>
      <c>attendee</c>
      <c><xref target="prop-participants"/></c>
      <c>optional</c>
      <c><xref target="prop-participants"/></c>
      <c>informational</c>
      <c><xref target="prop-participants"/></c>
      <c>chair</c>
      <c><xref target="prop-participants"/></c>
      <c>contact</c>
      <c><xref target="prop-participants"/></c>
    </texttable>

    <t>------------------------------------------------------------</t>

    <t>Property Name: scheduleAgent</t>
    <t>Context: Participant</t>
    <t>Change Controller: IETF</t>
    <t>Initial Contents:</t>

    <texttable anchor="table-iana-enum-participant-scheduleagent">
      <ttcol align='left'>Enum Value</ttcol>
      <ttcol align='left'>Reference or Description</ttcol>
      <c>server</c>
      <c><xref target="prop-participants"/></c>
      <c>client</c>
      <c><xref target="prop-participants"/></c>
      <c>none</c>
      <c><xref target="prop-participants"/></c>
    </texttable>

    <t>------------------------------------------------------------</t>

    <t>Property Name: status</t>
    <t>Context: JSEvent</t>
    <t>Change Controller: IETF</t>
    <t>Initial Contents:</t>

    <texttable anchor="table-iana-enum-status-jsevent">
      <ttcol align='left'>Enum Value</ttcol>
      <ttcol align='left'>Reference or Description</ttcol>
      <c>confirmed</c>
      <c><xref target="prop-status-jsevent"/></c>
      <c>cancelled</c>
      <c><xref target="prop-status-jsevent"/></c>
      <c>tentative</c>
      <c><xref target="prop-status-jsevent"/></c>
    </texttable>

  </section> Location)</name>
            <thead>
              <tr>
                <th align="left">Enum Value</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">start</td>
                <td align="left">
                  <xref target="prop-alerts" format="default"/></td>
              </tr>
              <tr>
                <td align="left">end</td>
                <td align="left">
                  <xref target="prop-alerts" format="default"/></td>
              </tr>
            </tbody>
          </table></dd>
</dl>
<dl spacing="compact" newline="false" indent="20">
          <dt>Property Name:</dt><dd>roles</dd>
          <dt>Context:</dt><dd>Participant</dd>
          <dt>Change Controller:</dt><dd>IETF</dd>
          <dt>Initial Contents:</dt><dd>
          <table anchor="tab-iana-enum-participant-role" align="left">
	        <name>JSCalendar Enum Values for roles (Context: Participant)</name>
            <thead>
              <tr>
                <th align="left">Enum Value</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">owner</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">attendee</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">optional</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">informational</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">chair</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">contact</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
            </tbody>
          </table></dd>
</dl>
<dl spacing="compact" newline="false" indent="20">
          <dt>Property Name:</dt><dd>scheduleAgent</dd>
          <dt>Context:</dt><dd>Participant</dd>
          <dt>Change Controller:</dt><dd>IETF</dd>
          <dt>Initial Contents:</dt><dd>
          <table anchor="tab-iana-enum-participant-scheduleagent" align="left">
	        <name>JSCalendar Enum Values for scheduleAgent (Context: Participant)</name>
            <thead>
              <tr>
                <th align="left">Enum Value</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">server</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">client</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
              <tr>
                <td align="left">none</td>
                <td align="left">
                  <xref target="prop-participants" format="default"/></td>
              </tr>
            </tbody>
          </table></dd>
</dl>
<dl spacing="compact" newline="false" indent="20">
          <dt>Property Name:</dt><dd>status</dd>
          <dt>Context:</dt><dd>Event</dd>
          <dt>Change Controller:</dt><dd>IETF</dd>
          <dt>Initial Contents:</dt><dd>
          <table anchor="tab-iana-enum-status-jsevent" align="left">
	        <name>JSCalendar Enum Values for status (Context: Event)</name>
            <thead>
              <tr>
                <th align="left">Enum Value</th>
                <th align="left">Reference or Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">confirmed</td>
                <td align="left">
                  <xref target="prop-status-jsevent" format="default"/></td>
              </tr>
              <tr>
                <td align="left">cancelled</td>
                <td align="left">
                  <xref target="prop-status-jsevent" format="default"/></td>
              </tr>
              <tr>
                <td align="left">tentative</td>
                <td align="left">
                  <xref target="prop-status-jsevent" format="default"/></td>
              </tr>
            </tbody>
          </table></dd>
</dl>
</section>
</section>

    <section anchor="acknowledgments" title="Acknowledgments">
      <t>The authors would like to thank the members of CalConnect for their valuable contributions. This specification originated from the work of the API technical committee of CalConnect, the Calendaring and Scheduling Consortium.</t>
</section>
</middle>
  <back>
    <references title="Normative References">
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2392.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2397.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3339.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4122.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4589.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4648.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5545.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5546.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5646.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5870.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6047.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6838.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6901.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7493.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7529.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7808.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8259.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8288.xml"?>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2392.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2397.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3339.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4122.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4589.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4648.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5322.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5545.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5546.xml"/>

<referencegroup anchor="BCP47" target="https://www.rfc-editor.org/info/bcp47">
  <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5646.xml"/>
</referencegroup>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5870.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6047.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6838.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6901.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7493.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7529.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7808.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8259.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8288.xml"/>

        <reference anchor="CLDR" target="http://cldr.unicode.org/">
          <front>
            <title>Unicode Common Locale Data Repository</title>
          <author />
          <date />
            <author/>
            <date/>
          </front>
        </reference>

        <reference anchor="TZDB" target="https://www.iana.org/time-zones">
          <front>
          <title>IANA Time
            <title>Time Zone Database</title>
          <author />
          <date />
            <author><organization>IANA</organization></author>
            <date/>
          </front>
        </reference>

        <reference anchor="COLORS" target="https://www.w3.org/TR/css-color-3/">
          <front>
            <title>CSS Color Module</title> Module Level 3</title>
<author initials='T' surname='Çelik' fullname='Tantek Çelik'>
    <organization />
          <date
</author>
<author initials='C' surname='Lilley' fullname='Chris Lilley'>
    <organization />
</author>
<author initials='L' surname='Baron' fullname='L. David Baron'>
    <organization />
</author>
            <date month="June" year="2018"/>
          </front>
	    <refcontent>W3C Recommendation</refcontent>
        </reference>
      </references>
    <references title="Informative References">
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6376.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7265.xml"?>
      <?rfc include="http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7986.xml"?>
      <references>
        <name>Informative References</name>

   <reference anchor="ISO.9070.1991" target="https://www.iso.org/standard/16645.html">
     <front>
       <title>Information technology -- SGML support facilities -- Registration
       procedures for public text owner identifiers</title>
       <author>
         <organization>ISO/IEC</organization>
       </author>

       <date month="April" year="1991"/>
     </front>
     <seriesInfo name="ISO/IEC" value="9070:1991"/>
     <seriesInfo name="Edition" value="2"/>
   </reference>

        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6376.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7265.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7986.xml"/>

        <reference anchor="LOCATIONTYPES" target="https://www.iana.org/assignments/location-type-registry/location-type-registry.xhtml"> target="https://www.iana.org/assignments/location-type-registry">
          <front>
          <title>IANA Location
            <title>Location Types Registry</title>
          <author />
          <date />
            <author><organization>IANA</organization></author>
          </front>
        </reference>

        <reference anchor="LINKRELS" target="https://www.iana.org/assignments/link-relations/link-relations.xhtml"> target="https://www.iana.org/assignments/link-relations">
          <front>
          <title>IANA
            <title>Link Relations: Link Relation Types</title>
          <author />
          <date />
            <author><organization>IANA</organization></author>
          </front>
        </reference>

        <reference anchor="MEDIATYPES" target="https://www.iana.org/assignments/media-types/media-types.xhtml"> target="https://www.iana.org/assignments/media-types">
          <front>
          <title>IANA Media
            <title>Media Types</title>
          <author />
          <date />
            <author><organization>IANA</organization></author>
          </front>
        </reference>
      </references>
    </references>
    <section anchor="acknowledgments" numbered="false" toc="default">
      <name>Acknowledgments</name>
      <t>The authors would like to thank the members of CalConnect for their valuable contributions. This specification originated from the work of the API technical committee of CalConnect: The Calendaring and Scheduling Consortium.</t>
    </section>
  </back>
</rfc>