How should we treat data? Like we were Humanists

broken relationships

*

It strikes me how we (digital humanists) have a very different relationship with structured data compared to the one we have with text and literature. This seems to me to be reflected in the way that we treat data. While many different initiatives around the world attempt to bring data from cultural organisations together, we seem intent on accepting a narrow view about the possibilities of data, computers and the interaction of people, and as a result are happy to ignore the possibilities and benefits of capturing the context (and meaning) attached to data by the experts (people) who produced it and who continually update and develop it. If humanist researchers digitise a book to learn more about it, isn’t the objective to discover more, to discover the hidden relationships and meanings and make connections with other evidence that we have? Do we seek to exclude the elements of it that would give us this insight and throw them away? If not, then why do we accept this situation with cultural data?

Many cultural information systems were designed as closed systems to be used internally in union with the knowledge of the institution and its experts. The original data schemas were often produced to create a functional inventory or reference, and as an internal system they offer a valuable resource – but they are used in combination with other internal knowledge about the data (a knowledge built up over time). If you separate data from its institutional knowledge and context then you lose this essential part of the overall ‘information system’. This is why, when we represent data it should not be just a technical process. It should involve and add institutional knowledge to ensure that the data carries with it as much of this additional and valuable local meaning as possible. Data providers, the institutions themselves, could be providing data that is far more expressive and far more likely to help people (researchers, teachers, ‘the public’ and the institutions themselves) understand their relationship with the past – the type of representations that we take for granted when working on digital literature projects.

“…what would we be without memory? We would not be capable of ordering even the simplest thoughts, the most sensitive heart would lose the ability to show affection, our existence would be a mere never-ending chain of meaningless moments, and there would not be the faintest trace of a past.”   Max Sebald (The Rings of Saturn)

Let’s not make data meaningless and technical, devoid of memory and perspective. Let’s treat it in such a way that it can also evoke meaningful and long lasting memories, and let’s allow it to make connections between different memories (perhaps ones separated by time and place) many of which have been long since forgotten and locked away in our knowledge/memory silos. Let’s use data to produce powerful narratives about history – like we do with literature. Let’s treat data like we were humanists.

For a more formal version of this blog see: http://www.dlib.org/dlib/july14/oldman/07oldman.html 

 

*By Kathy Kimpel (Flickr: IMG_0327) [CC-BY-2.0 (http://creativecommons.org/licenses/by/2.0)]

A British Museum Endpoint CIDOC CRM Example Query

An example of a query from the Endpoint (link http://tinyurl.com/ntwm7d6)

 

#The query retrieves gold coins from a particular time span and cultural period which have the words Augustus inscribed on them.
PREFIX crm: <http://erlangen-crm.org/current/>                  #Prefix for the CIDOC-CRM
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>               #Prefix for SKOS terminologies
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>                

PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX bmo: <http://collection.britishmuseum.org/id/ontology/>    #British Museum Ontology PX_
PREFIX fts: <http://www.ontotext.com/owlim/fts#>                #OWLIM Fast Text serach

select 
?object                        #Object URI
?objectphy                     #Object physical Description (sub propoerty of P2_has_note)
?inscriptext                   #Inscription text
?startdate                     #xsd start date for range
?enddate                       #xsd end date for range
?comment                       #curatorial comments on the object (sub propoerty of P2_has_note)
where

{

?object crm:P2_has_type ?objecttype .                        #An object has an object type
?objecttype skos:prefLabel "coin" .                          #the object type is "coin"

?object bmo:PX_physical_description ?objectphy .             #has a physical description
?object bmo:PX_curatorial_comment  ?comment .                #has a curatorial comment 

?object crm:P130_shows_features_of ?inscription .            #object has a feature
?inscription rdf:type crm:E34_Inscription .                  #the feature is an inscription 
?inscription rdfs:label ?inscriptext .                       #the inscription label has some text 

?object crm:P45_consists_of ?materialid .                    #The object is made of a material
?materialid skos:prefLabel ?metal .                          #The material label has some text 

?object crm:P108i_was_produced_by ?production .              #The Object was produced through a production event
?production crm:P9_consists_of ?productionpart  .            #The production event consists of parts
?productionpart crm:P4_has_time-span ?timespandate  .        #One part describes a time span    
?timespandate crm:P82a_begin_of_the_begin ?startdate .       #The time span has a begining date
?timespandate crm:P82b_end_of_the_end ?enddate .             #The time span has an end date

?object crm:P108i_was_produced_by ?production .              #The object was produced through a production event
?production crm:P9_consists_of ?productionpart1  .           #The production event consists of parts
?productionpart1 crm:P10_falls_within ?matcultureid .        #One part describes the cultural period
?matcultureid skos:prefLabel ?period .                       #The period has a descriptive label 
#FILTER regex(str(?period),"Roman Imperial","i")             #You can look the id up using regex
#<Imperial:Roman:> fts:exactMatch ?period .                  #You can also do this with OWLIM FTS    
?matcultureid skos:prefLabel "Roman Imperial" .              #You can also use the exact literal if you know it

{FILTER ((?startdate >= "-0035-01-01"^^xsd:date) &&          #the date range 
(?enddate <= "-0010-12-31"^^xsd:date))}                                                                              

FILTER (regex(?inscriptext, "AVGVST","i"))                   #the inscription contains the text AVGVST (Augustus)

FILTER (regex(?metal, "GOLD","i"))                           #the coin contains copper 

}

					

A Museum Mapping for the Real World

The BM Mapping in a Nutshell

The contextual generalisations of the Conceptual Reference Model (CRM) have been derived by examining a wide range of data models particularly from the cultural heritage and museums sector. This means that many of the concepts are familiar to those working with museum documentation. The following provides a summary of the mapping for a typical British Museum object based on some key CRM properties (it is not comprehensive and does not describe all elements). As you will see the CRM closely follows the events and concepts that many museum staff find familiar and uses real world descriptions rather than the technical labels commonly found in databases tables. The CRM differentiates itself from other aggregating frameworks because it does not attempt to strip down data sources into a common set of fields but instead provides a model for harmonising rich and complex data sets, from whatever source and however formed, to derive the maximum benefit.

The CRM requires an understanding of the domain and range of the properties that it uses. Every CRM property has a carefully selected scope of use. It will only be applicable for a specified domain (the subject of an RDF triple) and a specified range (the object of a triple). The CRM has a structure of classes and the while the domain and range are specified at the highest appropriate class its sub-classes are also implied. Therefore the range of E39_Actor includes the sub-classes E21_Person and E74_Group. A domain of E5_Event includes the sub-class E7_Activity and its sub-class E8_Acquisition – and so on.

The following summary is not an instruction in mapping CRM but an exercise in demonstrating the appropriateness of the ontology to cultural heritage objects. The narrative underlines terms that are reflected in the labels of properties and classes that are listed (again not comprehensively or in any order) next to the narratives. The summary is taken from a larger document that does describe the mapping process in more detail.

Narrative Properties Classes
Museums hold objects that tell the history of the world. These objects sometimes have a title and are recorded with an identifier (an accession number). Some objects form part of a sub-collection with a collection title.
  • P102_has_title
  • P1_is_identified_by
  • P46i_forms_part_of
  • E22_Man-Made_Object
  • E35_Title
  • E42_Identifier
  • E78_Collection
CRM Mapping NoteThe domain of the property P102_has_title is E71_Man-Made_Thing.  A BM object is typed as an E22_Man-Made_Object which is part of the E71_Man-Made_Thing class hierarchy. Therefore P102_has_title can be used with a man-made object. The range is E35_Title. Therefore the node that the triple uses as an object node (as in subject – predicate – object) must be of type, E35_Title.The domain of P1_is_identified_by is E1_CRM_Entity (so any entity in the CRM could have an identifier. The range is E41_Appellation. E41_Appellation has sub-classes that include E42_Identifier. Therefore to make the triple using P1_is_identified_by valid the object node in the triple is, and is typed as, an E42_Identifier.Lastly, P46i_forms_part_of is the inverse of the property P46_is_composed_of, and is used to show that the object forms part of a collection. It has a domain and a range of E18_Physical_Thing. This class includes the sub-class E24_Physical_Made-Made_thing which in turn has the sub-class E78_Collection. Therefore a collection is a type of E18_Physical_Thing and is valid for the mapping.
Most collection catalogue databases will allow curators to write some comments or notes about the object.
  • P3_has_note
  • E62_String
CRM Mapping NoteAs you might expect P3_has_note has the domain of E1_CRM_Entity and can therefore apply to any triple subject (you can write notes about anything). Its range is E62_String and therefore the node it points to must be of type E62_String. Straight forward, yes?(Note: You may be starting to understand how the CRM ensures integrity of mapping. This is essential for the end product to make sense, but also ensures data harmonisation.
Museums will record where the object came from and therefore the details of the various transfers of it from one person or organisation to another, and ultimately to the current owner. However, the current owner could be a third party if the object is on loan, and the acquisition may simply be a transfer of custody rather than of ownership.
  • P23_transferred_title_from
  • P51_has_former_or current owner.
  • P52_has_current_owner
  • P28_custody_surrendered_by
  • E22_Man_Made_object
  • E8_Acquisition
  • E10_Transfer of Custody
CRM Mapping NoteP23_transferred_title_from is a predicate that uses a subject node with a type of E8_Acquisition (domain) but must refer (range) to an E39_Actor (e.g. a person E21 or a Group E78). This makes sense because the object must come from some sort of group or person. For P51_has_former_owner we are talking about the object’s (E22_Man-Made_Object) former owner (the domain is E18_Physical_Thing) and a range of E39_Actor again (Acquisitions work around people or organisations). Likewise the property P52_has_current_owner also operates in the domain of the physical thing (E18_Physical_Thing) and the range of an Actor.P28_custody_surrendered_by has a range of E39_Actor but the domain is E10_Transfer_of _Custody. This triple operates between the acquisition node (typed as a transfer of custody as well as an acquisition) and the actor from which the object was transferred. Other forms of transfer exist likeP24_transferred_ownership_through (rather than ‘from’). The semantics are different and therefore there will be different forms of acquisition mapping. We call this different constructs
In some cases details of where an object was originally found are known and recorded.  The find itself is an event at which the object was present.
  • P12i_was_present_at
  • EX_Discovery (BM specialisation)
CRM Mapping NoteP12i_was_present_at is the inverse of the property P12_occurred_in_the_presence_of which is used in the domain of E5_Event. The Museum has created a sub-class of E5_Event called EX_Discovery to describe the event of discovery of an object. If the CRM doesn’t have a class that describes your entity fully then you can usually create a sub-class of an existing CRM class. The BM has limited the number of class specialisations to the absolute minimum and instead made use of typing by vocabularies.
Further investigation of the object will often provide more information about how the object was created or produced in the first place. Like an acquisition or a find, a production is an event with a range of useful information. For example, the technique used to produce the object. The BM records the broad production types to support precise searching.
  • P108i_was_produced_by
  • P32_used_general_technique
  • E12_Production
  • E55_Type
CRM Mapping NoteP108i_was_produced_by provides the initial relationship between the collection item and the production event node. Therefore the domain must be the classes that describe an object, in this case E24_Physical_Man-Made_Thing which clearly denotes that this is an artificial thing that has been produced (and encompasses E22_Man_Made_object).P32_used_general_technique works with activities (E7_Activity being the domain) and production is indeed an activity because it is a sub-class of E11_Modification which is, in turn, a sub-class of E7_Activity. The British Museum then uses a thesaurus of technique terms in a SKOS format – the term itself is typed as E55_Type – which is the range of P32_used_general_technique.
The period in which production falls within is a key piece of information and may be accompanied by a date or specific time period.
  • P10_falls_within
  • P4_has_time_span
  • E52_Time_Span
CRM Mapping NoteP10_falls_within has both a domain and a range of E4_Period.  An example of a period is an E7_Event and all activities are therefore within the sub-classes of E4_Period, including say, an E8_Acquisition. Therefore in the mapping we can use P10_falls_within with any event object but must ensure that the triple subject comes within the realms of E4_Period node before defining the details of the period. This is done by creating an appropriate date URI, typed as a time span, to hold the date information.
People and places are commonly associated with production information. The people, groups or artistic schools who carried out the production of the object and the locations where production took place (which might be various) are important material aspects of the object.
  • P14_carried_out_by
  • P7_took_place_at
  • E21_Person
  • E39_Actor
  • E74_Group
  • E53_Place
CRM Mapping Note The most frequent use of the generalisation P14_carried_out_by in the Museum’s mapping is in production, and in particular, the relationship with people and places (using P7_took_place_at).Unsurprisingly P14_carried_out_by has a domain of E7_Activity (as production is also an event) and a range of E39_Actor.  P7 P14_carried_out_by has the same domain but the range is, of course, E53_Place.
Other people indirectly involved in the process might be those who influenced the production (another artist for example) or were the motivation for it, like a coin minted for an emperor. Otherwise an object might have been made for an event.
  • P15_was_influenced_by
  • P17_was_motivated_by
  • E21_Person
  • E39_Actor
  • E74_Group
  • E53_Place
  • E5_Event
CRM Mapping NoteP15_was_influenced_by and P17_was_motivated_by are again talking about the domain of ‘activities’. In the BM mapping these might be people or groups who have influenced or motivated (although P15 and P17 have a range which includes all CRM entities (E1_CRM_Entity) a production process. These are generalisations that are very open to reification with internal vocabularies. For example, the motivation of something through an authority, like an emperor, is useful information to add to the mapping.
If the object has an inscription on it then this is a type of visual item which might directly refer to a subject, place, person or group.
  • P65_shows_visual_item
  • P67_refers
  • E65_Creation
  • E34_Inscription
CRM Mapping NoteP65_shows_visual_item refers to  E24_Physical_Man-Made_Thing and has a range of E36_Visual_Item. In the mapping this is a node created for the purpose of using P67_refers (which has the domain of E89_Propositional_Object – a class containing immaterial objects like information objects (E73_Information_Object). An Information object includes a visual item (E36_Visual_Item) that itself contains a class for ‘markings’ (E37_Mark) and this has the sub-class for inscriptions (E34_Inscription) – and therefore is a valid range for P65_shows_visual_item.
An inscription is a type of production process (a creation) in its own right and therefore we may record specific production information against it including the person who carried out the inscription (who may be different from the object producer).
  • P14_carried_out_by
  • E21_Person
CRM Mapping NoteSee production above
The object may directly depict or visually represent as an image place, person or group and so on.
  • P62_depicts
  • P65_shows_visual_item
  • P138_represents
  • E38_Image
  • E21_Person
  • E39_Actor
  • E53_Place
CRM Mapping NoteDepiction is a short cut for a visual image (picture) representation. P65_shows_visual_item can refer to a picture (image) on the object itself (the domain and range above). Instead of P67_refers a pictorial representation uses the property P138_represents. This operates with a (you guessed it) an E36_Visual_Item and any other CRM entity (E1_CRM_Entity).
The object may also have more indirect associations to these things and carry references. The object may also have conceptual subjects (information object) which can tell people more about the object and its meaning.
  • P128_carries P67_refers
  • P129_is_about
  • E73_Information_Object
CRM Mapping NoteAn object may refer to something in a more indirect conceptual way. The Museum has invented a URI node called ‘concept’ and typed it as an E73_Information_Object. P128_carries can use this node as its range (with a domain of E24_Physical_Man-Made_thing – the physical object) and this provides the basis for a reference to an E21_Actor (like an ethnic group – e.g. this visual design alludes to a particular culture)  or an recorded event. P67_refers has the domain E89_Propositional_Object (including an E28_Conceptual_Object) and can have a range of any concept.  P128 has the range E90_Symbolic_Object (including the “aggregation of symbols”) covering subject terms.
Other more technical information is also recorded against the object like the material it was made out of (or that it consists of).
  • P45_consists_of
  • E57_Material
CRM Mapping NoteThis one is straight forward. P45_consists_of has a domain and refers to an E19_Physical_Thing and has the range of E57_Material. This would be a thesauri identifier leading to a SKOS schema for the term.
Dimension measurements are taken for the object and these are stored as values and units.
  • P43_has_dimensionP90_has_value
  • P91_has_unit
  • E54_Dimension
CRM Mapping NoteP43_has_dimension operates over E70_Thing (our object again) and has the range of an E54_Dimension. E54 provides the domain for P90_has_value which has the range of E60_Number.   P91_has_unit has the same domain but the range E58_Measurement.
Objects will be documented in bibliographic material which is created through publishing and authoring. This includes journals (a component of a series) and references that are part (components) of a collection.
  • P70i_is_documented_in
  • P94i_was_created_by
  • P148i_is_a_component_of
  • E31_Document
  • EX_Bibliographic _Series
  • E65_Creation
CRM Mapping NoteNot surprisingly P70_documents (P70i _ is_documented_in) refers to E31_Document and can apply to any CRM entity. P94_has_created has the domain E65_Creation and applies to E28_Conceptual_Object. In this case the concept is ‘Authoring’. P148i refers to a document being part of a E89_Propositional_Object
People might be identified with different names (or appellations) and the Museum records people who belong to or were members of a school (of art for example). These are people of different (belong to) national groups.
  • P131_is_identified_by
  • P107i_is_current_or_former_member_of
  • E39_Actor
  • E21_Person
  • E74_Group
CRM Mapping NoteP131 is used specifically to identify the name of an E39_Actor with the range E82_Actor_Appellation. P107 deals with members of a group with the domain being E74_Group and a range of E39_Actor.

The Costs of Cultural Heritage Data Services: The CIDOC CRM or Aggregator formats?

Martin Doerr (Research Director at the Information Systems Laboratory and Head of the Centre for Cultural Informatics, FORTH)
Dominic Oldman (Principal Investigator of ResearchSpace, Deputy Head IS, British Museum

June 2013

Many larger cultural institutions are gradually increasing their engagement with the Internet and contributing to the growing provision of integrated and collaborative data services. This occurs in parallel with the upcoming so-called aggregation services, seemingly striving to achieve the same goal. At a closer look however, there are quite fundamental differences that produce very different outcomes.

Traditional knowledge production occurred in an author’s private space or a lab with local records, notwithstanding field research. This space or lab may be part of an institution such as a museum. The author (scholar or scientist) would publish results and by making content accessible it would then be collected by libraries. The author ultimately knows how to interpret the statements in his/her publication and relate that to the reality referred in the publication, from the field, from a lab or from a collection. Many authors are also curators of knowledge and things.

The librarian would not know this context, would not be a specialist of the respective field, and therefore must not alter in any way the content. However, (s)he would integrate the literature under common dominant generic concepts and references, such as “Shakespeare studies”, and preserve the content.

In the current cultural-historical knowledge life-cycle, we may distinguish three levels of stewardship of knowledge: (1) the curator or academic, (2) the disciplinary institution (such as the Smithsonian, the British Museum or smaller cultural heritage bodies) (3) the discipline-neutral aggregator (such as Europeana or IMLS-DCC).  Level (2) typically acts as “provider” to the “aggregator”.

Obviously, the highest level can make the least assumptions about common concepts, in particular a data model, in order to integrate content. Therefore, it can offer services only for very general relationships in the provided content. On the other side, questions needing such a global level of knowledge will be equally generic. Therefore, the challenge is NOT to find the most common fields in the provider schemata (“core fields”), but the most relevant generalizations (such as “refers to”, avoiding overgeneralizations (such as “has date”). These generalizations are for accessing content, but should NOT be confused with the demand of documenting knowledge. At that level some dozens of generic properties may be effective.

The preoccupation of providers and aggregators with a common set of fields has the result that they only support rudimentary connections between the datasets they collect and as a result reduce the ability for researchers to determine where the most relevant knowledge may be located. As with the library, the aggregator’s infrastructure can only support views of the data (search interfaces) that reflect their own limited knowledge because the data arrives with little or no context and over-generalized cross-correlations (“see also”, “relation”, ”coverage”).

The common aggregation process itself strips context away from the data creating silos within the aggregator’s repository. Without adequate contextual information searching becomes increasingly inadequate the larger the aggregation becomes. This limitation is passed on through any Application Programming Interfaces that the aggregator offers. Aggregators slowly begin to understand that metadata is an important form of content, and not only a means to query according to current technical constraints. Some aggregators, such as the German Digital Library, store and return rich “original metadata” received from providers and derive indexing data at the aggregator side, rather than asking providers to strip down their data.

The institution actually curating content must document it so that it will not only be found, but understood in the future. It therefore needs an adequate [1] representation of the context objects come from and their meaning. This representation already has some disciplinary focus, and ultimately allows for integrating the more specialized author knowledge or lab data. For instance, chronological data curves from a carbon dating (C14) lab should be integrated at a museum level (2) by exact reference to the excavation event and records, but on an aggregator level (3) may be described just by a creation date.

A current practice of provider institutions to manually normalize their data with millions of pounds, dollars or euros directly to aggregator formats appears to be an unbelievable waste of money and knowledge. The cost of doing so exceeds by far the cost of the software of whatever sophistication. It appears much more prudent to normalize data at an institutional level to an adequate representation, from which the generic properties of a global aggregator service can be produced automatically, rather than producing, in advance of the aggregation services, another huge set of simplified data for manual integration.

This is precisely the relationship between the CRM and aggregation formats like the EDM. The EDM is the minimal common generalization at the aggregator level, a form to index data at a first level. The CRM is a container, open for specialization, for data about cultural-historical contexts and objects. The CRM is not a format prescription. Concepts of the CRM are used as needed when respective data appear at the provider side. There is no notion of any mandatory field. Each department can select what it regards as mandatory for its own purpose, and even specialize further, without losing the capacity of consistent global querying by CRM concepts. CRM data can automatically be transformed to other data formats, but even quite complex data in a CRM compatible form can effectively be queried by quite simple terms [3].

Similarly, institutions may revise their data formats such that the more generic CRM concepts can automatically be produced from them, i.e., make their formats specializations of the CRM to the degree this is needed for more global questions. For instance, the features of the detailed curve of a C14 measurement are not a subject for a query at an institutional level. Researchers would rather query to retrieve the curve as a whole.

The British Museum understands this fundamental distinction and therefore understands the different risks and costs. This means both the long term financial costs of providing data services, important to organizations with scarce resources, but also the cost to cultural heritage knowledge communities and to society in general. As a consequence they publish using the CRM standard. They also realize that data in the richer CRM format is much more likely to be comprehensible in the future than in “core metadata” form.

Summarizing, we regard publishing and providing information in a CRM compatible form [2] at the institutional or disciplinary level to be much more effective in terms of research utility (and the benefits of this research to other educational and engagement activities). The long-term costs are reduced even with further specializations of such a form, and the costs of secondary transformation algorithms to aggregation formats like EDM are marginal.

Dominic Oldman

 

[1]  Smith B. Ontology. The Blackwell Guide to the Philosophy of Computing and Information., pages 155–166, 2003. Floridi, L. (ed). Oxford: Blackwell.

[2] Official Version of the CIDOC CRM, the version 5.0.4 of the reference document.
Nick Crofts, Martin Doerr, Tony Gill, Stephen Stead, Matthew Stiff (editors), Definition of the CIDOC Conceptual Reference Model, December 2011.
Available: doc file (3.64 Mb), pdf file (1.56 Mb)

[3] Tzompanaki, K., & Doerr, M. (2012). A New Framework For Querying Semantic NetworksMuseums and the Web 2012: the international conference for culture and heritage on-line. April 11-14, San Diego, CA, USA

 

The British Museum, CIDOC CRM and the Shaping of Knowledge

At the British Museum we are fast approaching a new production version of our currently beta Semantic Endpoint. The production version will remove some of the current restrictions and provide a more robust environment to develop applications against. It will also come with much needed documentation detailing a new mapping to the CIDOC CRM (Conceptual Reference Model) prompted by feedback received from the current version and by requirements to support the ResearchSpace project.

The use of the CIDOC CRM itself has raised questions and criticisms, mostly from developers. This comes about for a variety of reasons; the lack of current CRM resources; a lack of experience of using it (an issue with any new method or approach); a lack of documentation about particular implementations; but also, particular to this type of publication, a lack of domain knowledge by those creating cultural heritage web applications. The CRM exposes a real issue in the production and publication of cultural heritage information about the extent to which domain experts are involved in digital publication and, as a result, its quality.

The debate about whether we should focus on providing data in a simple format for others to use in web pages and at hack days, against a richer and more ontological approach (requiring a deeper understanding of collection data) is one in which the former position is currently dominant. To support this there are some exceptional projects using simple schemas designed to achieve specific and collaborative objectives. However, many linked data points lack the quality to be more than basic information jukeboxes that, in turn, support applications with limited usefulness and shelf life. In short, the current cultural heritage linked data movement, concentrating on access (a fundamental objective), may have ignored some of reasons for establishing networks of knowledge in the first place.

The British Museum’s source of object data has its stronger and weaker elements but it has descriptions, associations and taxonomies developed over the last 30 years of digitisation. In order to exploit this accumulated knowledge and provide support for a wide range of users, including humanist scholars, it needs to be described within a rich semantic framework. This is a first step to developing the new taxonomies needed to allow different relationships and interpretations of harmonised collections to be exposed. Semantic data harmonisation is not just about linking database records together but is about exploring and discovering (inferring) new knowledge.

The full power of the CRM comes when there is a sufficient mass of conforming data providing a coverage of topics such that the density of information and events generates a resource from which the inference of knowledge can occur. Research tool-kits built around such a collaboration of data would uncover new facts that could never be discovered using traditional methodologies. In this respect it is an ontology tailor made for making intelligent sense of the mass of online cultural heritage data. Its adoption continues to grow but it has also reached a ‘chicken and egg’ stage needing the implementation of public applications to clearly demonstrate its unique properties and value to humanities research.

By bringing data together in a meaningful way rather than just treating it as a technical process or act of systems integration we can start to deconstruct the years of separation and institutional classifications designed to support narrower curatorial and administrative aims. Regardless of the resources available to research projects, this historical limitation, and the lack of any cost effective digital solution, has made the problem of asking a broader range of questions a difficult challenge. But to ask the broader questions that may lead to more interesting, valuable and sustainable web applications, requires appropriate semantic infrastructures. The CRM provides a starting point.

The publication of BM data in the CRM format comes from a concern that many Semantic Web / Linked Data implementations will not provide adequate support for a next generation of collaborative data centric humanities projects. They may not support the types of tools necessary for examining, modelling and discovering relationships between knowledge owned by different organisations at a level currently limited to more controlled and localized data-sets. Indeed, the proliferation of different uncoordinated linked data schemas may create a confusing and complex environment of mappings between data stores and thereby limit the overall effectiveness of semantic technology and produce outputs that don’t push digital publications much beyond those achieved using existing database technology.

The CRM is difficult not because of what it is (a distillation of existing and known cultural heritage concepts and relationships) but because it requires real cross disciplinary collaboration to implement properly – and this type of collaboration is difficult. The aim of the British Museum Endpoint is to deliver a technical interface but also to demystify the processes underlying the implementation of the CRM as well as the BM’s CRM mapping itself. By doing this the Endpoint should support a wide range of publication objectives for different audiences, a wide range developers with varying experience and domain knowledge and crucially fulfill the future needs of humanities scholars.

In particular the aim is to raise the bar on what can be achieved on the Internet and allow researchers to transfer data modelling techniques, that are currently only serviced by specialist relational database models, into the online world. These techniques will allow scholars, with access to CRM aligned datasets, to make sense of and tackle ‘big data’ littered with many different classifications and taxonomies and allow a broader, specialist and contextual re-examination of historical data and historical events.

Dominic Oldman