Issue 557: Which family model should classes (i) Provision and (ii) Business Obligation appear under?

Starting Date: 
Working Group: 

In the 50th joint meeting of the CIDOC CRM SIG and SO/TC46/SC4/WG9; 43nd FRBR – CIDOC CRM Harmonization meeting, upon discussing issue 420, the SIG resolved to start a new issue where to determine what is the most appropriate CRM extension to host classes socExx Provision and socExx Business Obligation plus the set of relevant properties whereby to link from and to them. 

The definitions of the classes and their examples have been agreed upon in the context of issue 420
The two classes could either become part of the new extension for Activity Plans and Business Transactions (see issue 419) or they could lie in the newly-defined scope of CRMsoc.

HW for AK, MD, TV, SdS, FB to work on the properties and examples. 

June 2021

In the 52nd joint meeting of the CIDOC CRM SIG and ISO/TC46/SC4/WG9; 45th FRBR - CIDOC CRM Harmonization meeting; the SIG went through the diagrams illustrating the examples by AK for Provision and Business Obligations. MD proposed to make this model into a CRM extension of its own (CRMbiz or other label) that serves to document business transactions. 

The following outline was proposed (shaping the scope of the model as it were -a reference to everything else it covers, aside business transactions):

  • material provision of things (labor, services, money, goods)
  • social exchanges for material gain
  • incorporate constructs from SeaLit (and other projects –f.i. Spectrum, documentation of Nazi theft, BM project for illicit trading) to draft the practical scope of the document (discuss with RS, SdS)
  • museum transactions for object acquisition/exchange etc


  • The SIG accepted the proposal to create this extension 
  • HW assigned to SdS and MD to turn this outline into a practical scope for the definition document. They are to consult RS for this task. 
  • The label of the model will be discussed in a separate issue 
  • The issue can close once the practical scope has been accepted. 

Reference to Issues:

Meetings discussed: