Re: Status of v1.12 privileged specification
Allen Baum
Just to point out that I was pointing out only one specific example of a document (where I recently encountered this) that used section numbering references. It's not the only one, it's all over. This isn't just "if it hurts when you do that, don't do that" after the fact kind of advice that is required; we need a stronger statement somewhere that clearly says that external references to the spec must not use just section numbers because they will change. Andrew's suggestion is a good one - but it needs to be communicated. A slightly different issue is that these documents that this may not take into account references to extensions that have been ratified but have not been updated in the most up-to-date ratified spec yet but are in the draft). Maybe that problem will go away when it's all in asciidoc and updates can be made more timely.
On Tue, Jul 26, 2022 at 11:46 PM <krste@...> wrote:
|
|