Closed chris-little closed 2 years ago
@joanma747, @jonblower I think we could retitle this as “FULL SPECIFICATION: NORMATIVE WITH INFORMATIVE EXAMPLES”
I think that's helpful but I think @joanma747 was also questioning why a single chapter is called the "Full specification". I agree it does look odd.
@jonblower, Exactly. Can we call it "Coverages in JSON" or "JSON encoding for coverage data"? I believe it contains precisely that.
How about "CoverageJSON Encoding"? That would also avoid the debate on whether to use "specification" or "standard"
@joanma747 @joanma747 So the section heading will then read:
CoverageJSON Encoding: Normative with Informative Examples
@joanma747 @jonblower Added to PR #121, awaiting review and merge. Then will close issue.
Now merged into Master branch.
@joanma747 identified several areas of confusion requiring improvements to the text. These have been split into 8 separate sub-issues: