Skip to main content

User account menu

  • Log in
Home
CIDOC CRM

Cidoc Horizontal Menu

  • Home
    • About & Info
    • Use & Learn
    • Issues
    • Mappings
    • Compatible Models
    • Use Cases
    • Best Practices
  • Activities
  • Resources
  • Community
  • News

Issues

  • Short Intro
  • Issue Formulation
  • Issue Processing
  • CRM SIG archive

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

 

About the relationship between symmetry and transitivity

686
2024-10-26
1 - Editorial changes
Done

Dear All,

Apologies if this has already been discussed: I would suggest to reformulate a paragraph in the introduction of the CRMbase document about properties with identical domain and range. See here:
https://docs.google.com/document/d/1_3J5e6wscwNEQzPqpBfWBmoOiHoBmAx_o8_…

Best,
Wolfgang

Post by Christian-Emil Ore (28 October 2024)

It is clear that having the same domain and range is not a sufficient condition for a property to be either symmetric or transitive as your example with P152 has parent (is parent of) clearly demonstrates. Also "Properties that have identical domain and range are either symmetric, asymmetric or neither." covers all cases and is a tautology. Maybe it is better to reformulate the paragraph to

 


"Symmetric and transitive properties have identical domain and range. Instantiating a symmetric property implies that the same relation holds for both the domain-to-range and the range-to-domain directions. An example of this is E53 Place. P122 borders with: E53 Place. The names of symmetric properties have no parenthetical form, because reading in the range-to-domain direction is the same as the domain-to-range reading. 
Properties with identical domain and range that are not symmetric, such as E41 Appellation. P139 has alternative form (is alternative form of): E41 Appellation, have a parenthetical form that relates to the meaning of the inverse direction."

Best,
Christian-Emil
 

Post by Stephen Stead (28 October 2024)

This looks good to me

 

Stephen Stead

Post by Wolfgang Schmidle (28 October 2024)

This would be version 1 with a better first sentence, and split up into two paragraphs. Just one thing: Transitivity plays no further role here, so if it is mentioned, perhaps reflexivity should be mentioned as well? As in
Symmetric, transitive and reflexive properties have identical domain and range.

Best,
Wolfgang

Post by Daria Hookk (28 October 2024 --personal communication)

 

Your mean symmetric property is synonym and strictly speaking has no direction for the application like "to be brother of"?

Being interested in (non-symmetric),
Daria Hookk

Post by Christian-Emil Ore (28 October 2024)

A symmetric, reflexive  and transitive relation is what we call an equivalence relation (like equality)

Without reflexivity it like "siblinghood" (with same pair of parents).  

Chr-E

Post by Martin Doerr (28 October 2024)

Dear all,

Thank you Wolfgang for spotting the problem!

I think we are patching here. The full paragraph

  • Properties that have identical domain and range are either symmetric or transitive. Instantiating a symmetric property implies that the same relation holds for both the domain-to-range and the range-to-domain directions. An example of this is E53 Place. P122 borders with: E53 Place. The names of symmetric properties have no parenthetical form, because reading in the range-to-domain direction is the same as the domain-to-range reading. Transitive asymmetric properties, such as E4 Period. P9 consist of (forms part of): E4 Period, have a parenthetical form that relates to the meaning of the inverse direction.

appears as part of the naming conventions. The concepts of transitivity, reflexivity and symmetry are extensively explained in the terminology section. No reason to repeat them here, this causes pitfalls when updating the text. The only reason, why this should appear under "Naming Conventions" is the missing inverse label.

Therefore, I propose to replace the paragraph by:

  • Instantiating a symmetric property implies that the same relation holds for both the domain-to-range and the range-to-domain directions. Therefore the names of symmetric properties have no parenthetical form, because reading in the range-to-domain direction is the same as the domain-to-range reading. An example of this is E53 Place. P122 borders with: E53 Place (see also the definition of "symmetric" in the section "Terminology".)

It could even be shorter:

  • The names of symmetric properties have no parenthetical form, because reading in the range-to-domain direction is the same as the domain-to-range reading. An example of this is E53 Place. P122 borders with: E53 Place. See the definition of "symmetric" in the section "Terminology".

Opinions?

Cheers,

Martin

Post by Christian-Emil Ore (28 October 2024 --personal communication)

Your last alternative is in my opinion the best:

  • The names of symmetric properties have no parenthetical form, because reading in the range-to-domain direction is the same as the domain-to-range reading. An example of this is E53 Place. P122 borders with: E53 Place. See the definition of "symmetric" in the section "Terminology".

Chr-Emil

Post by Wolfgang Schmidle (28 October 2024)

  • The names of symmetric properties have no parenthetical form, because reading in the range-to-domain direction is the same as the domain-to-range reading. An example of this is E53 Place. P122 borders with: E53 Place. See the definition of "symmetric" in the section "Terminology“.


I think this version is clear and gets to the point.

Post by Eleni Tsouloucha (11 March 2025)

 

Dear all,

Do you agree with substituting the current phrasing concerning transitivity and symmetry in CIDOC CRM v7.3 for the one proposed by Martin, Wolfgang, and Christian-Emil?

Namely:

the bullet point under Naming Conventions that now reads:

  • "Properties that have identical domain and range are either symmetric or transitive. Instantiating a symmetric property implies that the same relation holds for both the domain-to-range and the range-to-domain directions. An example of this is E53 Place. P122 borders with: E53 Place. The names of symmetric properties have no parenthetical form, because reading in the range-to-domain direction is the same as the domain-to-range reading. Transitive asymmetric properties, such as E9 Period.P9 consists of (forms part of): E4 Period, have a parenthetical form that relates to the meaning of the inverse direction."

would become: 

  • "The names of symmetric properties have no parenthetical form, because reading in the range-to-domain direction is the same as the domain-to-range reading. An example of this is E53 Place. P122 borders with: E53 Place. See the definition of "symmetric" in the section "Terminology"."

 

The motivation is that the wording found under Naming Conventions in V7.3 is inaccurate, and the reason to delete the reference to transitive, asymmetric properties, seeing as the information is repeated in the Terminology section --see definitions therein.

Please reply by yes, no, or N/A by March 22.

All the best,
Eleni

Post by Wolfgang Schmildle (11 March 2025)

YES

Best,
Wolfgang

Post by Daria Hookk (11 March 2025) --personal communication

 

yes

Post by Martin Doerr (11 March 2025)

YES

Martin

Post by Christian-Emil Ore (12 March 2025)

 

yes

Chr-Emil

Post by Øyvind Eide (12 March 2025)

 

YES

Post by Guenther Goertz (12 March 2025)

yes

Best, Guenther

Post by Pat Riva (13 March 2025)

YES

 

Post by Muriel Van Ruymbeke (14 March 2025)

YES 

 

Post by Thanasis Velios (16 March 2025)

YES

The proposed change has been accepted, it will be incorporated in v7.3.1. 

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