As an ontologist, I need an RDFS expression of linked-places so I can incorporate linked-places statements in my data model
I'm working on a Pelagios-related project with data about historical places and events, and we are experimenting with CIDOC CRM to model the domain. Is there an "official" owl or rdfs version of your json-ld schema?
Sorry for the (long) delay! There is not yet an ontology to formalize the alias terms found in our model and examples. Well, there has been a beginning but only a bare beginning. The LP model is in active use by World Historical Gazetteer, some Pelagios projects, and elsewhere, but lacks that next step. We welcome help in getting this done. The idea of relating it to CIDOC-CRM is an interesting one to explore.
As a follow-up on this discussion: as part of my PhD project I'm building an urban gazetteer for the city of Ghent. I'm modelling place data with CIDOC CRM classes and partly following the model discussed by Schneider et al. in Challenge-derived design practices for a semantic gazetteer for medieval and early modern places. Relating the CIDOC CRM model to LPF would be great (and possible I believe). If there is interest, I would love to discuss this further.
Thank you for this suggestion! I will have a look at this doc. You can reach me at karl [at] kgeographer [dot] org
Vincent, if you get in touch by email, we can start arranging a meeting of some kind to discuss with others...thanks
As a follow-up on this discussion: as part of my PhD project I'm building an urban gazetteer for the city of Ghent. I'm modelling place data with CIDOC CRM classes and partly following the model discussed by Schneider et al. in Challenge-derived design practices for a semantic gazetteer for medieval and early modern places. Relating the CIDOC CRM model to LPF would be great (and possible I believe). If there is interest, I would love to discuss this further.
What exactly does "incorporate linked-places statements in my data model" mean?
- transform (via RDF representation of LP statements) into my data model (or a data model like CRM/CRMgeo)
- import/integrate (the RDF representation of LP statements) in my data model (considering the incorporated LP attestations as kind of factoids aligned with place instances modeled in e.g. CRM/CRMgeo)
in its current state the LPO provides lpo:has_certainty as a property of the class lawd:Attestion to represent knowledge about the (un)certainty on the level of a whole attestation. What are our requirements for representation of information about (un)certainty -- what levels of granularity do we need to handle?
There is a concept map of the LPO prepared by me in the context of our DigiKAR (Digitial Map Lab Holy Roman Empire) project:
https://cmapscloud.ihmc.us:443/rid=1XXY0XP3J-NKPBX6-S3/digikar_place_concept_lpo_geojson.cmap
Perhaps the diagram helps to clarify some conceptual modeling issues etc.