- From: Justin Richer <jricher@mit.edu>
- Date: Tue, 14 Jun 2022 16:11:15 -0400
- To: Roberto Polli <robipolli@gmail.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>, Giuseppe De Marco <giuseppe.demarco@teamdigitale.governo.it>
It depends on what parts you’re referencing. For example (and what might have triggered this question): Signatures only uses the WHATWG spec in order to define the query-parameters, which is not part of generic URI syntax. Everywhere else, Signatures uses the IETF RFCs because it’s talking about those general purpose URI parts like path and query. — Justin > On Jun 14, 2022, at 5:55 AM, Roberto Polli <robipolli@gmail.com> wrote: > > Dear all, > > I noted that some specs reference URL/URI from https://url.spec.whatwg.org/ > while others use https://www.rfc-editor.org/rfc/rfc3986 & co. > > This can be relevant if you need normative references to e.g. percent encoding > and/or application/www-form-urlencoded where IANA media type registration > references https://url.spec.whatwg.org/ > > > Which is the rationale for filing a specification under the w3c with > respect to the IETF? > I assume that those specs are aligned, isn't it? > Which is the organization that ensures that alignment? > Which spec should I reference in an HTTP derived protocol > such as OAuth2 ? > > Thanks and have a nice day, > R. >
Received on Tuesday, 14 June 2022 20:11:33 UTC