Re: [Gen-art] Genart last call review of draft-ietf-httpapi-link-template-02

[Mark Nottingham <[e-mail]>]

Hi Christer,

Thanks for the review; responses below.

> On 16 May 2023, at 1:37 pm, Christer Holmberg via Datatracker <[e-mail]> wrote:
[...]
> Q2_1: There is no ABNF for the header field. There are examples using both
> quotes ("/{username}") and angle brackets (</books/{book_id}/author>), so
> please include the ABNF.

This is a Structured Field; in the HTTP community, we've agreed that documenting them with ABNF is not good practice.

> Q2_2: The text says "Parameter values MUST be Strings."
> 
> It is unclear what "Strings" means. Does it mean that parameter values must be
> encoded as quoted-strings? If so, why? RFC8288 says that parameter values can
> be encoded both as token and quoted-string.

S 1.1: "This specification uses the following terms from [STRUCTURED-FIELDS]: List, String, Parameter."

> Q2_3: The text says:
> 
>      Link-Template: </books/{book_id}/author>;
>                       rel="author" anchor="#{book_id}"
> 
> Is there a ";" missing between the rel and anchor parameters?

Yes; already fixed.

> Q2_4: The text says:
> 
>        Link-Template: "/widgets/{widget_id}"
>                       rel="https://example.org/rel/widget";
>                       var-base="https://example.org/vars/"
> 
> Is there a ";" missing at the end of the first line?

Yes - thanks!

Cheers,

--
Mark Nottingham   https://www.mnot.net/