Issues in CIS JSON schema

[jerstlouis]

In http://schemas.opengis.net/cis/1.1/json/coverage-schema.json

• gridLimits property specifies that type is required, but type is not listed in the properties
• In rangeType there is a "description": "quantiy", typo (quantity)

Other issues? Is this schema validated?

[nmtoken]

According to https://www.jsonschemavalidator.net/ http://schemas.opengis.net/cis/1.1/json/coverage-schema.json is valid against the cited schema "$schema": "http://json-schema.org/draft-04/schema#"

I'm not sure how you might otherwise validate it.

[jerstlouis]

Thank you @nmtoken for testing/confirming this. I tried two other validators and they also all seem to validate.

It's odd that it doesn't check whether a required property actually exists.
Maybe it's by design to allow it to be anything as an additional property?
It's missing something like:

   "type": { "enum": [ "GridLimitsType" ] },

[jerstlouis]

2021-02-24 SWG:
[X] Add schemas to standard/schemas/
[X] Test generating a build matching the current standard
[X ] Make a release to baseline the existing 1.1 standard.
[ ] Address these issues.
[ ] Get new Revision number for the document corrigendum

[jerstlouis]

2021-04-21 SWG: Chuck will test generating a matching build and baseline a 1.1 version.

[cmheazel]

PDF and HTML generated using Asciidoctor can be found in the /standard directory
Do we want a Metanorma build as well?

[jerstlouis]

@cmheazel A better way to baseline versions and not clutter the git history and avoid enlarging the repository size would be to use GitHub releases instead, and upload the HTML and PDF documents as assets for those particular releases.

We could have different assets for each release: HTML, PDF, ZIPped / .tar.gz repository with the .adoc's.

I suggest we use this approach consistently across OGC specification repositories. @ghobona @gbuehler