In the 60th joint meeting of the CIDOC CRM and ISO/TC46/SC4/WG9 & 53rd FRBR/LRMoo SIG, upon discussing issue 672, the SIG resolved to start a new issue where to define the migration instructions for E13 Attribute Assignment (and subclasses), given that from v7.3.1 and on, all instances of of E13 Attribute Assignment (and subclasses) forms a single activity applied to exactly one object and yielding one value or dimension, which prohibits multiple values or dimensions as the objects of one (condition assessment | measurement | classification | observation, etc.).
This is a major model change, and new migration instructions should be provided for explaining how to bundle single E13 Attribute Assignments (and subclasses) into “cluster activities”.
This particular HW was not assigned to anyone.
Bern, April 2025.
Post by Christian-Emil Ore (8 October 2025)
Dear all,
I have created a document in the Google drive,
see https://docs.google.com/document/d/1TGR8ccpWSNcj4ZJZdVqxH_ax3x_jhn5neXy…
with a draft for the migration rule. I put a copy of the draft at the end of this email.
Best,
Christian-Emil
Migration Instructions for E13 Attribute Assignment, subclasses and (sub)properties
In cultural heritage institutions it is common practice to document condition assessment, measurement, classification, observation etc. for groups of objects. This has been reflected in the CRMbase by the quantification many-to-many of the properties P140 assigned attribute to (was attributed by) and P141 assigned (was assigned by) and their subproperties. From v7.3.1 and on, all instances of of E13 Attribute Assignment (and subclasses) forms a single activity applied to exactly one object and yielding one value or dimension, which prohibits multiple values or dimensions as the objects of one instance of E13 Attribute Assignment (condition assessment, measurement, classification, observation, etc.). After the change one has to replace the single instance of E13 Attribute Assignment or subclasses with an instance of E7 Activity as the grouping event and a new instance of E13 Attribute Assignment or subclasses for each of the objects in question. The grouping instance should hold the information about time, place and actor of the original instance of E13 Attribute Assignment and a type indicating the kind of event. Each of the new instances of E13 Attribute Assignment or subclasses should be sub-events, that is connected to the new instance of E7 activity via the property P9 consists of (forms part of)