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

Re: Structured Headers: URI type (#782)

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Thu, 09 May 2019 06:02:57 +0000
To: Matthew Kerwin <matthew@kerwin.net.au>
cc: Julian Reschke <julian.reschke@gmx.de>, Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <43350.1557381777@critter.freebsd.dk>
--------
In message <CACweHNCFSj-zGO-O=U4CZYBfqL-5FcnwmMZeB-oih7w1nAFC0g@mail.gmail.com>
, Matthew Kerwin writes:

>I keep thinking about, like, schemas or profiles or Java generics. I wonder
>if there's some sort of extension or informational document to write that
>could help, or at least offer guidance.

Mark and I talked about having a section about how other ID's should
use and point to SH, but sort of let it slip because A) we don't want
to write guidance based on zero experience and B) one wrong step and
you are ankle-deep in designing schemas.

At some point down the road a guidance document will probably be
appropriate.

PS: Reminds me: Why does ABNF not have an 'import' facility ?

This would be much clearer:

	import token68 from [RFC7235]

Than (from 7540):

	The ABNF [RFC5234] production for "token68" is defined in
	Section 2.1 of [RFC7235].


-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
Received on Thursday, 9 May 2019 06:03:33 UTC

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