Post by Martin Doerr (24 August 2025)
Dear All,
Since a long time there has been silence about CRMdig. In the meanwhile, the European ECHOES Project neds and makes use of CRMdig.
In the light of the last ecisions about CRMdig, and the successful work on CRMsci and CRMinf, I propose not to deprecate D9 Data Object, but make it consistent with E31 Document, CRMsci Data Evaluation and Argumentation.
Further, I propose to resolve the misfit between data and Dimension in the Digitization and Digital Measurement class, which George pointed out, as in the attached.
All changes are highlighted in yellow.
I will send as another issue the review of the "Area" concept.
In the attached, examples are not updated.
It is based on a copy from CRMdig 4.0
All the best,
Martin
Post by George Bruseker (24 August 2025)
Dear Martin,
I have a home work on the go and am actively consulting with Steve and pavlos. It is following the last issues assigned. There was no space in the last sigs for dis because of sci and inf.
We can take a look at these suggestions as we work through the active home work.
Best
George
Post by Athina Kritsotaki (27 August 2025)
Dear all,
In the context of Martin's new proposal, the current status on CRMdig and the new requirements from the ECHO project, I have some comments to add:
- Since we discuss again the concept of D9, perhaps we should add in the scope note a statement regarding the documentary (inherited by the E31) nature of D9, a characteristic that is not assigned to D1, for example.
- In my opinion, L60 property is not necessary : it is already expressed as a property inherited to D9 .
- We should also consider the "borndigital" objects (a requirement from ECHOES) and where they fit in the CRMdig. A "born digital" is the outcome of a E65 Creation and maybe of a case of D7 Digital Machine
Event? - And a last question: it seems that the only relationship that exists between a physical thing and D1 is the P67 refers to (inherited), right? In the CRM base "P138 represents" implies a relationship also resulting from digitisation processes- see the text (however there is no such relationship in CRMdig expressing the appearance representation or form expressed by a digital image for example).
Generally, I am happy to participate in the conversation about these things,
BRs,
Athina
Post by Martin Doerr (15 Sep 2025)
Dear All,
I made a modification in the proposed scope note of D9 about containing value sets from Dimensions, and added in the file to deprecate both L60 and L17.
L17 should be replaced by defining a temporary aggregate of objects of similar type measured in the particular instance.
See attached.
Best,
Martin
Post by Olivier Marlet (15 Sep 2025)
Dear all,
May we submit our model for your analysis, which represents data from the French National 3D Data Conservatory (Conservatoire national des données 3D) for which we used CRMdig, specifically properties L60 and L17? (see attached)
I imagine that L17 could easily be replaced by P2, but which property could replace L60 if it is deprecated ?
Perhaps our request is not relevant to this issue, in which case we apologise.
Best,
Olivier Marlet
Post by Martin Doerr (16 Sep 2025)
Dear Olivier, all,
Thank you so much!
D2 is subclass of D11, subclass of S21 in my harmonized version. Therefore it inherits O24.
O24 measured (was measured by): S15 Observable Entity completely replaces L60.
L17 should be replaced via a path to the aggregate, 'll give more details.
A kind reminder, please all members to send me cases of using CRMdig they are aware of!!
At CRM SIG, we desperately need o be informed about the use of our models, in particular the extensions.
Kind regards,
Martin
Post by Olivier Marlet (16 Sep 2025)
Dear all,
Thanks for the feedback, Martin.
Sorry, I didn't notice that the attachment didn't come through (thanks, Dimitris). You can find the CND3D model on the page dedicated to the OntoMatchGame card game (created with George and Anaïs).
https://ontomatchgame.huma-num.fr/papercards/
Other models are also presented on this page. Feel free to take a look and give us your feedback.
Olivier