Issue 413: Pursuit and Name Use Activity to CRMsoc

ID: 
413
Starting Date: 
2019-03-27
Working Group: 
3
Status: 
Open
Background: 

In the 43rd joint meeting of the CIDOC CRM SIG and ISO/TC46/SC4/WG9; 36th FRBR - CIDOC CRM Harmonization meeting, during the discussion about rights model (issue 408), the crm-sig took the decision the deprecated FRBR classes F51 Pursuit and F52 Name Use Activity to be introduced to CRMsoc and to open a new issue for this discussion.

Heraklion, March 2019

Current Proposal: 

In the 44th joint meeting of the CIDOC CRM SIG and ISO/TC46/SC4/WG9; 37th FRBR - CIDOC CRM Harmonization meeting, following the decision to import FRBR deprecated classes, F51 Pursuit and F52 Name Use Activity, to CRMsoc, the sig reviewed properties R45 assigned to (was assigned by) [D:F52,R:E1] and R63 named (was named by)[D:E52, R:E1] and decided that they should also be imported in CRMsoc. 
HW: FB is to rename the classes and properties according to the CRMsoc conventions. 
HW: FB,RS to check the scope notes of the rest of the properties  for consistency with the CRMsoc (naming conventions and relevance).  TV is to proofread. 
Also the sig decided that classes and properties will only be assigned number identifiers from the official published version and on. Until then, numbers will be arbitrarily assigned and will be subject to change. 

 

Paris, June 2019

In the 50th joint meeting of the CIDOC CRM SIG and SO/TC46/SC4/WG9; 43nd FRBR – CIDOC CRM Harmonization meeting, GB gave an outline of this issue. F51 and F52 have been deprecated in LRMoo and were supposed to be introduced to CRmsoc. It is important that ongoing work on CRMsoc does not create conflict with these classes –that’s not so much the case with F51 Pursuit but F52 Nomen Use Activity could cause frictions (see. how Appellations go through Institutional Facts in CRmsoc), in which case they should be put somewhere else.

Outcome of discussions: It is acknowledged that the decision to move F51 and F52 out of LRMoo and into CRMsoc was a hasty one. The issue cannot be resolved unless the scope and classes/properties of CRMsoc are clearly defined. They can be reintroduced to LRMoo with the indication that they are intended for a different model.

June 2021

Reference to Issues:

Meetings discussed: