rob-metalinkage
commented
4 years ago Hi Mark run into a slight but temporary snag even though i've already fixed this on development server the production URI rewriter has a snag with overriding default rules when the uri is a 'base register' - ie /def/something even though its fine with defs/something/x I'm still working through a bunch of complex stuff on the next version - including support for w3c Content negotiation by profile, describing all the profiles supported and improving backup/restore options so we can test and transfer a bunch of rules safely - at which point I'll get Kevin @ OGC on the line to update the deployment. In the meantime Kevin can you do a brute-force temporary solution and redirect ? https://www.opengis.net/def/binary-array-ld (but not https://www.opengis.net/def/binary-array-ld/X) to https://raw.githubusercontent.com/opengeospatial/NamingAuthority/master/incubation/binary-array-ld/binary-array-ld.ttl until we push the updates? I'll push the SKOS view to the defs server so that individual items resolve as HTML and JSON etc
This proposes the adoption of the Binary Array Linked Data vocabulary
This has been reviewed by the team working on the netCDF-LD encoding standard from the NETCDF SWG https://github.com/opengeospatial/netCDF-Classic-LD and is required for that work to proceed to review and approval stages.
Interest has been indicated from the GeoTIFF and HDF domains in this activity.
Hence the proposal to keep the naming of these resources independent of encoding standards that intend to make use of them.