diff --git a/ical-tasks/sources/draft-apthorp-ical-tasks.adoc b/ical-tasks/sources/draft-apthorp-ical-tasks.adoc index a8e58bb..d848889 100644 --- a/ical-tasks/sources/draft-apthorp-ical-tasks.adoc +++ b/ical-tasks/sources/draft-apthorp-ical-tasks.adoc @@ -68,7 +68,7 @@ include::sections/09-deadlines.adoc[] include::sections/10-scheduling.adoc[] include::sections/11-status-reporting.adoc[] -include::sections/50-new-parameters.adoc[] +include::sections/50-modifications-to-calendar-components.adoc[] include::sections/51-new-parameter-values.adoc[] include::sections/52-new-properties.adoc[] include::sections/53-property-extensions.adoc[] diff --git a/ical-tasks/sources/sections-ietf/98-references.adoc b/ical-tasks/sources/sections-ietf/98-references.adoc index 978ed0a..b5f278c 100644 --- a/ical-tasks/sources/sections-ietf/98-references.adoc +++ b/ical-tasks/sources/sections-ietf/98-references.adoc @@ -11,7 +11,12 @@ * [[[RFC9073,RFC 9073]]] * [[[RFC9074,RFC 9074]]] * [[[RFC9253,RFC 9253]]] -* [[[draft-ietf-calext-subscription-upgrade,draft-ietf-calext-subscription-upgrade]]] +* [[[draft-ietf-calext-subscription-upgrade]]], +span:surname[Douglass], span:initials[M.], +span:title[_draft-ietf-calext-subscription-upgrade_], +span:uri.src[https://datatracker.ietf.org/doc/draft-ietf-calext-subscription-upgrade/]. +span:type[book] + [bibliography] == Informative References diff --git a/ical-tasks/sources/sections/00-abstract.adoc b/ical-tasks/sources/sections/00-abstract.adoc index a6a40d8..ae3a90d 100644 --- a/ical-tasks/sources/sections/00-abstract.adoc +++ b/ical-tasks/sources/sections/00-abstract.adoc @@ -5,7 +5,7 @@ The Internet Calendaring and Scheduling Core Object Specification (iCalendar) (R 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 pther contexts, such as process control and project management. +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 diff --git a/ical-tasks/sources/sections/03-terms.adoc b/ical-tasks/sources/sections/03-terms.adoc index 5a278d8..45d74db 100644 --- a/ical-tasks/sources/sections/03-terms.adoc +++ b/ical-tasks/sources/sections/03-terms.adoc @@ -29,7 +29,10 @@ have interest in all tasks that have not been completed. Often represented as an "Attendee" with ROLE=NON-PARTICIPANT. Resource:: -A resource in the scheduling context is any shared entity that can be scheduled by a calendar user, but does not control its own attendance status. Resources can be of "Location", "Equipment", or "Role" type. +A resource in the scheduling context is any shared entity that can +be scheduled by a calendar user, but does not control its own +attendance status. Examples of such resources are locations such +as a booakble conference room or equipment such as projectors. Task:: 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. diff --git a/ical-tasks/sources/sections/07-task-extensions.adoc b/ical-tasks/sources/sections/07-task-extensions.adoc index e270143..be79c82 100644 --- a/ical-tasks/sources/sections/07-task-extensions.adoc +++ b/ical-tasks/sources/sections/07-task-extensions.adoc @@ -9,8 +9,8 @@ Task Specification:: improved ability to specify domain specific tasks Task Deadlines, Milestones and Time Planning:: clarification of deadlines and extension for task duration to support task time planning -Task Scheduling and Assignment:: ensure support for common pattens of scheduling and assigning tasks +Task Scheduling and Assignment:: ensure support for common patterns of scheduling and assigning tasks -Task Status Tracking:: improved granularity in status tracking information and alerting task actors to pending or actual task status changes +Task Status Tracking:: improved granularity in status tracking information and alerting task actors of pending or actual task status changes These extensions are supported mainly by additions to the properties and parameters used within the "VTODO" calendar component. diff --git a/ical-tasks/sources/sections/08-task-specification.adoc b/ical-tasks/sources/sections/08-task-specification.adoc index fb64733..675bd76 100644 --- a/ical-tasks/sources/sections/08-task-specification.adoc +++ b/ical-tasks/sources/sections/08-task-specification.adoc @@ -4,7 +4,7 @@ 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 current +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: @@ -51,7 +51,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 +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]] diff --git a/ical-tasks/sources/sections/09-deadlines.adoc b/ical-tasks/sources/sections/09-deadlines.adoc index 71e304a..02dfdcc 100644 --- a/ical-tasks/sources/sections/09-deadlines.adoc +++ b/ical-tasks/sources/sections/09-deadlines.adoc @@ -4,14 +4,15 @@ === Deadlines Deadlines for starting and finishing a task are defined -by the DTSTART, DUE and DURATION properties. DTSTART -represents the earliest start time for beginning work -on a task. DUE, or DTSTART + DURATION represent the +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, there is currently no way to +performed. However, <> provides no way to indicate how long the task is expected to take. This -document defines a new property, in <> ESTIMATED-DURATION, to +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 @@ -22,6 +23,6 @@ time to them. === Milestones A task that has intermediary deadlines (i.e., milestones) SHOULD be -expressed by child "VTODO" calendar component (i.e., sub-tasks +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. diff --git a/ical-tasks/sources/sections/102-iana.adoc b/ical-tasks/sources/sections/102-iana.adoc index cf35c65..c2c70d1 100644 --- a/ical-tasks/sources/sections/102-iana.adoc +++ b/ical-tasks/sources/sections/102-iana.adoc @@ -49,6 +49,7 @@ The following table has been used to initialize the Task Mode registry. | AUTOMATIC-COMPLETION | Current | This Spec, <> | AUTOMATIC-FAILURE | Current | This Spec, <> +| AUTOMATIC | Current | This Spec, <> | CLIENT | Current | This Spec, <> | SERVER | Current | This Spec, <> diff --git a/ical-tasks/sources/sections/11-status-reporting.adoc b/ical-tasks/sources/sections/11-status-reporting.adoc index aab72c4..6f1d4b9 100644 --- a/ical-tasks/sources/sections/11-status-reporting.adoc +++ b/ical-tasks/sources/sections/11-status-reporting.adoc @@ -7,7 +7,7 @@ This document defines a new "VSTATUS" calendar component (see section <>) 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. +information on why, the "REASON" property and when, the "DTSTAMP" property, a status has changed. In addition, new status values are specified to provide for task suspension, failure and preparation. @@ -25,7 +25,7 @@ END:VSTATUS === Comments associated to reasons and status changes Multiple comments and reasons may have the same status. As situations -change further VSTATUS components can be added to provide additional +change further "VSTATUS" calendar components can be added to provide additional information. [source] @@ -51,8 +51,10 @@ DTSTAMP:20220212T180451Z END:VSTATUS ---- -Note that the "VSTATUS" calendar component not intended to be used as a history -of changes to a tasks properties. The purpose of "VSTATUS" calendar component is only to document changes related to fulfilling the tasks +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. @@ -108,5 +110,5 @@ within a calendar (see <>). === Automated Status Changes -A new property, TASK-MODE, is introduced to instruct servers to apply +A new "TASK-MODE" property is introduced to instruct servers to apply automated operations for changing the status of a task. diff --git a/ical-tasks/sources/sections/50-modifications-to-calendar-components.adoc b/ical-tasks/sources/sections/50-modifications-to-calendar-components.adoc index e4953cb..4b5b834 100644 --- a/ical-tasks/sources/sections/50-modifications-to-calendar-components.adoc +++ b/ical-tasks/sources/sections/50-modifications-to-calendar-components.adoc @@ -10,12 +10,14 @@ 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 + 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 + todoprop *alarmc *participantc *locationc + *resourcec *statusc "END" ":" "VTODO" CRLF ; Addition of properties ESTIMATED-DURATION and TASK-MODE to VTODO