Can we separate the specification text into normative or informative?
Opened this issue · 5 comments
OGC Standard documents usually have a background in-depth description in Section 6, followed by normative text in Section 7.
Is this too much work? The current spec seems to have normative and informative text completely intermingled.
I suggest we leave the Spec more or less as we stripped it from covjson.org, but with the SHALL/MUST statements numbered, and keep them in a Section 6&7, both normative and informative together.
I have made a PR with an integrated version of the spec inside an OGC framework. Still need to number and extract to an Annex the SHALL/MUST and SHOULD statements,
Personally, I quite like having informative examples next to the relevant normative text. But it does mean that the document appears longer. There may be value in having a shorter normative section, and I suppose this does make it easier to derive a test suite.
I propose that this is for a full OGC Standard rather than an OGC Community Standard, as it would be too much work in the short term to separate out all of the normative and informative statements, and their examples, in the current document to populate two separate chapters.
The specification section is now titled "CoverageJSON Encoding: Normative with Informative Examples".