Currently we have fiboa_version and fiboa_extensions (list of schema URIs), inspired by the STAC equivalents.
Some thoughts:
fiboa_extensions is a bit like OGC conformance classes and we could reuse their conformsTo property. An issue is that we would expect extension URIs to resolve, but OGC conformance classes usually don't resolve to schemas. So probably not the way forward.
We could also express the version as a schema URI and make fiboa_extensions more generic.
How do we handle schemas for different encodings? We probably need different schema URIs per encoding to reflect the differences between the encodings, but if the schema URIs differ between encodings it makes it harder to translate them / convert between GeoJSON and GeoParquet.
Currently we have
fiboa_version
andfiboa_extensions
(list of schema URIs), inspired by the STAC equivalents.Some thoughts:
conformsTo
property. An issue is that we would expect extension URIs to resolve, but OGC conformance classes usually don't resolve to schemas. So probably not the way forward.cc @cholmes