Update EUMETSAT example

[gaubert]

The EUMETSAT example has been updated and is compliant except one part, the id.

It seems that the id: urn:x-wmo:md:int-eumetsat:EO:EUM:DAT:MSG:HRSEVIRI is not valid becaude int-eumetsat is not recognised as an organisation id.

Then there is a set of questions and proposals to improve the documentation or make some choices

• WIS 2 subscription link : How will the subscription link will be detected by WIS2 catalogues ?

The WIS 2 catalog will be primilarly used to discover datasets to subscribe to them so catalogues are expected to highlight the MQTT channels information to subscribe to the dataset. How will the catalog detect which link is a WIS2 notification one ?
Should there be a specific "tag" information allowing to easily automatically find it like a specific rel property ?
At the moment it is very generic.
Once a choice is made it should be added in the WCMP2 guide.

            "rel": "items",
            "channel": "origin/a/wis2/int-eumetsat/data/core/weather/space-based-observations/satellite4nowcasting/Meteosat-10/ImageL1-5",
            "href": "mqtts://example.org",
            "type": "application/json",
            "title": "Data notifications"}

• Improve the documentation regarding the choice of relationship
  It is not clear which rel type to use when and the IANA type for relationships might be not applicable, too generic or too specific or inappriate.

For a dataset (collection) you want to have the following:

• a link on the collection page (link to the description of the collection)
• a link to the service allowing to access the dataset items or to the data items themselves when appropriate. What can of link rel should it be and what to add ?
  For instance, when should it be data or items (not clear and especially for non-specialists)
• MQTT WIS2 subscription: a link to MQTT (see question above)
• additional information: documentation, training, ... In general information. What to put ?
• citation: Is it clear enough ?

All this is keeping in mind that this information should systematically ultimately be dispalyed in the catalog pages in a consistent way.

• Question relevant to EUMETSAT datasets that might be applicable to other organisations.
  EUMETSAT has collections that support two data policies. For instance for the Seviri dataset above, some data items are core and other are recommended: every hourly data item is core core as well as all data items older than one hour while the 15 min data items are recommended. Is it possible to have one metadata record describing that complexity ?
  At the moment it isn't possible. If EUMETSAT has this level of complexity other organisation will have similar ones.

[tomkralidis]

@gaubert I only see a deletion of the example. Is there a new/updated example that can be added?

[gaubert]

Ok I might have forgotten to add the example then. Will do it tomorrow morning.

…

On Tue, 16 Jan 2024 at 14:26, Tom Kralidis ***@***.***> wrote: @gaubert <https://github.com/gaubert> I only see a deletion of the example. Is there a new/updated example that can be added? — Reply to this email directly, view it on GitHub <#146 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAALSV6BIN53NAXCLJAERTYOZ5W5AVCNFSM6AAAAABB2EXDDSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJTG4ZTSNZSGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[gaubert]

@tomkralidis the example was indeed missing. It is now there.

[tomkralidis]

Thanks @gaubert. Tested locally and passes validation.