Issue 469: A phrase of every property of every extension

Starting Date: 
Working Group: 
Closing Date: 

In the 45th joint meeting of the CIDOC CRM SIG and SO/TC46/SC4/WG9; 38th FRBR – CIDOC CRM Harmonization meeting, the sig reviewed the HW by GH on the issue 400 and among the others agreed to start a new issue on how to phrase that for every property of every extension of the CRM, there either exists a CRMbase property, which they are subproperties of or there doesn’t.

Heraklion, October 2019

    Current Proposal: 

    Posted by Christian Emil on 13/2/2020

    I have done this for CRMinf, CRMsci and CRMarcheo on the plane to Geneva. I attach the draft and if it is ok, I can take the rest as well.

    I will also add a column for subproperties in CRmbase. 

    Posted  by Christian Emil on 14/2/2020

    Dear all,

    Sorry for spamming you. My email system sent the mail before I wanted.

    I worked through

     CRMinf, CRMsci,  CRMarcheo, CRMgeo, CRMdig, CRMba, CRMtex, CRMsoc, FRBRoo, PRESSoo

    I didn't find LRMoo.

    The attached spreadsheet contains the results. I didn’t convert FRBRoo and PRESSoo into the common schema.



    CRMgeo:  no CRMbase properties. To be reviewed?

     CRMdig: Strange property ‘label’, should be reviewed, class and property hierarchies should be added.

     CRMba: No crmbase superproperties mentioned, should be reviewed

     CRMtex: Only one crmbase superproperty, more?

     CRMsoc: just a draft

     FRBRoo: many properties without crmbase superproperties

     PRESSoo : ok, with respect to FRBRoo.

    Posted by Christian Emil on 20/2/2020

    Dear all,

    Here is an updated version of the excel file with the overview of the super properties. I have included LRMoo. 

    I worked through

     CRMinf, CRMsci,  CRMarcheo, CRMgeo, CRMdig, CRMba, CRMtex, CRMsoc, LRMoo, FRBRoo, PRESSoo


    In the 48th CIDOC CRM and 41st FRBR CRM sig meeting (virtual),CEO presented his HW (to establish the hierarchical relations among properties defined in the CRM-extensions and their superproperties in CRMbase). He has done that for all models, the output of this work can be found in this spreadsheet. It can be useful to determine a top-level ontology for all CRM classes and properties (for all CRM-family models). It shows which properties of CRMbase have subproperties in other models. 
    The sig decided to 
    (a) keep such tables updated at the CRM site.
    (b) Merge issues 469 and 365 into one (close issue 469, move the discussion to issue 365)
    (c) assign HW  to Emilio San Filippo, Mark Fichtner, CEO, Oyvind – Emilio San Filippo will make a doodle and share it with other sig members involved in the HW. Eleni will share the email addresses of the other sig members involved

    The  issue closed.

    October 2020

    Meetings discussed: