multiple geometry serialisations for dcat:bbox

[NielsHoffmann]

This is an issue for the GeoDCAT-AP 3.0.0 pilot

The XSLT seems to aim for a limited number of configuration parameters at the start of the file (deprecated yes/no for example) so that the rest of the transformation can be done accordingly.

For the dcat:bbox (and the locn:geometry property if deprecated=yes) this approach is not followed.
There are mutliple serialisations written to the output.

However, the GeoDCAT-AP proflie has a 0..1 cardinality defined for those proprerties. So the shacl validations fails on this implementation.

I think it would be good to settle on a preferred geometry serialization for the profile.

[hallinpihlatie]

Does any one have a use case for a 0..N cardinality?
If not, next step I suppose would be to agree which to preserve. Any proposal on this?

[hallinpihlatie]

Here's an example with the alternatives:

<dct:spatial rdf:parseType="Resource">
<rdf:type rdf:resource="http://purl.org/dc/terms/Location"/>
<locn:geometry rdf:datatype="http://www.opengis.net/ont/geosparql#wktLiteral"></locn:geometry>
<locn:geometry rdf:datatype="http://www.opengis.net/ont/geosparql#gmlLiteral">19.08317359 59.4541425831.58672881 70.09229553]]></locn:geometry>
<locn:geometry rdf:datatype="https://www.iana.org/assignments/media-types/application/vnd.geo+json"></locn:geometry>
<locn:geometry rdf:datatype="http://www.opengis.net/ont/geosparql#geoJSONLiteral"></locn:geometry>
<dcat:bbox rdf:datatype="http://www.opengis.net/ont/geosparql#wktLiteral"></dcat:bbox>
<dcat:bbox rdf:datatype="http://www.opengis.net/ont/geosparql#gmlLiteral">19.08317359 59.4541425831.58672881 70.09229553]]></dcat:bbox>
<dcat:bbox rdf:datatype="https://www.iana.org/assignments/media-types/application/vnd.geo+json"></dcat:bbox>
<dcat:bbox rdf:datatype="http://www.opengis.net/ont/geosparql#geoJSONLiteral"></dcat:bbox>
</dct:spatial>

[jakubklimek]

See SEMICeu/GeoDCAT-AP#68 SEMICeu/DCAT-AP#265 and SEMICeu/DCAT-AP#175