W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2019

Re: Structured Headers: URI type (#782)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 13 Jun 2019 11:06:31 +0200
To: Mark Nottingham <mnot@mnot.net>, Tommy Pauly <tpauly@apple.com>
Cc: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>, Poul-Henning Kamp <phk@phk.freebsd.dk>
Message-ID: <8e82a039-adaf-8542-a8b5-ab76a5653797@gmx.de>
On 13.06.2019 10:46, Mark Nottingham wrote:
> Again, I hope we're not voting.

No, we are not.

> My argument: given that the whole point of SH is to have strongly interoperable, crisply defined data models, and that anything beyond "it's a string" is a minefield regarding URIs, the prudent thing to do here is to punt on this until we're more confident. It's entirely possible to do this in a future revision / extension, and we really need to ship this spec.

I'm not convinced that adding things later will work well. I also note
that if we really need to ship this spec, we should try harder to finish
it (this thread started four weeks ago).

Finally, I still think that allowing to map complex fields like "Link"
to this syntax would be good in that it would encourage people to (a)
include the generic SH parser and (b) actually use if for "Link".

Best regards, Julian
Received on Thursday, 13 June 2019 09:07:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:34 UTC