- From: Mark Nottingham <mnot@mnot.net>
- Date: Wed, 21 Aug 2024 10:48:32 +1000
- To: Roman Danyliw <rdd@cert.org>
- Cc: The IESG <iesg@ietf.org>, draft-ietf-httpbis-compression-dictionary@ietf.org, httpbis-chairs@ietf.org, HTTP Working Group <ietf-http-wg@w3.org>
> On 21 Aug 2024, at 10:29 AM, Roman Danyliw via Datatracker <noreply@ietf.org> wrote: > > ** How to best cite living specifications? > > [FETCH] WHATWG, "Fetch - Living Standard", June 2024, > <https://fetch.spec.whatwg.org>. > [URLPattern] > WHATWG, "URL Pattern - Living Standard", March 2024, > <https://urlpattern.spec.whatwg.org/>. > > Realizing that these are living specifications, I don’t understand how the > above citations are providing stable references. How does one get the “March > 2024 version” of “URL Pattern”? Is there a specific GitHub commit reference > that can be used instead? This is well established practice previously approved by the IESG - See eg RFC9421, RFC9163, RFC9205, RFC8942. WHATWG guarantees semantic backwards compatibility of their specs, and can provide anchors if needed. See <https://whatwg.org/faq#change-at-any-time> and <https://whatwg.org/working-mode#anchors>. -- Mark Nottingham https://www.mnot.net/
Received on Wednesday, 21 August 2024 00:48:42 UTC