RFC Errata
Found 2 records.
Status: Reported (2)
RFC 9253, "Support for iCalendar Relationships", August 2022
Source of RFC: calext (art)
Errata ID: 8156
Status: Reported
Type: Technical
Publication Format(s) : HTML
Reported By: Robert Stepanek
Date Reported: 2024-10-24
Section 8.2 says:
linkparam = (";" "VALUE" "=" ("XML-REFERENCE" / "URI" / "UID")) 1*(";" linkrelparam) 1*(";" fmttypeparam) 1*(";" labelparam) 1*(";" languageparam) *(";" other-param) ; the elements herein may appear in any order, ; and the order is not significant.
It should say:
linkparam = (";" "VALUE" "=" ("XML-REFERENCE" / "URI" / "UID")) 1*(";" linkrelparam) [";" fmttypeparam] [";" labelparam] [";" languageparam] *(";" other-param) ; the elements herein may appear in any order, ; and the order is not significant.
Notes:
The original text defines that all of the LINKREL, FMTTYPE, LABEL, LANGUAGE parameters MUST be set at least once. However, the examples do not adhere to this rule. Instead they suggest that only LINKREL and VALUE are mandatory.
The corrected text defines the FMTTYPE, LABEL, and LANGUAGE parameters to be optional and that they only should be set at most once.
The linkparam definition still allows the LINKREL parameter to be set multiple times. This might not have been the original intent. The ABNF might also get updated to restrict it to be set exactly once.
Errata ID: 8157
Status: Reported
Type: Technical
Publication Format(s) : HTML
Reported By: Robert Stepanek
Date Reported: 2024-10-24
Section 8.2 says:
LINK;LINKREL=SOURCE;LABEL=Venue;VALUE=URI: https://example.com/events
It should say:
LINK;LINKREL=ABOUT;LABEL=Venue;VALUE=URI: https://example.com/events
Notes:
This section defines the "link relation type [to be] defined in Section 2.1 of [RFC8288]". But the SOURCE link relation in the example is not a valid link relation type according to RFC8288, as it is not registered at IANA (https://www.iana.org/assignments/link-relations/link-relations.xhtml).
The example should be updated to either:
1. replace SOURCE in the example with a registered link relation type (as depicted in the corrected text), or
2. register the SOURCE relation type at IANA according to RFC 8288, or
3. replace SOURCE in the example with an extension link relation type, e.g. https://example.com/rel/source