conformance testing

[marqh]

There is a newly minted 0.1 release of the OGC specification, which includes links to tagged files in the repository for conformance testing

it would be really good to see this kotlin library directly sourcing the input CDL files and testing the graph creation with respect to the targeted TTL files from the specification

Is this already within the testing scope?
Is this plausible to set up?

i would very much like to confirm that these test results are indeed delivered by this library (and to flush out any errors)

[marqh]

i am aware that, at the last minute, we put the Alias definitions for NetCDF into the specification respository, to ensure stability

I am now slightly aware that the naming of these entities within the graph may have Been altered in error

specifically:
https://raw.githubusercontent.com/opengeospatial/netcdf-ld/v0.1/standard/abstract_tests/CDL/ogcClassC.cdl
is expected to result in
https://raw.githubusercontent.com/opengeospatial/netcdf-ld/v0.1/standard/abstract_tests/TTL/ogcClassC.ttl
using
https://raw.githubusercontent.com/opengeospatial/netcdf-ld/v0.1/standard/abstract_tests/aliases/NetCDF.ttl
as aliases

however, the alias graph names it's entities http://def.scitools.org.uk/NetCDF/* so I am wary that the stated prefix for NetCDF in the expected output graph may be wrong

please may you provide some feedback on whether the interpretation of the spec would lead to a prefix definition of

• @prefix NetCDF: <https://raw.githubusercontent.com/opengeospatial/netcdf-ld/v0.1/standard/abstract_tests/aliases/NetCDF.ttl/> .
  or
• @prefix NetCDF: <http://def.scitools.org.uk/NetCDF/> .

given the stated input criteria?

[simonoakesepimorphics]

@marqh As far as I can tell from the inputs, there is nothing in particular to identify the URI http://def.scitools.org.uk/NetCDF/ with the prefix NetCDF so I would have to go with the former.