Re: [apps-discuss] URI templates in Link header fields

[Julian Reschke <[e-mail]>]

On 2016-08-29 17:30, Erik Wilde wrote:
> hello julian
>
> On 2016-08-29 01:42, Julian Reschke wrote:
>> In the meantime, I heard of a few cases where people were trying to use
>> templates in Link header fields (an obvious thing to do), and came up
>> with hacks to do so with the existing Link header field.
>> I'm tempted to work on a small spec that defines an experimental new
>> header field, similar to Link but allowing templates.
>
> @mnot has been working on collecting ideas for an update to RFC 5988 for
> a while now. maybe that's one more motivation to go forward with this?
> i'd certainly be willing to put in some time to get it off the ground.
>
> https://github.com/mnot/I-D/issues?q=is%3Aissue+is%3Aopen+label%3Arfc5988bis

Yep, I'm aware of that...

>> Is anybody aware of existing code trying to use templates in Link header
>> fields? If so, please report over here (or in doubt send private email).
>
> this is not really code, but people want to use URI templates and there
> have been some efforts to provide a context that makes that more easy:
>
> - @mnot's https://tools.ietf.org/html/draft-nottingham-link-hint
>
> - my own https://tools.ietf.org/html/draft-wilde-link-desc
>
> - part of the JSON home model:
> https://tools.ietf.org/html/draft-nottingham-json-home#section-3.1
>
> if i recall correctly all of these have slightly different use cases and
> models, but (unsurprisingly) also a lot of overlap. it would be great to
> consolidate all of this so that tooling and implementations can rely on
> a robust spec.

Agreed.

Thanks for the feedback, Julian