While not absolutely mandatory for URIs, it is not very user friendly that the conformance URIs currently don't resolve to anything, insted Github Pages returns 404. Ideally the URIs should send a redirect to the corresponding anchor on the HTML web page of the spec (".../metocean-edr-profile-DRAFT.html#_core"), so that it can easily be changed when the spec goes from draft to final version.
While technically possible (at least in MarkDown) on Github Pages by making a /spec tree with a MarkDown file with a redirect in the YAML preamble, it is very cumbersome. A much simpler solution would be a separate website with the redirects in an Nginx config file. Also, we should move away from using github.io in official specs to avoid vendor lockdown.
Håvard mentioned using meteogate.eu as a possible domain for hosting the profile. If we decide on using MOPED as a short name for the project, we could fix this using two DNS entries:
moped.meteogate.eu
This would be a standalone website, with maybe a static page and one redirect in Nginx for each conformance class. All the conformance classes must be changed from https://eumetnet.github.io/spec to https://moped.meteogate.eu/spec in the draft and the validator (along with all websites using the profile).
docs.moped.meteogate.eu
This would be the current github.io site, but we change the hostname in the GitHub config to something we have control over. (IIRC the old URL may still work, but maybe not with https.)
SEDR
The ˋsedrˋ command line tool may also be renamed to ˋmopedˋ just to keep everything short (but otherwise referred to as "the MOPED validator".
While not absolutely mandatory for URIs, it is not very user friendly that the conformance URIs currently don't resolve to anything, insted Github Pages returns 404. Ideally the URIs should send a redirect to the corresponding anchor on the HTML web page of the spec (".../metocean-edr-profile-DRAFT.html#_core"), so that it can easily be changed when the spec goes from draft to final version.
While technically possible (at least in MarkDown) on Github Pages by making a /spec tree with a MarkDown file with a redirect in the YAML preamble, it is very cumbersome. A much simpler solution would be a separate website with the redirects in an Nginx config file. Also, we should move away from using github.io in official specs to avoid vendor lockdown.
Håvard mentioned using meteogate.eu as a possible domain for hosting the profile. If we decide on using MOPED as a short name for the project, we could fix this using two DNS entries:
moped.meteogate.eu
This would be a standalone website, with maybe a static page and one redirect in Nginx for each conformance class. All the conformance classes must be changed from https://eumetnet.github.io/spec to https://moped.meteogate.eu/spec in the draft and the validator (along with all websites using the profile).
docs.moped.meteogate.eu
This would be the current github.io site, but we change the hostname in the GitHub config to something we have control over. (IIRC the old URL may still work, but maybe not with https.)
SEDR
The ˋsedrˋ command line tool may also be renamed to ˋmopedˋ just to keep everything short (but otherwise referred to as "the MOPED validator".