Re: [calsify] AD review of draft-ietf-calext-ical-relations-05

[Michael Douglass <[e-mail]>]

Just dealing with the abnf issues. Can I try out a suggestion for 
section 8.1 - The RELATED-TO abnf

On 11/19/20 14:08, Barry Leiba wrote:
> — Section 8.1 —
>
>        definition here extends the definition in Section 3.8.4.5. of
>        [RFC5545]
>
> Also here: remove the dot at the end of the section number.
>
> For the ABNF in this section I have the same comments as for the ABNF
> in Section 7.1.  In addition, this defines “relparam”, but “relparam”
> is already defined in Section 5.1.  That needs to be fixed.
>

OLD

related    = "RELATED-TO" relparam ( ":" text ) /
              (
                ";" "VALUE" "=" "UID"
                ":" uid
              )
              (
                ";" "VALUE" "=" "URI"
                ":" uri
              )
              CRLF

relparam   = *(
             ;
             ; The following are OPTIONAL,
             ; but MUST NOT occur more than once.
             ;
             (";" reltypeparam) /
             (";" gapparam) /
             ;
             ; The following is OPTIONAL,
             ; and MAY occur more than once.
             ;
             (";" other-param)
             ;
             )

NEW

related    = "RELATED-TO" relparam ( ":" text ) /
              (
                ";" "VALUE" "=" "UID"
                ":" uid
              ) /
              (
                ";" "VALUE" "=" "URI"
                ":" uri
              )
              CRLF

relparam   = ; the elements herein may appear in any order,
              ; and the order is not significant.
              [";" reltypeparam]
              [";" gapparam]
              *(";" other-param)

END

I'm not sure that this construct is still the best way to relate a VALUE 
parameter to a specific value type. It still seems to constrain the order.

Does this work better?

START

related    = "RELATED-TO" relparam ":"
              ( uid /  ; for VALUE=UID
                uri /  ; for VALUE=URI
                text ) ; for VALUE=TEXT or default
              CRLF

relparam   = ; the elements herein may appear in any order,
              ; and the order is not significant.
              [";" ("VALUE" "=" "UID" /
                    "VALUE" "=" "URI" /
                    "VALUE" "=" "TEXT")]
              [";" reltypeparam]
              [";" gapparam]
              *(";" other-param)

END

This seems to do the job - if it works I can redo the abnf for the other 
properties (and for eventpub)