The CRMgeo maintainers have tried to reformulate CRMgeo as an extension of CRM 7.1.2. This issue is for relevant discussions.
A summary of the proposed changes can be found here. See here for an overview of the model.
Post by Elias Tzortzakakis (16 February 2024)
Dear all,
The proposed changes have been applied in the most recent version of CRMgeo 1.2 and the rdf outcome is available here.
Note that these encodings have been created in order to assist the preparation of the next CRMgeo version and can only be used as DRAFT. Scope notes may still refer to deprecated classes.
Best,
Elias Tzortzakakis
In the 58th CIDOC CRM & 51st FRBR/LRMoo SIG meeting, upon discussing issue 676, the SIG decided to keep properties Q10, Q14, and Q16 from CRMgeo.
Paris, March 2024
Post by Gerald Hiebel (26 September 2025)
Dear All,
Martin and I have been working on a proposal for Issue: 674 - Harmonizing CRMgeo with CRMbase v7.1.2.
Please find attached the drawio diagram and the word document stating the changes. Once approved be CRMSIG we would write a new Word document that could be parsed by Elias to create an RDF version.
Any comments or suggestions welcome,
Best,
Gerald
In the 61st joint meeting of the CIDOC CRM and ISO/TC46/SC4/WG9 & 54th FRBR/LRMoo SIG, the group reviewed the HW by GH & MD. For a graphical representation of the model see here. The proposed changes can be found in the attached document.
Decision: A small subgroup was formed (GH, GB, WS, and anyone else interested) to redraft the scope notes, and the introduction.
For an overview of the points raised in the discussion see here.
Heraklion, October 2025
At the 62nd joint meeting of the CIDOC CRM and ISO/TC46/SC4/WG9 & 55th FRBR/LRMoo SIG, GH walked the SIG through the new release of CRMgeo (syntactic check by ETz, addition of diagrams and explanatory paragraphs under “Basic Concepts”, semantic check by MF & WS). The ensuing document and diagrams can be found here:
There are very few comments yet to be addressed, they primarily concern property quantification, FOL, alternatives to examples and they can be handled as an editorial update (following one last editing round). They are not expected to have any impact on the RDFs file for CRMgeo.
Proposal:
- Release this version (CRMgeo v2.0) as a stable one, aligned with CIDOC CRM v7.1.3.
- Flag it as a “release candidate”, meaning that it can be used for implementations but can change minimally shortly after: in practical terms this means that the status must be set to “Draft”, but the encodings should also be made available.
- Assign some readers to perform some final editing and issue the ensuing update as CRMgeo v2.0.1 (the RDFs won’t change).
Discussion points:
- Participants noted that the constructs in CRMgeo could possibly extend the D35 Area modelling in CRMdig (provide topological relations for digital files). It was a preliminary discussion, that will need to be supported by
Decision: Proceed as proposed.
- Concerning the new release of CRMgeo the following HW was assigned.
- OE, MvR, WD, AK will be reviewing the document before the stable release is issued.
- GH to share the latest version that WS edited with ETz
- Concerning the connection of CRMgeo to D35 Area in CRMdig: GH to consider it some more, provide an example for it.
Oxford, March 2026