Issue 570: FOL statements in prose -appropriate section of class/property definitions

Starting Date: 
Working Group: 

In the 51st CIDOC CRM & 44th FRBRoo SIG meeting, the SIG resolved to work out a well-formulated proposal for where the text rendering FOL statements should be put in the definitions of classes and properties. Probably at the end of the text, right before the examples. 

HW: MD to provide a reading guide for the FOL and where it goes on scope notes. GH, TV, CEO to proofread.

Comments on how to read the FOL statements: 
(i) maybe the labels of classes/properties should appear as well 
(ii) maybe we could draft graphs for the FOL statements.

Current Proposal: 

Post by Martin Doerr (21 January 2022)

Dear All,

Here some attempts to render FOL into language...

I think colors are useful to show which parts render syntax and which variable elements.

 I try to show the transition from literally reading to use of linguistic relative phrases, "which", "this", etc. by offering multiple ways of reading.

Graphical rendering would also be good for the more complex inferences.

Please comment.



Post by Martin Doerr (23 January 2022) 

Attached a more verbose introduction.

Post by Thanasis Velios (23 January 2022) 


Dear Martin,

Please find attached some comments / changes for discussion. I was imagining this as an automated process based on a translation table like e.g.:

∃ "there is"
⋀ "and"
⋁ "or"


to allow the FOL statement to be translated automatically into English. But maybe this is not possible if we need even marginal elegance in the resulting text.

All the best,


Post by Christian-Emil Ore (23 January 2022)


The first two FOL clauses for properties are always the domain and co-domain (range). 

It may be considered overkill to repeat the domain-range in plain words. If we should do that, then we could write one sentence:
If x P?? y then x is an instance of E?? and y is an instance of E??'


In the 52nd CIDOC CRM & 45th FRBRoo SIG meeting, the SIG reviewed the reading guide to FOL expressions (HW by MD). The comments TV had made on the document have not been discussed.

Discussion points


  • The verb “must” found in the statements is evocative of the necessity operator. But in most cases the relation expressed is that of subset, thus rendering the “must” superfluous (if not ambiguous btw a deontic and a possible interpretation)
  • If “must” is to appear in the textual descriptions of the FOL statements, it should be stated in an introductory text that “must” is to be read as “it is necessarily the case that p” (for whatever lies in its scope). 
  • The material implications apply to every instance of a class or property, not some. This is lost by not introducing the universal quantifier to its reading.
  • However the "for all" or "each" expressions in prose make the statement harder to read for those with no FOL training. 
  • "Must" has been used as a point of emphasis, not to introduce possible world semantics. 

Formulate a proposal re. 
(i) the form of the textual renditions of the FOL expressions
(ii) the position of the rendition  in prose of the FOL in the main body of the text vs. another document/appendix/reading guideline in the intro.

HW: GB, TV, MD and CM to help re-express the FOL statements in English without introducing any sort of ambiguity.

February, 2022

Meetings discussed: