Document: draft-ietf-calext-icalendar-jscalendar-extensions
Title: iCalendar Format Extensions for JSCalendar
Reviewer: Linda Dunbar
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-calext-icalendar-jscalendar-extensions-08
Reviewer: Linda Dunbar
Review Date: 2026-10-14
IETF LC End Date: 2026-10-14
IESG Telechat date: Not scheduled for a telechat

Summary: This document defines extensions to iCalendar to support semantics
introduced by JSCalendar. The document is well written, but have a few minor
issues.

Major issues: None.

Minor issues:

Section 4.1 specifies:
Value Type: URI -- no default

The ABNF defines:
coordparam = *(
    (";" "VALUE" "=" "URI") /
    (";" other-param)
)

The accompanying comment states that the VALUE=URI parameter is REQUIRED, but
the * repetition permits zero occurrences. Consequently, the grammar permits a
COORDINATES property without the VALUE parameter.

Question: is VALUE=URI is mandatory?  If yes, need to revise the ABNF to
require exactly one occurrence, while still allowing other parameters. The same
concern applies to SHOW-WITHOUT-TIME in Section 4.2.

Section 5.1 defines OWNER as indicating that a calendar user can make changes
affecting all participants. Section 6 correctly clarifies that the OWNER role
does not itself grant authorization. Nevertheless, Section 5.1 could be
misinterpreted as assigning editing privileges through the ROLE parameter.

Nits/editorial comments:

- 4.1   "In contrast to the the 'GEO' property": remove the duplicated "the"
- 4.1   "The property value MUST a URI" -> "The property value MUST be a URI"

Best Regards,
Linda Dunbar


_______________________________________________
Gen-art mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to