Closed jonblower closed 2 years ago
@ghobona When the specification is adopted as an OGC Community Standard, can we automatically copy to the original spec web site, http://covjson.org, perhaps with a script? And then subsequently when corrigenda or V1.x are created?
@jonblower @letmaik If fully automatic repopulation of the CovJSON.org repo not possible, would a one-off manual cloning/copying be acceptable?
I propose two things:
master
to GitHub pages to https://opengeospatial.github.io/CoverageJSON/draft.html or similar. This will help spot outstanding issues during editing/development.Yes, we can create cron job or GitHub Action to automatically copy to the original spec web site.
We would need the administrator of the original spec web site to liaise with the OGC Infrastructure Office (@gbuehler) regarding credentials.
Agreed that @jonblower and @letmaik will set up two iframes on the covjson.org website for standard spec and current working draft once the standard approved. Close when working.
Done in https://github.com/covjson/covjson.github.io/pull/7. See https://covjson.org/spec/. See the PR description on why it's not an iframe but a link only.
@letmaik @jonblower @ghobona Excellent.
We will retire the previous GitHub repo containing the original specification, and continue future discussions here. But we will need to embed the eventual OGC-approved spec in the covjson.org website. We should figure out if we can do this automatically. Also we may in future need to provide access to two versions: the latest release and the current in-progress draft.