binary-array-ld / net.binary_array_ld.bald

Java library for parsing, validating and managing binary array linked data files, e.g. HDF, netCDF.
Apache License 2.0
0 stars 3 forks source link

Root Container Identifier and representation #37

Closed marqh closed 3 years ago

marqh commented 3 years ago

There is a disconnect in the draft standard between the informative chapter (6) and normative chapter (7) regarding the identifier for the root group and the defining statements for the root group

using https://github.com/binary-array-ld/net.binary_array_ld.bald/releases/tag/untagged-5a2868ea73dc39a569cb

The clause 7 normative information is interpreted, but the desired behaviour in chapter 6 http://docs.opengeospatial.org/DRAFTS/19-002.html#_identity http://docs.opengeospatial.org/DRAFTS/19-002.html#_download_url is not implemented. The standard is poor/inconsistent in this regard

The current library provides two identified entities representing the root group, e.g.:

<http://example.binary-array-ld.net/GEMS_CO2_Apr2006.nc>
        a       <https://www.opengis.net/def/binary-array-ld/Container> ;
        <https://www.opengis.net/def/binary-array-ld/contains>
                <http://example.binary-array-ld.net/GEMS_CO2_Apr2006.nc/> .
<http://example.binary-array-ld.net/GEMS_CO2_Apr2006.nc/>
        a       <https://www.opengis.net/def/binary-array-ld/Container> ;

This doesn't seem like the desired behaviour. In this case, i would expect to only have http://example.binary-array-ld.net/GEMS_CO2_Apr2006.nc/ defined and not http://example.binary-array-ld.net/GEMS_CO2_Apr2006.nc

This is predominantly a standard issue, I will update this issue with a link to a proposed standard update

marqh commented 3 years ago

https://github.com/opengeospatial/netcdf-ld/pull/78