You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: