-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mapping Location #32
Comments
This class was added by Geert Thijs and directly imported from OSLO Generiek. I double checked the URI used in OSLO Generiek and it is the same one. If needed, I am happy to adapt this, but can you please share the correct URI for me to chance it accordingly? |
This was indeed intentionally. There is a difference between localization (indicating position) and a location (a place). PROV:Location stands for all possible ways to localize something, namely in a direct way by using DirectPosition or Geometry (resp coordinaties and coordinates+form) or indirectly by using an Address, a GeographicalName, a Place, a localized object (eg a Building, a Parcel), a webaddress. The concept Place in the aformentioned list is some designated and named area like a Municipality, a City, a Region, even a Country or StatisticalSector. This definition seemed to corresond with locn:Location. So we used PROV:Location rather than locn:Location for Consent.location to allow fore all possible ways (not only by mentioning a Place) to indicate where the Consent was given. |
Hi,
The class https://purl.eu/doc/applicationprofile/consent/#Location is mapped on prov-o:Location, why is it not locn:Location as in OSLO-generiek? (SEMIC Core Vocabularies).
The text was updated successfully, but these errors were encountered: