Skip to content

Commit fb9c670

Browse files
committed
Changes after AD evaluation.
1 parent 13a0901 commit fb9c670

File tree

6 files changed

+36
-13
lines changed

6 files changed

+36
-13
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
= Task Extensions to iCalendar
22
:doctype: internet-draft
3-
:docnumber: draft-ietf-calext-ical-tasks-11
3+
:docnumber: draft-ietf-calext-ical-tasks-12
44
:status: standard
55
:ipr: trust200902
66
:consensus: true
77
:updates: RFC5545
88
:submission-type: IETF
99
:area: Internet
1010
:intended-series: full-standard
11-
:revdate: 2024-12-01
11+
:revdate: 2025-02-24
1212
:fullname: Adrian Apthorp
1313
:lastname: Apthorp
1414
:forename_initials: A.

sources/sections/09-deadlines.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ visualize when tasks should be performed and allocate
2222
time to them.
2323

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

sources/sections/51-new-parameter-values.adoc

Lines changed: 21 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,30 @@ Participant status parameter type values are defined in
1010
<<RFC5545,section=3.2.12>>. This specification redefines that type
1111
to include the new value FAILED for "VTODO" calendar components.
1212

13-
Format Definition:: This property parameter is extended by the following notation:
13+
Format Definition:: This property parameter is redefined by the
14+
following notation which adds the value "FAILED":
1415

1516
[source,bnf]
1617
----
17-
partstat-todo =/ *("FAILED") ; To-do cannot be completed
18+
partstat-todo = ("NEEDS-ACTION" ; To-do needs action
19+
/ "ACCEPTED" ; To-do accepted
20+
/ "DECLINED" ; To-do declined
21+
/ "TENTATIVE" ; To-do tentatively
22+
; accepted
23+
/ "DELEGATED" ; To-do delegated
24+
/ "COMPLETED" ; To-do completed
25+
; COMPLETED property has
26+
; DATE-TIME completed
27+
/ "IN-PROCESS" ; To-do in process of
28+
; being completed
29+
/ "FAILED" ; To-do cannot be
30+
; completed
31+
/ x-name ; Experimental status
32+
/ iana-token) ; Other IANA-registered
33+
; status
34+
; These are the participation statuses for a "VTODO".
35+
; Default is NEEDS-ACTION.
36+
1837
----
1938

2039
Example::

sources/sections/52-new-properties.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ durparam = *(";" other-param)
2828
Description:: In a "VTODO" calendar component the property MAY be
2929
used to specify the estimated duration for the to-do, with or without
3030
an explicit time window in which the event should be started and completed.
31-
When present, "DTSTART" and "DUE"/"DURATION" properties represent the
31+
When present, "DTSTART" and "DUE" or "DTSTART" and "DURATION" properties represent the
3232
window in which the task can be performed. The "ESTIMATED-DURATION" property
3333
SHOULD be passed from the organizer to the "Attendee" in iTIP <<RFC5546>> messages.
3434

sources/sections/53-property-extensions.adoc

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -56,15 +56,19 @@ specification extends that property to include new values
5656
associated with "VTODO" calendar components (See Appendix A for
5757
examples of the task state lifecycle).
5858

59-
Format Definition:: The "STATUS" property parameter list is augmented
60-
as follows:
59+
Format Definition:: The "STATUS" property parameter list for tasks
60+
is redefined by the addition of the values "PENDING" and "FAILED":
6161

6262
[source,bnf]
6363
----
64-
statvalue-todo = / "PENDING" ;Indicates a to-do has been
65-
;created and accepted, but has
66-
; not yet started.
67-
/ "FAILED" ;Indicates to-do has failed.
64+
statvalue-todo = "NEEDS-ACTION" ;Indicates to-do needs action.
65+
/ "COMPLETED" ;Indicates to-do completed.
66+
/ "IN-PROCESS" ;Indicates to-do in process of.
67+
/ "CANCELLED" ;Indicates to-do was cancelled.
68+
/ "PENDING" ;Indicates a to-do has been
69+
;created and accepted, but has
70+
; not yet started.
71+
/ "FAILED" ;Indicates to-do has failed.
6872
;Extended status values for "VTODO" calendar component.
6973
----
7074

sources/sections/60-caldav.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ In order for a CalDAV client to know what task modes are available, a CalDAV ser
99

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

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

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

0 commit comments

Comments
 (0)