Re: [httpapi] New Version Notification for draft-nottingham-link-template-03.txt

We are also currently using Link headers with a templated="true" property,
but running into a specific problem when the URI Template contains a "*"
character (which isn't permitted in URIs, and therefore not permitted in a
Link header).

A simple approach that supports the equivalent of the Link header for URI
Templates would be ideal for what we're building - so I'm very supportive
of Mark's draft, and would encourage adoption.

To echo what others mentioned about "var-base", I also found it a bit
confusing, and I'm not sure if it's truly needed.

Thanks,

-Dan

On Wed, Sep 1, 2021 at 5:57 PM Mark Nottingham <mnot@mnot.net> wrote:

> Hi Max,
>
> I think that how variables are defined / operate is going to be one of the
> things we'll need to discuss. var-base is just an initial (and incomplete)
> stab at that.
>
> Cheers,
>
>
> > On 2 Sep 2021, at 10:49 am, Max Maton <info@maxmaton.nl> wrote:
> >
> > Hi Mark,
> >
> > It seems an interesting proposal, currently we use the Link header with
> an `templated="true"` property. I have a two questions:
> >
> >  - Am I correct in assuming that the variables are defined by the media
> type documentation for the returned Content-Type?
> >  - If so, wouldn't it make sense to leave the var-base out of the
> specification, given that people defining media types are free to add
> parameters and are free to define rules about how to resolve the variables?
> >
> > Best regards,
> >
> > Max Maton
> >
> >
> >
> > On Wed, Sep 1, 2021, at 07:36, Mark Nottingham wrote:
> >> Hi all,
> >>
> >> I've had this spec on the back burner for a *long* time, because I
> wanted to make sure it was actually useful to someone before progressing it.
> >>
> >> I've heard from a few people that it would be useful for them in the
> real world, so I'd like the WG to consider adoption.
> >>
> >> Any thoughts?
> >>
> >> Cheers,
> >>
> >>
> >>> Begin forwarded message:
> >>>
> >>> From: internet-drafts@ietf.org
> >>> Subject: New Version Notification for
> draft-nottingham-link-template-03.txt
> >>> Date: 1 September 2021 at 3:35:21 pm AEST
> >>> To: "Mark Nottingham" <mnot@mnot.net>
> >>>
> >>>
> >>> A new version of I-D, draft-nottingham-link-template-03.txt
> >>> has been successfully submitted by Mark Nottingham and posted to the
> >>> IETF repository.
> >>>
> >>> Name:  draft-nottingham-link-template
> >>> Revision: 03
> >>> Title:  The Link-Template HTTP Header Field
> >>> Document date: 2021-09-01
> >>> Group:  Individual Submission
> >>> Pages:  5
> >>> URL:
> https://www.ietf.org/archive/id/draft-nottingham-link-template-03.txt
> >>> Status:
> https://datatracker.ietf.org/doc/draft-nottingham-link-template/
> >>> Html:
> https://www.ietf.org/archive/id/draft-nottingham-link-template-03.html
> >>> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-nottingham-link-template
> >>> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-nottingham-link-template-03
> >>>
> >>> Abstract:
> >>>   This specification defines the Link-Template HTTP header field,
> >>>   providing a means for describing the structure of a link between two
> >>>   resources, so that new links can be generated.
> >>>
> >>>
> >>>
> >>>
> >>> The IETF Secretariat
> >>>
> >>
> >> --
> >> Mark Nottingham   https://www.mnot.net/
> >> --
> >> httpapi mailing list
> >> httpapi@ietf.org
> >> https://www.ietf.org/mailman/listinfo/httpapi
>
> --
> Mark Nottingham   https://www.mnot.net/
>
> --
> httpapi mailing list
> httpapi@ietf.org
> https://www.ietf.org/mailman/listinfo/httpapi
>

>