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 cd5b0e9..4b1da95 100644 --- a/ical-tasks/generated/draft-ietf-calext-ical-tasks.err.html +++ b/ical-tasks/generated/draft-ietf-calext-ical-tasks.err.html @@ -8,15 +8,41 @@ .severity3 { font-style: italic; color: grey; }

sources/draft-ietf-calext-ical-tasks.err.html errors

-

Relaton

+ +

Relaton

+ + + + + + + + + + + + + + + + + + @@ -29,41 +55,41 @@

Relaton

LineID MessageContextSeverity
--Downloaded index from https://​raw.​githubusercontent.com/​relaton/​relaton-data-rfcs/​main/index-v1.zip
3

 (Cal­Connect Task Architecture V1.0
 (Cal­Connect Task Architecture V1.0 does not have a recognised prefix
3

 
OMG BPMN 2.0.2Found: OMG BPMN 2.0.2
3
RFC 4791Found: RFC 4791
3
RFC 4918Found: RFC 4918
3
RFC 8174Found: RFC 8174
3
RFC 9074Found: RFC 9074
3

 RFC5545
 RFC5545 does not have a recognised prefix
3

 

 draft-ietf-calext-subscription-upgrade
 draft-ietf-calext-subscription-upgrade does not have a recognised prefix
3

 

-
Style

+
Style

 
-
+
-
+
-
+
-
+

 
LineID
 MessageContextSeverity

 
 
000031_​introduction000035_​introduction
 Hanging paragraph in clause
<clause id="_introduction" inline-header="false" obligation="normative">
 <title>Introduction</title>
 <p id="_99b259c5-536b-2212-29fb-dfa205a6eb6b">This document specifies extensions to the existing Internet Calendaring and Scheduling Core Object Specification (iCalendar) <eref type="inline" bibitemid="RFC5545" citeas="RFC 5545"/>, and associated protocols, in order to enhance the structured communication and execution of tasks. The enhancements allow for the communication, time planning and scheduling of tasks by and between automated systems (e.g. in smart power grids, business process management systems) as well as for human centered tasks.</p>
 
 <p id="_baa80340-ea14-cdb7-ec37-8a9dad6e962b">A "task" is a representation of an item of work assigned to an individual or organization. In the iCalendar Object Model <eref type="inline" bibitemid="RFC5545" citeas="RFC 5545"/> the representation of tasks is by "VTODO" calendar components. Tasks can be identified in a number of situations, either informally as ad-hoc tasks in personal "to-do" lists or more formally in:</p>
2

 
000232task-specification000298task-specification
 Hanging paragraph in clause
<clause id="task-specification" inline-header="false" obligation="normative">
 <title>Task Specification</title>
-<p id="_20962d09-f00b-ca47-e475-e0c2f4341097">The specification of tasks must be semantically explicit in order for them to be managed within the context of a business process or project, and be understood by both humans and IT systems. The <eref type="inline" bibitemid="RFC5545" citeas="RFC 5545"/> "VTODO" calendar component only provides for simple ad-hoc tasks or 'to do' lists, and is therefore extended by this specification as follows:</p>
+<p id="_7d34a8cb-accd-1ac9-f182-d621a228c1fe">The specification of tasks must be semantically explicit in order for them to be managed within the context of a business process or project, and be understood by both humans and IT systems. The  <eref type="inline" bibitemid="RFC5545" citeas="RFC 5545"/> "VTODO" calendar component only provides for simple ad-hoc tasks or 'to do' lists, and is therefore extended by this specification as follows:</p>
 
 <dl id="_de073d3c-5264-38a0-44f9-1a435528b1cc"> <dt>Task type</dt>
2

 
000814caldav-support001006caldav-support
 Hanging paragraph in clause
<clause id="caldav-support" inline-header="false" obligation="normative">
 <title>CalDAV Support for Task Mode</title>
 <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="_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

 
000872_new_and_​updated_​icalendar_​elements_​registration001064_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="_3d34ed84-e14c-860f-bc92-b8331536a1ff">This specification updates <eref type="inline" bibitemid="RFC5545" citeas="RFC 5545"/> by adding and updating a number of elements according to 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>
 
 <clause id="_update_of_the_status_registry" inline-header="false" obligation="normative">
2

 

-
Document Attributes

+
Document Attributes

 
@@ -72,226 +98,37 @@ 
Document Attributes

 
LineID
 MessageContextSeverity

 
--
 IETF: unrecognised working group calext
1

 

-
Metanorma XML Syntax

+
Metanorma XML Syntax

 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+

 
LineID
 MessageContextSeverity

 
 
XML Line 000004:54attribute "format" not allowed here; expected attribute "locale",​ "script" or "type"
2
XML Line 000029:75element "workgroup" not allowed here; expected the element end-tag or element "committee"
2
XML Line 000408:67attribute "lang" not allowed here; expected attribute "markers" or "number"
2
XML Line 000458:67attribute "lang" not allowed here; expected attribute "markers" or "number"
2
XML Line 000494:67attribute "lang" not allowed here; expected attribute "markers" or "number"
2
XML Line 000534:67attribute "lang" not allowed here; expected attribute "markers" or "number"
2
XML Line 000571:67attribute "lang" not allowed here; expected attribute "markers" or "number"
2
XML Line 000627:67attribute "lang" not allowed here; expected attribute "markers" or "number"
2
XML Line 000736:67attribute "lang" not allowed here; expected attribute "markers" or "number"
2
XML Line 000783:67attribute "lang" not allowed here; expected attribute "markers" or "number"
2
XML Line 000851:67attribute "lang" not allowed here; expected attribute "markers" or "number"
2
XML Line 000860:67attribute "lang" not allowed here; expected attribute "markers" or "number"
2
XML Line 001083:83attribute "inline-header" not allowed here; expected attribute "language", "numbered", "obligation", "removeInRFC", "script" or "toc"
2
XML Line 001087:227attribute "alt" not allowed here; expected attribute "align", "number" or "width"
2
XML Line 001087:227attribute "summary" not allowed here; expected attribute "align", "number" or "width"
2
XML Line 001234:40attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001241:148attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001243:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001245:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001247:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001250:40attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001261:148attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001263:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001265:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001268:40attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001275:148attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001278:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001280:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001283:40attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001290:148attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001292:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001294:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001297:40attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001304:148attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001306:98found attribute "format",​ but no attributes allowed here
2
XML Line 001308:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001310:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001313:40attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001320:148attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001321:98found attribute "format",​ but no attributes allowed here
2
XML Line 001323:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001325:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001327:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001330:40attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001337:148attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001339:98found attribute "format",​ but no attributes allowed here
2
XML Line 001341:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001343:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001346:40attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001355:148attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001357:98found attribute "format",​ but no attributes allowed here
2
XML Line 001359:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001361:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001364:40attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001371:148attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001372:98found attribute "format",​ but no attributes allowed here
2
XML Line 001374:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001376:28attribute "format" not allowed here; expected attribute "language", "locale",​ "script" or "type"
2
XML Line 001378:114found attribute "format",​ but no attributes allowed here
2
XML Line 001378:184element "link" missing required attribute "target"
2
XML Line 001391:68attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001392:420attribute "format" not allowed here; expected attribute "language", "locale" or "script"
2
XML Line 001392:999found attribute "format",​ but no attributes allowed here
2
XML Line 001393:100found attribute "format",​ but no attributes allowed here
2
XML Line 000010:30definition of "DlAttr" in "include" does not override anything
2

 
XML Line 001394:100found attribute "format",​ but no attributes allowed here
2
XML Line 000010:30definition of "Image­Attr" in "include" does not override anything
2

 
XML Line 001396:141element "link" missing required attribute "target"
2
XML Line 000010:30definition of "Note­Attr" in "include" does not override anything
2

 
XML Line 001396:51found attribute "format",​ but no attributes allowed here
2
XML Line 000010:30definition of "OlAttr" in "include" does not override anything
2

 
XML Line 001398:10element "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 000010:30definition of "ParagraphAttrs" in "include" does not override anything
2

 
XML Line 001401:19element "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 000010:30definition of "Pre­Attr" in "include" does not override anything
2

 
XML Line 001402:18element "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 000010:30definition of "SourceAttr" in "include" does not override anything
2

 
XML Line 001431:208element "link" missing required attribute "target"
2
XML Line 000010:30definition of "Table­Attr" in "include" does not override anything
2

 
XML Line 001431:51found attribute "format",​ but no attributes allowed here
2
XML Line 000010:30definition of "UlAttr" in "include" does not override anything
2

 

 
diff --git a/ical-tasks/generated/draft-ietf-calext-ical-tasks.html b/ical-tasks/generated/draft-ietf-calext-ical-tasks.html
index f5b8391..aad9ce2 100644
--- a/ical-tasks/generated/draft-ietf-calext-ical-tasks.html
+++ b/ical-tasks/generated/draft-ietf-calext-ical-tasks.html
@@ -12,19 +12,19 @@
        This document updates and defines extensions to VTODO to provide improved status tracking, scheduling and specification of tasks to allow its use in other contexts, such as process control and project management. 
        It also defines how Calendaring Extensions to WebDAV (CalDAV) (RFC 4791) servers can be extended to support certain automated task management behaviours. 
     " name="description">
-
-
+
+
 ]]>
 ]]>
 
 
- 
+
     
Security Considerations
 
 This specification introduces no new security considerations beyond those identified in ,  and .
@@ -768,7 +772,7 @@ uppercase preferred -->]]>
 
 
Components Registry
 
-The following table has been used to update the Components registry defined in  and located here: >.
+The following table has been used to update the Components registry defined in   and located here: >.
 
 Updated Components Registry
ComponentStatusReference
VSTATUS
 Current
@@ -778,9 +782,9 @@ uppercase preferred -->]]>
 
 
Properties registry
 
-The following table has been used to update the Properties registry defined in  and located here: >.
+The following table has been used to update the Properties registry defined in   and located here: >.
 
-Updated Properties Registry
PropertyStatusReference
ESTIMATED_DURATION
+Updated Properties Registry
PropertyStatusReference
ESTIMATED-DURATION
 Current
 This Spec, 
 
REASON
@@ -797,8 +801,8 @@ uppercase preferred -->]]>
 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:
@@ -806,7 +810,7 @@ uppercase preferred -->]]>
 John Chaffee, Marten Gajda, Ken Murchison
 
 The authors would also like to thank CalConnect, the Calendaring and Scheduling Consortium, for advice with this specification.
- 

+
   
   
     
@@ -839,11 +843,10 @@ uppercase preferred -->]]>
 
 Example of status changes in assigning and performing a task with two attendees (A1 and A2).
 
-Example for multiple Attendees
STATUSPARTSTAT (A1)PARTSTAT (A2)Action
1---Organizer draft.
2NEEDS-ACTIONNEEDS-ACTIONNEEDS-ACTIONOrganizer sends iTIP request.
4NEEDS-ACTIONACCEPTEDNEEDS-ACTIONAttendee 1 reply.
5NEEDS-ACTIONACCEPTEDACCEPTEDAttendee 2 reply.
6PENDINGACCEPTEDACCEPTEDTask accepted but waiting on some"trigger" to start (e.g. another task has to finish first)
7IN-PROCESSACCEPTEDIN-PROCESSAttendee 2 reply now working on the task.
8IN-PROCESSIN-PROCESSIN-PROCESSAttendee 1 reply now working on the task.
9IN-PROCESSCOMPLETEDIN-PROCESSAttendee 1 reply Completed (overall status still IN-PROCESS).
10IN-PROCESSCOMPLETEDCOMPLETEDAttendee 2 reply Completed
11COMPLETEDCOMPLETEDCOMPLETEDOrganizer changes overall state once both attendees are finished.

+Example for multiple Attendees
STATUSPARTSTAT (A1)PARTSTAT (A2)Action
1---Organizer draft.
2NEEDS-ACTIONNEEDS-ACTIONNEEDS-ACTIONOrganizer sends iTIP request.
4NEEDS-ACTIONACCEPTEDNEEDS-ACTIONAttendee 1 reply.
5NEEDS-ACTIONACCEPTEDACCEPTEDAttendee 2 reply.
6PENDINGACCEPTEDACCEPTEDTask accepted but waiting on some"trigger" to start (e.g. another task has to finish first)
7IN-PROCESSACCEPTEDIN-PROCESSAttendee 2 reply now working on the task.
8IN-PROCESSIN-PROCESSIN-PROCESSAttendee 1 reply now working on the task.
9IN-PROCESSCOMPLETEDIN-PROCESSAttendee 1 reply Completed (overall status still IN-PROCESS).
10IN-PROCESSCOMPLETEDCOMPLETEDAttendee 2 reply Completed
11COMPLETEDCOMPLETEDCOMPLETEDOrganizer changes overall state once both attendees are finished.

 
 
- 
+
 
 
Example of Failure
 
@@ -851,6 +854,6 @@ is determined by the task organizer based on the "ATTENDEE" property status and
 
 Example of Failure
STATUSPARTSTATAction
1--Organizer draft
2NEEDS-ACTIONNEEDS-ACTIONOrganizer sends iTIP request
3NEEDS-ACTIONACCEPTEDAttendee reply
4IN-PROCESSIN-PROCESSAttendee reply now working on the task
5IN-PROCESSFAILEDAttendee reply task failed
6FAILEDFAILEDOrganizer changes overall state

 

- 
+
   
 
diff --git a/ical-tasks/generated/draft-ietf-calext-ical-tasks.txt b/ical-tasks/generated/draft-ietf-calext-ical-tasks.txt
index 1647e6a..31732cf 100644
--- a/ical-tasks/generated/draft-ietf-calext-ical-tasks.txt
+++ b/ical-tasks/generated/draft-ietf-calext-ical-tasks.txt
@@ -6,11 +6,11 @@ calext                                                        A. Apthorp
 Internet-Draft                                               DHL Express
 Updates: RFC5545 (if approved)                               M. Douglass
 Intended status: Standards Track            Bedework Commercial Services
-Expires: 31 January 2025                                    30 July 2024
+Expires: 4 June 2025                                     1 December 2024
 
 
                       Task Extensions to iCalendar
-                    draft-ietf-calext-ical-tasks-10
+                    draft-ietf-calext-ical-tasks-11
 
 Abstract
 
@@ -43,7 +43,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 31 January 2025.
+   This Internet-Draft will expire on 4 June 2025.
 
 Copyright Notice
 
@@ -53,9 +53,9 @@ Copyright Notice
 
 
 
-Apthorp & Douglass       Expires 31 January 2025                [Page 1]
+Apthorp & Douglass         Expires 4 June 2025                  [Page 1]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
    This document is subject to BCP 78 and the IETF Trust's Legal
@@ -109,9 +109,9 @@ Table of Contents
 
 
 
-Apthorp & Douglass       Expires 31 January 2025                [Page 2]
+Apthorp & Douglass         Expires 4 June 2025                  [Page 2]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
    17. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  26
@@ -165,9 +165,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025                [Page 3]
+Apthorp & Douglass         Expires 4 June 2025                  [Page 3]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
 1.1.  Terms and Definitions
@@ -221,9 +221,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025                [Page 4]
+Apthorp & Douglass         Expires 4 June 2025                  [Page 4]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
    BPMS  Business Process Management Software
@@ -277,9 +277,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025                [Page 5]
+Apthorp & Douglass         Expires 4 June 2025                  [Page 5]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
    a binding or packaging of elements, i.e., software systems may be
@@ -333,9 +333,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025                [Page 6]
+Apthorp & Douglass         Expires 4 June 2025                  [Page 6]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
         Task        +-------+
@@ -389,9 +389,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025                [Page 7]
+Apthorp & Douglass         Expires 4 June 2025                  [Page 7]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
                     Figure 1: Task architecture diagram
@@ -445,9 +445,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025                [Page 8]
+Apthorp & Douglass         Expires 4 June 2025                  [Page 8]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
       Process Management System, Project Management System, Bug Tracking
@@ -501,9 +501,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025                [Page 9]
+Apthorp & Douglass         Expires 4 June 2025                  [Page 9]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
 5.  Task Extensions
@@ -557,9 +557,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 10]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 10]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
    CONCEPT:http://example.com/task/delivery
@@ -613,9 +613,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 11]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 11]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
 7.1.  Deadlines
@@ -669,9 +669,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 12]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 12]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
 9.1.  Improved granularity in status reporting information
@@ -725,9 +725,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 13]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 13]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
 9.3.  Relating reason and comments to "ATTENDEE" property status
@@ -781,9 +781,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 14]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 14]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
       component, to identify which task events the stakeholder/party is
@@ -837,9 +837,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 15]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 15]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
    ; Addition of VSTATUS as a valid component for VEVENT
@@ -876,8 +876,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
                   "END" ":" "PARTICIPANT" CRLF
 
 
-   ; Addition of propertY REASON to PARTICIPANT
-   partprop =/ reason
+   ; Addition of properties PERCENT-COMPLETE and REASON to PARTICIPANT
+   partprop =/ percent / ; OPTIONAL but MUST NOT occur more than once.
+               reason    ; OPTIONAL but MUST NOT occur more than once.
 
 11.  New Parameter Values
 
@@ -892,10 +893,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-
-Apthorp & Douglass       Expires 31 January 2025               [Page 16]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 16]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
    partstat-todo    =/ *("FAILED")  ; To-do cannot be completed
@@ -949,9 +949,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 17]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 17]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
 12.2.  Reason
@@ -1005,9 +1005,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 18]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 18]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
       notation:
@@ -1061,9 +1061,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 19]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 19]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
    Property Parameters  IANA and non-standard property parameters can be
@@ -1117,9 +1117,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 20]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 20]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
       indicates to the server that it SHOULD change the "VTODO" calendar
@@ -1173,9 +1173,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 21]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 21]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
    is replaced by
@@ -1229,9 +1229,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 22]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 22]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
    STATUS:FAILED
@@ -1285,9 +1285,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 23]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 23]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
    statusc = "BEGIN" ":" "VSTATUS" CRLF
@@ -1341,9 +1341,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 24]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 24]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
    In order for a CalDAV client to know what task modes are available, a
@@ -1397,9 +1397,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 25]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 25]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
    Example
@@ -1453,9 +1453,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 26]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 26]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
              +===========+=========+=========================+
@@ -1509,9 +1509,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 27]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 27]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
 17.1.5.  Components Registry
@@ -1537,7 +1537,7 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
         +====================+=========+=========================+
         | Property           | Status  | Reference               |
         +====================+=========+=========================+
-        | ESTIMATED_DURATION | Current | This Spec, Section 12.1 |
+        | ESTIMATED-DURATION | Current | This Spec, Section 12.1 |
         +--------------------+---------+-------------------------+
         | REASON             | Current | This Spec, Section 12.2 |
         +--------------------+---------+-------------------------+
@@ -1565,9 +1565,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 28]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 28]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
@@ -1621,9 +1621,9 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 29]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 29]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
 20.  Informative References
@@ -1677,9 +1677,9 @@ A.1.  Simple Case Status Change
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 30]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 30]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
 A.2.  Example for multiple Attendees
@@ -1733,9 +1733,9 @@ A.2.  Example for multiple Attendees
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 31]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 31]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
    |    |              |              |              | reply          |
@@ -1789,9 +1789,9 @@ Authors' Addresses
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 32]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 32]
 
-Internet-Draft        Task Extensions to iCalendar             July 2024
+Internet-Draft        Task Extensions to iCalendar         December 2024
 
 
    Adrian Apthorp
@@ -1845,4 +1845,4 @@ Internet-Draft        Task Extensions to iCalendar             July 2024
 
 
 
-Apthorp & Douglass       Expires 31 January 2025               [Page 33]
+Apthorp & Douglass         Expires 4 June 2025                 [Page 33]
diff --git a/ical-tasks/generated/draft-ietf-calext-ical-tasks.xml b/ical-tasks/generated/draft-ietf-calext-ical-tasks.xml
index e754fea..1047832 100644
--- a/ical-tasks/generated/draft-ietf-calext-ical-tasks.xml
+++ b/ical-tasks/generated/draft-ietf-calext-ical-tasks.xml
@@ -1,8 +1,8 @@
 
-
+
 
 Task Extensions to iCalendar
-draft-ietf-calext-ical-tasks-10draft-ietf-calext-ical-tasks-10
+draft-ietf-calext-ical-tasks-11draft-ietf-calext-ical-tasks-11
 Adrian Apthorp
 
 DHL Express
@@ -12,12 +12,12 @@
 Bedework Commercial Services
 
226 3rd StreetTroyNYUnited States of America
mdouglass@bedework.com
 Internet Engineering Task Force
-IETF2024-07-30en
The Internet Calendaring and Scheduling Core Object Specification (iCalendar) (RFC5545) VTODO calendar component has been seen as the poor relation of VEVENT - useful only for personal reminders and to-do lists.

+IETF2024-12-01en
The Internet Calendaring and Scheduling Core Object Specification (iCalendar) (RFC5545) VTODO calendar component has been seen as the poor relation of VEVENT - useful only for personal reminders and to-do lists.

 
 
This document updates and defines extensions to VTODO to provide improved status tracking, scheduling and specification of tasks to allow its use in other contexts, such as process control and project management.

 
 
It also defines how Calendaring Extensions to WebDAV (CalDAV) (RFC 4791) servers can be extended to support certain automated task management behaviours.

- standard2024
+standard2024
 Internet Engineering Task Force
 IETF
 --
@@ -26,13 +26,13 @@
 IETF
 
 full-standard
-internet-draftcalextInternettrust200902trueyesTOC Heading Levels2HTML TOC Heading Levels2DOC TOC Heading Levels2PDF TOC Heading Levels2
+internet-draftietfcalextInternettrust200902trueyesTOC Heading Levels2HTML TOC Heading Levels2DOC TOC Heading Levels2PDF TOC Heading Levels2
 Abstract
The Internet Calendaring and Scheduling Core Object Specification (iCalendar) (RFC5545) VTODO calendar component has been seen as the poor relation of VEVENT - useful only for personal reminders and to-do lists.

 
 
This document updates and defines extensions to VTODO to provide improved status tracking, scheduling and specification of tasks to allow its use in other contexts, such as process control and project management.

 
 
It also defines how Calendaring Extensions to WebDAV (CalDAV) (RFC 4791) servers can be extended to support certain automated task management behaviours.

- 
+
 
 Introduction
 
This document specifies extensions to the existing Internet Calendaring and Scheduling Core Object Specification (iCalendar) , and associated protocols, in order to enhance the structured communication and execution of tasks. The enhancements allow for the communication, time planning and scheduling of tasks by and between automated systems (e.g. in smart power grids, business process management systems) as well as for human centered tasks.

@@ -49,7 +49,7 @@
 
 
 Terms and Definitions
-
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14   when, and only when, they appear in all capitals, as shown here.

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

 
 
Calendaring and scheduling roles are referred to in quoted-strings of text with the first character of each word in upper case.  For example, "Organizer" refers to a role of a "Calendar User" (CU) within the scheduling protocol.

 
@@ -67,7 +67,7 @@
 
 
Terms defined and used in this specification include:

 
-
Assignee

+
Assignee

 
A calendar user assigned to perform a given task. An assignee is equivalent to an "A"ttendee" of a task.

 

 
BPMS

@@ -88,7 +88,7 @@
 
A calendar user who might be able to perform a given task, prior to actually being assigned the task, e.g., a dispatcher has a list of taxi drivers (candidates) from which one will be selected to pick-up a passenger.

 

 
Organizer

-
A calendar user who creates a calendar item, requests free/busy information, or published free/busy information. It is an "Organizer" who invites "Attendees" .

+
A calendar user who creates a calendar item, requests free/busy information, or published free/busy information. It is an "Organizer" who invites "Attendees"  .

 

 
Observer

 
A calendar user interested in a calendar component, e.g., a manager may have interest in all tasks that have not been completed. Often represented as an "Attendee" with ROLE=NON-PARTICIPANT.

@@ -100,12 +100,12 @@
 
A representation of an item of work that can be assigned to one or more task actor assignees. In , these are "VTODO" calendar components, which are groupings of component properties and possibly "VALARM" calendar components that represent an action-item or assignment.

 

 

- 
- 
+
+
 
 
 Task Architecture
-
A reference architecture for task calendaring and scheduling is defined in order to identify the key logical elements involved in task management and the interfaces between them to enable interoperability. The logical elements identified here establish an appropriate separation of concerns and clarify the responsibilities of different elements. However, the architecture does not prescribe a binding or packaging of elements, i.e., software systems may be developed where some elements are tightly bound and the interfaces between bound elements are not exposed. The task architecture is also described in .

+
A reference architecture for task calendaring and scheduling is defined in order to identify the key logical elements involved in task management and the interfaces between them to enable interoperability. The logical elements identified here establish an appropriate separation of concerns and clarify the responsibilities of different elements. However, the architecture does not prescribe a binding or packaging of elements, i.e., software systems may be developed where some elements are tightly bound and the interfaces between bound elements are not exposed. The task architecture is also described in  .

 
 

 Task architecture diagram
@@ -156,13 +156,13 @@
 |          Candidate(s)        Observer(s)  |    |           |
 | Assignee(s)       Resource(s)             |    |           |
 +-------------------------------------------+    +-----------+

- 
+
 
 
 Task Architecture Elements
 
The following logical elements form the task architecture that this specification is based on:

 
-
Task Actors

+
Task Actors

 
Various calendar users that may be involved in the monitoring or performing of a task. The set of actors includes: Organizers, Observers, Resources, Assignees, and Candidates.

 

 
Task Organizer

@@ -181,14 +181,15 @@
 
This is some event that gives rise to the generation of a task according to Process Logic. Task triggers can come from many sources including, for example; a task being requested through the calendaring system, a status change in the progression of a business process being managed by a business process management or Enterprise resource planning (ERP) system.

 

 
Task Assignment Rules

-
Govern how actors are assigned to a task. A range of different assignment patterns  may be considered, including the two general cases:

+
Govern how actors are assigned to a task. A range of different assignment patterns   may be considered, including the two general cases:

 
  1. Delegation to a named actor or group of actors
    
 
    2. 
 
  2. Advertising to a pool of actors for self-selection
    
 
    3. 
 

- 
In either case the assignment may be made based on a variety of criteria including, name, availability, skills, capacity, etc.

- 

+
+
In either case the assignment may be made based on a variety of criteria including, name, availability, skills, capacity, etc.

+
 
Task Generating System

 
A system that creates and assigns tasks in response to some initiating event (task trigger). Task creation is according to Process Logic with task assignment determined by Task Assignment Rules. This system also tracks the status of tasks and will initiate further actions based upon the status. A task generating system can take many forms, for example; Business Process Management System, Project Management System, Bug Tracking System, Building Control System. A Task Generating System may also be a human. In iCalendar terms the Task Generating System is the organizer.

 

@@ -208,10 +209,10 @@
 
 
 Architecture Foundations
-
The key standards that enable interoperability between the logical elements of the architecture are the Internet Calendaring and Scheduling Core Object Specification (iCalendar)  and associated protocols. Task and task status are represented by the "VTODO" calendar component. Protocols include, in particular, the iCalendar Transport-Independent Interoperability Protocol (iTIP)  for task assignment and scheduling, and Calendaring Extensions to WebDAV (CalDAV)  for client server communication.

+
The key standards that enable interoperability between the logical elements of the architecture are the Internet Calendaring and Scheduling Core Object Specification (iCalendar)   and associated protocols. Task and task status are represented by the "VTODO" calendar component. Protocols include, in particular, the iCalendar Transport-Independent Interoperability Protocol (iTIP)   for task assignment and scheduling, and Calendaring Extensions to WebDAV (CalDAV)   for client server communication.

 
-
Additionally, this specification uses definitions from Support for iCalendar Relationships . The "LINK", "REFID", "RELATED-TO" and "CONCEPT" properties enable context and a rich set of relationships between tasks and other calendar components to be specified.

- 
+
Additionally, this specification uses definitions from Support for iCalendar Relationships  . The "LINK", "REFID", "RELATED-TO" and "CONCEPT" properties enable context and a rich set of relationships between tasks and other calendar components to be specified.

+
 
 
 Task Extensions
@@ -236,7 +237,7 @@
 
 
 Task Specification
-
The specification of tasks must be semantically explicit in order for them to be managed within the context of a business process or project, and be understood by both humans and IT systems. The  "VTODO" calendar component only provides for simple ad-hoc tasks or 'to do' lists, and is therefore extended by this specification as follows:

+
The specification of tasks must be semantically explicit in order for them to be managed within the context of a business process or project, and be understood by both humans and IT systems. The   "VTODO" calendar component only provides for simple ad-hoc tasks or 'to do' lists, and is therefore extended by this specification as follows:

 
 
Task type

 
explicitly what type of task is to be performed is identified.

@@ -279,7 +280,7 @@ REFID:1234567890
 
 
 
Extensions to the "RELATED-TO" property defined in  allow temporal relationships between tasks as found in project management to be specified as well as parent/child relationships and dependencies (DEPENDS-ON). Tasks ("VTODO" calendar components) may also be related to other calendar components; for example to a "VEVENT" calendar component to block time to perform a task.

- 
+
 
 
 Task Specific Data
@@ -295,29 +296,29 @@ REFID:1234567890
  http://example.com/delivery/sig1234.jpg
 
 
- 
+
 
 
 Task Deadlines, Milestones and Time Planning
 
 Deadlines
-
Deadlines for starting and finishing a task are defined by the "DTSTART", "DUE" and "DURATION" properties. The "DTSTART" property represents the earliest start time for beginning work on a task. The "DUE", or "DTSTART" + "DURATION" properties represent the latest finish time for a task. Thus, these properties define a "window" within which a task has to be performed. However,  provides no way to indicate how long the task is expected to take. This document defines a new "ESTIMATED-DURATION" property, in , 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 therefore allow calendar users to visualize when tasks should be performed and allocate time to them.

- 
+
Deadlines for starting and finishing a task are defined by the "DTSTART", "DUE" and "DURATION" properties. The "DTSTART" property represents the earliest start time for beginning work on a task. The "DUE", or "DTSTART" + "DURATION" properties represent the latest finish time for a task. Thus, these properties define a "window" within which a task has to be performed. However,   provides no way to indicate how long the task is expected to take. This document defines a new "ESTIMATED-DURATION" property, in  , 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 therefore allow calendar users to visualize when tasks should be performed and allocate time to them.

+
 
 
 Milestones
 
A task that has intermediary deadlines (i.e., milestones) SHOULD be expressed by child "VTODO" calendar components (i.e., sub-tasks associated with each of the milestones) in conjunction with the "RELATED-TO" property to relate the parent and child tasks.

- 
+
 
 
 
 Task Scheduling and Assignment
-
Tasks are assigned to actors using one or more  "ATTENDEE" properties and/or one or more  "PARTICIPANT" calendar components.

+
Tasks are assigned to actors using one or more  "ATTENDEE" properties and/or one or more   "PARTICIPANT" calendar components.

 
 
Communication of task assignment or delegation to one or more actors who are allocated to a task by the organizer is directly supported by iTIP, i.e., all included "ATTENDEE" properties in an iTIP REQUEST are expected to perform the task.

 
 
The offering or advertising of a task to one or more (potential) actors where only one or a subset of the candidates may accept the task will be addressed by a later specification.

- 
+
 
 
 Status Reporting
@@ -361,7 +362,7 @@ END:VSTATUS
 
 
 
Note that the "VSTATUS" calendar component is not intended to be used as a history of changes to a tasks properties. The purpose of the "VSTATUS" calendar component is only to document changes related to fulfilling the tasks

- 
+
 
 
 Relating reason and comments to "ATTENDEE" property status changes.
@@ -382,30 +383,30 @@ END:PARTICIPANT
 Task Alerts and Notifications
 
Different needs to alert or notify task actors of pending or actual task status changes are recognized:

 
-
Alarms

+
Alarms

 
"VALARM" calendar components operate in the calendar user agent space to notify the task actor of a pending task state for a task they are assigned to or are interested in.

 
Current standards (see ) indicate "VALARM" calendar components SHOULD be removed from incoming data and many systems in fact do so. In a task assignment scenario it may be appropriate for the organizer to be able to set alarms for the participants. A system implementing these standards may choose to preserve "VALARM" calendar components but sending a task via some external service may result in them being removed. This issue is not addressed by this specification.

- 

+

 
Escalations

 
An escalation or notification to the "Attendee", "Organizer", or other task actor may be required if a deadline associated with a task is exceeded or for some other reason. Process Logic identifying when and who to propagate escalations is the responsibility of the Task Generating System, e.g., a BPMS.

 

 
Notifications

-
Task actors (observers) not directly involved in performing a task, but with a known interest in a given task's status, can be identified by the "PARTICIPANT" calendar component  against certain components e.g. the "VALARM" calendar component, to identify which task events the stakeholder/party is interested in. Notifications on shared calendars will allow task actors to register an interest in changes to tasks within a calendar (see ).

+
Task actors (observers) not directly involved in performing a task, but with a known interest in a given task's status, can be identified by the "PARTICIPANT" calendar component   against certain components e.g. the "VALARM" calendar component, to identify which task events the stakeholder/party is interested in. Notifications on shared calendars will allow task actors to register an interest in changes to tasks within a calendar (see  ).

 

 

- 
+
 
 
 Automated Status Changes
 
A new "TASK-MODE" property 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  and Event Publishing Extensions to iCalendar  are made here. New elements are defined in subsequent sections.

+
The following changes to the syntax defined in iCalendar  and Event Publishing Extensions to iCalendar   are made here. New elements are defined in subsequent sections.

 
-; Addition of VSTATUS as a valid component for VEVENT
+; Addition of VSTATUS as a valid component for VEVENT
 eventc     = "BEGIN" ":" "VEVENT" CRLF
              eventprop *alarmc *participantc *locationc
                  *resourcec *statusc
@@ -439,8 +440,9 @@ participantc = "BEGIN" ":" "PARTICIPANT" CRLF
                "END" ":" "PARTICIPANT" CRLF
 
 
-; Addition of propertY REASON to PARTICIPANT
-partprop =/ reason
+; Addition of properties PERCENT-COMPLETE and REASON to PARTICIPANT
+partprop =/ percent / ; OPTIONAL but MUST NOT occur more than once.
+            reason    ; OPTIONAL but MUST NOT occur more than once.
 
 
 
@@ -465,7 +467,7 @@ partprop =/ reason
  PARTSTAT=FAILED:mailto:jsmith@example.com
 
 
- 
+
 
 
 New Properties
@@ -497,8 +499,8 @@ partprop =/ reason
 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" properties represent the window in which the task can be performed. The "ESTIMATED-DURATION" property SHOULD be passed from the organizer to the "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" properties represent the window in which the task can be performed. The "ESTIMATED-DURATION" property SHOULD be passed from the organizer to the "Attendee" in iTIP   messages.

 

 
Example

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

@@ -636,11 +638,13 @@ END:VSTATUS
 taskmodeparam      = *(";" other-param)
 
 
-
Description

+
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.

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

- 
The property value is an IANA registered token that defines the mode to be used for the task. The modes are described in the following subsections.

- 
If the "TASK-MODE" property is absent then the "CLIENT" value is assumed.

+
+
The property value is an IANA registered token that defines the mode to be used for the task. The modes are described in the following subsections.

+
+
If the "TASK-MODE" property is absent then the "CLIENT" value is assumed.

 

 

 
@@ -658,7 +662,7 @@ taskmodeparam      = *(";" other-param)
 
Completing the task MUST be handled by a client.

 
 
- 

+

 

 
 
AUTOMATIC Task Mode

@@ -682,7 +686,7 @@ TASK-MODE:AUTOMATIC-FAILURE
 TASK-MODE:SERVER
 
 
- 
+
 
 
 Property Extensions and Clarifications
@@ -751,7 +755,7 @@ TASK-MODE:SERVER
 STATUS:FAILED
 
 
- 
+
 
 
 New Components
@@ -814,7 +818,7 @@ DTSTAMP:20220212T120000Z
 END:VSTATUS
 
 
- 
+
 
 
 CalDAV Support for Task Mode
@@ -865,7 +869,7 @@ uppercase preferred -->
 </C:supported-task-mode-set>
 
 
- 
+
 
 
 Security Considerations
@@ -1002,7 +1006,7 @@ uppercase preferred -->
 
 
 Components Registry
-
The following table has been used to update the Components registry defined in 8.3.1 and located here: <>.

+
The following table has been used to update the Components registry defined in  8.3.1 and located here: <>.

 
 Updated Components Registry
@@ -1022,15 +1026,15 @@ uppercase preferred -->
 Properties registry
-
The following table has been used to update the Properties registry defined in 8.3.2 and located here: <>.

+
The following table has been used to update the Properties registry defined in  8.3.2 and located here: <>.

 
-

 
 
 

+
Updated Properties Registry
-
@@ -1063,8 +1067,8 @@ uppercase preferred -->

 
 
Property
 Status
 Reference
 
ESTIMATED_DURATION

+
ESTIMATED-DURATION

 		
 
Current

 		
 

 

 
- 
- 
+
+
 
 
 Acknowledgements
@@ -1073,14 +1077,14 @@ uppercase preferred -->
 
John Chaffee, Marten Gajda, Ken Murchison

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

- 
+
 
 
 
 
 
 
- 
+
 Examples of Task State Lifecycle
 
 Simple Case Status Change
@@ -1126,7 +1130,7 @@ uppercase preferred -->
 Example for multiple Attendees
 
Example of status changes in assigning and performing a task with two attendees (A1 and A2).

 
-
+
Example for multiple Attendees
@@ -1184,12 +1188,11 @@ uppercase preferred -->
-
The logic for determining the status change to the "VTODO" calendar component
-is determined by the task organizer based on the "ATTENDEE" property status and other business logic.

+
The logic for determining the status change to the "VTODO" calendar component is determined by the task organizer based on the "ATTENDEE" property status and other business logic.

 

 
 
STATUS
 PARTSTAT (A1)
 COMPLETED
 Organizer changes overall state once both attendees are finished.
 

 
 
- 
+
 
 
 Example of Failure
@@ -1228,211 +1231,719 @@ is determined by the task organizer based on the "ATTENDEE" property status and
 

 

 
- 
+
 Normative References
-   2024-07-30   
+
+  2024-10-16
+  
 Key words for use in RFCs to Indicate Requirement Levels
-   https://www.rfc-editor.org/info/rfc2119   RFC 2119   10.17487/RFC2119   RFC2119        1997-03                       
-         S. Bradner       
-                            
+
+  https://www.rfc-editor.org/info/rfc2119
+  RFC 2119
+  10.17487/RFC2119
+  RFC2119
+  
+    1997-03
+  
+  
+    
+    
+      
+          S. Bradner       
+
+    
+  
+  
+    
+    
+      
 RFC Publisher
-                            
+
+    
+  
+  
+    
+    
+      
 RFC Series
-           en           
In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

-           
+
+    
+  
+  en
+  
+  
+    
In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

+
+  
+  
+    
 BCP
-     14           
+
+    14
+  
+  
+    
 RFC
-     2119           
+
+    2119
+  
+  
+    
 IETF
-      Standards   Track   Documents 
-   2024-07-30   
+
+  
+  Standards
+  Track
+  Documents
+
+
+  2024-12-01
+  
 Calendaring Extensions to WebDAV (CalDAV)
-   https://www.rfc-editor.org/info/rfc4791   RFC 4791   10.17487/RFC4791   RFC4791        2007-03                       
-         C. Daboo       
-                            
-         B. Desruisseaux       
-                            
-         L. Dusseault       
-                            
+
+  https://www.rfc-editor.org/info/rfc4791
+  RFC 4791
+  10.17487/RFC4791
+  RFC4791
+  
+    2007-03
+  
+  
+    
+    
+      
+          C. Daboo       
+
+    
+  
+  
+    
+    
+      
+          B. Desruisseaux       
+
+    
+  
+  
+    
+    
+      
+          L. Dusseault       
+
+    
+  
+  
+    
+    
+      
 RFC Publisher
-                            
+
+    
+  
+  
+    
+    
+      
 RFC Series
-           en           
This document defines extensions to the Web Distributed Authoring and Versioning (WebDAV) protocol to specify a standard way of accessing, managing, and sharing calendaring and scheduling information based on the iCalendar format. This document defines the "calendar-access" feature of CalDAV. [STANDARDS-TRACK]

-           
+
+    
+  
+  en
+  
+  
+    
This document defines extensions to the Web Distributed Authoring and Versioning (WebDAV) protocol to specify a standard way of accessing, managing, and sharing calendaring and scheduling information based on the iCalendar format. This document defines the "calendar-access" feature of CalDAV. [STANDARDS-TRACK]

+
+  
+  
+    
 RFC
-     4791           
+
+    4791
+  
+  
+    
 IETF
-      calsched   calsch   calcav   calendar   calendaring   scheduling   webdav   ical   icalendar   itip   text/calendar   http 
-   2024-07-30   
+
+  
+  calsched
+  calsch
+  calcav
+  calendar
+  calendaring
+  scheduling
+  webdav
+  ical
+  icalendar
+  itip
+  text/calendar
+  http
+
+
+  2024-12-01
+  
 HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)
-   https://www.rfc-editor.org/info/rfc4918   RFC 4918   10.17487/RFC4918   RFC4918        2007-06                       
-         L. Dusseault       
-                            
+
+  https://www.rfc-editor.org/info/rfc4918
+  RFC 4918
+  10.17487/RFC4918
+  RFC4918
+  
+    2007-06
+  
+  
+    
+    
+      
+          L. Dusseault       
+
+    
+  
+  
+    
+    
+      
 RFC Publisher
-                            
+
+    
+  
+  
+    
+    
+      
 RFC Series
-           en           
Web Distributed Authoring and Versioning (WebDAV) consists of a set of methods, headers, and content-types ancillary to HTTP/1.1 for the management of resource properties, creation and management of resource collections, URL namespace manipulation, and resource locking (collision avoidance).

-     
RFC 2518 was published in February 1999, and this specification obsoletes RFC 2518 with minor revisions mostly due to interoperability experience. [STANDARDS-TRACK]

-           
+
+    
+  
+  en
+  
+  
+    
Web Distributed Authoring and Versioning (WebDAV) consists of a set of methods, headers, and content-types ancillary to HTTP/1.1 for the management of resource properties, creation and management of resource collections, URL namespace manipulation, and resource locking (collision avoidance).

+
+    
RFC 2518 was published in February 1999, and this specification obsoletes RFC 2518 with minor revisions mostly due to interoperability experience. [STANDARDS-TRACK]

+
+  
+  
+    
 RFC
-     4918           
+
+    4918
+  
+  
+    
 IETF
-      WEBDAV   hypertext   transfer   protocol   web   content 
-   2024-07-30   
+
+  
+  WEBDAV
+  hypertext
+  transfer
+  protocol
+  web
+  content
+
+
+  2024-10-16
+  
 Internet Calendaring and Scheduling Core Object Specification (iCalendar)
-   https://www.rfc-editor.org/info/rfc5545   RFC 5545   10.17487/RFC5545   RFC5545        2009-09                       
-         B. Desruisseaux       
-                            
+
+  https://www.rfc-editor.org/info/rfc5545
+  RFC 5545
+  10.17487/RFC5545
+  RFC5545
+  
+    2009-09
+  
+  
+    
+    
+      
+          B. Desruisseaux       
+
+    
+  
+  
+    
+    
+      
 RFC Publisher
-                            
+
+    
+  
+  
+    
+    
+      
 RFC Series
-           en           
This document defines the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol. [STANDARDS-TRACK]

-           
+
+    
+  
+  en
+  
+  
+    
This document defines the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol. [STANDARDS-TRACK]

+
+  
+  
+    
 RFC
-     5545           
+
+    5545
+  
+  
+    
 IETF
-      calsify   calsched   calsch   caldav   calendar   calendaring   meeting   event   task   to-do   journal   appointment   agenda   schedule   scheduling   ical   icalendar   itip   imip   text/calendar   ischedule   xCalendar 
-   2024-07-30   
+
+  
+  calsify
+  calsched
+  calsch
+  caldav
+  calendar
+  calendaring
+  meeting
+  event
+  task
+  to-do
+  journal
+  appointment
+  agenda
+  schedule
+  scheduling
+  ical
+  icalendar
+  itip
+  imip
+  text/calendar
+  ischedule
+  xCalendar
+
+
+  2024-10-16
+  
 iCalendar Transport-Independent Interoperability Protocol (iTIP)
-   https://www.rfc-editor.org/info/rfc5546   RFC 5546   10.17487/RFC5546   RFC5546        2009-12                       
-         C. Daboo       
-                            
+
+  https://www.rfc-editor.org/info/rfc5546
+  RFC 5546
+  10.17487/RFC5546
+  RFC5546
+  
+    2009-12
+  
+  
+    
+    
+      
+          C. Daboo       
+
+    
+  
+  
+    
+    
+      
 RFC Publisher
-                            
+
+    
+  
+  
+    
+    
+      
 RFC Series
-           en           
This document specifies a protocol that uses the iCalendar object specification to provide scheduling interoperability between different calendaring systems. This is done without reference to a specific transport protocol so as to allow multiple methods of communication between systems. Subsequent documents will define profiles of this protocol that use specific, interoperable methods of communication between systems.

-     
The iCalendar Transport-Independent Interoperability Protocol (iTIP) complements the iCalendar object specification by adding semantics for group scheduling methods commonly available in current calendaring systems. These scheduling methods permit two or more calendaring systems to perform transactions such as publishing, scheduling, rescheduling, responding to scheduling requests, negotiating changes, or canceling. [STANDARDS-TRACK]

-                  RFC5545       RFC5545     
-           
+
+    
+  
+  en
+  
+  
+    
This document specifies a protocol that uses the iCalendar object specification to provide scheduling interoperability between different calendaring systems. This is done without reference to a specific transport protocol so as to allow multiple methods of communication between systems. Subsequent documents will define profiles of this protocol that use specific, interoperable methods of communication between systems.

+
+    
The iCalendar Transport-Independent Interoperability Protocol (iTIP) complements the iCalendar object specification by adding semantics for group scheduling methods commonly available in current calendaring systems. These scheduling methods permit two or more calendaring systems to perform transactions such as publishing, scheduling, rescheduling, responding to scheduling requests, negotiating changes, or canceling. [STANDARDS-TRACK]

+
+  
+  
+    
+      RFC5545
+      RFC5545
+    
+
+  
+  
+    
 RFC
-     5546           
+
+    5546
+  
+  
+    
 IETF
-      calendar   scheduling 
-   2024-07-30   
+
+  
+  calendar
+  scheduling
+
+
+  2024-12-01
+  
 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
-   https://www.rfc-editor.org/info/rfc8174   RFC 8174   10.17487/RFC8174   RFC8174        2017-05                       
-         B. Leiba       
-                            
+
+  https://www.rfc-editor.org/info/rfc8174
+  RFC 8174
+  10.17487/RFC8174
+  RFC8174
+  
+    2017-05
+  
+  
+    
+    
+      
+          B. Leiba       
+
+    
+  
+  
+    
+    
+      
 RFC Publisher
-                            
+
+    
+  
+  
+    
+    
+      
 RFC Series
-           en           
RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.

-                  RFC2119       RFC2119     
-           
+
+    
+  
+  en
+  
+  
+    
RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.

+
+  
+  
+    
+      RFC2119
+      RFC2119
+    
+
+  
+  
+    
 BCP
-     14           
+
+    14
+  
+  
+    
 RFC
-     8174           
+
+    8174
+  
+  
+    
 IETF
-    
-   2024-07-30   
+
+  
+
+
+  2024-10-16
+  
 Event Publishing Extensions to iCalendar
-   https://www.rfc-editor.org/info/rfc9073   RFC 9073   10.17487/RFC9073   RFC9073        2021-08                       
-         M. Douglass       
-                            
+
+  https://www.rfc-editor.org/info/rfc9073
+  RFC 9073
+  10.17487/RFC9073
+  RFC9073
+  
+    2021-08
+  
+  
+    
+    
+      
+          M. Douglass       
+
+    
+  
+  
+    
+    
+      
 RFC Publisher
-                            
+
+    
+  
+  
+    
+    
+      
 RFC Series
-           en           
This specification updates RFC 5545 by introducing a number of new iCalendar properties and components that are of particular use for event publishers and in social networking.

-     
This specification also defines a new "STRUCTURED-DATA" property for iCalendar (RFC 5545) to allow for data that is directly pertinent to an event or task to be included with the calendar data.

-                  RFC5545       RFC5545     
-           
+
+    
+  
+  en
+  
+  
+    
This specification updates RFC 5545 by introducing a number of new iCalendar properties and components that are of particular use for event publishers and in social networking.

+
+    
This specification also defines a new "STRUCTURED-DATA" property for iCalendar (RFC 5545) to allow for data that is directly pertinent to an event or task to be included with the calendar data.

+
+  
+  
+    
+      RFC5545
+      RFC5545
+    
+
+  
+  
+    
 RFC
-     9073           
+
+    9073
+  
+  
+    
 IETF
-      iCalendar   properties 
-   2024-07-30   
+
+  
+  iCalendar
+  properties
+
+
+  2024-12-01
+  
 "VALARM" Extensions for iCalendar
-   https://www.rfc-editor.org/info/rfc9074   RFC 9074   10.17487/RFC9074   RFC9074        2021-08                       
-         C. Daboo       
-                            
-         K. Murchison       
-                            
+
+  https://www.rfc-editor.org/info/rfc9074
+  RFC 9074
+  10.17487/RFC9074
+  RFC9074
+  
+    2021-08
+  
+  
+    
+    
+      
+          C. Daboo       
+
+    
+  
+  
+    
+    
+      
+          K. Murchison       
+
+    
+  
+  
+    
+    
+      
 RFC Publisher
-                            
+
+    
+  
+  
+    
+    
+      
 RFC Series
-           en           
This document defines a set of extensions to the iCalendar "VALARM" component to enhance the use of alarms and improve interoperability between clients and servers.

-     
This document updates RFC 5545.

-                  RFC5545       RFC5545     
-           
+
+    
+  
+  en
+  
+  
+    
This document defines a set of extensions to the iCalendar "VALARM" component to enhance the use of alarms and improve interoperability between clients and servers.

+
+    
This document updates RFC 5545.

+
+  
+  
+    
+      RFC5545
+      RFC5545
+    
+
+  
+  
+    
 RFC
-     9074           
+
+    9074
+  
+  
+    
 IETF
-      alarms   calendaring   iCalendar   CalDAV 
-   2024-07-30   
+
+  
+  alarms
+  calendaring
+  iCalendar
+  CalDAV
+
+
+  2024-10-16
+  
 Support for iCalendar Relationships
-   https://www.rfc-editor.org/info/rfc9253   RFC 9253   10.17487/RFC9253   RFC9253        2022-08                       
-         M. Douglass       
-                            
+
+  https://www.rfc-editor.org/info/rfc9253
+  RFC 9253
+  10.17487/RFC9253
+  RFC9253
+  
+    2022-08
+  
+  
+    
+    
+      
+          M. Douglass       
+
+    
+  
+  
+    
+    
+      
 RFC Publisher
-                            
+
+    
+  
+  
+    
+    
+      
 RFC Series
-           en           
This specification updates the iCalendar RELATED-TO property defined in RFC 5545 by adding new relation types and introduces new iCalendar properties (LINK, CONCEPT, and REFID) to allow better linking and grouping of iCalendar components and related data.

-                  RFC5545       RFC5545     
-           
+
+    
+  
+  en
+  
+  
+    
This specification updates the iCalendar RELATED-TO property defined in RFC 5545 by adding new relation types and introduces new iCalendar properties (LINK, CONCEPT, and REFID) to allow better linking and grouping of iCalendar components and related data.

+
+  
+  
+    
+      RFC5545
+      RFC5545
+    
+
+  
+  
+    
 RFC
-     9253           
+
+    9253
+  
+  
+    
 IETF
-      iCalendar   link   related-to   relationships 
-Douglass, M., draft-ietf-calext-subscription-upgrade, . 
-  <em>draft-ietf-calext-subscription-upgrade</em>
-https://datatracker.ietf.org/doc/draft-ietf-calext-subscription-upgrade/draft-ietf-calext-subscription-upgrade
+
+  
+  iCalendar
+  link
+  related-to
+  relationships
+
+Douglass, M.,
+draft-ietf-calext-subscription-upgrade,
+.
+    <em>draft-ietf-calext-subscription-upgrade</em>https://datatracker.ietf.org/doc/draft-ietf-calext-subscription-upgrade/draft-ietf-calext-subscription-upgrade
   
   
-    
-      M.
-      Douglass
-    
+            M.        Douglass     
   
 
 
-Informative References   2024-07-30   
+Informative References
+  2024-12-01
+  
 Business Process Model and Notation
-   https://www.omg.org/spec/BPMN/2.0.2/About-BPMN   https://www.omg.org/spec/BPMN/2.0.2/PDF   BPMN 2.0.2        2014-01           2014-01-01     2.0.2      Business Process Model and Notation has become the de-facto standard for business processes diagrams. It is intended to be used directly by the stakeholders who design, manage and realize business processes, but at the same time be precise enough to allow BPMN diagrams to be translated into software process components. BPMN has an easy-to-use flowchart-like notation that is independent of any particular implementation environment.        formal                  OMG BPMN 1.2     
-                  OMG BPMN 1.1     
-                  OMG BPMN 1.0     
-      RF-RAND   Business Modeling   Domain 
-  Apthorp, A., Daboo, C., Douglass, M., CalConnect, Task Architecture V1.0, . 
+
+  https://www.omg.org/spec/BPMN/2.0.2/About-BPMN
+  https://www.omg.org/spec/BPMN/2.0.2/PDF
+  OMG BPMN 2.0.2
+  
+    2014-01
+  
+  
+    2014-01-01
+    2.0.2
+  
+  Business Process Model and Notation has become the de-facto standard for business processes diagrams. It is intended to be used directly by the stakeholders who design, manage and realize business processes, but at the same time be precise enough to allow BPMN diagrams to be translated into software process components. BPMN has an easy-to-use flowchart-like notation that is independent of any particular implementation environment.
+  
+    formal
+  
+  
+    
+      OMG BPMN 1.2
+    
+
+  
+  
+    
+      OMG BPMN 1.1
+    
+
+  
+  
+    
+      OMG BPMN 1.0
+    
+
+  
+  RF-RAND
+  Business Modeling
+  Domain
+
+  Apthorp, A.,
+Daboo, C.,
+Douglass, M.,
+CalConnect, Task Architecture V1.0,
+.
+
   1.0
-  
-  <em>CalConnect, Task Architecture V1.0</em>
-
+      <em>CalConnect, Task Architecture V1.0</em>
   https://www.calconnect.org/architectures/Task%20Architecture%201.0.pdf
   (CalConnect Task Architecture V1.0
   
   
   
-    
-      A.
-      Apthorp
-    
+            A.        Apthorp     
   
 
   
   
   
-    
-      C.
-      Daboo
-    
+            C.        Daboo     
   
 
   
   
   
-    
-      M.
-      Douglass
-    
+            M.        Douglass     
   
 
 
-  Russell, N., ter Hofstede, A.H.M., Edmond, T., van der Aalst,, W.M.P., Workflow Resource Patterns, Eindhoven University of Technology, 2004, . 
+  Russell, N.,
+ter Hofstede, A.H.M.,
+Edmond, T.,
+van der Aalst,, W.M.P.,
+Workflow Resource Patterns,
+Eindhoven University of Technology,
+2004,
+.
+
   
-  
-  <em>Workflow Resource Patterns</em>
-
+      <em>Workflow Resource Patterns</em>
   http://www.workflowpatterns.com/patterns/resource/
   WfRP
   
@@ -1441,37 +1952,25 @@ is determined by the task organizer based on the "ATTENDEE" property status and
   
   
   
-    
-      N.
-      Russell
-    
+            N.        Russell     
   
 
   
   
   
-    
-      A.H.M.
-      ter Hofstede
-    
+            A.H.M.        ter Hofstede     
   
 
   
   
   
-    
-      T.
-      Edmond
-    
+            T.        Edmond     
   
 
   
   
   
-    
-      W.M.P.
-      van der Aalst,
-    
+            W.M.P.        van der Aalst,