This is the second appointment with the knowledge representation seminar we're having at CCH (Kings College, London). If you are in the area and are interested in taking part in this, please drop me an email. We're looking at these topics from the specific perspective of the digital humanities, but even if your take on things is different, we'd love to hear from you!
Last meeting we discussed quite generally about ontologies and other KR technologies, so this time we decided to start looking more meticulously into the details of a widely known ontology for the cultural heritage domain, the CIDOC-CMR conceptual model (an ISO standard since 2006).
Doerr. The CIDOC conceptual reference module: an ontological approach to semantic interoperability of metadata. AI Magazine archive (2003) vol. 24 (3) pp. 75-92
The CIDOC-CRM is the de facto standard for data integration in the museum community. Its authors claim that it "is intended to be a common language for domain experts and implementers to formulate requirements for information systems and to serve as a guide for good practice of conceptual modelling. In this way, it can provide the "semantic glue" needed to mediate between different sources of cultural heritage information, such as that published by museums, libraries and archives".
CIDOC contains a wealth of inspiring ideas and useful approaches; in our first meeting about it we highlighted only a few of them, including:- the need for interoperability at the semantic level - the difference between data capturing and interpreting data - the read-only integration approach - the notion of a property-centric ontology - the top-level classes in CIDOC - the nature of cultural historical knowledge - general principles and methodology in CIDOC-CMR
Here are some slides including key passages from the CIDOC paper mentioned above:
One thing that CIDOC doesn't cover much is the domain of information objects, which is a fancy term ontologists use to refer to anything that can carry information, such as a book, a stone inscription, or a piece of music. Modeling this type of entities using a clear (and possibly formal) language may seem straightforward at first: a book is a simple physical object, isn't it?
However this is not always the case: things easily get muddled as soon as you start thinking about the fact that a book can have multiple copies, that it can be translated into many languages, or it can be included into a different edition. In all these cases, what is the 'book' entity we're talking about? Not the physical object, apparently.
How to model information objects is a topic that librarians (among others) have discussed quite extensively in the years. As a result of these discussion librarians developed a conceptual model called FRBR, which has become a standard to follow when dealing with this type of problems.
FRBR (represented schematically above) summarizes quite well various important features of information objects, especially when considered under the perspective many library scientists have. However it is also true that FRBR doesn't present its results using the rigourous and unambiguous language of formal ontologies. As a result, people end up interpreting the meaning of its concepts in slightly different ways. For example, if you are a librarian with little knowledge of computer science, you might end up using FRBR in a totally different way than that of a computer scientist who'd designing a software system for librarians.
To address this limitation, and also in order to open up the CIDOC-CRM model to the librarian community, the CIDOC committee has started 'ontologizing' FRBR. The second part of our seminar focused on this (ongoing) enterprise, which is outlined in this article:
Bekiari, C., Doerr, M., & Boeuf, P. L. (2009). FRBR: Object-Oriented Definition and Mapping to FRBR-ER (version 1.0). International Working Group on FRBR and CIDOC CRM Harmonisation.
Here are the slides I used in the seminar, which contain some of the most salient visual representation of the ontology:
That's all for now - in the future we'll be looking at specific situations where using CIDOC and FRBR presents challenges to the digital humanist: stay tuned!
Cite this blog post:
Representing Knowledge in the Digital Humanities, Lawrence, Kansas, Sep 2011.