Issue 667: hierarchical dependencies between extensions or through CRMbase?
In the 57th CIDOC CRM & 50th FRBR/LRMoo SIG Meeting, the SIG resolved to start a new issue where to discuss whether hierarchical dependencies should be declared between extensions or between a given extension and the CIDOC CRM instead.
For some context, see the definition of J2 concluded that in CRMinf.
- Secifically, based on the decisions concerning issue 469, in October 2020 J2 concluded that was declared a subproperty of P116 starts (is started by).
- Subsequently, P116 starts (is started by) moved to CRMarchaeo (in v2.0: it has been assigned the number ID AP24 starts (is started by)).
- Among its superproperties feature
- P175 starts before or with the start of (starts after or with the start of)
- P175i starts after or with the start of (starts before or with the start of)
- P185 ends before the end of (ends after the end of)
These properties also feature in the migration instructions for P116 (from 7.1.1 onwards)
- We should not be listing both [AP24 starts] AND [P175, P175i, P185], given that the former is declared a subproperty of the latter set., but the SIG needs to determine which link to state for the superproperty of J2 concluded that.
HW: CRM Editors to determine the best way to go about it
Marseille, October 2023
In the 58th CIDOC CRM & 51st FRBR/LRMoo SIG Meeting, the SIG resolved to close the issue.
Following the decision to deprecate P116 starts (is started by) from CRMbase and its admission into CRMarchaeo, J2 concluded that was left without a superproperty in CRMbase.
The migration path for the deprecated P116, involved declaring it a subproperty of P175, P175i AND P185.
The question whether to declare J2 a subproperty of AP24 or the set of properties that formed the migration path for P116 arose upon updating CRMinf.
It was considered an editorial change for the CRMinf editors to take care of, and the latter option was adopted.
Issue closed
Paris, March 2024