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

automatically detect incompatibilities between CRM extensions and the CIDOC CRM

647
2023-08-03
2 - Application guidelines
Open

In the 56th joint meeting of the CIDOC CRM and ISO/TC46/SC4/WG9 &49th FRBR/LRMoo SIG, the SIG resolved to start a new issue in order to automatically detect incompatibilities between the CIDOC CRM & its extensions. 

HW: PF & ETz to work on that. 
Nb: Consult with VA (LAHRA), because OntoME does exactly that. 

 

Crete, May 2023
 

In the 57th CIDOC CRM & 50th FRBR/LRMoo SIG Meeting, VA shared a presentation with the SIG on features of the OntoME that allow for a consistency check btw CRM and family models. The slide deck can be found here. 

Decision: 

HW: Based on the discussion that folloewd, ETz, PF & VA will be working towards performing additional checks to automatically generate rdf files for CRMbase and extensions, namely: 

  1. vocabulary checking regarding class and property labels
  2. detection of wrong domain or range of a property
  3. hierarchical cycles
  4. unique hierarchical branch position (If A subClassOf B, B subClassOf C then A cannot be subClassOf C)
  5. domain/range of a property must be subClass or equal to the domain/range of its superProperty
  6. Avoid hierarchical relationships of owl:DatatypeProperties with owl:ObjectProperties, and document the cases

Nb. OntoME can probably be extended by points 3-6. 

Nb.': check out for potential inconsistencies btw a model and its translations. 

 

Marseille, October 2023
 

510   belief adoption

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