Change conformance link to profile

[geira]

Currently the validator is checking for a link to RODEO:

http://rodeo-project.eu/spec/rodeo-edr-profile/1/req/core

Since this is no longer a RODEO project (and the link returns 404) we should instead use something more representative.

The spec currently resides at eumetnet.github.io. While obviously not ideal, it does at least link to a readable spec. If OGC or WMO at some point would adopt the standard profile it should naturally resolve to their domains, but I think that can wait until a future version (we also need to discuss how to specify version numbers). I therefore suggest that the canonical URI for the metocean EDR profile should be:

https://eumetnet.github.io/spec/metocean-edr-profile/1/req/core (edited)

And for the observations:

https://eumetnet.github.io/spec/metocean-edr-profile/1/req/insitu-observations

(Obviously this also depends on the outcome of Part 3 of the EDR spec, but as we agreed on at the last meeting we should make an example proposal and ask for approval/correction, rather than wait for explanations on how to use it. @havardf do you agree?)

[havardf]

@geira Yes, we might as well change it now. We might need to revisit this soon, but https://eumetnet.github.io/metocean-edr-profile/ is anyway better than http://rodeo-project.eu/spec/rodeo-edr-profile/.

[geira]

Then I suggest the following logic to determine whether to apply the profile or not, based on conformance class URI and the command line flag:

CC URI \ Flag	On	Off
eumetnet core	check core	check core
eumetnet core + extension	check core + ext	check core + ext
eumetnet extension without core	error	error
rodeo	error	error
none	check core	ignore

[havardf]

Looks good!

[geira]

The only problem though is that these URIs don't resolve to anything and returns 404. Ideally they should redirect to the corresponding heading in the HTML draft. Is that even possible in AsciiDoc?

[geira]

Also, the use of "github.io" results in vendor lock-in which is unfortunate in an official spec. We need a good, short name for the project and a permanent domain which we have control over to host web pages and URIs. See the discussion on Slack for suggestions.