diff --git a/ical-tasks/generated/draft-ietf-calext-ical-tasks.err.html b/ical-tasks/generated/draft-ietf-calext-ical-tasks.err.html index 98311df..84c6eca 100644 --- a/ical-tasks/generated/draft-ietf-calext-ical-tasks.err.html +++ b/ical-tasks/generated/draft-ietf-calext-ical-tasks.err.html @@ -28,17 +28,17 @@

Style

<dl id="_84a1b574-a1d0-cb32-fe06-7a3ba795ce6e"> <dt>Task type</dt>2 -000921caldav-support +000953caldav-support Hanging paragraph in clause
<clause id="caldav-support" inline-header="false" obligation="normative">
 <title>CalDAV Support for Task Mode</title>
-<p id="_2d196c81-78e9-89f9-358e-fcb6f29c60cf">The CalDAV <eref type="inline" bibitemid="RFC4791" citeas="RFC 4791"/> calendar access protocol allows clients and servers to exchange iCalendar data. With the introduction of the "TASK-MODE" property in this specification, different automated task management behaviours may be delegated to the server by the Task Organizer depending upon the value of "TASK-MODE".</p>
+<p id="_af710561-e720-81cb-9069-2c2e67257f6c">The CalDAV <eref type="inline" bibitemid="RFC4791" citeas="RFC 4791"/> calendar access protocol allows clients and servers to exchange iCalendar data. With the introduction of the "TASK-MODE" property in this specification, different automated task management behaviours may be delegated to the server by the Task Organizer depending upon the value of "TASK-MODE".</p>
 
-<p id="_74176d3f-620c-8387-0107-28c7549072ba">In order for a CalDAV client to know what task modes are available, a CalDAV server advertises a CALDAV:supported-task-mode-set WebDAV property on calendar home or calendar collections if it supports the use of the "TASK-MODE" property as described in this specification.  The server can advertise a specific set of supported task modes by including one or more CALDAV:supported-task-mode XML elements within the CALDAV:supported-task-mode-set XML element. If no CALDAV:supported-task-mode XML elements are included in the WebDAV property, then clients can try any task mode, but need to be prepared for a failure when attempting to store the calendar data.</p>
2 +<p id="_81045c8e-8478-2d32-05fd-a1e8e2d64741">In order for a CalDAV client to know what task modes are available, a CalDAV server advertises a CALDAV:supported-task-mode-set WebDAV property on calendar home or calendar collections if it supports the use of the "TASK-MODE" property as described in this specification. The server can advertise a specific set of supported task modes by including one or more CALDAV:supported-task-mode XML elements within the CALDAV:supported-task-mode-set XML element. If no CALDAV:supported-task-mode XML elements are included in the WebDAV property, then clients can try any task mode, but need to be prepared for a failure when attempting to store the calendar data.</p>2 -000979_new_and_​updated_​icalendar_​elements_​registration +001011_new_and_​updated_​icalendar_​elements_​registration Hanging paragraph in clause
<clause id="_new_and_updated_icalendar_elements_registration" inline-header="false" obligation="normative">
 <title>New and updated iCalendar Elements Registration</title>
-<p id="_352db091-95f0-ef78-7d9e-d919e5fcb6f8">This specification updates <eref type="inline" bibitemid="RFC5545" citeas="RFC 5545"/> by adding and updating
+<p id="_d048e05d-bde6-8e22-6f7b-9005cb0354a7">This specification updates <eref type="inline" bibitemid="RFC5545" citeas="RFC 5545"/> by adding and updating
 a number of elements. The procedures and templates specified in
 <eref type="inline" bibitemid="RFC5545" citeas="RFC 5545"> <localityStack> <locality type="section"> <referenceFrom>8.2</referenceFrom> </locality> </localityStack> </eref> </p>
2 @@ -78,415 +78,415 @@

Metanorma XML Syntax

XML Line 000031:75 element "workgroup" not allowed here; expected the element end-tag or element "committee"
2
 
-XML Line 001253:82
+XML Line 001285:82
 attribute "inline-header" not allowed here; expected attribute "language", "numbered", "obligation", "removeInRFC", "script" or "toc"
2
 
-XML Line 001257:237
+XML Line 001289:237
 element "colgroup" not allowed here; expected element "name", "tbody" or "thead"
2
 
-XML Line 001257:259
+XML Line 001289:259
 found attribute "width", but no attributes allowed here
2
 
-XML Line 001257:281
+XML Line 001289:281
 found attribute "width", but no attributes allowed here
2
 
-XML Line 001257:303
+XML Line 001289:303
 found attribute "width", but no attributes allowed here
2
 
-XML Line 001257:326
+XML Line 001289:326
 found attribute "width", but no attributes allowed here
2
 
-XML Line 001299:114
+XML Line 001331:114
 found attribute "width", but no attributes allowed here
2
 
-XML Line 001299:132
+XML Line 001331:132
 found attribute "width", but no attributes allowed here
2
 
-XML Line 001299:150
+XML Line 001331:150
 found attribute "width", but no attributes allowed here
2
 
-XML Line 001299:61
+XML Line 001331:61
 element "colgroup" not allowed here; expected element "name", "tbody" or "thead"
2
 
-XML Line 001299:78
+XML Line 001331:78
 found attribute "width", but no attributes allowed here
2
 
-XML Line 001299:96
+XML Line 001331:96
 found attribute "width", but no attributes allowed here
2
 
-XML Line 001367:105
+XML Line 001399:105
 found attribute "width", but no attributes allowed here
2
 
-XML Line 001367:127
+XML Line 001399:127
 found attribute "width", but no attributes allowed here
2
 
-XML Line 001367:150
+XML Line 001399:150
 found attribute "width", but no attributes allowed here
2
 
-XML Line 001367:61
+XML Line 001399:61
 element "colgroup" not allowed here; expected element "name", "tbody" or "thead"
2
 
-XML Line 001367:83
+XML Line 001399:83
 found attribute "width", but no attributes allowed here
2
 
-XML Line 001403:40
+XML Line 001435:40
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001410:143
+XML Line 001442:143
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001410:143
+XML Line 001442:143
 found attribute "language", but no attributes allowed here
2
 
-XML Line 001410:143
+XML Line 001442:143
 found attribute "script",​ but no attributes allowed here
2
 
-XML Line 001410:150
+XML Line 001442:150
 element "p" missing required attribute "id"
2
 
-XML Line 001410:150
+XML Line 001442:150
 element "p" not allowed here; expected the element end-tag, text or element "add", "bcp14", "bookmark", "br", "concept", "date", "del", "em", "eref", "erefstack", "hr", "image", "index", "index-xref", "keyword", "link", "pagebreak", "review",​ "ruby", "smallcap", "span", "stem", "strike",​ "strong",​ "sub", "sup", "tt", "underline" or "xref"
2
 
-XML Line 001412:28
+XML Line 001444:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001414:28
+XML Line 001446:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001416:28
+XML Line 001448:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001419:40
+XML Line 001451:40
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001430:143
+XML Line 001462:143
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001430:143
+XML Line 001462:143
 found attribute "language", but no attributes allowed here
2
 
-XML Line 001430:143
+XML Line 001462:143
 found attribute "script",​ but no attributes allowed here
2
 
-XML Line 001430:150
+XML Line 001462:150
 element "p" missing required attribute "id"
2
 
-XML Line 001430:150
+XML Line 001462:150
 element "p" not allowed here; expected the element end-tag, text or element "add", "bcp14", "bookmark", "br", "concept", "date", "del", "em", "eref", "erefstack", "hr", "image", "index", "index-xref", "keyword", "link", "pagebreak", "review",​ "ruby", "smallcap", "span", "stem", "strike",​ "strong",​ "sub", "sup", "tt", "underline" or "xref"
2
 
-XML Line 001432:28
+XML Line 001464:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001434:28
+XML Line 001466:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001437:40
+XML Line 001469:40
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001444:143
+XML Line 001476:143
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001444:143
+XML Line 001476:143
 found attribute "language", but no attributes allowed here
2
 
-XML Line 001444:143
+XML Line 001476:143
 found attribute "script",​ but no attributes allowed here
2
 
-XML Line 001444:150
+XML Line 001476:150
 element "p" missing required attribute "id"
2
 
-XML Line 001444:150
+XML Line 001476:150
 element "p" not allowed here; expected the element end-tag, text or element "add", "bcp14", "bookmark", "br", "concept", "date", "del", "em", "eref", "erefstack", "hr", "image", "index", "index-xref", "keyword", "link", "pagebreak", "review",​ "ruby", "smallcap", "span", "stem", "strike",​ "strong",​ "sub", "sup", "tt", "underline" or "xref"
2
 
-XML Line 001445:8
+XML Line 001477:8
 element "p" missing required attribute "id"
2
 
-XML Line 001445:8
+XML Line 001477:8
 element "p" not allowed here; expected the element end-tag, text or element "add", "bcp14", "bookmark", "br", "concept", "date", "del", "em", "eref", "erefstack", "hr", "image", "index", "index-xref", "keyword", "link", "pagebreak", "review",​ "ruby", "smallcap", "span", "stem", "strike",​ "strong",​ "sub", "sup", "tt", "underline" or "xref"
2
 
-XML Line 001447:28
+XML Line 001479:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001449:28
+XML Line 001481:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001452:40
+XML Line 001484:40
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001459:143
+XML Line 001491:143
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001459:143
+XML Line 001491:143
 found attribute "language", but no attributes allowed here
2
 
-XML Line 001459:143
+XML Line 001491:143
 found attribute "script",​ but no attributes allowed here
2
 
-XML Line 001459:150
+XML Line 001491:150
 element "p" missing required attribute "id"
2
 
-XML Line 001459:150
+XML Line 001491:150
 element "p" not allowed here; expected the element end-tag, text or element "add", "bcp14", "bookmark", "br", "concept", "date", "del", "em", "eref", "erefstack", "hr", "image", "index", "index-xref", "keyword", "link", "pagebreak", "review",​ "ruby", "smallcap", "span", "stem", "strike",​ "strong",​ "sub", "sup", "tt", "underline" or "xref"
2
 
-XML Line 001461:28
+XML Line 001493:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001463:28
+XML Line 001495:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001466:40
+XML Line 001498:40
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001473:143
+XML Line 001505:143
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001473:143
+XML Line 001505:143
 found attribute "language", but no attributes allowed here
2
 
-XML Line 001473:143
+XML Line 001505:143
 found attribute "script",​ but no attributes allowed here
2
 
-XML Line 001473:150
+XML Line 001505:150
 element "p" missing required attribute "id"
2
 
-XML Line 001473:150
+XML Line 001505:150
 element "p" not allowed here; expected the element end-tag, text or element "add", "bcp14", "bookmark", "br", "concept", "date", "del", "em", "eref", "erefstack", "hr", "image", "index", "index-xref", "keyword", "link", "pagebreak", "review",​ "ruby", "smallcap", "span", "stem", "strike",​ "strong",​ "sub", "sup", "tt", "underline" or "xref"
2
 
-XML Line 001474:8
+XML Line 001506:8
 element "p" missing required attribute "id"
2
 
-XML Line 001474:8
+XML Line 001506:8
 element "p" not allowed here; expected the element end-tag, text or element "add", "bcp14", "bookmark", "br", "concept", "date", "del", "em", "eref", "erefstack", "hr", "image", "index", "index-xref", "keyword", "link", "pagebreak", "review",​ "ruby", "smallcap", "span", "stem", "strike",​ "strong",​ "sub", "sup", "tt", "underline" or "xref"
2
 
-XML Line 001475:94
+XML Line 001507:94
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001477:28
+XML Line 001509:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001479:28
+XML Line 001511:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001482:40
+XML Line 001514:40
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001489:143
+XML Line 001521:143
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001489:143
+XML Line 001521:143
 found attribute "language", but no attributes allowed here
2
 
-XML Line 001489:143
+XML Line 001521:143
 found attribute "script",​ but no attributes allowed here
2
 
-XML Line 001489:150
+XML Line 001521:150
 element "p" missing required attribute "id"
2
 
-XML Line 001489:150
+XML Line 001521:150
 element "p" not allowed here; expected the element end-tag, text or element "add", "bcp14", "bookmark", "br", "concept", "date", "del", "em", "eref", "erefstack", "hr", "image", "index", "index-xref", "keyword", "link", "pagebreak", "review",​ "ruby", "smallcap", "span", "stem", "strike",​ "strong",​ "sub", "sup", "tt", "underline" or "xref"
2
 
-XML Line 001490:94
+XML Line 001522:94
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001492:28
+XML Line 001524:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001494:28
+XML Line 001526:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001496:28
+XML Line 001528:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001499:40
+XML Line 001531:40
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001506:143
+XML Line 001538:143
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001506:143
+XML Line 001538:143
 found attribute "language", but no attributes allowed here
2
 
-XML Line 001506:143
+XML Line 001538:143
 found attribute "script",​ but no attributes allowed here
2
 
-XML Line 001506:150
+XML Line 001538:150
 element "p" missing required attribute "id"
2
 
-XML Line 001506:150
+XML Line 001538:150
 element "p" not allowed here; expected the element end-tag, text or element "add", "bcp14", "bookmark", "br", "concept", "date", "del", "em", "eref", "erefstack", "hr", "image", "index", "index-xref", "keyword", "link", "pagebreak", "review",​ "ruby", "smallcap", "span", "stem", "strike",​ "strong",​ "sub", "sup", "tt", "underline" or "xref"
2
 
-XML Line 001507:8
+XML Line 001539:8
 element "p" missing required attribute "id"
2
 
-XML Line 001507:8
+XML Line 001539:8
 element "p" not allowed here; expected the element end-tag, text or element "add", "bcp14", "bookmark", "br", "concept", "date", "del", "em", "eref", "erefstack", "hr", "image", "index", "index-xref", "keyword", "link", "pagebreak", "review",​ "ruby", "smallcap", "span", "stem", "strike",​ "strong",​ "sub", "sup", "tt", "underline" or "xref"
2
 
-XML Line 001508:94
+XML Line 001540:94
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001510:28
+XML Line 001542:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001512:28
+XML Line 001544:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001515:40
+XML Line 001547:40
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001524:143
+XML Line 001556:143
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001524:143
+XML Line 001556:143
 found attribute "language", but no attributes allowed here
2
 
-XML Line 001524:143
+XML Line 001556:143
 found attribute "script",​ but no attributes allowed here
2
 
-XML Line 001524:150
+XML Line 001556:150
 element "p" missing required attribute "id"
2
 
-XML Line 001524:150
+XML Line 001556:150
 element "p" not allowed here; expected the element end-tag, text or element "add", "bcp14", "bookmark", "br", "concept", "date", "del", "em", "eref", "erefstack", "hr", "image", "index", "index-xref", "keyword", "link", "pagebreak", "review",​ "ruby", "smallcap", "span", "stem", "strike",​ "strong",​ "sub", "sup", "tt", "underline" or "xref"
2
 
-XML Line 001525:8
+XML Line 001557:8
 element "p" missing required attribute "id"
2
 
-XML Line 001525:8
+XML Line 001557:8
 element "p" not allowed here; expected the element end-tag, text or element "add", "bcp14", "bookmark", "br", "concept", "date", "del", "em", "eref", "erefstack", "hr", "image", "index", "index-xref", "keyword", "link", "pagebreak", "review",​ "ruby", "smallcap", "span", "stem", "strike",​ "strong",​ "sub", "sup", "tt", "underline" or "xref"
2
 
-XML Line 001526:94
+XML Line 001558:94
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001528:28
+XML Line 001560:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001530:28
+XML Line 001562:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001533:40
+XML Line 001565:40
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001540:143
+XML Line 001572:143
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001540:143
+XML Line 001572:143
 found attribute "language", but no attributes allowed here
2
 
-XML Line 001540:143
+XML Line 001572:143
 found attribute "script",​ but no attributes allowed here
2
 
-XML Line 001540:150
+XML Line 001572:150
 element "p" missing required attribute "id"
2
 
-XML Line 001540:150
+XML Line 001572:150
 element "p" not allowed here; expected the element end-tag, text or element "add", "bcp14", "bookmark", "br", "concept", "date", "del", "em", "eref", "erefstack", "hr", "image", "index", "index-xref", "keyword", "link", "pagebreak", "review",​ "ruby", "smallcap", "span", "stem", "strike",​ "strong",​ "sub", "sup", "tt", "underline" or "xref"
2
 
-XML Line 001541:94
+XML Line 001573:94
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001543:28
+XML Line 001575:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001545:28
+XML Line 001577:28
 attribute "format" not allowed here; expected attribute "type"
2
 
-XML Line 001549:68
+XML Line 001581:68
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001549:68
+XML Line 001581:68
 found attribute "language", but no attributes allowed here
2
 
-XML Line 001549:68
+XML Line 001581:68
 found attribute "script",​ but no attributes allowed here
2
 
-XML Line 001550:409
+XML Line 001582:409
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001550:409
+XML Line 001582:409
 found attribute "language", but no attributes allowed here
2
 
-XML Line 001550:409
+XML Line 001582:409
 found attribute "script",​ but no attributes allowed here
2
 
-XML Line 001550:982
+XML Line 001582:982
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001551:96
+XML Line 001583:96
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001552:96
+XML Line 001584:96
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001554:141
+XML Line 001586:141
 element "link" missing required attribute "target"
2
 
-XML Line 001554:51
+XML Line 001586:51
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001556:10
+XML Line 001588:10
 element "title" not allowed here; expected the element end-tag or element "abstract", "accesslocation", "classification", "contributor", "copyright", "date", "depiction", "edition", "extent",​ "keyword", "language", "license", "locale",​ "medium",​ "note", "place", "price", "relation", "script",​ "series",​ "size", "status",​ "validity" or "version"
2
 
-XML Line 001559:19
+XML Line 001591:19
 element "uri" not allowed here; expected the element end-tag or element "abstract", "accesslocation", "classification", "contributor", "copyright", "date", "depiction", "edition", "extent",​ "keyword", "language", "license", "locale",​ "medium",​ "note", "place", "price", "relation", "script",​ "series",​ "size", "status",​ "validity" or "version"
2
 
-XML Line 001560:18
+XML Line 001592:18
 element "docidentifier" not allowed here; expected the element end-tag or element "abstract", "accesslocation", "classification", "contributor", "copyright", "date", "depiction", "edition", "extent",​ "keyword", "language", "license", "locale",​ "medium",​ "note", "place", "price", "relation", "script",​ "series",​ "size", "status",​ "validity" or "version"
2
 
-XML Line 001589:136
+XML Line 001621:136
 element "link" missing required attribute "target"
2
 
-XML Line 001589:51
+XML Line 001621:51
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001591:10
+XML Line 001623:10
 element "title" not allowed here; expected the element end-tag or element "abstract", "accesslocation", "classification", "contributor", "copyright", "date", "depiction", "edition", "extent",​ "keyword", "language", "license", "locale",​ "medium",​ "note", "place", "price", "relation", "script",​ "series",​ "size", "status",​ "validity" or "version"
2
 
-XML Line 001592:19
+XML Line 001624:19
 element "uri" not allowed here; expected the element end-tag or element "abstract", "accesslocation", "classification", "contributor", "copyright", "date", "depiction", "edition", "extent",​ "keyword", "language", "license", "locale",​ "medium",​ "note", "place", "price", "relation", "script",​ "series",​ "size", "status",​ "validity" or "version"
2
 
-XML Line 001593:28
+XML Line 001625:28
 element "docidentifier" not allowed here; expected the element end-tag or element "abstract", "accesslocation", "classification", "contributor", "copyright", "date", "depiction", "edition", "extent",​ "keyword", "language", "license", "locale",​ "medium",​ "note", "place", "price", "relation", "script",​ "series",​ "size", "status",​ "validity" or "version"
2
 
-XML Line 001604:208
+XML Line 001636:208
 element "link" missing required attribute "target"
2
 
-XML Line 001604:51
+XML Line 001636:51
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001657:68
+XML Line 001689:68
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001657:68
+XML Line 001689:68
 found attribute "language", but no attributes allowed here
2
 
-XML Line 001657:68
+XML Line 001689:68
 found attribute "script",​ but no attributes allowed here
2
 
-XML Line 001674:255
+XML Line 001706:255
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001674:255
+XML Line 001706:255
 found attribute "language", but no attributes allowed here
2
 
-XML Line 001674:255
+XML Line 001706:255
 found attribute "script",​ but no attributes allowed here
2
 
-XML Line 001675:68
+XML Line 001707:68
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001675:68
+XML Line 001707:68
 found attribute "language", but no attributes allowed here
2
 
-XML Line 001675:68
+XML Line 001707:68
 found attribute "script",​ but no attributes allowed here
2
 
-XML Line 001682:138
+XML Line 001714:138
 found attribute "format",​ but no attributes allowed here
2
 
-XML Line 001682:138
+XML Line 001714:138
 found attribute "language", but no attributes allowed here
2
 
-XML Line 001682:138
+XML Line 001714:138
 found attribute "script",​ but no attributes allowed here
2
 
 
diff --git a/ical-tasks/generated/draft-ietf-calext-ical-tasks.html b/ical-tasks/generated/draft-ietf-calext-ical-tasks.html
index 7c44e71..5f47f9a 100644
--- a/ical-tasks/generated/draft-ietf-calext-ical-tasks.html
+++ b/ical-tasks/generated/draft-ietf-calext-ical-tasks.html
@@ -1217,7 +1217,7 @@
 
 
 Apthorp & Douglass
-Expires 14 October 2024
+Expires 15 October 2024
 [Page]
 
 
@@ -1235,12 +1235,12 @@
 RFC5545 (if approved)
 
Published:

 

-
+
     

 
Intended Status:

 
Standards Track

 
Expires:

-

+

 
Authors:

 

 

@@ -1289,7 +1289,7 @@ 

         time. It is inappropriate to use Internet-Drafts as reference
         material or to cite them other than as "work in progress."

 

-        This Internet-Draft will expire on 14 October 2024.

+        This Internet-Draft will expire on 15 October 2024.

 
 

 
-

+

 

+      

+10. Modifications to Calendar Components
+      

+

+
The following changes to the syntax defined in iCalendar [RFC5545]
+are made here. New elements are defined in subsequent sections.

+

+

+

+
; Addition of VSTATUS as a valid component for VEVENT
+eventc     = "BEGIN" ":" "VEVENT" CRLF
+             eventprop *alarmc *participantc *locationc *resourcec *statusc
+             "END" ":" "VEVENT" CRLF
+
+; Addition of VSTATUS as a valid component for VTODO
+todoc      = "BEGIN" ":" "VTODO" CRLF
+             todoprop *alarmc *participantc *locationc *resourcec *statusc
+             "END" ":" "VTODO" CRLF
+
+; Addition of properties ESTIMATED-DURATION and TASK-MODE to VTODO
+todoprop =/ est-duration /
+            task-mode
+
+; Addition of VSTATUS as a valid component for VJOURNAL
+journalc   = "BEGIN" ":" "VJOURNAL" CRLF
+              jourprop *statusc
+              "END" ":" "VJOURNAL" CRLF
+
+
+; Addition of VSTATUS as a valid component for VFREEBUSY
+freebusyc  = "BEGIN" ":" "VFREEBUSY" CRLF
+             fbprop *participantc *locationc *resourcec *statusc
+             "END" ":" "VFREEBUSY" CRLF

+

+

+

+

+

+

       

-10. New Parameter Values
+11. New Parameter Values
       

 

-

+

         

-10.1. Redefined VTODO Participant Status
+11.1. Redefined VTODO Participant Status
         

-

-
Participant status parameter type values are defined in
+

+
Participant status parameter type values are defined in
 Section 3.2.12 of [RFC5545].  This specification redefines that type
-to include the new value FAILED for VTODO iCalendar components.

+to include the new value FAILED for VTODO iCalendar components.

 

-

-

-          
Format Definition

-          

-            

-
This property parameter is extended by the following notation:

+

+

+          
Format Definition

+          

+            

+
This property parameter is extended by the following notation:

 

 

         

 

 

-

-

-
partstat-todo    =/ *("FAILED")  ; To-do cannot be completed

+

+

+
partstat-todo    =/ *("FAILED")  ; To-do cannot be completed

 

 

-

-

-          
Example

-          

+

+

+          
Example

+          

         

 

 

-

-

+

+

 
ATTENDEE;REASON="https://example.com/reason/not-enough-time";
- PARTSTAT=FAILED:mailto:jsmith@example.com

+ PARTSTAT=FAILED:mailto:jsmith@example.com
 

 

 

@@ -2300,231 +2342,231 @@ 

 

 

 

-

+

       

-11. New Properties
+12. New Properties
       

 

-

+

         

-11.1. Estimated Duration
+12.1. Estimated Duration
         

-

-

-          
Property Name

-          

-            

-
ESTIMATED-DURATION

+

+

+          
Property Name

+          

+            

+
ESTIMATED-DURATION

 

 

           

-
Purpose

-          

-            

-
This property specifies the estimated positive duration of time the corresponding task will take to complete.

+
Purpose

+          

+            

+
This property specifies the estimated positive duration of time the corresponding task will take to complete.

 

 

           

-
Value Type

-          

-            

-
DURATION

+
Value Type

+          

+            

+
DURATION

 

 

           

-
Property Parameters

-          

-            

-
IANA and non-standard property parameters can be specified on this property.

+
Property Parameters

+          

+            

+
IANA and non-standard property parameters can be specified on this property.

 

 

           

-
Conformance

-          

-            

-
This property can be specified in "VTODO" calendar components.

+
Conformance

+          

+            

+
This property can be specified in "VTODO" calendar components.

 

 

           

-
Format Definition

-          

-            

-
This property is defined by the following notation:

+
Format Definition

+          

+            

+
This property is defined by the following notation:

 

 

         

 

 

-

-

+

+

 
est-duration  = "ESTIMATED-DURATION" durparam ":" dur-value CRLF
                 ;consisting of a positive duration of time.
 
-durparam      = *(";" other-param)

+durparam      = *(";" other-param)
 

 

-

-

-          
Description

-          

-            

-
In a "VTODO" calendar component the property MAY be used to specify the estimated duration for the to-do, with or without an explicit time window in which the event should be started and completed.  When present, DTSTART and DUE/DURATION represent the window in which the task can be performed. ESTIMATED-DURATION SHOULD be passed from ORGANIZER to ATTENDEE in iTIP [RFC5546] messages.

+

+

+          
Description

+          

+            

+
In a "VTODO" calendar component the property MAY be used to specify the estimated duration for the to-do, with or without an explicit time window in which the event should be started and completed.  When present, DTSTART and DUE/DURATION represent the window in which the task can be performed. ESTIMATED-DURATION SHOULD be passed from ORGANIZER to ATTENDEE in iTIP [RFC5546] messages.

 

 

           

-
Example

-          

-            

-
The following is an example of this property that estimates the duration of a task to be one hour:

+
Example

+          

+            

+
The following is an example of this property that estimates the duration of a task to be one hour:

 

 

         

 

 

-

-

-
ESTIMATED-DURATION:PT1H

+

+

+
ESTIMATED-DURATION:PT1H

 

 

 

 

 

-

+

         

-11.2. Reason
+12.2. Reason
         

-

-

-          
Property name

-          

-            

-
REASON

+

+

+          
Property name

+          

+            

+
REASON

 

 

           

-
Purpose

-          

-            

-
To indicate the reason for a status change or change of attendee participation status.

+
Purpose

+          

+            

+
To indicate the reason for a status change or change of attendee participation status.

 

 

           

-
Value Type

-          

-            

-
URI

+
Value Type

+          

+            

+
URI

 

 

           

-
Property Parameters

-          

-            

-
IANA and non-standard property parameters can be specified on this property.

+
Property Parameters

+          

+            

+
IANA and non-standard property parameters can be specified on this property.

 

 

           

-
Conformance

-          

-            

-
This property can be specified in "VSTATUS" and PARTICIPANT calendar components.

+
Conformance

+          

+            

+
This property can be specified in "VSTATUS" and PARTICIPANT calendar components.

 

 

           

-
Format Definition

-          

-            

-
This property is defined by the following notation:

+
Format Definition

+          

+            

+
This property is defined by the following notation:

 

 

         

 

 

-

-

+

+

 
reason      = "REASON" reasonparam ":" uri CRLF
 
-reasonparam = *(";" other-param)

+reasonparam = *(";" other-param)
 

 

-

-

-          
Description

-          

-            

-
This property allows the change in status of a
+

+

+          
Description

+          

+            

+
This property allows the change in status of a
 task or participant status to be qualified by the reason for the change
 with a codified reason. Typically, reasons are defined within the
 context of the task type and therefore SHOULD include the name-space
-of the authority defining the task.

+of the authority defining the task.

 

 

           

-
Example

-          

+
Example

+          

         

 

 

-

-

-
REASON:https://example.com/reason/delivered-on-time

+

+

+
REASON:https://example.com/reason/delivered-on-time

 

 

 

 

 

-

+

         

-11.3. Sub-State
+12.3. Sub-State
         

-

-

-          
Property name

-          

-            

-
SUBSTATE

+

+

+          
Property name

+          

+            

+
SUBSTATE

 

 

           

-
Purpose

-          

-            

-
To provide additional granularity of task status for e.g.
-IN-PROCESS.

+
Purpose

+          

+            

+
To provide additional granularity of task status for e.g.
+IN-PROCESS.

 

 

           

-
Value Type

-          

-            

-
TEXT

+
Value Type

+          

+            

+
TEXT

 

 

           

-
Property Parameters

-          

-            

-
IANA and non-standard property parameters can be specified on this property.

+
Property Parameters

+          

+            

+
IANA and non-standard property parameters can be specified on this property.

 

 

           

-
Conformance

-          

-            

-
This property can be specified in a "VSTATUS" calendar component.

+
Conformance

+          

+            

+
This property can be specified in a "VSTATUS" calendar component.

 

 

           

-
Format Definition

-          

-            

-
This property is defined by the following notation:

+
Format Definition

+          

+            

+
This property is defined by the following notation:

 

 

         

 

 

-

-

+

+

 
substate          = "SUBSTATE" substateparam ":" substatevalue CRLF
 
 substateparam     = *(";" other-param)
@@ -2536,31 +2578,31 @@ 

                      ;               complete or availability of a
                      ;               resource (REASON code explains
                      ;               why)
-                     / iana-token) ; Other IANA-registered type

+                     / iana-token) ; Other IANA-registered type
 

 

-

-

-          
Description

-          

-            

-
The sub-state property allows additional qualification
+

+

+          
Description

+          

+            

+
The sub-state property allows additional qualification
 and granularity of states to be recorded, in particular for the
 IN-PROCESS state. It allows individual sub-states to be recorded
 without the need to define and publish a sub-task associated with a
 parent task purely to track that a particular state has been reached.
 This property also allows parallel states to be expressed e.g. that a
-task has been suspended at whatever state it has reached.

+task has been suspended at whatever state it has reached.

 

 

           

-
Example

-          

+
Example

+          

         

 

 

-

-

+

+

 
BEGIN:VSTATUS
 STATUS:FAILED
 REASON:https://example.com/reason/no-one-home
@@ -2571,66 +2613,66 @@ 

 STATUS:IN-PROCESS
 REASON:https://example.com/reason/paint-drying
 SUBSTATE:SUSPENDED
-END:VSTATUS

+END:VSTATUS
 

 

 

 

 

-

+

         

-11.4. Task Mode
+12.4. Task Mode
         

-

-

-          
Property Name

-          

-            

-
TASK-MODE

+

+

+          
Property Name

+          

+            

+
TASK-MODE

 

 

           

-
Purpose

-          

-            

-
This property specifies automatic operations that servers
+
Purpose

+          

+            

+
This property specifies automatic operations that servers
 acting on behalf of the organizer apply to tasks based on changes in
-attendee status (PARTSTAT).

+attendee status (PARTSTAT).

 

 

           

-
Value Type

-          

-            

-
TEXT

+
Value Type

+          

+            

+
TEXT

 

 

           

-
Property Parameters

-          

-            

-
IANA and non-standard property parameters can be specified on this property.

+
Property Parameters

+          

+            

+
IANA and non-standard property parameters can be specified on this property.

 

 

           

-
Conformance

-          

-            

-
This property can be specified zero or more times in a "VTODO" calendar component.

+
Conformance

+          

+            

+
This property can be specified zero or more times in a "VTODO" calendar component.

 

 

           

-
Format Definition

-          

-            

-
This property is defined by the following notation:

+
Format Definition

+          

+            

+
This property is defined by the following notation:

 

 

         

 

 

-

-

+

+

 
task-mode   = "TASK-MODE taskmodeparam ":" taskvalue
               *("," taskvalue) CRLF
 
@@ -2642,73 +2684,73 @@ 

                 / iana-token
                 / x-name
 
-taskmodeparam      = *(";" other-param)

+taskmodeparam      = *(";" other-param)
 

 

-

-

-          
Description

-          

-            

-
In a "VTODO" calendar component this property MAY be
+

+

+          
Description

+          

+            

+
In a "VTODO" calendar component this property MAY be
 used to indicate to servers how they can automatically change the
 state of the task based on iTIP replies from Attendees. For example,
 the server can automatically set the overall task status to COMPLETED
 when every attendee has marked their own status (PARTSTAT) as COMPLETED,
 or the server could mark the task as FAILED if its DUE date passes
-without it being completed. TASK-MODE processing is performed on the organizer's copy of the task.

+without it being completed. TASK-MODE processing is performed on the organizer's copy of the task.

 

 

         

 

 

-

-
To set the status, add a VSTATUS component as specified in Section 13.1.

+

+
To set the status, add a VSTATUS component as specified in Section 14.1.

 

-

-
The property value is a list of one or more IANA registered tokens that defines modes to be used for the task. This specification defines three modes which are described in the following subsections.

+

+
The property value is a list of one or more IANA registered tokens that defines modes to be used for the task. This specification defines three modes which are described in the following subsections.

 

-

-

-          
Examples

-          

+

+

+          
Examples

+          

         

 

 

-

-

+

+

 
TASK-MODE:AUTOMATIC-COMPLETION,AUTOMATIC-FAILURE
 TASK-MODE:SERVER
-TASK-MODE:AUTOMATIC-FAILURE

+TASK-MODE:AUTOMATIC-FAILURE
 

 

 

-

-          
AUTOMATIC-COMPLETION Task Mode

-          

-            

-
The task mode value "AUTOMATIC-COMPLETION" indicates to the server
+

+          
AUTOMATIC-COMPLETION Task Mode

+          

+            

+
The task mode value "AUTOMATIC-COMPLETION" indicates to the server
 that it can change the "VTODO" component's status to "COMPLETED" as
 soon as all ATTENDEEs in the task have replied with a "PARTSTAT"
-parameter set to "COMPLETED".

+parameter set to "COMPLETED".

 

 

         

 

 

 

-

-          
AUTOMATIC-FAILURE Task Mode

-          

-            

-
The task mode value "AUTOMATIC-FAILURE" indicates to the server that
-it SHOULD change the "VTODO" component's status to "FAILED" if either:

-

-

-
    
-
  1. the PARTSTAT of one ATTENDEE is set to FAILED; or
+
    
+          
    AUTOMATIC-FAILURE Task Mode
    
+          
    
+            
    
+
    The task mode value "AUTOMATIC-FAILURE" indicates to the server that
+it SHOULD change the "VTODO" component's status to "FAILED" if either:
    
+
    
+
    
+
      
+
    1. the PARTSTAT of one ATTENDEE is set to FAILED; or
 
      2. 
-              
    2. the current time is past the effective due date of the component and the task has not yet been completed.
+              
    3. the current time is past the effective due date of the component and the task has not yet been completed.
 
      4. 
             
    
 
    
@@ -2716,37 +2758,37 @@ 
    
         
    
 
    
 

-

-

 

 

-

+

       

-12. Property Extensions and Clarifications
+13. Property Extensions and Clarifications
       

 

-

+

         

-12.1. Updated DURATION Property definition
+13.1. Updated DURATION Property definition
         

-

-
[RFC5545] section 3.6.2 introduced a constraint on the duration property requiring
+

+
[RFC5545] section 3.6.2 introduced a constraint on the duration property requiring
 that a DURATION MUST be accompanied by a DTSTART.
 This constraint is dropped reverting to the situation as specified
-previously.

+previously.

 

-

-
Thus the text:

+

+
Thus the text:

 

-

-

+

+

 
                  ; Either 'due' or 'duration' MAY appear in
                   ; a 'todoprop', but 'due' and 'duration'
                   ; MUST NOT occur in the same 'todoprop'.
                   ; If 'duration' appear in a 'todoprop',
                   ; then 'dtstart' MUST also appear in
-                  ; the same 'todoprop'.

+                  ; the same 'todoprop'.
 

 

-

-
is replaced by

+

+
is replaced by

 

-

-

+

+

 
                  ; Either 'due' or 'duration' MAY appear in
                   ; a 'todoprop', but 'due' and 'duration'
-                  ; MUST NOT occur in the same 'todoprop'.

+                  ; MUST NOT occur in the same 'todoprop'.
 

 

-

-
This allows a VTODO to only have a DURATION property.

+

+
This allows a VTODO to only have a DURATION property.

 

-

-
Furthermore, the following text:

+

+
Furthermore, the following text:

 

-

-

+

+

 
     A "VTODO" calendar component without the "DTSTART" and "DUE" (or
      "DURATION") properties specifies a to-do that will be associated
-     with each successive calendar date, until it is completed.

+     with each successive calendar date, until it is completed.
 

 

-

-
is replaced by

+

+
is replaced by

 

-

-

+

+

 
     A "VTODO" calendar component without the "DTSTART" and "DUE"
      properties specifies a to-do that will be associated
-     with each successive calendar date, until it is completed.

+     with each successive calendar date, until it is completed.
 

 

 

 

 

-

+

         

-12.2. Redefined STATUS Property
+13.2. Redefined STATUS Property
         

-

-
The Status property is defined in Section 3.8.1.11 of [RFC5545]. This
+

+
The Status property is defined in Section 3.8.1.11 of [RFC5545]. This
 specification extends that property to include new values
 associated with VTODO iCalendar components (See Appendix A for
-examples of the task state lifecycle).

+examples of the task state lifecycle).

 

-

-

-          
Format Definition

-          

-            

-
The "STATUS" property parameter list is augmented
-as follows:

+

+

+          
Format Definition

+          

+            

+
The "STATUS" property parameter list is augmented
+as follows:

 

 

         

 

 

-

-

+

+

 
statvalue-todo = / "PENDING"    ;Indicates a to-do has been
                                 ;created and accepted, but has
                                 ; not yet started.
                 / "FAILED"      ;Indicates to-do has failed.
-;Extended status values for "VTODO".

+;Extended status values for "VTODO".
 

 

-

-
Description:

+

+
Description:

 

-

-
PENDING - A to-do has been created and accepted but has not yet
+

+
PENDING - A to-do has been created and accepted but has not yet
 started and is ready
 to start subject to other dependencies (e.g. preceding task or
-DTSTART). This is the default state.

+DTSTART). This is the default state.

 

-

-
FAILED - to-do has failed and may need some follow-up from the
-organizer to re-schedule or cancel

+

+
FAILED - to-do has failed and may need some follow-up from the
+organizer to re-schedule or cancel

 

-

-
Example: The following is an example of this property for a "VTODO"
-calendar component:

+

+
Example: The following is an example of this property for a "VTODO"
+calendar component:

 

-

-

-
STATUS:FAILED

+

+

+
STATUS:FAILED

 

 

 

@@ -2879,71 +2921,71 @@ 

 

 

 

-

+

       

-13. New Components
+14. New Components
       

 

-

+

         

-13.1. Status Component
+14.1. Status Component
         

-

-

-          
Component Name

-          

-            

-
VSTATUS

+

+

+          
Component Name

+          

+            

+
VSTATUS

 

 

           

-
Purpose

-          

-            

-
This component allows information to be
-associated with a status, for example comments and date stamps.

+
Purpose

+          

+            

+
This component allows information to be
+associated with a status, for example comments and date stamps.

 

 

           

-
Conformance

-          

-            

-
This component can be specified multiple times in
-any calendar component.

+
Conformance

+          

+            

+
This component can be specified multiple times in
+any calendar component.

 

 

           

-
Description

-          

-            

-
This component provides a way for multiple date-stamped
-statuses to be associated with a component such as a participant, task or event.

+
Description

+          

+            

+
This component provides a way for multiple date-stamped
+statuses to be associated with a component such as a participant, task or event.

 

 

         

 

 

-

-
This component may be added to the [RFC9073] PARTICIPANT component
-to allow participants in a task to specify their own status.

+

+
This component may be added to the [RFC9073] PARTICIPANT component
+to allow participants in a task to specify their own status.

 

-

-
For backwards compatibility, when a VSTATUS component is added the
-[RFC5545] STATUS property MUST be set on the parent component.

+

+
For backwards compatibility, when a VSTATUS component is added the
+[RFC5545] STATUS property MUST be set on the parent component.

 

-

-

-          
Format Definition

-          

-            

-
This component is defined by the following notation:

+

+

+          
Format Definition

+          

+            

+
This component is defined by the following notation:

 

 

         

 

 

-

-

+

+

 
statusc = "BEGIN" ":" "VSTATUS" CRLF
           statusprop
           "END" ":" "VSTATUS" CRLF
@@ -2965,23 +3007,23 @@ 

                ;
                comment / styleddescription / iana-prop
                ;
-               )

+               )
 

 

-

-

-          
Examples

-          

+

+

+          
Examples

+          

         

 

 

-

-

+

+

 
BEGIN:VSTATUS
 STATUS:COMPLETED
 REASON: https://example.com/reason/delivered-on-time
 DTSTAMP:20220212T120000Z
-END:VSTATUS

+END:VSTATUS
 

 

 

@@ -2989,95 +3031,95 @@ 

 

 

 

-

+

       

-14. CalDAV Support for Task Mode
+15. CalDAV Support for Task Mode
       

-

-
The CalDAV [RFC4791] calendar access protocol allows clients and servers to exchange iCalendar data. With the introduction of the "TASK-MODE" property in this specification, different automated task management behaviours may be delegated to the server by the Task Organizer depending upon the value of "TASK-MODE".

+

+
The CalDAV [RFC4791] calendar access protocol allows clients and servers to exchange iCalendar data. With the introduction of the "TASK-MODE" property in this specification, different automated task management behaviours may be delegated to the server by the Task Organizer depending upon the value of "TASK-MODE".

 

-

-
In order for a CalDAV client to know what task modes are available, a CalDAV server advertises a CALDAV:supported-task-mode-set WebDAV property on calendar home or calendar collections if it supports the use of the "TASK-MODE" property as described in this specification.  The server can advertise a specific set of supported task modes by including one or more CALDAV:supported-task-mode XML elements within the CALDAV:supported-task-mode-set XML element. If no CALDAV:supported-task-mode XML elements are included in the WebDAV property, then clients can try any task mode, but need to be prepared for a failure when attempting to store the calendar data.

+

+
In order for a CalDAV client to know what task modes are available, a CalDAV server advertises a CALDAV:supported-task-mode-set WebDAV property on calendar home or calendar collections if it supports the use of the "TASK-MODE" property as described in this specification.  The server can advertise a specific set of supported task modes by including one or more CALDAV:supported-task-mode XML elements within the CALDAV:supported-task-mode-set XML element. If no CALDAV:supported-task-mode XML elements are included in the WebDAV property, then clients can try any task mode, but need to be prepared for a failure when attempting to store the calendar data.

 

-

-
Clients MUST NOT attempt to store iCalendar data containing "TASK-MODE" elements if the CALDAV:supported-task-mode-set WebDAV property is not advertised by the server.

+

+
Clients MUST NOT attempt to store iCalendar data containing "TASK-MODE" elements if the CALDAV:supported-task-mode-set WebDAV property is not advertised by the server.

 

-

-
The server SHOULD return an HTTP 403 response with a DAV:error element containing a CALDAV:supported-task-mode XML element, if a client attempts to store iCalendar data with an "TASK-MODE" element value not supported by the server.

+

+
The server SHOULD return an HTTP 403 response with a DAV:error element containing a CALDAV:supported-task-mode XML element, if a client attempts to store iCalendar data with an "TASK-MODE" element value not supported by the server.

 

-

-
It is possible for a "TASK-MODE" value to be present in calendar data on the server being accessed by a client that does not support the "TASK-MODE" property. It is expected that existing clients, unaware of "TASK-MODE", will fail gracefully by ignoring the calendar property.

+

+
It is possible for a "TASK-MODE" value to be present in calendar data on the server being accessed by a client that does not support the "TASK-MODE" property. It is expected that existing clients, unaware of "TASK-MODE", will fail gracefully by ignoring the calendar property.

 

 

-

+

         

-14.1. CALDAV:supported-task-mode-set Property
+15.1. CALDAV:supported-task-mode-set Property
         

-

-

-          
Name

-          

-            

-
supported-task-mode-set

+

+

+          
Name

+          

+            

+
supported-task-mode-set

 

 

           

-
Namespace

-          

-            

-
urn:ietf:params:xml:ns:caldav

+
Namespace

+          

+            

+
urn:ietf:params:xml:ns:caldav

 

 

           

-
Purpose

-          

-            

-
Enumerates the set of supported iCalendar "TASK-MODE" element values supported by the server.

+
Purpose

+          

+            

+
Enumerates the set of supported iCalendar "TASK-MODE" element values supported by the server.

 

 

           

-
Protected

-          

-            

-
This property MUST be protected and SHOULD NOT be returned by a PROPFIND allprop request (as defined in Section 14.2 of [RFC4918]).

+
Protected

+          

+            

+
This property MUST be protected and SHOULD NOT be returned by a PROPFIND allprop request (as defined in Section 14.2 of [RFC4918]).

 

 

           

-
Description

-          

-            

-
See above.

+
Description

+          

+            

+
See above.

 

 

           

-
Definition

-          

+
Definition

+          

         

 

 

-

-

+

+

 
<!ELEMENT supported-task-mode-set(supported-task-mode*)>
 <!ELEMENT supported-task-mode (#PCDATA)>
 <!-- PCDATA value: string - case insensitive but
-uppercase preferred -->

+uppercase preferred -->
 

 

-

-

-          
Example

-          

+

+

+          
Example

+          

         

 

 

-

-

+

+

 
<C:supported-task-mode-set xmlns:C="urn:ietf:params:xml:ns:caldav">
   <C:supported-task-mode>AUTOMATIC-COMPLETION</C:supported-task-mode>
   <C:supported-task-mode>AUTOMATIC-FAILURE</C:supported-task-mode>
   <C:supported-task-mode>SERVER</C:supported-task-mode>
   <C:supported-task-mode>CLIENT</C:supported-task-mode>
-</C:supported-task-mode-set>

+</C:supported-task-mode-set>
 

 

 

@@ -3085,39 +3127,39 @@ 

 

 

 

-

+

       

-15. Security Considerations
+16. Security Considerations
       

-

-
This specification introduces no new security considerations beyond those identified in [RFC5545], [RFC5546] and [RFC4791].

+

+
This specification introduces no new security considerations beyond those identified in [RFC5545], [RFC5546] and [RFC4791].

 

 

 

 

-

+

       

-16. IANA Considerations
+17. IANA Considerations
       

 

-

+

         

-16.1. New and updated iCalendar Elements Registration
+17.1. New and updated iCalendar Elements Registration
         

-

-
This specification updates [RFC5545] by adding and updating
+

+
This specification updates [RFC5545] by adding and updating
 a number of elements. The procedures and templates specified in
-Section 8.2 of [RFC5545]

+Section 8.2 of [RFC5545]

 

 

-

+

           

-16.1.1. Initialization of the Status registry
+17.1.1. Initialization of the Status registry
           

-

-
This specification updates [RFC5545] by adding a Status value registry to the iCalendar Elements registry and initializing it as per [RFC5545].

+

+
This specification updates [RFC5545] by adding a Status value registry to the iCalendar Elements registry and initializing it as per [RFC5545].

 

-

+

 
@@ -3273,14 +3315,14 @@ 

 
 
 

-

+

           

-16.1.2. Update of the Status registry
+17.1.2. Update of the Status registry
           

-

-
This specification further updates the Status registry with additional values defined in this document.

+

+
This specification further updates the Status registry with additional values defined in this document.

 

-

+

 

             
 Table 1:
@@ -3133,137 +3175,137 @@ 

             

               

                 
-                  

-
CANCELLED

+                  

+
CANCELLED

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
Section 3.8.1.11 of [RFC5545]

+                  

+
Section 3.8.1.11 of [RFC5545]

 

 

               

               

                 
-                  

-
COMPLETED

+                  

+
COMPLETED

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
Section 3.8.1.11 of [RFC5545]

+                  

+
Section 3.8.1.11 of [RFC5545]

 

 

               

               

                 
-                  

-
CONFIRMED

+                  

+
CONFIRMED

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
Section 3.8.1.11 of [RFC5545]

+                  

+
Section 3.8.1.11 of [RFC5545]

 

 

               

               

                 
-                  

-
DRAFT

+                  

+
DRAFT

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
Section 3.8.1.11 of [RFC5545]

+                  

+
Section 3.8.1.11 of [RFC5545]

 

 

               

               

                 
-                  

-
FINAL

+                  

+
FINAL

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
Section 3.8.1.11 of [RFC5545]

+                  

+
Section 3.8.1.11 of [RFC5545]

 

 

               

               

                 
-                  

-
IN-PROCESS

+                  

+
IN-PROCESS

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
Section 3.8.1.11 of [RFC5545]

+                  

+
Section 3.8.1.11 of [RFC5545]

 

 

               

               

                 
-                  

-
NEEDS-ACTION

+                  

+
NEEDS-ACTION

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
Section 3.8.1.11 of [RFC5545]

+                  

+
Section 3.8.1.11 of [RFC5545]

 

 

               

               

                 
-                  

-
TENTATIVE

+                  

+
TENTATIVE

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
Section 3.8.1.11 of [RFC5545]

+                  

+
Section 3.8.1.11 of [RFC5545]

 

 

               

@@ -3334,14 +3376,14 @@ 

 
 
 

-

+

           

-16.1.3. Sub-State value registry
+17.1.3. Sub-State value registry
           

-

-
The following table has been used to initialize the Sub-State registry.

+

+
The following table has been used to initialize the Sub-State registry.

 

-

+

 

             
 Table 2:
@@ -3296,35 +3338,35 @@ 

             

               

                 
-                  

-
PENDING

+                  

+
PENDING

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
This Spec, Section 12.2

+                  

+
This Spec, Section 13.2

 

 

               

               

                 
-                  

-
FAILED

+                  

+
FAILED

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
This Spec, Section 12.2

+                  

+
This Spec, Section 13.2

 

 

               

@@ -3412,14 +3454,14 @@ 

 
 
 

-

+

           

-16.1.4. Task Mode value registry
+17.1.4. Task Mode value registry
           

-

-
The following table has been used to initialize the Task Mode registry.

+

+
The following table has been used to initialize the Task Mode registry.

 

-

+

 

             
 Table 3:
@@ -3357,52 +3399,52 @@ 

             

               

                 
-                  

-
OK

+                  

+
OK

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
This Spec, Section 11.3

+                  

+
This Spec, Section 12.3

 

 

               

               

                 
-                  

-
ERROR

+                  

+
ERROR

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
This Spec, Section 11.3

+                  

+
This Spec, Section 12.3

 

 

               

               

                 
-                  

-
SUSPENDED

+                  

+
SUSPENDED

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
This Spec, Section 11.3

+                  

+
This Spec, Section 12.3

 

 

               

@@ -3507,14 +3549,14 @@ 

 
 
 

-

+

           

-16.1.5. Participation Statuses registry
+17.1.5. Participation Statuses registry
           

-

-
The following table has been used to update the Participation Statuses registry.

+

+
The following table has been used to update the Participation Statuses registry.

 

-

+

 

             
 Table 4:
@@ -3435,69 +3477,69 @@ 

             

               

                 
-                  

-
AUTOMATIC-COMPLETION

+                  

+
AUTOMATIC-COMPLETION

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
This Spec, Section 11.4

+                  

+
This Spec, Section 12.4

 

 

               

               

                 
-                  

-
AUTOMATIC-FAILURE

+                  

+
AUTOMATIC-FAILURE

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
This Spec,  Section 11.4

+                  

+
This Spec,  Section 12.4

 

 

               

               

                 
-                  

-
CLIENT

+                  

+
CLIENT

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
This Spec,  Section 11.4

+                  

+
This Spec,  Section 12.4

 

 

               

               

                 
-                  

-
SERVER

+                  

+
SERVER

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
This Spec,  Section 11.4

+                  

+
This Spec,  Section 12.4

 

 

               

@@ -3551,15 +3593,15 @@ 

 
 
 

-

+

           

-16.1.6. Components Registry
+17.1.6. Components Registry
           

-

-
The following table has been used to update the Components registry
-defined in Section 8.3.1 of [RFC5545].

+

+
The following table has been used to update the Components registry
+defined in Section 8.3.1 of [RFC5545].

 

-

+

 

             
 Table 5:
@@ -3530,18 +3572,18 @@ 

             

               

                 
-                  

-
FAILED

+                  

+
FAILED

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
This Spec, Section 10.1

+                  

+
This Spec, Section 11.1

 

 

               

@@ -3596,15 +3638,15 @@ 

 
 
 

-

+

           

-16.1.7. Properties registry
+17.1.7. Properties registry
           

-

-
The following table has been used to update the Properties registry
-defined in Section 8.3.2 of [RFC5545].

+

+
The following table has been used to update the Properties registry
+defined in Section 8.3.2 of [RFC5545].

 

-

+

 

             
 Table 6:
@@ -3575,18 +3617,18 @@ 

             

               

                 
-                  

-
VSTATUS

+                  

+
VSTATUS

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
This Spec, Section 13.1

+                  

+
This Spec, Section 14.1

 

 

               

@@ -3713,26 +3755,26 @@ 

 
 
 

-

+

       

-17. Acknowledgements
+18. Acknowledgements
       

-

-
The authors would like to thank the members of the Calendaring and Scheduling Consortium technical committees and the following individuals for contributing their ideas, support and comments:

+

+
The authors would like to thank the members of the Calendaring and Scheduling Consortium technical committees and the following individuals for contributing their ideas, support and comments:

 

-

-
John Chaffee, Marten Gajda, Ken Murchison

+

+
John Chaffee, Marten Gajda, Ken Murchison

 

-

-
The authors would also like to thank CalConnect, the Calendaring and
-Scheduling Consortium, for advice with this specification.

+

+
The authors would also like to thank CalConnect, the Calendaring and
+Scheduling Consortium, for advice with this specification.

 

 

 

 

-

+

       

-18. Normative References
+19. Normative References
       

 

 
[RFC2119]

@@ -3775,9 +3817,9 @@ 

 

 

 

-

+

       

-19. Informative References
+20. Informative References
       

 

 
[BPMN]

diff --git a/ical-tasks/generated/draft-ietf-calext-ical-tasks.rfc.xml b/ical-tasks/generated/draft-ietf-calext-ical-tasks.rfc.xml
index 88e2db4..6df2a58 100644
--- a/ical-tasks/generated/draft-ietf-calext-ical-tasks.rfc.xml
+++ b/ical-tasks/generated/draft-ietf-calext-ical-tasks.rfc.xml
@@ -434,24 +434,55 @@ within a calendar (see ).
 A new property, TASK-MODE, is introduced to instruct servers to apply
 automated operations for changing the status of a task.
 

+

+    
Modifications to Calendar Components
+
+The following changes to the syntax defined in iCalendar 
+are made here. New elements are defined in subsequent sections.
+
+
+
 

     
New Parameter Values
 
 
Redefined VTODO Participant Status
 
-Participant status parameter type values are defined in
+Participant status parameter type values are defined in
 .  This specification redefines that type
 to include the new value FAILED for VTODO iCalendar components.
 
-
Format Definition
This property parameter is extended by the following notation:
+
Format Definition
This property parameter is extended by the following notation:
 

 
-
+
 
 
-
Example

+
Example

 
-
 
 

@@ -460,66 +491,66 @@ to include the new value FAILED for VTODO iCalendar components.
 
 
Estimated Duration
 
-
Property Name
ESTIMATED-DURATION
-
Purpose
This property specifies the estimated positive duration of time the corresponding task will take to complete.
-
Value Type
DURATION
-
Property Parameters
IANA and non-standard property parameters can be specified on this property.
-
Conformance
This property can be specified in "VTODO" calendar components.
-
Format Definition
This property is defined by the following notation:
+
Property Name
ESTIMATED-DURATION
+
Purpose
This property specifies the estimated positive duration of time the corresponding task will take to complete.
+
Value Type
DURATION
+
Property Parameters
IANA and non-standard property parameters can be specified on this property.
+
Conformance
This property can be specified in "VTODO" calendar components.
+
Format Definition
This property is defined by the following notation:
 

 
-
 
 
-
Description
In a "VTODO" calendar component the property MAY be used to specify the estimated duration for the to-do, with or without an explicit time window in which the event should be started and completed.  When present, DTSTART and DUE/DURATION represent the window in which the task can be performed. ESTIMATED-DURATION SHOULD be passed from ORGANIZER to ATTENDEE in iTIP  messages.
-
Example
The following is an example of this property that estimates the duration of a task to be one hour:
+
Description
In a "VTODO" calendar component the property MAY be used to specify the estimated duration for the to-do, with or without an explicit time window in which the event should be started and completed.  When present, DTSTART and DUE/DURATION represent the window in which the task can be performed. ESTIMATED-DURATION SHOULD be passed from ORGANIZER to ATTENDEE in iTIP  messages.
+
Example
The following is an example of this property that estimates the duration of a task to be one hour:
 

 
-
+
 
 

 
 
Reason
 
-
Property name
REASON
-
Purpose
To indicate the reason for a status change or change of attendee participation status.
-
Value Type
URI
-
Property Parameters
IANA and non-standard property parameters can be specified on this property.
-
Conformance
This property can be specified in "VSTATUS" and PARTICIPANT calendar components.
-
Format Definition
This property is defined by the following notation:
+
Property name
REASON
+
Purpose
To indicate the reason for a status change or change of attendee participation status.
+
Value Type
URI
+
Property Parameters
IANA and non-standard property parameters can be specified on this property.
+
Conformance
This property can be specified in "VSTATUS" and PARTICIPANT calendar components.
+
Format Definition
This property is defined by the following notation:
 

 
-
 
 
-
Description
This property allows the change in status of a
+
Description
This property allows the change in status of a
 task or participant status to be qualified by the reason for the change
 with a codified reason. Typically, reasons are defined within the
 context of the task type and therefore SHOULD include the name-space
 of the authority defining the task.
 
Example

 
-
+
 
 

 
 
Sub-State
 
-
Property name
SUBSTATE
-
Purpose
To provide additional granularity of task status for e.g.
+
Property name
SUBSTATE
+
Purpose
To provide additional granularity of task status for e.g.
 IN-PROCESS.
-
Value Type
TEXT
-
Property Parameters
IANA and non-standard property parameters can be specified on this property.
-
Conformance
This property can be specified in a "VSTATUS" calendar component.
-
Format Definition
This property is defined by the following notation:
+
Value Type
TEXT
+
Property Parameters
IANA and non-standard property parameters can be specified on this property.
+
Conformance
This property can be specified in a "VSTATUS" calendar component.
+
Format Definition
This property is defined by the following notation:
 

 
-
 
 
-
Description
The sub-state property allows additional qualification
+
Description
The sub-state property allows additional qualification
 and granularity of states to be recorded, in particular for the
 IN-PROCESS state. It allows individual sub-states to be recorded
 without the need to define and publish a sub-task associated with a
@@ -542,7 +573,7 @@ This property also allows parallel states to be expressed e.g. that a
 task has been suspended at whatever state it has reached.
 
Example

 
-
 
 
Task Mode
 
-
Property Name
TASK-MODE
-
Purpose
This property specifies automatic operations that servers
+
Property Name
TASK-MODE
+
Purpose
This property specifies automatic operations that servers
 acting on behalf of the organizer apply to tasks based on changes in
 attendee status (PARTSTAT).
-
Value Type
TEXT
-
Property Parameters
IANA and non-standard property parameters can be specified on this property.
-
Conformance
This property can be specified zero or more times in a "VTODO" calendar component.
-
Format Definition
This property is defined by the following notation:
+
Value Type
TEXT
+
Property Parameters
IANA and non-standard property parameters can be specified on this property.
+
Conformance
This property can be specified zero or more times in a "VTODO" calendar component.
+
Format Definition
This property is defined by the following notation:
 

 
-
 
 
-
Description
In a "VTODO" calendar component this property MAY be
+
Description
In a "VTODO" calendar component this property MAY be
 used to indicate to servers how they can automatically change the
 state of the task based on iTIP replies from Attendees. For example,
 the server can automatically set the overall task status to COMPLETED
@@ -591,42 +622,42 @@ or the server could mark the task as FAILED if its DUE date passes
 without it being completed. TASK-MODE processing is performed on the organizer's copy of the task.
 

 
-To set the status, add a VSTATUS component as specified in .
+To set the status, add a VSTATUS component as specified in .
 
-The property value is a list of one or more IANA registered tokens that defines modes to be used for the task. This specification defines three modes which are described in the following subsections.
+The property value is a list of one or more IANA registered tokens that defines modes to be used for the task. This specification defines three modes which are described in the following subsections.
 
-
Examples

+
Examples

 
-
 
 
-
AUTOMATIC-COMPLETION Task Mode
The task mode value "AUTOMATIC-COMPLETION" indicates to the server
+
AUTOMATIC-COMPLETION Task Mode
The task mode value "AUTOMATIC-COMPLETION" indicates to the server
 that it can change the "VTODO" component's status to "COMPLETED" as
 soon as all ATTENDEEs in the task have replied with a "PARTSTAT"
 parameter set to "COMPLETED".
 

 
-
AUTOMATIC-FAILURE Task Mode
The task mode value "AUTOMATIC-FAILURE" indicates to the server that
+
AUTOMATIC-FAILURE Task Mode
The task mode value "AUTOMATIC-FAILURE" indicates to the server that
 it SHOULD change the "VTODO" component's status to "FAILED" if either:
-
  1. the PARTSTAT of one ATTENDEE is set to FAILED; or
    2. 
+
    1. the PARTSTAT of one ATTENDEE is set to FAILED; or
      2. 
 
    2. the current time is past the effective due date of the component and the task has not yet been completed.
      3. 
 
    
 

 
-

@@ -635,14 +666,14 @@ the client that it will be managing the status.
 
 
Updated DURATION Property definition
 
- section 3.6.2 introduced a constraint on the duration property requiring
+ section 3.6.2 introduced a constraint on the duration property requiring
 that a DURATION MUST be accompanied by a DTSTART.
 This constraint is dropped reverting to the situation as specified
 previously.
 
-Thus the text:
+Thus the text:
 
-
                   ; the same 'todoprop'.]]>
 
 
-is replaced by
+is replaced by
 
-
 
 
-This allows a VTODO to only have a DURATION property.
+This allows a VTODO to only have a DURATION property.
 
-Furthermore, the following text:
+Furthermore, the following text:
 
-
 
 
-is replaced by
+is replaced by
 
-
 
@@ -676,36 +707,36 @@ previously.
 
 
Redefined STATUS Property
 
-The Status property is defined in . This
+The Status property is defined in . This
 specification extends that property to include new values
 associated with VTODO iCalendar components (See Appendix A for
 examples of the task state lifecycle).
 
-
Format Definition
The "STATUS" property parameter list is augmented
+
Format Definition
The "STATUS" property parameter list is augmented
 as follows:
 

 
-
 
 
-Description:
+Description:
 
-PENDING - A to-do has been created and accepted but has not yet
+PENDING - A to-do has been created and accepted but has not yet
 started and is ready
 to start subject to other dependencies (e.g. preceding task or
 DTSTART). This is the default state.
 
-FAILED - to-do has failed and may need some follow-up from the
+FAILED - to-do has failed and may need some follow-up from the
 organizer to re-schedule or cancel
 
-Example: The following is an example of this property for a "VTODO"
+Example: The following is an example of this property for a "VTODO"
 calendar component:
 
-
+
 
 

 

@@ -713,25 +744,25 @@ calendar component:
 
 
Status Component
 
-
Component Name
VSTATUS
-
Purpose
This component allows information to be
+
Component Name
VSTATUS
+
Purpose
This component allows information to be
 associated with a status, for example comments and date stamps.
-
Conformance
This component can be specified multiple times in
+
Conformance
This component can be specified multiple times in
 any calendar component.
-
Description
This component provides a way for multiple date-stamped
+
Description
This component provides a way for multiple date-stamped
 statuses to be associated with a component such as a participant, task or event.
 

 
-This component may be added to the  PARTICIPANT component
+This component may be added to the  PARTICIPANT component
 to allow participants in a task to specify their own status.
 
-For backwards compatibility, when a VSTATUS component is added the
+For backwards compatibility, when a VSTATUS component is added the
  STATUS property MUST be set on the parent component.
 
-
Format Definition
This component is defined by the following notation:
+
Format Definition
This component is defined by the following notation:
 

 
-
 
 
-
Examples

+
Examples

 
-
 

     
CalDAV Support for Task Mode
 
-The CalDAV  calendar access protocol allows clients and servers to exchange iCalendar data. With the introduction of the "TASK-MODE" property in this specification, different automated task management behaviours may be delegated to the server by the Task Organizer depending upon the value of "TASK-MODE".
+The CalDAV  calendar access protocol allows clients and servers to exchange iCalendar data. With the introduction of the "TASK-MODE" property in this specification, different automated task management behaviours may be delegated to the server by the Task Organizer depending upon the value of "TASK-MODE".
 
-In order for a CalDAV client to know what task modes are available, a CalDAV server advertises a CALDAV:supported-task-mode-set WebDAV property on calendar home or calendar collections if it supports the use of the "TASK-MODE" property as described in this specification.  The server can advertise a specific set of supported task modes by including one or more CALDAV:supported-task-mode XML elements within the CALDAV:supported-task-mode-set XML element. If no CALDAV:supported-task-mode XML elements are included in the WebDAV property, then clients can try any task mode, but need to be prepared for a failure when attempting to store the calendar data.
+In order for a CalDAV client to know what task modes are available, a CalDAV server advertises a CALDAV:supported-task-mode-set WebDAV property on calendar home or calendar collections if it supports the use of the "TASK-MODE" property as described in this specification.  The server can advertise a specific set of supported task modes by including one or more CALDAV:supported-task-mode XML elements within the CALDAV:supported-task-mode-set XML element. If no CALDAV:supported-task-mode XML elements are included in the WebDAV property, then clients can try any task mode, but need to be prepared for a failure when attempting to store the calendar data.
 
-Clients MUST NOT attempt to store iCalendar data containing "TASK-MODE" elements if the CALDAV:supported-task-mode-set WebDAV property is not advertised by the server.
+Clients MUST NOT attempt to store iCalendar data containing "TASK-MODE" elements if the CALDAV:supported-task-mode-set WebDAV property is not advertised by the server.
 
-The server SHOULD return an HTTP 403 response with a DAV:error element containing a CALDAV:supported-task-mode XML element, if a client attempts to store iCalendar data with an "TASK-MODE" element value not supported by the server.
+The server SHOULD return an HTTP 403 response with a DAV:error element containing a CALDAV:supported-task-mode XML element, if a client attempts to store iCalendar data with an "TASK-MODE" element value not supported by the server.
 
-It is possible for a "TASK-MODE" value to be present in calendar data on the server being accessed by a client that does not support the "TASK-MODE" property. It is expected that existing clients, unaware of "TASK-MODE", will fail gracefully by ignoring the calendar property.
+It is possible for a "TASK-MODE" value to be present in calendar data on the server being accessed by a client that does not support the "TASK-MODE" property. It is expected that existing clients, unaware of "TASK-MODE", will fail gracefully by ignoring the calendar property.
 
 
CALDAV:supported-task-mode-set Property
 
-
Name
supported-task-mode-set
-
Namespace
urn:ietf:params:xml:ns:caldav
-
Purpose
Enumerates the set of supported iCalendar "TASK-MODE" element values supported by the server.
-
Protected
This property MUST be protected and SHOULD NOT be returned by a PROPFIND allprop request (as defined in Section 14.2 of ).
-
Description
See above.
+
Name
supported-task-mode-set
+
Namespace
urn:ietf:params:xml:ns:caldav
+
Purpose
Enumerates the set of supported iCalendar "TASK-MODE" element values supported by the server.
+
Protected
This property MUST be protected and SHOULD NOT be returned by a PROPFIND allprop request (as defined in Section 14.2 of ).
+
Description
See above.
 
Definition

 
-
+
 
 ]]>
 
 
-
Example

+
Example

 
-
+
   AUTOMATIC-COMPLETION
   AUTOMATIC-FAILURE
   SERVER
@@ -805,147 +836,147 @@ uppercase preferred -->]]>
 

     
Security Considerations
 
-This specification introduces no new security considerations beyond those identified in ,  and .
+This specification introduces no new security considerations beyond those identified in ,  and .
 

     
IANA Considerations
 
 
New and updated iCalendar Elements Registration
 
-This specification updates  by adding and updating
+This specification updates  by adding and updating
 a number of elements. The procedures and templates specified in
 
 
 
Initialization of the Status registry
 
-This specification updates  by adding a Status value registry to the iCalendar Elements registry and initializing it as per .
-
-

             
 Table 7:
@@ -3620,86 +3662,86 @@ 

             

               

                 
-                  

-
ESTIMATED_DURATION

+                  

+
ESTIMATED_DURATION

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
This Spec, Section 11.1

+                  

+
This Spec, Section 12.1

 

 

               

               

                 
-                  

-
REASON

+                  

+
REASON

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
This Spec, Section 11.2

+                  

+
This Spec, Section 12.2

 

 

               

               

                 
-                  

-
SUBSTATE

+                  

+
SUBSTATE

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
This Spec, Section 11.3

+                  

+
This Spec, Section 12.3

 

 

               

               

                 
-                  

-
STATUS

+                  

+
STATUS

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
This Spec, Section 12.2

+                  

+
This Spec, Section 13.2

 

 

               

               

                 
-                  

-
TASK-MODE

+                  

+
TASK-MODE

 

 

                 
-                  

-
Current

+                  

+
Current

 

 

                 
-                  

-
This Spec, Section 11.4

+                  

+
This Spec, Section 12.4

 

 

               
Initial Status Value Registry
NameStatusReference
CANCELLED
-Current
-
-
COMPLETED
-Current
-
-
CONFIRMED
-Current
-
-
DRAFT
-Current
-
-
FINAL
-Current
-
-
IN-PROCESS
-Current
-
-
NEEDS-ACTION
-Current
-
-
TENTATIVE
-Current
-
+This specification updates  by adding a Status value registry to the iCalendar Elements registry and initializing it as per .
+
+Initial Status Value Registry
NameStatusReference
CANCELLED
+Current
+
+
COMPLETED
+Current
+
+
CONFIRMED
+Current
+
+
DRAFT
+Current
+
+
FINAL
+Current
+
+
IN-PROCESS
+Current
+
+
NEEDS-ACTION
+Current
+
+
TENTATIVE
+Current
+
 

 
 
 
Update of the Status registry
 
-This specification further updates the Status registry with additional values defined in this document.
+This specification further updates the Status registry with additional values defined in this document.
 
-Updated Status Value Registry
ValueStatusReference
PENDING
-Current
-This Spec, 
-
FAILED
-Current
-This Spec, 
+Updated Status Value Registry
ValueStatusReference
PENDING
+Current
+This Spec, 
+
FAILED
+Current
+This Spec, 
 

 
 
 
Sub-State value registry
 
-The following table has been used to initialize the Sub-State registry.
-
-Sub-State registry
SubstateStatusReference
OK
-Current
-This Spec, 
-
ERROR
-Current
-This Spec, 
-
SUSPENDED
-Current
-This Spec, 
+The following table has been used to initialize the Sub-State registry.
+
+Sub-State registry
SubstateStatusReference
OK
+Current
+This Spec, 
+
ERROR
+Current
+This Spec, 
+
SUSPENDED
+Current
+This Spec, 
 

 
 
 
Task Mode value registry
 
-The following table has been used to initialize the Task Mode registry.
-
-Task Mode Value Registry
Task ModeStatusReference
AUTOMATIC-COMPLETION
-Current
-This Spec, 
-
AUTOMATIC-FAILURE
-Current
-This Spec,  
-
CLIENT
-Current
-This Spec,  
-
SERVER
-Current
-This Spec,  
+The following table has been used to initialize the Task Mode registry.
+
+Task Mode Value Registry
Task ModeStatusReference
AUTOMATIC-COMPLETION
+Current
+This Spec, 
+
AUTOMATIC-FAILURE
+Current
+This Spec,  
+
CLIENT
+Current
+This Spec,  
+
SERVER
+Current
+This Spec,  
 

 
 
 
Participation Statuses registry
 
-The following table has been used to update the Participation Statuses registry.
+The following table has been used to update the Participation Statuses registry.
 
-Participation Statuses Registry
ValueStatusReference
FAILED
-Current
-This Spec, 
+Participation Statuses Registry
ValueStatusReference
FAILED
+Current
+This Spec, 
 

 
 
 
Components Registry
 
-The following table has been used to update the Components registry
+The following table has been used to update the Components registry
 defined in .
 
-Updated Components Registry
ComponentStatusReference
VSTATUS
-Current
-This Spec, 
+Updated Components Registry
ComponentStatusReference
VSTATUS
+Current
+This Spec, 
 

 
 
 
Properties registry
 
-The following table has been used to update the Properties registry
+The following table has been used to update the Properties registry
 defined in .
 
-Updated Properties Registry
PropertyStatusReference
ESTIMATED_DURATION
-Current
-This Spec, 
-
REASON
-Current
-This Spec, 
-
SUBSTATE
-Current
-This Spec, 
-
STATUS
-Current
-This Spec, 
-
TASK-MODE
-Current
-This Spec, 
+Updated Properties Registry
PropertyStatusReference
ESTIMATED_DURATION
+Current
+This Spec, 
+
REASON
+Current
+This Spec, 
+
SUBSTATE
+Current
+This Spec, 
+
STATUS
+Current
+This Spec, 
+
TASK-MODE
+Current
+This Spec, 
 

 
 
 
     
Acknowledgements
 
-The authors would like to thank the members of the Calendaring and Scheduling Consortium technical committees and the following individuals for contributing their ideas, support and comments:
+The authors would like to thank the members of the Calendaring and Scheduling Consortium technical committees and the following individuals for contributing their ideas, support and comments:
 
-John Chaffee, Marten Gajda, Ken Murchison
+John Chaffee, Marten Gajda, Ken Murchison
 
-The authors would also like to thank CalConnect, the Calendaring and
+The authors would also like to thank CalConnect, the Calendaring and
 Scheduling Consortium, for advice with this specification.
 

   
diff --git a/ical-tasks/generated/draft-ietf-calext-ical-tasks.txt b/ical-tasks/generated/draft-ietf-calext-ical-tasks.txt
index cc21d1a..e376dc2 100644
--- a/ical-tasks/generated/draft-ietf-calext-ical-tasks.txt
+++ b/ical-tasks/generated/draft-ietf-calext-ical-tasks.txt
@@ -6,7 +6,7 @@ calext                                                        A. Apthorp
 Internet-Draft                                               DHL Express
 Updates: RFC5545 (if approved)                               M. Douglass
 Intended status: Standards Track            Bedework Commercial Services
-Expires: 14 October 2024                                   12 April 2024
+Expires: 15 October 2024                                   13 April 2024
 
 
                       Task Extensions to iCalendar
@@ -38,7 +38,7 @@ Status of This Memo
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on 14 October 2024.
+   This Internet-Draft will expire on 15 October 2024.
 
 Copyright Notice
 
@@ -53,7 +53,7 @@ Copyright Notice
 
 
 
-Apthorp & Douglass       Expires 14 October 2024                [Page 1]
+Apthorp & Douglass       Expires 15 October 2024                [Page 1]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -85,46 +85,47 @@ Table of Contents
      9.3.  Comments associated to reasons and status changes . . . .  12
      9.4.  Task Alerts and Notifications . . . . . . . . . . . . . .  13
      9.5.  Automated Status Changes  . . . . . . . . . . . . . . . .  14
-   10. New Parameter Values  . . . . . . . . . . . . . . . . . . . .  14
-     10.1.  Redefined VTODO Participant Status . . . . . . . . . . .  14
-   11. New Properties  . . . . . . . . . . . . . . . . . . . . . . .  14
-     11.1.  Estimated Duration . . . . . . . . . . . . . . . . . . .  14
-     11.2.  Reason . . . . . . . . . . . . . . . . . . . . . . . . .  15
-     11.3.  Sub-State  . . . . . . . . . . . . . . . . . . . . . . .  16
-     11.4.  Task Mode  . . . . . . . . . . . . . . . . . . . . . . .  17
-   12. Property Extensions and Clarifications  . . . . . . . . . . .  19
-     12.1.  Updated DURATION Property definition . . . . . . . . . .  19
-     12.2.  Redefined STATUS Property  . . . . . . . . . . . . . . .  19
-   13. New Components  . . . . . . . . . . . . . . . . . . . . . . .  20
-     13.1.  Status Component . . . . . . . . . . . . . . . . . . . .  20
-   14. CalDAV Support for Task Mode  . . . . . . . . . . . . . . . .  21
-     14.1.  CALDAV:supported-task-mode-set Property  . . . . . . . .  22
-   15. Security Considerations . . . . . . . . . . . . . . . . . . .  23
-   16. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  23
-     16.1.  New and updated iCalendar Elements Registration  . . . .  23
-       16.1.1.  Initialization of the Status registry  . . . . . . .  23
-       16.1.2.  Update of the Status registry  . . . . . . . . . . .  24
-       16.1.3.  Sub-State value registry . . . . . . . . . . . . . .  24
-       16.1.4.  Task Mode value registry . . . . . . . . . . . . . .  25
-
-
-
-Apthorp & Douglass       Expires 14 October 2024                [Page 2]
+   10. Modifications to Calendar Components  . . . . . . . . . . . .  14
+   11. New Parameter Values  . . . . . . . . . . . . . . . . . . . .  14
+     11.1.  Redefined VTODO Participant Status . . . . . . . . . . .  15
+   12. New Properties  . . . . . . . . . . . . . . . . . . . . . . .  15
+     12.1.  Estimated Duration . . . . . . . . . . . . . . . . . . .  15
+     12.2.  Reason . . . . . . . . . . . . . . . . . . . . . . . . .  16
+     12.3.  Sub-State  . . . . . . . . . . . . . . . . . . . . . . .  16
+     12.4.  Task Mode  . . . . . . . . . . . . . . . . . . . . . . .  17
+   13. Property Extensions and Clarifications  . . . . . . . . . . .  19
+     13.1.  Updated DURATION Property definition . . . . . . . . . .  19
+     13.2.  Redefined STATUS Property  . . . . . . . . . . . . . . .  20
+   14. New Components  . . . . . . . . . . . . . . . . . . . . . . .  21
+     14.1.  Status Component . . . . . . . . . . . . . . . . . . . .  21
+   15. CalDAV Support for Task Mode  . . . . . . . . . . . . . . . .  22
+     15.1.  CALDAV:supported-task-mode-set Property  . . . . . . . .  23
+   16. Security Considerations . . . . . . . . . . . . . . . . . . .  24
+   17. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  24
+     17.1.  New and updated iCalendar Elements Registration  . . . .  24
+       17.1.1.  Initialization of the Status registry  . . . . . . .  24
+       17.1.2.  Update of the Status registry  . . . . . . . . . . .  25
+       17.1.3.  Sub-State value registry . . . . . . . . . . . . . .  25
+
+
+
+Apthorp & Douglass       Expires 15 October 2024                [Page 2]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
-       16.1.5.  Participation Statuses registry  . . . . . . . . . .  25
-       16.1.6.  Components Registry  . . . . . . . . . . . . . . . .  25
-       16.1.7.  Properties registry  . . . . . . . . . . . . . . . .  26
-   17. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  26
-   18. Normative References  . . . . . . . . . . . . . . . . . . . .  26
-   19. Informative References  . . . . . . . . . . . . . . . . . . .  27
-   Appendix A.  Examples of Task State Lifecycle . . . . . . . . . .  28
-     A.1.  Simple Case Status Change . . . . . . . . . . . . . . . .  28
-     A.2.  Example for multiple Attendees  . . . . . . . . . . . . .  29
-     A.3.  Example of Failure  . . . . . . . . . . . . . . . . . . .  30
-   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  30
+       17.1.4.  Task Mode value registry . . . . . . . . . . . . . .  26
+       17.1.5.  Participation Statuses registry  . . . . . . . . . .  26
+       17.1.6.  Components Registry  . . . . . . . . . . . . . . . .  26
+       17.1.7.  Properties registry  . . . . . . . . . . . . . . . .  27
+   18. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  27
+   19. Normative References  . . . . . . . . . . . . . . . . . . . .  27
+   20. Informative References  . . . . . . . . . . . . . . . . . . .  28
+   Appendix A.  Examples of Task State Lifecycle . . . . . . . . . .  29
+     A.1.  Simple Case Status Change . . . . . . . . . . . . . . . .  29
+     A.2.  Example for multiple Attendees  . . . . . . . . . . . . .  30
+     A.3.  Example of Failure  . . . . . . . . . . . . . . . . . . .  31
+   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  31
 
 1.  Introduction
 
@@ -164,8 +165,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-
-Apthorp & Douglass       Expires 14 October 2024                [Page 3]
+Apthorp & Douglass       Expires 15 October 2024                [Page 3]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -221,7 +221,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024                [Page 4]
+Apthorp & Douglass       Expires 15 October 2024                [Page 4]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -277,7 +277,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024                [Page 5]
+Apthorp & Douglass       Expires 15 October 2024                [Page 5]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -333,7 +333,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024                [Page 6]
+Apthorp & Douglass       Expires 15 October 2024                [Page 6]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -389,7 +389,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024                [Page 7]
+Apthorp & Douglass       Expires 15 October 2024                [Page 7]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -445,7 +445,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024                [Page 8]
+Apthorp & Douglass       Expires 15 October 2024                [Page 8]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -501,7 +501,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024                [Page 9]
+Apthorp & Douglass       Expires 15 October 2024                [Page 9]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -557,7 +557,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024               [Page 10]
+Apthorp & Douglass       Expires 15 October 2024               [Page 10]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -571,7 +571,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
    properties define a "window" within which a task has to be performed.
    However, there is currently no way to indicate how long the task is
    expected to take.  This document defines a new property, in
-   Section 11.1 ESTIMATED-DURATION, to allow the estimated time that a
+   Section 12.1 ESTIMATED-DURATION, to allow the estimated time that a
    task should take to be specified separately from the deadlines for
    starting and finishing a task.  This supports time planning by
    enabling calendar user agents to display when tasks should occur and
@@ -604,7 +604,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 9.1.  Improved granularity in status reporting information
 
    This document defines a new "VSTATUS" component (see section
-   Section 13.1) that can be used to group related information about the
+   Section 14.1) that can be used to group related information about the
    status of the task.  This might include information on why (REASON)
    and when (DTSTAMP) a status has changed.  In addition, new status
    values are specified to provide for task suspension, failure and
@@ -613,7 +613,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024               [Page 11]
+Apthorp & Douglass       Expires 15 October 2024               [Page 11]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -669,7 +669,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024               [Page 12]
+Apthorp & Douglass       Expires 15 October 2024               [Page 12]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -725,7 +725,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024               [Page 13]
+Apthorp & Douglass       Expires 15 October 2024               [Page 13]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -742,9 +742,51 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
    A new property, TASK-MODE, is introduced to instruct servers to apply
    automated operations for changing the status of a task.
 
-10.  New Parameter Values
+10.  Modifications to Calendar Components
+
+   The following changes to the syntax defined in iCalendar [RFC5545]
+   are made here.  New elements are defined in subsequent sections.
+
+   ; Addition of VSTATUS as a valid component for VEVENT
+   eventc     = "BEGIN" ":" "VEVENT" CRLF
+                eventprop *alarmc *participantc *locationc *resourcec *statusc
+                "END" ":" "VEVENT" CRLF
+
+   ; Addition of VSTATUS as a valid component for VTODO
+   todoc      = "BEGIN" ":" "VTODO" CRLF
+                todoprop *alarmc *participantc *locationc *resourcec *statusc
+                "END" ":" "VTODO" CRLF
+
+   ; Addition of properties ESTIMATED-DURATION and TASK-MODE to VTODO
+   todoprop =/ est-duration /
+               task-mode
+
+   ; Addition of VSTATUS as a valid component for VJOURNAL
+   journalc   = "BEGIN" ":" "VJOURNAL" CRLF
+                 jourprop *statusc
+                 "END" ":" "VJOURNAL" CRLF
+
+
+   ; Addition of VSTATUS as a valid component for VFREEBUSY
+   freebusyc  = "BEGIN" ":" "VFREEBUSY" CRLF
+                fbprop *participantc *locationc *resourcec *statusc
+                "END" ":" "VFREEBUSY" CRLF
 
-10.1.  Redefined VTODO Participant Status
+11.  New Parameter Values
+
+
+
+
+
+
+
+
+Apthorp & Douglass       Expires 15 October 2024               [Page 14]
+
+Internet-Draft        Task Extensions to iCalendar            April 2024
+
+
+11.1.  Redefined VTODO Participant Status
 
    Participant status parameter type values are defined in
    Section 3.2.12 of [RFC5545].  This specification redefines that type
@@ -760,9 +802,9 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
    ATTENDEE;REASON="https://example.com/reason/not-enough-time";
     PARTSTAT=FAILED:mailto:jsmith@example.com
 
-11.  New Properties
+12.  New Properties
 
-11.1.  Estimated Duration
+12.1.  Estimated Duration
 
    Property Name  ESTIMATED-DURATION
 
@@ -778,14 +820,6 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
       components.
 
    Format Definition  This property is defined by the following
-
-
-
-Apthorp & Douglass       Expires 14 October 2024               [Page 14]
-
-Internet-Draft        Task Extensions to iCalendar            April 2024
-
-
       notation:
 
    est-duration  = "ESTIMATED-DURATION" durparam ":" dur-value CRLF
@@ -801,12 +835,19 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
       SHOULD be passed from ORGANIZER to ATTENDEE in iTIP [RFC5546]
       messages.
 
+
+
+Apthorp & Douglass       Expires 15 October 2024               [Page 15]
+
+Internet-Draft        Task Extensions to iCalendar            April 2024
+
+
    Example  The following is an example of this property that estimates
       the duration of a task to be one hour:
 
    ESTIMATED-DURATION:PT1H
 
-11.2.  Reason
+12.2.  Reason
 
    Property name  REASON
 
@@ -834,19 +875,11 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
       context of the task type and therefore SHOULD include the name-
       space of the authority defining the task.
 
-
-
-
-Apthorp & Douglass       Expires 14 October 2024               [Page 15]
-
-Internet-Draft        Task Extensions to iCalendar            April 2024
-
-
    Example
 
    REASON:https://example.com/reason/delivered-on-time
 
-11.3.  Sub-State
+12.3.  Sub-State
 
    Property name  SUBSTATE
 
@@ -858,6 +891,13 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
    Property Parameters  IANA and non-standard property parameters can be
       specified on this property.
 
+
+
+Apthorp & Douglass       Expires 15 October 2024               [Page 16]
+
+Internet-Draft        Task Extensions to iCalendar            April 2024
+
+
    Conformance  This property can be specified in a "VSTATUS" calendar
       component.
 
@@ -888,16 +928,6 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
    Example
 
-
-
-
-
-
-Apthorp & Douglass       Expires 14 October 2024               [Page 16]
-
-Internet-Draft        Task Extensions to iCalendar            April 2024
-
-
    BEGIN:VSTATUS
    STATUS:FAILED
    REASON:https://example.com/reason/no-one-home
@@ -910,11 +940,20 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
    SUBSTATE:SUSPENDED
    END:VSTATUS
 
-11.4.  Task Mode
+12.4.  Task Mode
 
    Property Name  TASK-MODE
 
    Purpose  This property specifies automatic operations that servers
+
+
+
+
+Apthorp & Douglass       Expires 15 October 2024               [Page 17]
+
+Internet-Draft        Task Extensions to iCalendar            April 2024
+
+
       acting on behalf of the organizer apply to tasks based on changes
       in attendee status (PARTSTAT).
 
@@ -946,21 +985,13 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
       used to indicate to servers how they can automatically change the
       state of the task based on iTIP replies from Attendees.  For
       example, the server can automatically set the overall task status
-
-
-
-Apthorp & Douglass       Expires 14 October 2024               [Page 17]
-
-Internet-Draft        Task Extensions to iCalendar            April 2024
-
-
       to COMPLETED when every attendee has marked their own status
       (PARTSTAT) as COMPLETED, or the server could mark the task as
       FAILED if its DUE date passes without it being completed.  TASK-
       MODE processing is performed on the organizer's copy of the task.
 
    To set the status, add a VSTATUS component as specified in
-   Section 13.1.
+   Section 14.1.
 
    The property value is a list of one or more IANA registered tokens
    that defines modes to be used for the task.  This specification
@@ -972,6 +1003,13 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
    TASK-MODE:SERVER
    TASK-MODE:AUTOMATIC-FAILURE
 
+
+
+Apthorp & Douglass       Expires 15 October 2024               [Page 18]
+
+Internet-Draft        Task Extensions to iCalendar            April 2024
+
+
    AUTOMATIC-COMPLETION Task Mode  The task mode value "AUTOMATIC-
       COMPLETION" indicates to the server that it can change the "VTODO"
       component's status to "COMPLETED" as soon as all ATTENDEEs in the
@@ -1002,17 +1040,9 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
       The server can add this property to a "VTODO" component to
       indicate to the client that it will be managing the status.
 
+13.  Property Extensions and Clarifications
 
-
-
-Apthorp & Douglass       Expires 14 October 2024               [Page 18]
-
-Internet-Draft        Task Extensions to iCalendar            April 2024
-
-
-12.  Property Extensions and Clarifications
-
-12.1.  Updated DURATION Property definition
+13.1.  Updated DURATION Property definition
 
    [RFC5545] section 3.6.2 introduced a constraint on the duration
    property requiring that a DURATION MUST be accompanied by a DTSTART.
@@ -1028,6 +1058,14 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
                      ; then 'dtstart' MUST also appear in
                      ; the same 'todoprop'.
 
+
+
+
+Apthorp & Douglass       Expires 15 October 2024               [Page 19]
+
+Internet-Draft        Task Extensions to iCalendar            April 2024
+
+
    is replaced by
 
                      ; Either 'due' or 'duration' MAY appear in
@@ -1048,7 +1086,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
         properties specifies a to-do that will be associated
         with each successive calendar date, until it is completed.
 
-12.2.  Redefined STATUS Property
+13.2.  Redefined STATUS Property
 
    The Status property is defined in Section 3.8.1.11 of [RFC5545].
    This specification extends that property to include new values
@@ -1058,14 +1096,6 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
    Format Definition  The "STATUS" property parameter list is augmented
       as follows:
 
-
-
-
-Apthorp & Douglass       Expires 14 October 2024               [Page 19]
-
-Internet-Draft        Task Extensions to iCalendar            April 2024
-
-
    statvalue-todo = / "PENDING"    ;Indicates a to-do has been
                                    ;created and accepted, but has
                                    ; not yet started.
@@ -1084,11 +1114,19 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
    Example: The following is an example of this property for a "VTODO"
    calendar component:
 
+
+
+
+Apthorp & Douglass       Expires 15 October 2024               [Page 20]
+
+Internet-Draft        Task Extensions to iCalendar            April 2024
+
+
    STATUS:FAILED
 
-13.  New Components
+14.  New Components
 
-13.1.  Status Component
+14.1.  Status Component
 
    Component Name  VSTATUS
 
@@ -1117,7 +1155,25 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024               [Page 20]
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Apthorp & Douglass       Expires 15 October 2024               [Page 21]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -1153,7 +1209,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
    DTSTAMP:20220212T120000Z
    END:VSTATUS
 
-14.  CalDAV Support for Task Mode
+15.  CalDAV Support for Task Mode
 
    The CalDAV [RFC4791] calendar access protocol allows clients and
    servers to exchange iCalendar data.  With the introduction of the
@@ -1173,7 +1229,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024               [Page 21]
+Apthorp & Douglass       Expires 15 October 2024               [Page 22]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -1204,7 +1260,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
    of "TASK-MODE", will fail gracefully by ignoring the calendar
    property.
 
-14.1.  CALDAV:supported-task-mode-set Property
+15.1.  CALDAV:supported-task-mode-set Property
 
    Name  supported-task-mode-set
 
@@ -1229,7 +1285,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024               [Page 22]
+Apthorp & Douglass       Expires 15 October 2024               [Page 23]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -1243,20 +1299,20 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
      CLIENT
    
 
-15.  Security Considerations
+16.  Security Considerations
 
    This specification introduces no new security considerations beyond
    those identified in [RFC5545], [RFC5546] and [RFC4791].
 
-16.  IANA Considerations
+17.  IANA Considerations
 
-16.1.  New and updated iCalendar Elements Registration
+17.1.  New and updated iCalendar Elements Registration
 
    This specification updates [RFC5545] by adding and updating a number
    of elements.  The procedures and templates specified in Section 8.2
    of [RFC5545]
 
-16.1.1.  Initialization of the Status registry
+17.1.1.  Initialization of the Status registry
 
    This specification updates [RFC5545] by adding a Status value
    registry to the iCalendar Elements registry and initializing it as
@@ -1285,7 +1341,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024               [Page 23]
+Apthorp & Douglass       Expires 15 October 2024               [Page 24]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -1312,7 +1368,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
                   Table 1: Initial Status Value Registry
 
-16.1.2.  Update of the Status registry
+17.1.2.  Update of the Status registry
 
    This specification further updates the Status registry with
    additional values defined in this document.
@@ -1320,14 +1376,14 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
               +=========+=========+=========================+
               | Value   | Status  | Reference               |
               +=========+=========+=========================+
-              | PENDING | Current | This Spec, Section 12.2 |
+              | PENDING | Current | This Spec, Section 13.2 |
               +---------+---------+-------------------------+
-              | FAILED  | Current | This Spec, Section 12.2 |
+              | FAILED  | Current | This Spec, Section 13.2 |
               +---------+---------+-------------------------+
 
                    Table 2: Updated Status Value Registry
 
-16.1.3.  Sub-State value registry
+17.1.3.  Sub-State value registry
 
    The following table has been used to initialize the Sub-State
    registry.
@@ -1341,7 +1397,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024               [Page 24]
+Apthorp & Douglass       Expires 15 October 2024               [Page 25]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -1349,16 +1405,16 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
              +===========+=========+=========================+
              | Substate  | Status  | Reference               |
              +===========+=========+=========================+
-             | OK        | Current | This Spec, Section 11.3 |
+             | OK        | Current | This Spec, Section 12.3 |
              +-----------+---------+-------------------------+
-             | ERROR     | Current | This Spec, Section 11.3 |
+             | ERROR     | Current | This Spec, Section 12.3 |
              +-----------+---------+-------------------------+
-             | SUSPENDED | Current | This Spec, Section 11.3 |
+             | SUSPENDED | Current | This Spec, Section 12.3 |
              +-----------+---------+-------------------------+
 
                         Table 3: Sub-State registry
 
-16.1.4.  Task Mode value registry
+17.1.4.  Task Mode value registry
 
    The following table has been used to initialize the Task Mode
    registry.
@@ -1366,18 +1422,18 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
        +======================+=========+=========================+
        | Task Mode            | Status  | Reference               |
        +======================+=========+=========================+
-       | AUTOMATIC-COMPLETION | Current | This Spec, Section 11.4 |
+       | AUTOMATIC-COMPLETION | Current | This Spec, Section 12.4 |
        +----------------------+---------+-------------------------+
-       | AUTOMATIC-FAILURE    | Current | This Spec, Section 11.4 |
+       | AUTOMATIC-FAILURE    | Current | This Spec, Section 12.4 |
        +----------------------+---------+-------------------------+
-       | CLIENT               | Current | This Spec, Section 11.4 |
+       | CLIENT               | Current | This Spec, Section 12.4 |
        +----------------------+---------+-------------------------+
-       | SERVER               | Current | This Spec, Section 11.4 |
+       | SERVER               | Current | This Spec, Section 12.4 |
        +----------------------+---------+-------------------------+
 
                     Table 4: Task Mode Value Registry
 
-16.1.5.  Participation Statuses registry
+17.1.5.  Participation Statuses registry
 
    The following table has been used to update the Participation
    Statuses registry.
@@ -1385,19 +1441,19 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
               +========+=========+=========================+
               | Value  | Status  | Reference               |
               +========+=========+=========================+
-              | FAILED | Current | This Spec, Section 10.1 |
+              | FAILED | Current | This Spec, Section 11.1 |
               +--------+---------+-------------------------+
 
                  Table 5: Participation Statuses Registry
 
-16.1.6.  Components Registry
+17.1.6.  Components Registry
 
    The following table has been used to update the Components registry
    defined in Section 8.3.1 of [RFC5545].
 
 
 
-Apthorp & Douglass       Expires 14 October 2024               [Page 25]
+Apthorp & Douglass       Expires 15 October 2024               [Page 26]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -1405,12 +1461,12 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
              +===========+=========+=========================+
              | Component | Status  | Reference               |
              +===========+=========+=========================+
-             | VSTATUS   | Current | This Spec, Section 13.1 |
+             | VSTATUS   | Current | This Spec, Section 14.1 |
              +-----------+---------+-------------------------+
 
                     Table 6: Updated Components Registry
 
-16.1.7.  Properties registry
+17.1.7.  Properties registry
 
    The following table has been used to update the Properties registry
    defined in Section 8.3.2 of [RFC5545].
@@ -1418,20 +1474,20 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
         +====================+=========+=========================+
         | Property           | Status  | Reference               |
         +====================+=========+=========================+
-        | ESTIMATED_DURATION | Current | This Spec, Section 11.1 |
+        | ESTIMATED_DURATION | Current | This Spec, Section 12.1 |
         +--------------------+---------+-------------------------+
-        | REASON             | Current | This Spec, Section 11.2 |
+        | REASON             | Current | This Spec, Section 12.2 |
         +--------------------+---------+-------------------------+
-        | SUBSTATE           | Current | This Spec, Section 11.3 |
+        | SUBSTATE           | Current | This Spec, Section 12.3 |
         +--------------------+---------+-------------------------+
-        | STATUS             | Current | This Spec, Section 12.2 |
+        | STATUS             | Current | This Spec, Section 13.2 |
         +--------------------+---------+-------------------------+
-        | TASK-MODE          | Current | This Spec, Section 11.4 |
+        | TASK-MODE          | Current | This Spec, Section 12.4 |
         +--------------------+---------+-------------------------+
 
                    Table 7: Updated Properties Registry
 
-17.  Acknowledgements
+18.  Acknowledgements
 
    The authors would like to thank the members of the Calendaring and
    Scheduling Consortium technical committees and the following
@@ -1442,7 +1498,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
    The authors would also like to thank CalConnect, the Calendaring and
    Scheduling Consortium, for advice with this specification.
 
-18.  Normative References
+19.  Normative References
 
    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
               Requirement Levels", IETF, DOI 10.17487/RFC2119, BCP 14,
@@ -1453,7 +1509,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024               [Page 26]
+Apthorp & Douglass       Expires 15 October 2024               [Page 27]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -1495,7 +1551,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
               DOI 10.17487/RFC9253, RFC 9253, August 2022,
               .
 
-19.  Informative References
+20.  Informative References
 
    [BPMN]     "Business Process Model and Notation", OMG BPMN 2.0.2,
               January 2014,
@@ -1509,7 +1565,7 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024               [Page 27]
+Apthorp & Douglass       Expires 15 October 2024               [Page 28]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -1565,7 +1621,7 @@ A.1.  Simple Case Status Change
 
 
 
-Apthorp & Douglass       Expires 14 October 2024               [Page 28]
+Apthorp & Douglass       Expires 15 October 2024               [Page 29]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -1621,7 +1677,7 @@ A.2.  Example for multiple Attendees
 
 
 
-Apthorp & Douglass       Expires 14 October 2024               [Page 29]
+Apthorp & Douglass       Expires 15 October 2024               [Page 30]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -1677,7 +1733,7 @@ Authors' Addresses
 
 
 
-Apthorp & Douglass       Expires 14 October 2024               [Page 30]
+Apthorp & Douglass       Expires 15 October 2024               [Page 31]
 
 Internet-Draft        Task Extensions to iCalendar            April 2024
 
@@ -1733,4 +1789,4 @@ Internet-Draft        Task Extensions to iCalendar            April 2024
 
 
 
-Apthorp & Douglass       Expires 14 October 2024               [Page 31]
+Apthorp & Douglass       Expires 15 October 2024               [Page 32]
diff --git a/ical-tasks/generated/draft-ietf-calext-ical-tasks.xml b/ical-tasks/generated/draft-ietf-calext-ical-tasks.xml
index ae8006d..a404d34 100644
--- a/ical-tasks/generated/draft-ietf-calext-ical-tasks.xml
+++ b/ical-tasks/generated/draft-ietf-calext-ical-tasks.xml
@@ -503,26 +503,58 @@ automated operations for changing the status of a task.

 
 
 
+
+Modifications to Calendar Components
+
The following changes to the syntax defined in iCalendar 
+are made here. New elements are defined in subsequent sections.

+
+; Addition of VSTATUS as a valid component for VEVENT
+eventc     = "BEGIN" ":" "VEVENT" CRLF
+             eventprop *alarmc *participantc *locationc *resourcec *statusc
+             "END" ":" "VEVENT" CRLF
+
+; Addition of VSTATUS as a valid component for VTODO
+todoc      = "BEGIN" ":" "VTODO" CRLF
+             todoprop *alarmc *participantc *locationc *resourcec *statusc
+             "END" ":" "VTODO" CRLF
+
+; Addition of properties ESTIMATED-DURATION and TASK-MODE to VTODO
+todoprop =/ est-duration /
+            task-mode
+
+; Addition of VSTATUS as a valid component for VJOURNAL
+journalc   = "BEGIN" ":" "VJOURNAL" CRLF
+              jourprop *statusc
+              "END" ":" "VJOURNAL" CRLF
+
+
+; Addition of VSTATUS as a valid component for VFREEBUSY
+freebusyc  = "BEGIN" ":" "VFREEBUSY" CRLF
+             fbprop *participantc *locationc *resourcec *statusc
+             "END" ":" "VFREEBUSY" CRLF
+
+
+
 
 New Parameter Values
 
 Redefined VTODO Participant Status
-
Participant status parameter type values are defined in
+
Participant status parameter type values are defined in
 3.2.12.  This specification redefines that type
 to include the new value FAILED for VTODO iCalendar components.

 
-
Format Definition

-
This property parameter is extended by the following notation:

+
Format Definition

+
This property parameter is extended by the following notation:

 

 

 
-partstat-todo    =/ *("FAILED")  ; To-do cannot be completed
+partstat-todo    =/ *("FAILED")  ; To-do cannot be completed
 
 
-
Example

+
Example

 

 
-ATTENDEE;REASON="https://example.com/reason/not-enough-time";
+ATTENDEE;REASON="https://example.com/reason/not-enough-time";
  PARTSTAT=FAILED:mailto:jsmith@example.com
 
 
@@ -532,73 +564,73 @@ to include the new value FAILED for VTODO iCalendar components.

 New Properties
 
 Estimated Duration
-
Property Name

-
ESTIMATED-DURATION

+
Property Name

+
ESTIMATED-DURATION

 

 
Purpose

-
This property specifies the estimated positive duration of time the corresponding task will take to complete.

+
This property specifies the estimated positive duration of time the corresponding task will take to complete.

 

 
Value Type

-
DURATION

+
DURATION

 

 
Property Parameters

-
IANA and non-standard property parameters can be specified on this property.

+
IANA and non-standard property parameters can be specified on this property.

 

 
Conformance

-
This property can be specified in "VTODO" calendar components.

+
This property can be specified in "VTODO" calendar components.

 

 
Format Definition

-
This property is defined by the following notation:

+
This property is defined by the following notation:

 

 

 
-est-duration  = "ESTIMATED-DURATION" durparam ":" dur-value CRLF
+est-duration  = "ESTIMATED-DURATION" durparam ":" dur-value CRLF
                 ;consisting of a positive duration of time.
 
 durparam      = *(";" other-param)
 
 
-
Description

-
In a "VTODO" calendar component the property MAY be used to specify the estimated duration for the to-do, with or without an explicit time window in which the event should be started and completed.  When present, DTSTART and DUE/DURATION represent the window in which the task can be performed. ESTIMATED-DURATION SHOULD be passed from ORGANIZER to ATTENDEE in iTIP  messages.

+
Description

+
In a "VTODO" calendar component the property MAY be used to specify the estimated duration for the to-do, with or without an explicit time window in which the event should be started and completed.  When present, DTSTART and DUE/DURATION represent the window in which the task can be performed. ESTIMATED-DURATION SHOULD be passed from ORGANIZER to ATTENDEE in iTIP  messages.

 

 
Example

-
The following is an example of this property that estimates the duration of a task to be one hour:

+
The following is an example of this property that estimates the duration of a task to be one hour:

 

 

 
-ESTIMATED-DURATION:PT1H
+ESTIMATED-DURATION:PT1H
 
 
 
 
 Reason
-
Property name

-
REASON

+
Property name

+
REASON

 

 
Purpose

-
To indicate the reason for a status change or change of attendee participation status.

+
To indicate the reason for a status change or change of attendee participation status.

 

 
Value Type

-
URI

+
URI

 

 
Property Parameters

-
IANA and non-standard property parameters can be specified on this property.

+
IANA and non-standard property parameters can be specified on this property.

 

 
Conformance

-
This property can be specified in "VSTATUS" and PARTICIPANT calendar components.

+
This property can be specified in "VSTATUS" and PARTICIPANT calendar components.

 

 
Format Definition

-
This property is defined by the following notation:

+
This property is defined by the following notation:

 

 

 
-reason      = "REASON" reasonparam ":" uri CRLF
+reason      = "REASON" reasonparam ":" uri CRLF
 
 reasonparam = *(";" other-param)
 
 
-
Description

-
This property allows the change in status of a
+
Description

+
This property allows the change in status of a
 task or participant status to be qualified by the reason for the change
 with a codified reason. Typically, reasons are defined within the
 context of the task type and therefore SHOULD include the name-space
@@ -607,34 +639,34 @@ of the authority defining the task.

 
Example

 

 
-REASON:https://example.com/reason/delivered-on-time
+REASON:https://example.com/reason/delivered-on-time
 
 
 
 
 Sub-State
-
Property name

-
SUBSTATE

+
Property name

+
SUBSTATE

 

 
Purpose

-
To provide additional granularity of task status for e.g.
+
To provide additional granularity of task status for e.g.
 IN-PROCESS.

 

 
Value Type

-
TEXT

+
TEXT

 

 
Property Parameters

-
IANA and non-standard property parameters can be specified on this property.

+
IANA and non-standard property parameters can be specified on this property.

 

 
Conformance

-
This property can be specified in a "VSTATUS" calendar component.

+
This property can be specified in a "VSTATUS" calendar component.

 

 
Format Definition

-
This property is defined by the following notation:

+
This property is defined by the following notation:

 

 

 
-substate          = "SUBSTATE" substateparam ":" substatevalue CRLF
+substate          = "SUBSTATE" substateparam ":" substatevalue CRLF
 
 substateparam     = *(";" other-param)
 
@@ -648,8 +680,8 @@ substatevalue       = ("OK"        ; everything is fine(the default)
                      / iana-token) ; Other IANA-registered type
 
 
-
Description

-
The sub-state property allows additional qualification
+
Description

+
The sub-state property allows additional qualification
 and granularity of states to be recorded, in particular for the
 IN-PROCESS state. It allows individual sub-states to be recorded
 without the need to define and publish a sub-task associated with a
@@ -660,7 +692,7 @@ task has been suspended at whatever state it has reached.

 
Example

 

 
-BEGIN:VSTATUS
+BEGIN:VSTATUS
 STATUS:FAILED
 REASON:https://example.com/reason/no-one-home
 SUBSTATE:ERROR
@@ -676,29 +708,29 @@ END:VSTATUS
 
 
 Task Mode
-
Property Name

-
TASK-MODE

+
Property Name

+
TASK-MODE

 

 
Purpose

-
This property specifies automatic operations that servers
+
This property specifies automatic operations that servers
 acting on behalf of the organizer apply to tasks based on changes in
 attendee status (PARTSTAT).

 

 
Value Type

-
TEXT

+
TEXT

 

 
Property Parameters

-
IANA and non-standard property parameters can be specified on this property.

+
IANA and non-standard property parameters can be specified on this property.

 

 
Conformance

-
This property can be specified zero or more times in a "VTODO" calendar component.

+
This property can be specified zero or more times in a "VTODO" calendar component.

 

 
Format Definition

-
This property is defined by the following notation:

+
This property is defined by the following notation:

 

 

 
-task-mode   = "TASK-MODE taskmodeparam ":" taskvalue
+task-mode   = "TASK-MODE taskmodeparam ":" taskvalue
               *("," taskvalue) CRLF
 
 taskvalue   = "AUTOMATIC-COMPLETION" ; set STATUS completed
@@ -712,8 +744,8 @@ taskvalue   = "AUTOMATIC-COMPLETION" ; set STATUS completed
 taskmodeparam      = *(";" other-param)
 
 
-
Description

-
In a "VTODO" calendar component this property MAY be
+
Description

+
In a "VTODO" calendar component this property MAY be
 used to indicate to servers how they can automatically change the
 state of the task based on iTIP replies from Attendees. For example,
 the server can automatically set the overall task status to COMPLETED
@@ -723,20 +755,20 @@ without it being completed. TASK-MODE processing is performed on the organizer's
 

 

 
-
To set the status, add a VSTATUS component as specified in .

+
To set the status, add a VSTATUS component as specified in .

 
-
The property value is a list of one or more IANA registered tokens that defines modes to be used for the task. This specification defines three modes which are described in the following subsections.

+
The property value is a list of one or more IANA registered tokens that defines modes to be used for the task. This specification defines three modes which are described in the following subsections.

 
-
Examples

+
Examples

 

 
-TASK-MODE:AUTOMATIC-COMPLETION,AUTOMATIC-FAILURE
+TASK-MODE:AUTOMATIC-COMPLETION,AUTOMATIC-FAILURE
 TASK-MODE:SERVER
 TASK-MODE:AUTOMATIC-FAILURE
 
 
 
AUTOMATIC-COMPLETION Task Mode

-
The task mode value "AUTOMATIC-COMPLETION" indicates to the server
+
The task mode value "AUTOMATIC-COMPLETION" indicates to the server
 that it can change the "VTODO" component's status to "COMPLETED" as
 soon as all ATTENDEEs in the task have replied with a "PARTSTAT"
 parameter set to "COMPLETED".

@@ -744,32 +776,32 @@ parameter set to "COMPLETED".

 

 
 
AUTOMATIC-FAILURE Task Mode

-
The task mode value "AUTOMATIC-FAILURE" indicates to the server that
+
The task mode value "AUTOMATIC-FAILURE" indicates to the server that
 it SHOULD change the "VTODO" component's status to "FAILED" if either:

-
  1. the PARTSTAT of one ATTENDEE is set to FAILED; or
    
+
    1. the PARTSTAT of one ATTENDEE is set to FAILED; or
      
 
      2. 
-
    2. the current time is past the effective due date of the component and the task has not yet been completed.
      
+
    3. the current time is past the effective due date of the component and the task has not yet been completed.
      
 
      4. 
 
    
 

 

 
-
The effective due date is either the "DUE" property value or the
+
The effective due date is either the "DUE" property value or the
 combination of the "DTSTART" and "DURATION" property values.

 
 
 
CLIENT Task Mode

-
The task mode value "CLIENT" is an instruction to the server to honour
+
The task mode value "CLIENT" is an instruction to the server to honour
 the status set by the client.

 

 

 
 
SERVER Task Mode

-
The task mode value "SERVER" indicates to the server that it can change
+
The task mode value "SERVER" indicates to the server that it can change
 the "VTODO" component's status to an appropriate value, based on
 implementation defined "business rules", as ATTENDEE responses are
 processed or as deadlines related to the task pass.

-
The server can add this property to a "VTODO" component to indicate to
+
The server can add this property to a "VTODO" component to indicate to
 the client that it will be managing the status.

 

 

@@ -780,14 +812,14 @@ the client that it will be managing the status.

 Property Extensions and Clarifications
 
 Updated DURATION Property definition
-
 section 3.6.2 introduced a constraint on the duration property requiring
+
 section 3.6.2 introduced a constraint on the duration property requiring
 that a DURATION MUST be accompanied by a DTSTART.
 This constraint is dropped reverting to the situation as specified
 previously.

 
-
Thus the text:

+
Thus the text:

 
-                  ; Either 'due' or 'duration' MAY appear in
+                  ; Either 'due' or 'duration' MAY appear in
                   ; a 'todoprop', but 'due' and 'duration'
                   ; MUST NOT occur in the same 'todoprop'.
                   ; If 'duration' appear in a 'todoprop',
@@ -795,25 +827,25 @@ previously.

                   ; the same 'todoprop'.
 
 
-
is replaced by

+
is replaced by

 
-                  ; Either 'due' or 'duration' MAY appear in
+                  ; Either 'due' or 'duration' MAY appear in
                   ; a 'todoprop', but 'due' and 'duration'
                   ; MUST NOT occur in the same 'todoprop'.
 
 
-
This allows a VTODO to only have a DURATION property.

+
This allows a VTODO to only have a DURATION property.

 
-
Furthermore, the following text:

+
Furthermore, the following text:

 
-     A "VTODO" calendar component without the "DTSTART" and "DUE" (or
+     A "VTODO" calendar component without the "DTSTART" and "DUE" (or
      "DURATION") properties specifies a to-do that will be associated
      with each successive calendar date, until it is completed.
 
 
-
is replaced by

+
is replaced by

 
-     A "VTODO" calendar component without the "DTSTART" and "DUE"
+     A "VTODO" calendar component without the "DTSTART" and "DUE"
      properties specifies a to-do that will be associated
      with each successive calendar date, until it is completed.
 
@@ -821,38 +853,38 @@ previously.

 
 
 Redefined STATUS Property
-
The Status property is defined in 3.8.1.11. This
+
The Status property is defined in 3.8.1.11. This
 specification extends that property to include new values
 associated with VTODO iCalendar components (See Appendix A for
 examples of the task state lifecycle).

 
-
Format Definition

-
The "STATUS" property parameter list is augmented
+
Format Definition

+
The "STATUS" property parameter list is augmented
 as follows:

 

 

 
-statvalue-todo = / "PENDING"    ;Indicates a to-do has been
+statvalue-todo = / "PENDING"    ;Indicates a to-do has been
                                 ;created and accepted, but has
                                 ; not yet started.
                 / "FAILED"      ;Indicates to-do has failed.
 ;Extended status values for "VTODO".
 
 
-
Description:

+
Description:

 
-
PENDING - A to-do has been created and accepted but has not yet
+
PENDING - A to-do has been created and accepted but has not yet
 started and is ready
 to start subject to other dependencies (e.g. preceding task or
 DTSTART). This is the default state.

 
-
FAILED - to-do has failed and may need some follow-up from the
+
FAILED - to-do has failed and may need some follow-up from the
 organizer to re-schedule or cancel

 
-
Example: The following is an example of this property for a "VTODO"
+
Example: The following is an example of this property for a "VTODO"
 calendar component:

 
-STATUS:FAILED
+STATUS:FAILED
 
 
 
@@ -861,35 +893,35 @@ calendar component:

 New Components
 
 Status Component
-
Component Name

-
VSTATUS

+
Component Name

+
VSTATUS

 

 
Purpose

-
This component allows information to be
+
This component allows information to be
 associated with a status, for example comments and date stamps.

 

 
Conformance

-
This component can be specified multiple times in
+
This component can be specified multiple times in
 any calendar component.

 

 
Description

-
This component provides a way for multiple date-stamped
+
This component provides a way for multiple date-stamped
 statuses to be associated with a component such as a participant, task or event.

 

 

 
-
This component may be added to the  PARTICIPANT component
+
This component may be added to the  PARTICIPANT component
 to allow participants in a task to specify their own status.

 
-
For backwards compatibility, when a VSTATUS component is added the
+
For backwards compatibility, when a VSTATUS component is added the
  STATUS property MUST be set on the parent component.

 
-
Format Definition

-
This component is defined by the following notation:

+
Format Definition

+
This component is defined by the following notation:

 

 

 
-statusc = "BEGIN" ":" "VSTATUS" CRLF
+statusc = "BEGIN" ":" "VSTATUS" CRLF
           statusprop
           "END" ":" "VSTATUS" CRLF
 
@@ -913,10 +945,10 @@ statusprop     = *(
                )
 
 
-
Examples

+
Examples

 

 
-BEGIN:VSTATUS
+BEGIN:VSTATUS
 STATUS:COMPLETED
 REASON: https://example.com/reason/delivered-on-time
 DTSTAMP:20220212T120000Z
@@ -927,46 +959,46 @@ END:VSTATUS
 
 
 CalDAV Support for Task Mode
-
The CalDAV  calendar access protocol allows clients and servers to exchange iCalendar data. With the introduction of the "TASK-MODE" property in this specification, different automated task management behaviours may be delegated to the server by the Task Organizer depending upon the value of "TASK-MODE".

+
The CalDAV  calendar access protocol allows clients and servers to exchange iCalendar data. With the introduction of the "TASK-MODE" property in this specification, different automated task management behaviours may be delegated to the server by the Task Organizer depending upon the value of "TASK-MODE".

 
-
In order for a CalDAV client to know what task modes are available, a CalDAV server advertises a CALDAV:supported-task-mode-set WebDAV property on calendar home or calendar collections if it supports the use of the "TASK-MODE" property as described in this specification.  The server can advertise a specific set of supported task modes by including one or more CALDAV:supported-task-mode XML elements within the CALDAV:supported-task-mode-set XML element. If no CALDAV:supported-task-mode XML elements are included in the WebDAV property, then clients can try any task mode, but need to be prepared for a failure when attempting to store the calendar data.

+
In order for a CalDAV client to know what task modes are available, a CalDAV server advertises a CALDAV:supported-task-mode-set WebDAV property on calendar home or calendar collections if it supports the use of the "TASK-MODE" property as described in this specification.  The server can advertise a specific set of supported task modes by including one or more CALDAV:supported-task-mode XML elements within the CALDAV:supported-task-mode-set XML element. If no CALDAV:supported-task-mode XML elements are included in the WebDAV property, then clients can try any task mode, but need to be prepared for a failure when attempting to store the calendar data.

 
-
Clients MUST NOT attempt to store iCalendar data containing "TASK-MODE" elements if the CALDAV:supported-task-mode-set WebDAV property is not advertised by the server.

+
Clients MUST NOT attempt to store iCalendar data containing "TASK-MODE" elements if the CALDAV:supported-task-mode-set WebDAV property is not advertised by the server.

 
-
The server SHOULD return an HTTP 403 response with a DAV:error element containing a CALDAV:supported-task-mode XML element, if a client attempts to store iCalendar data with an "TASK-MODE" element value not supported by the server.

+
The server SHOULD return an HTTP 403 response with a DAV:error element containing a CALDAV:supported-task-mode XML element, if a client attempts to store iCalendar data with an "TASK-MODE" element value not supported by the server.

 
-
It is possible for a "TASK-MODE" value to be present in calendar data on the server being accessed by a client that does not support the "TASK-MODE" property. It is expected that existing clients, unaware of "TASK-MODE", will fail gracefully by ignoring the calendar property.

+
It is possible for a "TASK-MODE" value to be present in calendar data on the server being accessed by a client that does not support the "TASK-MODE" property. It is expected that existing clients, unaware of "TASK-MODE", will fail gracefully by ignoring the calendar property.

 
 
 CALDAV:supported-task-mode-set Property
-
Name

-
supported-task-mode-set

+
Name

+
supported-task-mode-set

 

 
Namespace

-
urn:ietf:params:xml:ns:caldav

+
urn:ietf:params:xml:ns:caldav

 

 
Purpose

-
Enumerates the set of supported iCalendar "TASK-MODE" element values supported by the server.

+
Enumerates the set of supported iCalendar "TASK-MODE" element values supported by the server.

 

 
Protected

-
This property MUST be protected and SHOULD NOT be returned by a PROPFIND allprop request (as defined in Section 14.2 of ).

+
This property MUST be protected and SHOULD NOT be returned by a PROPFIND allprop request (as defined in Section 14.2 of ).

 

 
Description

-
See above.

+
See above.

 

 
Definition

 

 
-<!ELEMENT supported-task-mode-set(supported-task-mode*)>
+<!ELEMENT supported-task-mode-set(supported-task-mode*)>
 <!ELEMENT supported-task-mode (#PCDATA)>
 <!-- PCDATA value: string - case insensitive but
 uppercase preferred -->
 
 
-
Example

+
Example

 

 
-<C:supported-task-mode-set xmlns:C="urn:ietf:params:xml:ns:caldav">
+<C:supported-task-mode-set xmlns:C="urn:ietf:params:xml:ns:caldav">
   <C:supported-task-mode>AUTOMATIC-COMPLETION</C:supported-task-mode>
   <C:supported-task-mode>AUTOMATIC-FAILURE</C:supported-task-mode>
   <C:supported-task-mode>SERVER</C:supported-task-mode>
@@ -978,74 +1010,74 @@ uppercase preferred -->
 
 
 Security Considerations
-
This specification introduces no new security considerations beyond those identified in ,  and .

+
This specification introduces no new security considerations beyond those identified in ,  and .

 
 
 
 IANA Considerations
 
 New and updated iCalendar Elements Registration
-
This specification updates  by adding and updating
+
This specification updates  by adding and updating
 a number of elements. The procedures and templates specified in
 8.2

 
 
 Initialization of the Status registry
-
This specification updates  by adding a Status value registry to the iCalendar Elements registry and initializing it as per .

+
This specification updates  by adding a Status value registry to the iCalendar Elements registry and initializing it as per .

 
-
+
Initial Status Value Registry
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-

 
 
Name
 Status
 Reference
 
CANCELLED

+
CANCELLED

 
Current

+
Current

 
3.8.1.11

+
3.8.1.11

 
COMPLETED

+
COMPLETED

 
Current

+
Current

 
3.8.1.11

+
3.8.1.11

 
CONFIRMED

+
CONFIRMED

 
Current

+
Current

 
3.8.1.11

+
3.8.1.11

 
DRAFT

+
DRAFT

 
Current

+
Current

 
3.8.1.11

+
3.8.1.11

 
FINAL

+
FINAL

 
Current

+
Current

 
3.8.1.11

+
3.8.1.11

 
IN-PROCESS

+
IN-PROCESS

 
Current

+
Current

 
3.8.1.11

+
3.8.1.11

 
NEEDS-ACTION

+
NEEDS-ACTION

 
Current

+
Current

 
3.8.1.11

+
3.8.1.11

 
TENTATIVE

+
TENTATIVE

 
Current

+
Current

 
3.8.1.11

+
3.8.1.11

 		
 

 

@@ -1053,25 +1085,25 @@ a number of elements. The procedures and templates specified in
 
 
 Update of the Status registry
-
This specification further updates the Status registry with additional values defined in this document.

+
This specification further updates the Status registry with additional values defined in this document.

 
-
+
Updated Status Value Registry
-
-
-
-
-
-

 
 
Value
 Status
 Reference
 
PENDING

+
PENDING

 
Current

+
Current

 
This Spec, 

+
This Spec, 

 
FAILED

+
FAILED

 
Current

+
Current

 
This Spec, 

+
This Spec, 

 		
 

 

@@ -1079,31 +1111,31 @@ a number of elements. The procedures and templates specified in
 
 
 Sub-State value registry
-
The following table has been used to initialize the Sub-State registry.

+
The following table has been used to initialize the Sub-State registry.

 
-
+
Sub-State registry
-
-
-
-
-
-
-
-
-

 
 
Substate
 Status
 Reference
 
OK

+
OK

 
Current

+
Current

 
This Spec, 

+
This Spec, 

 
ERROR

+
ERROR

 
Current

+
Current

 
This Spec, 

+
This Spec, 

 
SUSPENDED

+
SUSPENDED

 
Current

+
Current

 
This Spec, 

+
This Spec, 

 		
 

 

@@ -1111,37 +1143,37 @@ a number of elements. The procedures and templates specified in
 
 
 Task Mode value registry
-
The following table has been used to initialize the Task Mode registry.

+
The following table has been used to initialize the Task Mode registry.

 
-
+
Task Mode Value Registry
-
-
-
-
-
-
-
-
-
-
-
-

 
 
Task Mode
 Status
 Reference
 
AUTOMATIC-COMPLETION

+
AUTOMATIC-COMPLETION

 
Current

+
Current

 
This Spec, 

+
This Spec, 

 
AUTOMATIC-FAILURE

+
AUTOMATIC-FAILURE

 
Current

+
Current

 
This Spec,  

+
This Spec,  

 
CLIENT

+
CLIENT

 
Current

+
Current

 
This Spec,  

+
This Spec,  

 
SERVER

+
SERVER

 
Current

+
Current

 
This Spec,  

+
This Spec,  

 		
 

 

@@ -1149,19 +1181,19 @@ a number of elements. The procedures and templates specified in
 
 
 Participation Statuses registry
-
The following table has been used to update the Participation Statuses registry.

+
The following table has been used to update the Participation Statuses registry.

 
-
+
Participation Statuses Registry
-
-
-

 
 
Value
 Status
 Reference
 
FAILED

+
FAILED

 
Current

+
Current

 
This Spec, 

+
This Spec, 

 		
 

 

@@ -1169,20 +1201,20 @@ a number of elements. The procedures and templates specified in
 
 
 Components Registry
-
The following table has been used to update the Components registry
+
The following table has been used to update the Components registry
 defined in 8.3.1.

 
-
+
Updated Components Registry
-
-
-

 
 
Component
 Status
 Reference
 
VSTATUS

+
VSTATUS

 
Current

+
Current

 
This Spec, 

+
This Spec, 

 		
 

 

@@ -1190,44 +1222,44 @@ defined in 
 Properties registry
-
The following table has been used to update the Properties registry
+
The following table has been used to update the Properties registry
 defined in 8.3.2.

 
-
+
Updated Properties Registry
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-

 
 
Property
 Status
 Reference
 
ESTIMATED_DURATION

+
ESTIMATED_DURATION

 
Current

+
Current

 
This Spec, 

+
This Spec, 

 
REASON

+
REASON

 
Current

+
Current

 
This Spec, 

+
This Spec, 

 
SUBSTATE

+
SUBSTATE

 
Current

+
Current

 
This Spec, 

+
This Spec, 

 
STATUS

+
STATUS

 
Current

+
Current

 
This Spec, 

+
This Spec, 

 
TASK-MODE

+
TASK-MODE

 
Current

+
Current

 
This Spec, 

+
This Spec, 

 		
 

 

@@ -1237,11 +1269,11 @@ defined in 
 Acknowledgements
-
The authors would like to thank the members of the Calendaring and Scheduling Consortium technical committees and the following individuals for contributing their ideas, support and comments:

+
The authors would like to thank the members of the Calendaring and Scheduling Consortium technical committees and the following individuals for contributing their ideas, support and comments:

 
-
John Chaffee, Marten Gajda, Ken Murchison

+
John Chaffee, Marten Gajda, Ken Murchison

 
-
The authors would also like to thank CalConnect, the Calendaring and
+
The authors would also like to thank CalConnect, the Calendaring and
 Scheduling Consortium, for advice with this specification.