Skip to main content

User account menu

  • Log in
Home
CIDOC CRM

Cidoc Horizontal Menu

  • Home
    • About & Info
    • Last official release
    • Versions
    • Compatible Models
    • Translations
    • Issues
    • SIG's activities overview
    • SIG meetings
    • Minutes
    • Workshops
    • Working Groups
    • Versions
    • Figures & Diagrams
    • Data examples
    • Templates
    • Publications & Documents
    • External Tools
    • Short Intro & Methodology
    • Mappings
    • Functional Overview
    • Tutorials
    • Concept Search
    • Use Cases
    • Best Practices
    • Recommendation for Museums
    • Short Intro
    • SIG Members
    • Host Organizations
    • Stakeholders
    • Activity Documentation
    • Mailing list
  • News

Choose a shortcut

Compatible models & Collaborations
Link to old CIDOC CRM website
Next meeting
Use cases
CIDOC CRM Tutorial
CIDOC CRM Website designs and logos 
CRM SIG mailing list
Editorial Suggestions
Site Support

 

inline_menu_issues

  • List of Issues
  • Issue formulation
  • CRM SIG Archive

adjusting properties of E54 Dimension

680
2024-09-05
3 - Changes in the CIDOC CRM model
Open

Post by Martin Doerr (4 September 2024). 

 

Dear All,

I propose the following modifications for P179 and P191, as attached, following issue 665.

 

Specificity of the "Monetary amount" for a transaction is much more relevant for querying, and unambiguous, than asking for all transactions or things having the same monetary nominal value. Indeed, I cannot grasp the sense of the latter.
Therefore I change the quantifier to one to one, necessary, and enhance the scope note.

Best,

Martin

Proposal by Martin Doerr & Christian-Emil to adjust the FOL statements for P191 had duration and P179 had sales price, to include inferences excluding the use of P43 and (P179|P191) respectively (personal communication: 19 August 2024)

 P191 had duration (was duration of) - v7.3

In first-order logic:

  • P191(x,y) ⇒ E52(x)
  • P191(x,y) ⇒ E54(y)

Exclusion statements for CRMbase:

  • P191(x,y) ⇒ ¬(∃z) [E54(z) ⋀ P43(x,z)]
  • P191(x,y) ⇒ ¬(∃z) [E54(z) ⋀ P179(x,z)]

Exclusion statements for CRMsci to go under O12:

  • P191(x,y) ⇒ ¬(∃z) [E54(z) ⋀ O12(x,z)]

 

P179 had sales price (was sales price of) -v7.3

In first-order logic:

  • P179(x,y) ⇒ E96(x)
  • P179(x,y) ⇒ E97(y)

Exclusion statements for CRMbase:

  • P179(x,y) ⇒ ¬(∃z) [E54(z) ⋀ P43(x,z)]
  • P179(x,y) ⇒ ¬(∃z) [E54(z) ⋀ P191(x,z)]

Exclusion statements for CRMsci to go under O12:

  • P179(x,y) ⇒ ¬(∃z) [E54(z) ⋀ O12(x,z)]

     

In the 60th joint meeting of the CIDOC CRM and ISO/TC46/SC4/WG9 & 53rd FRBR/LRMoo SIG, the SIG reviewed the proposal by MD & CEO to adjust the FOL statements, property quantifiers and scope notes for P179 had sales prices (was sales price of) and P191 had duration (was duration of) to exclude unwarranted inferences concerning the kinds of entities the dimensions in question belong to. 

Decision: the proposal was approved, except for the exclusion statements (the details of the proposal and the ensuing discussion can be found in the attached document). 

N.b.: the exclusion statements proposed for P43, P179, P191 were not part of this discussion
HW: MD, CEO, WS to revise them
 

HW: WS to start a new issue where he will propose a statement explaining that historical aspects of each documented value (comparisons and whatnots) do not fall within the scope of CIDOC CRM

 

Bern, April 2025

Post by Christian-Emil Ore (6 October 2025)

Dear all,
Issue 679 "multiple objects cannot share the same instance of E54 Dimension" 
and issue 680 "adjusting properties of E54 Dimension" are strongly related and both are almost completed. 
 
In fact,  these issues are also connected to the closed issue 664 "redefine the scope note and FOL of P191 had duration" and the open issue 665 "Harmonize the quantification of P43 & O12 has dimension (also P179 had sales price)". The open issue 665 gives the context:
  1. P43 has dimension: change quantification to “one to many (0,n:0,1)”
  2. P191 had duration: change quantification to “one to one, necessary (1,1:0,1)”
  3. P179 had sales price: change quantification to “one to one, necessary (1,1:0,1)” 
  4.  
    1. Provide additional FOL conditions to disallow one instance of E54 Dimension to be the dimension of an E18 Physical Thing and an E96 Purchase, and an E52 Time-Span simultaneously.
    2. Ο12 has dimension: change quantification to “many to many (0,n:0,n)” 
  5. Provide additional condition that if a dimension pertains to multiple instances of S15 Observable Entity, then this dimension is an instance of S25 Relative Dimension.
  6. Assign HW to define a shortcut property (S21 Measurement. Oxx7 observed dimension: E54 Dimension; “one to one, necessary (1,1:0,1)”. The model can generalize to Observation.
Point 1, 2, 3, 4a were accepted and 4b and 5 given as homework.  This is done by MD and will be discussed in the meeting.
The SIG voted in favor introducing these property quantifiers and assigning HW to MD, CEO to do the FOL constraints to their semantics.
Start a new issue (679) about prohibiting multiple objects from sharing the same instance of E54 Dimension.
Issue 680 is also partly done and what remains of 679 and 680 is the FOL-expressions:
 
 
The SIG has already accepted the following  restrictions expressed by the quantifications:
 
An instance of E54 dimension can only be the dimension of one instance of E70 Thing via P43
ensured by the quantification (0,n, 0,1)
 
An instance of E54 dimension can only be the observed dimension of one instance of E16 Measurement via P40
ensured by the quantification (1,1, 0,1)
 
An instance of E97 Monetary Amount (E54 dimension) can only be the sale price of one instance of E96 Purchase via P179
ensured by the quantification (1,1, 0,1)
 
An instance of E54 dimension can only be the duration of one instance of E52 Time-Span P191
ensured by the quantification (1,1, 0,1)
 
All four classes are in separate subclass trees. 
 
To be decided in the meeting (issue 679/680)::
In addition to the above, the SIG  wants the class E54 Dimension   to have de facto three distinct subclasses one for E54 Thing, one for E96 Purchase and one for E52 Time-Span. This could be done by declaring three (four) disjoint subclasses which we don't want to do, or by explicit use of types or by FOL axioms. The latter is the solution we have been asked to express. Therefore, we propose the following additional axioms:
 
P43:
P43(x,y) ⇒ ¬(∃z) [E52(z) ⋀ P191(z,y)]
P43(x,y) ⇒ ¬(∃z) [E96(z) ⋀ P179(z,y)
 
P191:
P191(x,y) ⇒ ¬(∃z) [E96(z) ⋀ P179(z,y)]
P191(x,y) ⇒ ¬(∃z) [E70(z) ⋀ P43(z,y)]
 
P179:
P179(x,y) ⇒ ¬(∃z) [E52(z) ⋀ P191(z,y)]
P179(x,y) ⇒ ¬(∃z) [E70(z) ⋀ P43(z,y)]
 
Best,
Christian-Emil

679   multiple objects cannot share the same instance of E54 Dimension
665   Harmonize the quantification of P43 & O12 has dimension (also P179 had sales price)

THE MODEL

  • About & Info
  • Short Intro
  • Scope
  • Recommendations
  • References
  • Critics
  • Important Theories
  • Use&Learn
  • Short Intro
  • User Guidance
  • Methodology
  • Tutorials
  • Functional Overview
  • Last Official Release
  • Concept Search
  • Issues
  • Short Intro
  • Issue Formulation
  • Issue Processing
  • CRM SIG Archive
  • Mappings
  • Short Intro
  • Mapping Methods
  • Mapping Tools
  • Mapping Memory
  • Reports about Mappings
  • Compatible Models
  • Short Intro
  • Models
  • Use Cases
  • Short Intro
  • Use Cases

RESOURCES

  • Related Activities
  • Versions
  • References
  • Presentations
  • Technical Papers
  • Tutorials
  • Critics
  • Important Theories
  • Publications
  • Mappings
  • Compatible Models
  • Translations
  • Best Practices
  • Meeting Contributions
  • Minutes
  • Issues
  • CRM SIG Archive
  • Meeting Contributions

ACTIVITIES

  • Short Intro
  • SIG Meetings
  • Minutes
  • Workshops
  • Related Activities

PEOPLE

  • Short Intro
  • Related Stakeholders
  • SIG Members
  • Hosts

NEWS

HOME

 

 

Copyright © 2025 Company Name - All rights reserved

Developed & Designed by Alaa Haddad