Issue 336: Assistance for reducing to core CRM model

Starting Date: 

In the 38th joined meeting of the CIDOC CRM SIG and ISO/TC46/SC4/WG9 and the 31st FRBR - CIDOC CRM Harmonization meeting and  within the framework of the issue 309, the crm - sig decided that a guideline must be written  about the case of  someone using an extension  would like to reduce to  CRM base model. The sig assigned to CEO to write this guideline and assigned to CEO and Gerald to make the appropriate adjustments for all CRM extensions. In addition, the sig decided to open a new issue for these guidelines.

Heraklion, April 2017

Posted by Martin on 18/9/2017

Dear All,

Our apologies that the sense of issue 336 came out garbled.

Here my formulation:

Extensions of the CRM may declare a superclass A of a class B in "CRMbase" or another extension. It may be the case that a property p of B also holds for the new class A. This is to be understood as the effect of widening the scope of CRMbase to that of the new extension, which then comprises domains in which p not only holds for B but also for A. Taken on its own, CRMbase should not be affected by that extension of scope, since it is not concerned with A. This construct is necessary for an effective
modular management of ontologies, but is not possible with the current way RDF/OWL treats it.
We need a logical theory for that and an implementation. The logical theory must describe the scope of CRMbase and that of the extensions in terms of logic (e.g., as sets).



Current Proposal: 

Posted by Christian Emil on 5/10/2017

The issue is resolved:

A super property (for all classes in crm and extensions)  is an extension in domain and range if the extra condition iff
A(x) & B(y) & P’(x,y) ⊃ P(x,y)​
​is true and  of course the standard ones
                               P (x,y) ⊃ A(x)
                               P(x,y) ⊃ B(y)
                               P(x,y) ⊃ P’(x,y)
                               A(x)⊃ A'(x)
                               A(x) ⊃ B'(x)
                               P'(x,y) ⊃ A'(x)
                               P'(x,y) ⊃ B'(y)

Martin, Carlos and i have had a long email exchange on the topic, see a summary below. We  need an understandable syntax and a sort term for the phenomenon for the readers of the standard.  I suggest we put  an entry in the term listof CRM or extend the one for sub/super property.


To sum up what we seems to agree on: Assume, as you write, we study a part of the reality/world W and formulate a conceptualisation/ontology O for a given purpose. We then extend our focus from W to W’ and formulate an extension of O’ such that O’ union O is a conceptualization/ontology for W’.  Assume  in O P:A<->B. I O’ union O we extend P to P’ such that P:A’ <-> B’ where A’ and B’ are superclasses of A and B respectively in O’.

Martin: “We can regard the property P, originally declared in W, to extend into W' as you describe below. “

C-E: “Assume that P’:A’ <-> B’ in CRM. Assume extension where there A is a superclass of A’, B a superclass of B’  and  a property P:A<-> B  such that P’ is equal to P|A’ <-> P|B’. That is, as long as we restrict P to instances of A’ and B’ then P(x,y) iff P’(x,y).  Is the issue how to express the relation between P and P’ in FOL? ”

Martin: The point is, that we regard P not different from P' in its semantics, we only find out that it has a wider applicability, than anticipated restricting ourselves to W'.

As I understand the issue we need a syntax for restricting the subclass definition in FOL to ensure that P and P’ are identical when P’ is restricted to A and B:
Ordinary sub propery:
                               P (x,y) ⊃ A(x)
                               P(x,y) ⊃ B(y)
                               P(x,y) ⊃ P’(x,y)

The superproperty is an extension in domain and range otherwise it is the subproperty
                               P (x,y) ⊃ A(x)
                               P(x,y) ⊃ B(y)
                               P(x,y) ⊃ P’(x,y)
                               A(x) & B(y) & P’(x,y) ⊃ P(x,y)

Reference to Issues:

Meetings discussed: