More changes after AD evaluation.

Author: douglm

generated/draft-ietf-calext-ical-tasks.txt

@@ -257,7 +257,7 @@ Internet-Draft        Task Extensions to iCalendar            March 2025
    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 the "role"
-      paramdeter set to the value "NON-PARTICIPANT".
+      parameter set to the value "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

sources/sections-ietf/98-references.adoc

@@ -31,6 +31,14 @@ span:title[_CalConnect, Task Architecture V1.0_],
 span:uri.src[https://www.calconnect.org/architectures/Task%20Architecture%201.0.pdf].
 span:type[book]
 
+* [[[WsCalendar,nofetch(WsCalendar)]]],
+span:surname[Considine], span:initials[T.],
+span:surname[Douglass], span:initials[M.],
+span:title[_WS-Calendar Version 1.0_],
+span:date[2011],
+span:uri.src[https://docs.oasis-open.org/ws-calendar/ws-calendar-spec/v1.0/cs01/ws-calendar-spec-v1.0-cs01.pdf].
+span:type[book]
+
 * [[[WfRP,nofetch(WfRP)]]],
 span:surname[Russell], span:initials[N.],
 span:surname[ter Hofstede], span:initials[A.H.M.],

sources/sections/00-intro.adoc

@@ -2,7 +2,7 @@
 == Introduction
 
 This document specifies extensions to the existing Internet Calendaring and Scheduling Core Object Specification (iCalendar) <<RFC5545>>, 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. taxi dispatch systems,
-in smart power grids, business process management systems) as well as for human centered tasks.
+in smart power grids (see <<WsCalendar>>), business process management systems) as well as for human centered tasks.
 
 A "task" is a representation of an item of work assigned to an individual or organization. In the iCalendar Object Model <<RFC5545>> 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:
 Business processes - ranging from repetitive workflows to adaptive cases and trouble ticketing

sources/sections/03-terms.adoc

@@ -26,7 +26,7 @@ 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 the "role" paramdeter set to the value "NON-PARTICIPANT".
+an "Attendee" with the "role" parameter set to NON-PARTICIPANT.
 
 Resource::
 A resource in the scheduling context is any shared entity that can

sources/sections/08-task-specification.adoc

@@ -40,6 +40,8 @@ The external information may be data to be manipulated in performing the task.
 
 The "LINK" property can be used to relate a domain specific service to the task. For example, it might be a URI pointing to a web page where the status of the task can be directly manipulated.
 
+(Note: link relations below are for illustration only)
+
 [source]
 ----
 LINK;LINKREL="vacation-system";VALUE=URI:
@@ -49,7 +51,11 @@ LINK;LINKREL="vacation-system";VALUE=URI:
 Additionally, it might be used to link data specific to the task, for example an electronic copy
 of a signature taken to confirm delivery of a package.
 
-(Note: link relations below are for illustration only)
+[source]
+----
+LINK;LINKREL="electronic-signature";VALUE=URI:
+ http://example.com/delivery/sig1234.jpg
+----
 
 The <<RFC9253>> "REFID" property is used to identify a key
 used to group tasks by that key.
@@ -66,9 +72,3 @@ between tasks as found in project management to be specified as well as parent/c
 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.
 
-
-[source]
-----
-LINK;LINKREL="electronic-signature";VALUE=URI:
- http://example.com/delivery/sig1234.jpg
-----

sources/sections/11-status-reporting.adoc

@@ -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" calendar components can be added to provide additional
+change, further "VSTATUS" calendar components can be added to provide additional
 information.
 
 [source]
@@ -54,13 +54,23 @@ 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
+the tasks.
+
+=== Updating the overall status
+Only the Task Organizer, or the server acting as the Organizers proxy,
+may change or add "VSTATUS" calendar components and the "STATUS" property.
+
+The overall VSTATUS will be changed in response to incoming Attendee replies. Each change of the overall VSTATUS MUST be accompanied by a change to the STATUS.
+
+Note there is no defined ordering of properties and components so the
+DTSTAMP property SHOULD be set for each VSTATUS component to preserve ordering.
 
 [[attendee-participant]]
 === Relating reason and comments to "ATTENDEE" property status changes.
 
 The <<RFC9073>> "PARTICIPANT" calendar component can be used to provide additional
-information about why an "ATTENDEE" property participation status has changed.
+information about why an "ATTENDEE" property participation status has changed
+following the guidelines set out in <<RFC9073, section=7.1>>.
 The "COMMENT" property can also
 be used to include additional human-readable information about why the
 associated "STATUS" or "ATTENDEE" property changed. For example, if a driver