Examples consistency

[amilan17]

I'm reviewing the examples for consistency and will use this issue to bring up questions that I have.

[amilan17]

1. Is the links.type intended to describe the data format at that link or the type of link itself, which would mostly be "text/html".

[amilan17]

2. all records should have an created/updated dates that are in 2024

[amilan17]

3. Are there alternatives to using ISO codelists in concepts?
   e.g.
   { "concepts": [ { "id": "continual" } ], "scheme": "https://standards.iso.org/iso/19139/resources/gmxCodelists.xml#MD_FrequencyCode" }

[amilan17]

4. formats vs availableFormats
   In some of the examples there is a "formats" property. While technically legal, I think the way we should do as the standard says and put this in links.distribution.availableFormats

"formats": [ "GRIB2" ]

[amilan17]

@wmo-im/tt-wismd I recently reviewed the example records, made some changes for consistency and added a lot of questions. Specific questions/requests are in the PR and general questions are above. It would be good to have these ready to post on schemas.wmo.int shortly after the next meeting on Monday.

#199

[amilan17]

1. Is the links.type intended to describe the data format at that link or the type of link itself, which would mostly be "text/html".

As discussed with Tom, the links.type property should represent what is returned when you click on the link. For example, if it's a WAF with a list of XML files then the type should be "text/html", but if clicking on the link returns an XML file, then the type should be "text/xml".

[tomkralidis]

A PR is put forth in #201 .

As discussed with Tom, the links.type property should represent what is returned when you click on the link. For example, if it's a WAF with a list of XML files then the type should be "text/html", but if clicking on the link returns an XML file, then the type should be "text/xml".

Per RFC7303, text/xml is an alias for application/xml, so we use the latter as required in WCMP2 and beyond.