Listing 1
Codeblock representing different ways to assign a name to an artwork using CIDOC-CRM. Prefixes used are listed on prefix.cc.
Figure 1
Overview of basic documentation structure.
Figure 2
Relationship between reference entities, semantic reference data models and ontological scope. The analysis of a domain of discourse elicits a set of reference entities which reflect the documentation needs. Each reference entity is then described using one or more reference data models.
Table 1
Semantic Reference Data Model Metadata Specifications.
| ATTRIBUTE NAME | FIELD DESCRIPTION | EXAMPLE |
|---|---|---|
| Identifier | A unique, stable identifier to identify the field across usage contexts. | fie_92_Coordinates |
| System Name | A developer-friendly name for the field to be used in data modelling/mapping contexts. | wkt_coordinates |
| UI Name | A user-friendly name for the field to be used in user interface. Naming conventions may change to reflect intended interpretation of the field as employed within a specific reference model as distinct from another. | Coordinates |
| Description | A user friendly prose description of the intended use/function of the field. | This field is used to indicate the coordinates of the documented geographic place. |
| Ontological Scope | An ontological class that provides the maximal ontological scope for the field according to its defined function. Whenever the field is to be employed in a reference model, the ontological scope of the model must match or fall within the ontological scope of the field (i.e., the scope of the field must be equal to or wider than the reference entity captured in the reference model). | crm:E53_Place |
| Semantic Path | Edge and node representation of a defined semantic path syntax representing the meaning of the field in the target ontology. Uses a more readily human-readable notation form for class and property abbreviations. | E53 → P168 → geosparql:wkt |
| RDF Encoding | An RDF representation of the Semantic Path using Turtle Syntax. | <https://ex.org/place/fie_75_1> a crm:E53_Place; crm:P168_place_is_defined_by“”^^geosparql:wkt. |
| Expected Value Type | The kind of data value the field expects (e.g.: string, integer, date, concept, collection, reference model, URI) | Well-known text (WKT) |
Figure 3
The process of creation of the Semantic Reference Data Models follows a series of iterative steps, shared by domain experts and knowledge engineers, to determine the relevant reference entities. Following this process, each entity is collaboratively examined to identify and determine the more comprehensive and reusable ontological patterns for describing it.
Table 2
Data Sources and Access Points. Source: https://docs.swissartresearch.net/et/persons/.
| ACRONYM | SOURCE NAME | MAINTAINED BY |
|---|---|---|
| Agrelon | Agrelon, an Agent Relationship Ontology | Deutsche Nationalbibliothek |
| SIKART | Dictionary of Art in Switzerland | SIK-ISEA |
| MARC 21 | Marc 21 – Bibliography Heading Fields | Library of Congress |
| VIAF | Virtual International Authority File | OCLC |
| ULAN | Union List of Artist Names | Getty |
| Schema.org | Schema.org | Schema.org |
| CDWA | Categories for the Description of Works of Art | Getty |
| CCO | Cataloging Cultural Objects | CCO Commons |
| VRA Core | Visual Resources Association core categories | Visual Resources Association |
Figure 4
Interconnection between fields and SRDMs. A field (example: artwork_90_material) can be interlinked with multiple SRDMs or with only one (Pattern artwork_91_technique).
Figure 5
Example of the cluster of properties grouped under the category ’Existence’ within the SRDM of a Person.
Listing 2
Turtle representation of the semantic paths used for the documentation of a birthplace and birthdate. Prefixes used are listed on prefix.cc.