In terms of technical writing the spec in its current form is very hard to read.
I believe the text has some very basic technical writing quality issues.
Im must say im not a technical writer professional.
Most of the basic technical writing ideas in say https://developers.google.com/tech-writing/one could solve these issues.
If you are a naive registry implementor like me, one challenge is skimming the text, and scanning it quickly. Finding logical organization of say protocol requests / responses, header rules etc and notes.
But its also part of the specs charm.
The spec is a perfect, exercise in applying these ideas, i did a rewrite here (withouth llm) https://github.com/martencassel/distribution-spec
A simple solution is to break up the very long paragraphs into logical chunks that flow with the content, and present them in a more skimmable way.
In terms of technical writing the spec in its current form is very hard to read.
I believe the text has some very basic technical writing quality issues.
Im must say im not a technical writer professional.
Most of the basic technical writing ideas in say https://developers.google.com/tech-writing/one could solve these issues.
If you are a naive registry implementor like me, one challenge is skimming the text, and scanning it quickly. Finding logical organization of say protocol requests / responses, header rules etc and notes.
But its also part of the specs charm.
The spec is a perfect, exercise in applying these ideas, i did a rewrite here (withouth llm) https://github.com/martencassel/distribution-spec
A simple solution is to break up the very long paragraphs into logical chunks that flow with the content, and present them in a more skimmable way.