Data Access

• latest version by Vlado: svn https://svn.ontotext.com/svn/researchspace/data/: thesauri.ttl, susana.ttl
• syntax-colored version on web: susana.ttl, thesauri.ttl

Obsolete

The rest of this page is obsolete
The images give you some idea about the mapping, but are not precise

• draft versions by Mariana: https://svn.ontotext.com/svn/researchspace/data/mariana/
• RDF Workbench: http://researchspace.ontotext.com/openrdf-workbench/repositories/ResearchSpace/query
• Forest: http://researchspace.ontotext.com/forest-workbench-1.1/sparql
• deprecated http://192.168.130.198:8080/openrdf-workbench/repositories/ResearchSpace/query
• CLOSED- AVAILABLE ON DEMAND: SPARQL endpoint on Mariana's workstation: http://britishmuseum.ontotext.com/sparql.
  Blank nodes are seen as literals. Some URIs don't connect.
• CLOSED- AVAILABLE ON DEMAND: RDF Workbench on Mariana's workstation: http://192.168.129.184:8080/openrdf-workbench/repositories/ResearchSpace/query. One can inspect the blank nodes here. Maybe some URIs also don't connect.

Museum Object Components and Shape

The proposed model refers to the description of paintings described in the Entry of the painting Die Badende Susanna. This entry contains metadata about the properties of the painting as image, and about its frame. To cover this distinction, we introduce the concept MuseumObject which we define as a subClassOf crm:E22_Man-Made_Object, and represent the painting and the frame as part of this Museum object.

Production of Museum Object Parts

Depending on the type of object described, its author is associated with crm:E65_Creation or crm:E12_Production event. In our particular case, of a museum object consisting of a painting and a frame, the painting is linked to a Creation event, whereas the frame is linked to a Production event, which in term convey information about their authors, and the times of the events.

Title and Related Object

The Entry of the painting Die Badende Susanna contains information about a related art work created by a different painter. To capture this relation we introduce the property relatedObject. It is equivalent to the BMX extension property bmx:PX.is_related_to. The property relatedObject links two crm:E22_Man-Made_Object.

The title of the painting from the raw data is attached to the MuseumObject.

Museum Object Identifiers and Dimensions

The Entry of Die Badende Susanna has a unique database identifier, represented in the field priref. We model this identifier in the class crm:E42_Identifier and link it to the museum object with the property crm:P48_has_preferred_identifier. This is not the only identifier of Die Badende Susanna though. Additionally, we find a catalog number assigned to the painting in a given collection. The catalog number has also been modelled as crm:E42_Identifier, but linked to the museum object with the property crm:P1_is_identified_by.

Bibliographical Reference

To represent the bibliographical references about the museum object that are available in the data we make use of the Bibliography Ontology. The bibliographical reference is defined as crm:E31_Document, and the bibliographical characteristics of the document are represented with properties from the bibliography ontology. The author of the document is

Remarks on Museum Object - Attribute Assignment

There are many comments in the Entry of Die Badende Susanna that are attached to the Museum Object, but pertain to different entities characterizing it, such as dimension, dating, frame, support and technique, object title, commissioner, etc. They are modeled as attached to the entities they pertain to. For clarity of the notes, new properties, defined as sub properties of crm:P3_has_note are being introduced.

Image Elements

This section describes the elements of painting for which there are metadata in the Entry of Die Badende Susanna. The painting is one of the two parts of the museum object. It is represented as depicting (crm:P62_depicts) a visual item with type - the icon class it represents and as carrying (crm:P28_carries) an Inscription (crm:E34_Inscription). The inscription is further specified with its type, e.g. signature, and with the position of the signature. Note that a new class is being introduced for signature as a sub class of crm:E55_Type.

Museum Object in Collection

The Collection in this interpretation is a Physical Man-Made_Thing. The Museum object is represented as part of this collection with a series of events which describe its addition (crm:E79_Part_Addition) and its removal (crm:E80_Part_Removal). Its location (crm:P54_has_current_permanent_location, crm:P53_has_former_or_current_location) and owner (crm:P52_has_current_owner) are taken from the information about the collection in the Entry of Die Badende Susanna. The Collection on the other hand is represented as having an owner (crm:P52_has_current_owner). Additionally, its type as a private collection is also specified.

The following schema draws the relations of change of custody and acquisition of the Museum Object. It represents two situations, the one of transfering of the title from Napoleon museum to Rijksmuseum, via an event of crm:E8_Acquisition, and the transfer of Custody from Rijksmuseum to Mauritshuis, via an event of crm:E10_Transfer_of_Custody.

Museum Object in Exhibition

Museum Object in Auction

CIDOC-CRM Extentions

URI convention

• The namespaces for ResearchSpace models and data will be as follows:

The museum objects will be part of the rs: (<http://www.researchspace.org/resource/>) namespace, e.g. they will be assigned an rs: URI when acquired from an external database. If a museum object has already an URI, a owl:sameAs statement will be created.

• The museum object URI contains a string denoting the type of the object, and its preferred identifier. For the Rembrandt entry, the URI will be:

• The CRM concepts relating to the main museum objects or its characteristics will contain the URI of the node describing the main museum object or its characteristic, further specified with slash and abbreviation of the characteristic. For example, the node of the painting of Susanna Bathing, will have the uri:

• The node of the production of Susanna Bathing (linked with the property crm:P108_has_produced) will have the URI:

• The node of the time span of the production of Susanna Bathing (linked with the property crm:P4.has_time_span) will have the URI:

etc.

This will allow direct access to these nodes.

Some URIs will have to have sequential numbers automatically generated. For example, it is possible to have multiple attribute assignments for a single object. The URI of the attribute assignment for a given object will comply with the convention from the previous points, and will have additionally a randomly generated sequential number at the end. For example, the attribute assignment for the shape of Susanna Bathing will have the following URI:

The thesaurus URIs are conditional for the time being. They will be adjusted when we obtain the real data. Currently, the thesaurus namespace contains the type of the entities described in it, e.g.

/thesaurusperson
/thesaurusplace
/thesauruscollection

The names of the entities in the thesaurus are also conditional.