Resources for testing netCDF-LD

[jyucsiro]

Tools and software libraries are being developed to support exploring the design and usage of netCDF-LD. We want a set of resources that we can use to help with this for the purposes of having curated examples. These will likely be:

• RDF vocabularies/collections
• netCDF (and HDF) files examples with candidate netCDF-LD encodings
• Deployed services to access resources, e.g. triple stores/vocabulary services and registries

a) Are there any of these existing resources we can leverage as exemplars or test cases?
b) Do we need to find alternate homes for them?
c) Do we need to stand up any infrastructure to host the example resources for testing? (e.g. triple stores)

[jyucsiro]

Could we use URIs minted by NVS or MMI for CF terms to create a set of netcdf-LD examples?
e.g. for sea_surface_skin_temperature - http://vocab.nerc.ac.uk/collection/P07/current/CFV9N2/ or http://mmisw.org/ont/cf/parameter/sea_surface_skin_temperature

This assumes access to the definitions via those services without having to host any files/services for those examples.

[adamml]

If we choose to go the NVS route, there is a URL using the Standard Name which is a bit cleaner, I'll dig it out later

[adamml]

OK - the full CF standard names list is available through NVS at

http://vocab.nerc.ac.uk/standard_name/

Similarly, a single standard name can be accessed as

http://vocab.nerc.ac.uk/standard_name/{standard_name}/

e.g.

http://vocab.nerc.ac.uk/standard_name/acoustic_signal_roundtrip_travel_time_in_sea_water/

[jyucsiro]

Ok thanks Adam. It could be interesting to explore parsing netcdf(-LD) headers with CF standard names and then providing a discovery layers.

A while ago, an ELDA interface was setup to query NVS via SPARQL.

The following call allows rendering of the content as JSON:
http://auscope-services-test.arrc.csiro.au/elda-demo/nerc/resource.json?uri=http://vocab.nerc.ac.uk/standard_name/acoustic_signal_roundtrip_travel_time_in_sea_water/

Potentially could use this as an alternative to parsing RDF/XML. In some cases like web frontends, this could be advantageous.