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
{{ message }}
This repository was archived by the owner on Jul 16, 2024. It is now read-only.
Prez has recently dropped the dcterms:isPartOf predicate as semantic conver of membership. It is now using rdfs:member, following the recent update to GeoSPARQL. Since this profile is meant to guide the creation of datasets usable by Prez (and earlier ogcldapi), a review/update is in order.
Considering how the profile is currently relying exclusively on DCTerms, I would rather leave it as it is and adapt the software instead. That would be a semantically sounder option in my view. But the important thing is to keep all these different assets in synchronicity.
The text was updated successfully, but these errors were encountered:
@recalcitrantsupplant thank you for updating the profile. There is still the lingering issue with the semantics of rdfs:member, please recall the discussion yesterday, this predicate translates to "has member" in natural language. It is not intuitive and for sure it confounded me.
In principle, the rdfs:member predicate cannot be used to fulfill the requirements Requirement D-member and Requirement FC-member. In this case you might need to re-introduce dcterms:isPartOf.
In any event, with the requirements Requirement FC-memberof and Requirement F-memberof it should now be possible to get a compliant knowledge graph.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Prez has recently dropped the
dcterms:isPartOf
predicate as semantic conver of membership. It is now usingrdfs:member
, following the recent update to GeoSPARQL. Since this profile is meant to guide the creation of datasets usable by Prez (and earlier ogcldapi), a review/update is in order.Considering how the profile is currently relying exclusively on DCTerms, I would rather leave it as it is and adapt the software instead. That would be a semantically sounder option in my view. But the important thing is to keep all these different assets in synchronicity.
The text was updated successfully, but these errors were encountered: