Skip to content

Commit 6c7d4a3

Browse files
committed
Changes requested bty Mohamed Boucadair
1 parent 02fd6f7 commit 6c7d4a3

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

sources/draft-ietf-calext-ical-tasks.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
= Task Extensions to iCalendar
22
:doctype: internet-draft
3-
:docnumber: draft-ietf-calext-ical-tasks-15
3+
:docnumber: draft-ietf-calext-ical-tasks-16
44
:status: standard
55
:ipr: trust200902
66
:consensus: true

sources/sections/00-intro.adoc

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
== Introduction
33

4-
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,
4+
This document specifies extensions to the 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,
55
in smart power grids (see <<WsCalendar>>), business process management systems) as well as for human centered tasks.
66

77
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:
@@ -12,11 +12,11 @@ The extensions specified in this document enhance and standardize the following:
1212

1313
The specification of tasks:: how a task type is defined and the relationships between tasks See <<task-specification>>.
1414

15-
Their planning and scheduling:: Improved specification of deadlines and
16-
estimated time. See <<deadlines>>
15+
Task planning and scheduling:: Improved specification of deadlines and
16+
estimated time for completion. See <<deadlines>>
1717

18-
Task assignment, and status reporting:: The addition of VSTATUS,
19-
see <<modifications-to-calendar-components>> allows for more detailed
18+
Task assignment and status reporting:: The addition of VSTATUS,
19+
(<<modifications-to-calendar-components>>) allows for more detailed
2020
reports. See <<status-reporting>>.
2121

2222
These extensions are defined within the context of an overall architecture for task calendaring and scheduling, which elaborates that supported by <<RFC5545>> and related standards.

0 commit comments

Comments
 (0)