Aller au contenu principal

xDX Application Profile

Note

This application profile is under construction and may not fully reflect the current dataset. The pattern examples and Turtle data samples are subject to change.

Purpose

The purpose of this application profile is to document how xDX Project data is modelled for compatibility with the wider LINCS data model. This document provides patterns used in the mapping of xDX data which correspond to the categories of the main LINCS Application Profiles.

This document introduces classes and properties as used in this specific context (LINCS and the xDX dataset), without providing complete definitions for them. You can find the full definitions in the documentation of CIDOC CRM version 7.3.1 and other reference ontologies.

Dependencies

This section reports the ontologies, vocabularies, and authority files adopted in the xDX application profile. The tables below list the acronyms used to refer to each resource and the prefixes used to compose the URIs in Turtle code examples found in the document.

Ontologies

For more information about ontologies, see Linked Open Data Basics – Ontologies.

AcronymPrefixOntologyPurpose
CIDOC-CRMcrm:CIDOC Conceptual Reference ModelMain reference ontology
CRMdigcrmdig:CRM DigitalTo represent digital objects

Vocabularies

For more information about vocabularies, see Linked Open Data Basics – Vocabularies.

AcronymPrefixVocabulary or AuthorityPurpose
AATaat:Getty AATTo represent object types, note types, material types, technique types, and dimension types.
Biographybiography:LINCS BiographyTo represent name types.
Lexvolexvo:LexvoTo represent languages.
XSDxsd:XML Schema DatatypesFor literal datatypes.

Authority Files

For more information about authority files, see Terms – Authority File.

AcronymPrefixAuthority FilePurpose
GeoNamesgeonames:GeoNamesFor place URIs.
LINCSlincs:LINCS-minted entitiesTo represent any entities not described elsewhere.
LOCloc:Library of CongressFor people and group URIs.
ULANulan:Getty Union List of Artist NamesFor people and group URIs.
VIAFviaf:Virtual International Authority FileFor people and group URIs.
Wikidatawikidata:Wikidata Knowledge BaseFor people and group URIs.

Main Classes

The classes listed below are imported from CIDOC CRM and use prefix crm: except where otherwise noted.

Entity TypeClassDeclaration Snippet (Turtle Syntax)
xDX ObjectE22 Human-Made Object
<object> a crm:E22_Human-Made_Object ;
crm:P2_has_type <object_type> .
OwnerE39 Actor
<owner> a crm:E39_Actor .
Production CompanyE74 Group
<owner> a crm:E74_Group .
ProductionE12 Production
<production> a crm:E12_Production .
AcquisitionE8 Acquisition
<acquisition> a crm:E8_Acquisition .
MaterialE57 Material
<material> a crm:E57_Material ;
crm:P2_has_type <material_type> .
DimensionE54 Dimension
<dimension> a crm:E54_Dimension ;
crm:P2_has_type <dimension_type> .
DesignE29_Design_or_Procedure
<design> a crm:E29_Design_or_Procedure .
CreationE65 Creation
<creation> a crm:E65_Creation .
IP RightE30 Right
<ip_right> a crm:E30_Right ;
crm:P2_has_type <ip_right_type> .
PlaceE53 Place
<place> a crm:E53_Place .
DesignerE21 Person
<designer> a crm:E21_Person .
Design FirmE74 Group
<design_firm> a crm:E74_Group .
ModelE99 Product Type
<conceptual_object_model> a crm:E99_Product_Type .
SeriesE99 Product Type
<conceptual_object_series> a crm:E99_Product_Type .
BrandE99 Product Type
<brand> a crm:E99_Product_Type .
ClassificationE99 Product Type
<classification> a crm:E99_Product_Type .
Archival FileE73 Information Object
<archival_file> a crm:E73_Information_Object ;
crm:P2_has_type <archival_file_type> .
Name or TitleE33_E41 Linguistic Appellation
<name_or_title> a crm:E33_E41_Linguistic_Appellation ;
crm:P2_has_type <name_or_title_type> .
IdentifierE42 Identifier
<identifier> a crm:E42_Identifier ;
crm:P2_has_type <identifier_type> .
NoteE33 Linguistic Object
<note> a crm:E33_Linguistic_Object ;
crm:P2_has_type <note_type> .
Actor in a RolePC14 Actor in a Role
<actor_in_role> a crm:PC14_Actor_in_a_Role ;
crm:P01_has_domain <actor> ;
crm:P02_has_range <role> .
WebpageD1 Digital Object (CRMdig)
<webpage> a crmdig:D1_Digital_Object .

Overview

The xDX dataset reconstitutes the former Design Exchange (DX) collection, documenting the unique history of design in Canada. The dataset describes the design objects along with their creators, producers, and owners.

The image below shows an overview of the entire xDX application profile. Each section of the diagram is described in detail in one of the sections of this document. Click here or on the image for a large-scale, more readable version.

Application profile

Graph Patterns

This section presents the graph patterns adopted in the xDX application profile, along with examples of usage. The URI of the xDX graph which can be used to query the dataset through the SPARQL endpoint is <http://graph.lincsproject.ca/xdx>.

Basic Patterns

This section describes basic patterns that are reused across the xDX dataset.

Type

Diagram
Application profile
PatternDefinitionAn entity has a type.
AbstractionE1 CRM Entity
P2 has type
E55 Type
Applies to
ValuesType of ValueUniform Resource Identifier (URI).
Expected ValueURI from vocabulary or minted by LINCS.
Authorities
ExamplesTypical ExampleThe xDX object with ID 2018.308.10.2 a-b has type aat:300037776 (armchairs).
Example Abstraction<http://temp.lincsproject.ca/xdx/object/2018.308.100> →
P2 has type
aat:300037776
Generalized Pattern (Turtle)
<entity> a crm:E1_CRM_Entity ;  
rdfs:label "<entity>" ;
crm:P2_has_type <type> .

<type> a crm:E55_Type ;
rdfs:label "<type>"@en .
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/object/2018.308.100>
a crm:E22_Human-Made_Object ;
rdfs:label "armchair"@en ;
crm:P2_has_type aat:300037776 .

aat:300037776 a crm:E55_Type ;
rdfs:label "armchairs"@en .
NoteClass E1 CRM Entity represents all entities, but is not actually found in the dataset. More specific classes are applied instead (see Main Classes above).

Identifier

Diagram
Application profile
PatternDefinitionAn entity is identified by an ID.
AbstractionE1 CRM Entity
P1 is identified by
E42 Identifier
P190 has symbolic content
xsd:string
Applies to
ValuesType of Valuexsd:string  (a string of text).
Expected ValueAn string of text that uniquely identifies the entity.
Authorities
  • AAT and LINCS for the identifier type. All xDX IDs and archival file IDs have type aat:300404012 (unique identifiers). All accession identifiers have type aat:300312355 (accession numbers). All identifiers also have a specific LINCS-minted type.
  • XSD for the datatype of the identifier value.
ExamplesTypical ExampleThe xDX object Talking table has xDX ID 2024.YU.xDX.00065 and accession ID 997.16.
Example Abstraction<http://temp.lincsproject.ca/xdx/object/2024.YU.xDX.00065>
P1 is identified by
<http://temp.lincsproject.ca/xdx/xdx_identifier_of_object/2024.YU.xDX.00065>
P190 has symbolic content
"2024.YU.xDX.00065"^^xsd:string
Generalized Pattern (Turtle)
<entity> a crm:E1_CRM_Entity ;  
rdfs:label "<entity>" ;
crm:P1_is_identified_by <identifier> .

<identifier> a crm:E42_identifier ;
rdfs:label "Identifier of entity <entity>"@en ;
crm:P2_has_type <identifier_type> ;
crm:P190_has_symbolic_content "<value>" .
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/object/2024.YU.xDX.00065> a crm:E22_Human-Made_Object ;
rdfs:label "Talking table"@en ;
crm:P1_is_identified_by <http://temp.lincsproject.ca/xdx/accession_identifier/997.16> ,
<http://temp.lincsproject.ca/xdx/xdx_identifier_of_object/2024.YU.xDX.00065> .

<http://temp.lincsproject.ca/xdx/accession_identifier/997.16> a crm:E42_identifier ;
rdfs:label "Accession identifier of Talking table"@en ;
crm:P190_has_symbolic_content "997.16" ;
crm:P2_has_type <http://temp.lincsproject.ca/xdx/type/dx_accession>, aat:300312355 .

<http://temp.lincsproject.ca/xdx/accession_identifier/997.16> a crm:E42_identifier ;
rdfs:label "xDX identifier of Talking table"@en ;
crm:P190_has_symbolic_content "2024.YU.xDX.00065" ;
crm:P2_has_type <http://temp.lincsproject.ca/xdx/type/xdx_id>, aat:300404012 .
NoteClass E1 CRM Entity represents all entities, but is not actually found in the dataset. More specific classes are applied instead (see Main Classes above).

Name & Title

Diagram
Application profile
PatternDefinitionAn entity is identified by an appellation (name or title).
AbstractionE1 CRM Entity
P1 is identified by
E33 E41 Linguistic Appellation
P190 has symbolic contentxsd:string
Applies to
  • xDX Object. Every object has one preferred name and may have one or more alternative names.
  • Archival File. Every archival file has exactly one title.
  • Designer. Every designer has one or more names.
  • Design Firm. Every firm has one or more names.
  • Owner. Every owner has one or more names.
  • Production Company. Every company has one or more names.
ValuesType of Valuexsd:string  (a string of text).
Expected ValueA string of text that identifies the entity.
Authorities
  • AAT for archival file titles. All titles have type aat:300417193 (titles [general, names]).
  • Biography for the type of person names and company names.
  • Lexvo for the language of the name or title.
  • XSD for the datatype of the name value.
ExamplesTypical ExampleThe object with xDX ID 2024.YU.xDX.00063 is named Roo Chair (in English).
Example Abstraction<http://temp.lincsproject.ca/xdx/object/2024.YU.xDX.00063> →
P1 is identified by →
<http://temp.lincsproject.ca/xdx/preferred_name_of_object/2024.YU.xDX.00063> →
P190 has symbolic content → "Roo Chair"@en
Generalized Pattern (Turtle)
<entity> a crm:E1_CRM_Entity ;  
rdfs:label "<entity>" ;
crm:P1_is_identified_by <name_or_title> .

<name_or_title> a crm:E33_E41_Linguistic_Appellation ;
rdfs:label "English title of the entity <name_or_title>"@en ;
crm:P2_has_type <type> ;
crm:P190_has_symbolic_content "<name_or_title>" .
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/object/2024.YU.xDX.00063> a crm:E22_Human-Made_Object ;
rdfs:label "Roo Chair"@en ;
crm:P1_is_identified_by <http://temp.lincsproject.ca/xdx/preferred_name_of_object/2024.YU.xDX.00063> .

<http://temp.lincsproject.ca/xdx/preferred_name_of_object/2024.YU.xDX.00063>
rdfs:label "Preferred name of Roo Chair"@en ;
crm:P190_has_symbolic_content "Roo Chair"@en ;
crm:P2_has_type aat:300417193 ;
crm:P72_has_language <http://lexvo.org/id/term/eng> .
NoteClass E1 CRM Entity represents all entities, but is not actually found in the dataset. More specific classes are applied instead (see Main Classes above).

Location

Diagram
Application profile
PatternDefinitionAn event happens at a location.
AbstractionE1 CRM Entity
P7 took place at
E53 Place
Applies toActivity (including Production and Creation). Every activity happens at exactly one location.
ValuesType of ValueA URI uniquely identifying the location (Place).
Expected ValueUniform Resource Identifier (URI).
AuthoritiesGeoNames for the place URI.
ExamplesTypical ExampleThe production of Swivel Chair took place in Toronto, Canada.
Example AbstractionE12 Production
P7 took place at
E53 Place
Generalized Pattern (Turtle)
<activity> a crm:E7_Activity ;
rdfs:label "<activity>" ;
crm:P7_took_place_at <place> .

<place> a crm:E53_Place ;
rdfs:label "<place>" .
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/production_of_object/2018.308.156> a crm:E12_Production ;
rdfs:label "Production of Swivel Chair"@en ;
crm:P7_took_place_at geonames:6167865 .

geonames:6167865 a crm:E53_Place ;
rdfs:label "Toronto, Canada"@en .

Date

Diagram
Application profile
PatternDefinitionAn event happens on a certain date (or date range).
AbstractionE1 CRM Entity
P4 has time-span
E52 Time-Span
P82 at some point withinxsd:string
P82a begin of the beginxsd:dateTime
P82b end of the endxsd:dateTime
Applies toActivity (including Production and Creation). Every activity happens on a certain date (or date range).
ValuesType of Valuexsd:string for the human-readable date.
xsd:dateTime for the date's begin of begin.
xsd:dateTime for the date's end of end.
Expected ValueA string of text expressing the date (or date range) of the event.
A datetime value expressing the earliest possible beginning time.
A datetime value expressing the latest possible end time.
AuthoritiesXSD for the datatypes of date values.
ExamplesTypical ExampleThe production of Swivel Chair took place in 1967.
Example AbstractionE12 Production
P4 has time-span
E52 Time-Span
P82 at some point withinxsd:string
P82a begin of the beginxsd:dateTime
P82b end of the endxsd:dateTime
Generalized Pattern (Turtle)
<activity> a crm:E7_Activity ;
rdfs:label "<activity>"@en ;
crm:P4_has_time-span <time_span> .

<time_span> a crm:E52_Time-Span ;
rdfs:label "<time_span>"@en ;
crm:P82_at_some_time_within "<date>"@en ;
crm:P82a_begin_of_the_begin "<begin_date>"^^xsd:dateTime ;
crm:P82b_end_of_the_end "<end_date>"^^xsd:dateTime .
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/production_of_object/2018.308.156> a crm:E12_Production ;
rdfs:label "Production of Swivel Chair"@en ;
crm:P4_has_time-span <http://temp.lincsproject.ca/xdx/time_span_of_production_of_object/2018.308.156> .

<http://temp.lincsproject.ca/xdx/time_span_of_production_of_object/2018.308.156> a crm:E52_Time-Span ;
rdfs:label "Time span of production of Swivel Chair"@en ;
crm:P82_at_some_time_within "1967"@en ;
crm:P82a_begin_of_the_begin "1967-01-01T00:00:00"^^xsd:dateTime ;
crm:P82b_end_of_the_end "1967-12-31T23:59:59"^^xsd:dateTime .

Actor in a Role

Diagram
Application profile
PatternDefinitionAn activity may have a number of participants, each with a certain role.
AbstractionE7 Activity
P01i is domain of
PC14 Carried Out By
P02 has range
E39 Actor


PC14 Carried Out By
P14.1 in the role of
E55 Type
Applies toActivity (including Production and Creation). Every activity may have one or more participants, each with a certain role.
ValuesType of ValueUniform Resource Identifier (URI)
Expected ValueURI from authority file or minted by LINCS (activity).
URI from authority file or minted by LINCS (actor).
URI from vocabulary or minted by LINCS (role).
URI minted by LINCS (actor with role).
AuthoritiesLINCS for the URI of the activity.
Virtual International Authority File, Wikidata, or LINCS for the URI of the actor.
Wikidata for the URI of the role.
LINCS for the URI of the actor with role.
Example Values<http://temp.lincsproject.ca/xdx/production_of_object/2018.308.81> (Production of radio)
<http://temp.lincsproject.ca/addison_industries> (Addison Industries)
<http://id.loc.gov/vocabulary/relators/mfr> (manufacturer)
<http://temp.lincsproject.ca/xdx/producer_role_of/Addison%20Industries/2018.308.81> (Addison Industries in the role of manufacturer producing radio)
ExamplesTypical ExampleAddison Industries produced the radio with xDX ID 2018.308.81 in the role of manufacturer.
Example Abstraction<http://temp.lincsproject.ca/xdx/production_of_object/2018.308.81>
P01i is domain of
PC14 Carried Out By
P02 has range
<http://temp.lincsproject.ca/addison_industries>


PC14 Carried Out By
P14.1 in the role of
<http://id.loc.gov/vocabulary/relators/mfr>
Generalized Pattern (Turtle)
<activity> a crm:E7_Activity ;
rdfs:label "<activity>"@en ;
crm:P01i_is_domain_of <actor_in_role> .

<actor_in_role> a crm:PC14_carried_out_by ;
rdfs:label "<actor_in_role>"@en ;
crm:P02_has_range <actor> ;
crm:P14.1_in_the_role_of <role> .
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/production_of_object/2018.308.81> a crm:E12_Production ;
rdfs:label "Production of radio"@en ;
crm:P01i_is_domain_of <http://temp.lincsproject.ca/xdx/producer_role_of/Addison%20Industries/2018.308.81> .

<http://temp.lincsproject.ca/xdx/producer_role_of/Addison%20Industries/2018.308.81> a crm:PC14_carried_out_by ;
rdfs:label "Addison Industries in the role of manufacturer producing radio"@en ;
crm:P02_has_range <http://temp.lincsproject.ca/addison_industries> ;
crm:P14.1_in_the_role_of <http://id.loc.gov/vocabulary/relators/mfr> .

xDX Object

An xDX object is a human-made object designed by one or more designers and produced by a company. The dataset represents basic information about the object, including its material(s), dimensions, and acquisition history. The dataset also describes the object's model, brand, and classification.

xDX objects were originally part of the Design Exchange (DX) collection and are currently held by public institutions including the Royal Ontario Museum, the Canadian Museum of History, the Archives of Ontario, Carleton University, and York University.

Production

xDX objects were produced between 1940 and 2010 by Canadian and international production companies.

Diagram
Application profile
PatternDefinitionA production has a number of participants, each with a certain role.
AbstractionE22 Human-Made Object
P108i_was_produced_by
E12 Production
Applies toxDX Object. Every object has exactly one production.
ValuesType of ValueUniform Resource Identifier (URI).
Expected ValueA URI that identifies the production event.
AuthoritiesLINCS for the URI of the production event.
Example Values<http://temp.lincsproject.ca/xdx/production_of_object/2018.308.156> (Production of Swivel Chair)
ExamplesTypical ExampleThe xDX object with ID 2018.308.156 (Swivel Chair) was produced by production event <http://temp.lincsproject.ca/xdx/production_of_object/2018.308.156>
Example Abstraction<http://temp.lincsproject.ca/xdx/object/2018.308.156>
P108i_was_produced_by
<http://temp.lincsproject.ca/xdx/production_of_object/2018.308.156>
Generalized Pattern (Turtle)
<object> a crm:E22_Human-Made_Object ;
rdfs:label "<object>"@en ;
crm:P108i_was_produced_by <production> .

<production> a crm:E12_Production ;
rdfs:label "<production>"@en .
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/object/2018.308.156> a crm:E22_Human-Made_Object ;
rdfs:label "Swivel Chair"@en ;
crm:P108i_was_produced_by <http://temp.lincsproject.ca/xdx/production_of_object/2018.308.156> .

<http://temp.lincsproject.ca/xdx/production_of_object/2018.308.156> a crm:E12_Production ;
rdfs:label "Production of Swivel Chair"@en .

Design

xDX objects were designed by designers who could be employed by firms or work independently. For the modelling of individual designers, see the Designer section below. For the modelling of firms, see the Design Firm section.

Diagram
Application profile
PatternDefinitionA design is about an object.
AbstractionE29 Design or Procedure
P129 is about
E22 Human-Made Object
Applies toxDX Object. Every object has exactly one design.
ValuesType of ValueUniform Resource Identifier (URI)
Expected ValueA URI that identifies the design.
AuthoritiesLINCS for the URI of the design.
Example Values

<http://temp.lincsproject.ca/xdx/design_of_object/2019.CU.DX.00060>

ExamplesTypical ExampleThe design of Umbra Ah chair is about xDX object Umbra Ah chair.
Example Abstraction<http://temp.lincsproject.ca/xdx/design_of_object/2019.CU.DX.00060> →
P129 is about
<http://temp.lincsproject.ca/xdx/object/2019.CU.DX.00060>
Generalized Pattern (Turtle)
<design> a crm:E29_Design_or_Procedure ;
rdfs:label "<design>"@en ;
crm:P129_is_about <object> .
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/design_of_object/2019.CU.DX.00060> a crm:E29_Design_or_Procedure ;
rdfs:label "Design of Umbra Ah Chair"@en ;
crm:P129_is_about <http://temp.lincsproject.ca/xdx/object/2019.CU.DX.00060> .

Acquisition

xDX objects may have been acquired by one or more owners (people or groups) over the years. For the modelling of individual owners, see the Owner section below.

Diagram
Application profile
NoteThe modelling of object acquisitions is described in detail in the Acquisition section below.

Material

Diagram
Application profile
PatternDefinitionAn object is made of a certain material.
AbstractionE22 Human-Made Object
P45 consists of
E57 Material
Applies toxDX Object. Every object consists of one or more materials.
ValuesType of ValueUniform Resource Identifier (URI)
Expected ValueA URI that identifies the material.
AuthoritiesAAT or LINCS for the URI of the material.
Example Valuesaat:300010900 (metal)
ExamplesTypical ExampleThe MS-SC Stacking Chair is made of metal.
Example Abstraction<http://temp.lincsproject.ca/xdx/object/2020.24.20>
P45 consists of
aat:300010900
Generalized Pattern (Turtle)
<object> a crm:E22_Human-Made_Object ;
rdfs:label "<object>"@en ;
crm:P45_consists_of <material> .
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/object/2020.24.20> a crm:E22_Human-Made_Object ;
rdfs:label "MS-SC Stacking Chair"@en ;
crm:P45_consists_of aat:300010900 .

Dimension

Diagram
Application profile
PatternDefinitionAn object has certain dimensions.
AbstractionE22 Human-Made Object
P43 has dimension
E54 Dimension
   P2 has typeE55 Type
   P91 has unitE55 Type
   P90 has valuexsd:decimal
Applies toxDX Object. Each object may have one or more recorded dimensions.
ValuesType of ValueUniform Resource Identifier (URI) for the dimension, type, and unit.
Literal for the dimension value.
Expected ValueA URI that identifies the dimension.
A URI that identifies the dimension type.
A URI that identifies the dimension unit.
A literal that expresses the dimension value.
AuthoritiesLINCS for the URI of the dimension.
LINCS for the dimension type.
AAT for the dimension unit.
XSD for the dimension value.
Example Values<http://temp.lincsproject.ca/xdx/dimension_of_object/2020.24.21/depth> (dimension).
<http://temp.lincsproject.ca/depth> (dimension type).
aat:300379098 (dimension unit).
50.4 (dimension value).
ExamplesTypical ExampleThe Roo Stacking Chair has a recorded width of 52.1 cm and a recorded depth of 50.4 cm.
Example Abstractionhttp://temp.lincsproject.ca/xdx/object/2020.24.21 →
P43 has dimension
<http://temp.lincsproject.ca/xdx/dimension_of_object/2020.24.21/depth>
   P2 has type<http://temp.lincsproject.ca/depth>
   P91 has unitaat:300379098
   P90 has value50.4
Generalized Pattern (Turtle)
<object> a crm:E22_Human-Made_Object ;
rdfs:label "<object>"@en ;
crm:P43_has_dimension <dimension> .

<dimension> a crm:E54_Dimension ;
rdfs:label "<dimension>"@en ;
crm:P2_has_type <dimension_type> ;
crm:P90_has_value "<value>"^^xsd:decimal ;
crm:P91_has_unit <dimension_unit> .
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/object/2020.24.21> a crm:E22_Human-Made_Object ;
rdfs:label "Roo Stacking Chair"@en ;
crm:P43_has_dimension <http://temp.lincsproject.ca/xdx/dimension_of_object/2020.24.21/depth>,
<http://temp.lincsproject.ca/xdx/dimension_of_object/2020.24.21/width> .

<http://temp.lincsproject.ca/xdx/dimension_of_object/2020.24.21/depth> a crm:E54_Dimension ;
rdfs:label "depth of 2020.24.21"@en ;
crm:P2_has_type <http://temp.lincsproject.ca/depth> ;
crm:P90_has_value 50.4 ;
crm:P91_has_unit aat:300379098 .

<http://temp.lincsproject.ca/xdx/dimension_of_object/2020.24.21/width> a crm:E54_Dimension ;
rdfs:label "width of 2020.24.21"@en ;
crm:P2_has_type <http://temp.lincsproject.ca/width> ;
crm:P90_has_value 52.1 ;
crm:P91_has_unit aat:300379098 .

Identifier

Each object has exactly one xDX identifier and one accession identifier.

Diagram
Application profile
NoteThe modelling of xDX object identifiers follows the basic pattern for Identifiers. See the corresponding section for more information.

Name

Each object has exactly one preferred name and may have one or more alternative names.

Diagram
Application profile
NoteThe modelling of xDX object names follows the basic pattern for Names & Titles. See the corresponding section for more information.

Work Type

Each object has a specific work type, such as chair or kettle.

Diagram
Application profile
NoteThe modelling of object classifications follows the basic pattern for Types. See also the Conceptual Layer section for more information.

Classification

Each object may have a general classification, such as furniture.

Diagram
Application profile
NoteThe modelling of object classifications follows the basic pattern for Types. See also the Conceptual Layer section for more information.

Model

Each object may have a specific model, such as MS-SC Stacking Chair or Umbra Ah Chair.

Diagram
Application profile
NoteThe modelling of xDX object models follows the basic pattern for Types. See also the Conceptual Layer section for more information.

Series

Each object may have a specific series, intended as a grouping of models, such as Clairtone G Series.

Diagram
Application profile
NoteThe modelling of xDX object models follows the basic pattern for Types. See also the Conceptual Layer section for more information.

Brand

Each object may have a specific brand, such as General Electric.

Diagram
Application profile
NoteThe modelling of xDX object brands follows the basic pattern for Types. See the Conceptual Layer section section for more information.

Prototype

An object may be assigned a special type to indicate that it is a prototype. A prototype is a unique object that serves as a model for other objects of the same type.

Diagram
Application profile
NoteThe modelling of prototypes follows the basic pattern for Types. See the corresponding section for more information.

Object Set

Each object may part of an object set. A set is always composed of multiple objects, while each object may be part of at most one set.

Diagram
Application profile
PatternDefinitionAn object may be part of an object set.
AbstractionE22 Human-Made Object
P46i forms part of
E22 Human-Made Object
Applies toxDX Object. Each object may be part of at most one set.
ValuesType of ValueUniform Resource Identifier (URI).
Expected ValueA URI that uniquely identifies the object set.
AuthoritiesLINCS for the URI of the object set.
Example Value<http://temp.lincsproject.ca/xdx/object/2020.24.12.1-2> (Habitat Chair and Ottoman).
ExamplesTypical ExampleThe objects Habitat Chair and Habitat Ottoman are part of the object set Habitat Chair and Ottoman.
Example Abstraction<http://temp.lincsproject.ca/xdx/object/2020.24.12.1> →
P46i forms part of
<http://temp.lincsproject.ca/xdx/object/2020.24.12.1-2>

<http://temp.lincsproject.ca/xdx/object/2020.24.12.2> →
P46i forms part of
<http://temp.lincsproject.ca/xdx/object/2020.24.12.1-2>
Generalized Pattern (Turtle)
<object_1> a crm:E22_Human-Made_Object;  
rdfs:label "<object_1>" ;
crm:P46i_forms_part_of <object_set> .

<object_2> a crm:E22_Human-Made_Object;
rdfs:label "<object_2>" ;
crm:P46i_forms_part_of <object_set> .

<object_set> a crm:E22_Human-Made_Object;
rdfs:label "<object_set>" .
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/object/2020.24.12.1> a crm:E22_Human-Made_Object;  
rdfs:label "Habitat Chair"@en ;
crm:P46i_forms_part_of <object_set> .

<http://temp.lincsproject.ca/xdx/object/2020.24.12.2> a crm:E22_Human-Made_Object;
rdfs:label "Habitat Ottoman"@en ;
crm:P46i_forms_part_of <object_set> .

<http://temp.lincsproject.ca/xdx/object/2020.24.12.1-2> a crm:E22_Human-Made_Object;
rdfs:label "Habitat Chair and Ottoman"@en .

Image

An object may have one or more images associated with it.

Diagram
Application profile
PatternDefinitionAn object is represented by an image.
AbstractionE22 Human-Made Object (CRMdig)
P138i has representation
E36 Visual Item
ValuesType of ValueUniform Resource Identifier (URI).
Expected ValueA URI representing an image.
AuthoritiesLINCS for the URI of the image.
Example Value
ExamplesTypical ExampleThe armchair with xDX ID 2018.308.100 is represented by the image with URI https://www.historymuseum.ca/ke/_resources/5740244/IMG2021-0040-0007-Dm-cmhsize-large.jpg.
Example Abstraction<https://collections.ssac.carleton.ca/index.php/Detail/objects/2870>
P138i has representation

Production

A production is an event through which an xDX object is produced. The dataset represents basic information about the production, including the production company, technique, date, and location. Each xDX object has exactly one production event, but each production event may have produced multiple xDX objects.

Company

Diagram
Application profile
NoteThe modelling of production companies follows the basic pattern for Actors in a Role. See the corresponding section for more information.

Technique

Diagram
Application profile
PatternDefinitionA production may employ a technique.
AbstractionE12 Production
P32 used general technique
E55 Type
Applies toProduction. Each production may employ one or more techniques.
ValuesType of ValueUniform Resource Identifier (URI).
Expected ValueA URI that uniquely identifies the technique.
AuthoritiesAAT or LINCS for the URI of the technique.
Example Valueaat:300053796 (lacquering).
ExamplesTypical ExampleThe production of the object with xDX ID 2018.308.129 (a lampshade) used technique aat:300053796 (lacquering).
Example Abstraction<http://temp.lincsproject.ca/xdx/production_of_object/2018.308.129> →
P32 used general technique
aat:300053796
Generalized Pattern (Turtle)
<production> a crm:E12_Production ;  
rdfs:label "<production>" ;
crm:P32_used_general_technique <technique> .
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/production_of_object/2018.308.129> a crm:E12_Production ;  
rdfs:label "Production of lampshade"@en ;
crm:P32_used_general_technique aat:300053796 .

Design

Diagram
Application profile
PatternDefinitionA production may employ a specific design.
AbstractionE12 Production
P33 used specific technique
E29 Design or Procedure
Applies toProduction. Each production employs exactly one design.
ValuesType of ValueUniform Resource Identifier (URI).
Expected ValueA URI that uniquely identifies the design.
AuthoritiesLINCS for the URI of the design.
Example Value<http://temp.lincsproject.ca/xdx/design_of_object/2024.YU.xDX.00102> (design of Boogie Board)
ExamplesTypical ExampleThe production of the object with xDX ID 2024.YU.xDX.00102 (Boogie Board) employed design Design of Boogie Board.
Example Abstraction<http://temp.lincsproject.ca/xdx/production_of_object/2024.YU.xDX.00102> →
P33 used specific technique
<http://temp.lincsproject.ca/xdx/design_of_object/2024.YU.xDX.00102>
Generalized Pattern (Turtle)
<production> a crm:E12_Production ;  
rdfs:label "<production>"@en ;
crm:P33_used_specific_technique <design> .
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/production_of_object/2024.YU.xDX.00102> a crm:E12_Production ;  
rdfs:label "Production of Boogie Board"@en ;
crm:P33_used_specific_technique <http://temp.lincsproject.ca/xdx/design_of_object/2024.YU.xDX.00102> .

Location

Diagram
Application profile
NoteThe modelling of production locations follows the basic pattern for Locations. See the corresponding section for more information.

Date

Diagram
Application profile
NoteThe modelling of production dates follows the basic pattern for Dates. See the corresponding section for more information.

Type

Diagram
Application profile
NoteThe production type follows the basic pattern for Types. See the corresponding section for more information.

Design

A design is a plan for the production of an xDX object. The dataset represents basic information about the design, including the designer, date, and location. Each xDX object has exactly one design, but each design is usually employed for producing multiple xDX objects. However, in the case of prototypes, the design may have led to the production of a single object.

Creation

A design is created by a designer at a certain date and location. The designer may or may not belong to a design firm.

Diagram
Application profile
PatternDefinitionA design is created through a creation event.
AbstractionE65 Creation
P94 has created
E29 Design or Procedure
Applies toDesign. Every design is created through exactly one creation event.
ValuesType of ValueUniform Resource Identifier (URI).
Expected ValueA URI that uniquely identifies the creation event.
AuthoritiesLINCS for the URI of the creation event.
Example Values<http://temp.lincsproject.ca/xdx/creation_of_design_of_object/2018.308.100>
ExamplesTypical ExampleThe design of object 2018.308.100 (armchair) was created through the event Creation of design of armchair.
Example AbstractionE65 Creation
P94 has created
E29 Design or Procedure
Generalized Pattern (Turtle)
<design> a crm:E29_Design_or_Procedure ;
rdfs:label "<design>"@en ;
crm:P94i_was_created_by <creation> .

<creation> a crm:E65_Creation ;
rdfs:label "<creation>"@en ;
crm:P01i_is_domain_of <actor_in_role> ;
crm:P7_took_place_at <place> .
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/design_of_object/2018.308.100> a crm:E29_Design_or_Procedure ;
rdfs:label "Design of armchair"@en ;
crm:P94i_was_created_by <http://temp.lincsproject.ca/xdx/creation_of_design_of_object/2018.308.100> .

<http://temp.lincsproject.ca/xdx/creation_of_design_of_object/2018.308.100> a crm:E65_Creation ;
rdfs:label "Creation of design of armchair"@en ;
crm:P01i_is_domain_of <http://temp.lincsproject.ca/xdx/designer_role_of/Russell%20Spanner/2018.308.100> ;
crm:P7_took_place_at geonames:6167865 .

IP Right

A design may be subject to intellectual property rights, such as copyright or design patents.

Diagram
Application profile
PatternDefinitionA design is subject to a certain intellectual property right.
AbstractionE29 Design or Procedure
P104 is subject to
E30 Right
Applies toDesign. Each design may be subject to one or more intellectual property rights.
ValuesType of ValueUniform Resource Identifier (URI).
Expected ValueA URI that uniquely identifies the intellectual property right.
AuthoritiesLINCS for the URI of the intellectual property right.
Example Values<http://temp.lincsproject.ca/xdx/ip_right_of_design_of_object/2018.308.109>
ExamplesTypical ExampleThe design of object 2018.308.109 (snowboard helmet) is subject to right IP right of design of snowboard helmet.
Example Abstraction<http://temp.lincsproject.ca/xdx/design_of_object/2018.308.109> →
P104 is subject to
<http://temp.lincsproject.ca/xdx/ip_right_of_design_of_object/2018.308.109>
Generalized Pattern (Turtle)
<design> a crm:E29_Design_or_Procedure ;
rdfs:label "<design>"@en ;
crm:P104_is_subject_to <right> ;

<right> a crm:E30_Right ;
rdfs:label "<right>"@en ;
crm:P75i_is_possessed_by <design_firm> .
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/design_of_object/2018.308.109> a crm:E29_Design_or_Procedure ;
rdfs:label "Design of snowboard helmet"@en ;
crm:P104_is_subject_to <http://temp.lincsproject.ca/xdx/ip_right_of_design_of_object/2018.308.109> ;

<http://temp.lincsproject.ca/xdx/ip_right_of_design_of_object/2018.308.109> a crm:E30_Right ;
rdfs:label "IP right of design of snowboard helmet"@en ;
crm:P75i_is_possessed_by <http://temp.lincsproject.ca/paradox_design> .

Model

A design may be the production plan of a specific model. A model may correspond to multiple designs, such as in the case of the same chair model in different colors. On the contrary, each individual design corresponds to a single model.

Diagram
Application profile
PatternDefinitionA model may have a design as its production plan.
AbstractionE29 Design or Procedure
P187i is production plan for
E99 Product Type
Applies toDesign. Each design may be used as the production plan of a model.
ValuesType of ValueUniform Resource Identifier (URI)
Expected ValueA URI representing the model.
AuthoritiesLINCS for the URI of the model.
Example Values<http://temp.lincsproject.ca/xdx/model/1000>
ExamplesTypical ExampleThe design of Electric Kettle Model 1000 is the production plan of Electric Kettle Model 1000.
Example Abstraction<http://temp.lincsproject.ca/xdx/design_of_object/2024.YU.xDX.00078>
P187i is production plan for
<http://temp.lincsproject.ca/xdx/model/1000>
Generalized Pattern (Turtle)
  <model> a crm:E99_Product_Type ;
rdfs:label "<model>"@en ;
crm:P187_has_production_plan <design> .

<design> a crm:E29_Design_or_Procedure ;
rdfs:label "<design>"@en .
Sample Data (Turtle)
  <http://temp.lincsproject.ca/xdx/model/1000> a crm:E99_Product_Type ;
rdfs:label "Electric Kettle Model 1000"@en ;
crm:P187_has_production_plan <http://temp.lincsproject.ca/xdx/design_of_object/2024.YU.xDX.00078> .

<http://temp.lincsproject.ca/xdx/design_of_object/2024.YU.xDX.00078> a crm:E29_Design_or_Procedure ;
rdfs:label "Design of Electric Kettle Model 1000"@en .

Designer

A designer is a person who has created one or more designs for xDX objects. Each person has a name, a birth, a death (if no longer living), and one or more occupations. A designer may belong to one or more design firms across their career.

Creation & Role

Diagram
Application profile
NoteThe modelling of design creation activities follows the basic pattern for Actors in a Role. See the corresponding section for more information.

Design Firm

A designer may belong to a design firm, which is an organization that employs designers and is responsible for the design of xDX objects. A design firm may have one or more designers, and a designer may work for one or more design firms across their career.

Diagram
Application profile
PatternDefinitionA design firm employs a designer.
AbstractionE74 Group
P107 has former or current member
E21 Person
Applies toDesigner. Each design firms employs one or more designers.
ValuesType of ValueUniform Resource Identifier (URI)
Expected ValueA URI that uniquely identifies the designer.
Example Values<http://vocab.getty.edu/ulan/500460448> (Koen de Winter)
ExamplesTypical ExampleThe design firm Danesco Inc. employed designer Koen de Winter.
Example Abstractionviaf:135979730
P107 has former or current member
ulan:500460448
Generalized Pattern (Turtle)
<firm> a crm:E74_Group ;
rdfs:label "<firm>"@en ;
crm:P107_has_current_or_former_member <designer> .
Sample Data (Turtle)
viaf:135979730 a crm:E74_Group ;
rdfs:label "Danesco Inc."@en ;
crm:P107_has_current_or_former_member <http://vocab.getty.edu/ulan/500460448> .

Name

Diagram
Application profile
NoteThe modelling of designer names follows the basic pattern for Names & Titles. See the corresponding section for more information.

Archival File

An archival file contains information about the design of one or more xDX objects.

Creation

An archival file is created by a designer at a certain date and location.

Diagram
Application profile
PatternDefinitionAn archival file is created through a creation event.
AbstractionE65 Creation
P94 has created
E73 Information Object
Applies toArchival File. Every archival file is created through exactly one creation event.
ValuesType of ValueUniform Resource Identifier (URI).
Expected ValueA URI that uniquely identifies the creation event.
AuthoritiesLINCS for the URI of the creation event.
Example Values<http://temp.lincsproject.ca/xdx/creation_of_archival_file/F%204720-3-0-1>
ExamplesTypical ExampleThe archival file F 4720-3-0-1 was created by the creation event Creation of archival file of Essex Franklin Library.
Example Abstraction<http://temp.lincsproject.ca/xdx/archival_file/F%204720-3-0-1>
P94i was created by
<http://temp.lincsproject.ca/xdx/creation_of_archival_file/F%204720-3-0-1>
Generalized Pattern (Turtle)
<archival_file> a crm:E73_Information_Object ;
rdfs:label "<archival_file>"@en ;
crm:P94i_was_created_by <creation> .

<creation> a crm:E65_Creation ;
rdfs:label "<creation>"@en ;
crm:P14_carried_out_by <designer> ;
crm:P4_has_time-span <time_span> .
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/archival_file/F%204720-3-0-1> a crm:E73_Information_Object ;
crm:P94i_was_created_by <http://temp.lincsproject.ca/xdx/creation_of_archival_file/F%204720-3-0-1> .

<http://temp.lincsproject.ca/xdx/creation_of_archival_file/F%204720-3-0-1> a crm:E65_Creation ;
rdfs:label "Creation of archival file of Essex Franklin Library"@en ;
crm:P14_carried_out_by <http://vocab.getty.edu/ulan/500269553> ;
crm:P4_has_time-span <http://temp.lincsproject.ca/xdx/time_span_of_creation_of_archival_file/F%204720-3-0-1> .

Topic

Diagram
Application profile
PatternDefinitionAn archival file is about one or more topics.
AbstractionE73 Information Object
P129 is about
E55 Type
ValuesType of ValueUniform Resource Identifier (URI)
Expected ValueA URI that uniquely identifies the topic.
Applies toArchival File. Each archival file may be about one or more topics.
Example Valueswikidata:Q611723 (Ryerson University)
ExamplesTypical ExampleThe archival file Al Faux Archives Ryerson Polytechnical Institute Furniture & Fixtures is about the topic Ryerson University.
Example Abstraction<http://temp.lincsproject.ca/xdx/archival_file/94>
P129 is about
wikidata:Q611723

Title

NoteThe modelling of archival file titles follows the basic pattern for Names & Titles. See the corresponding section for more information.

Identifier

NoteThe modelling of archival file identifiers follows the basic pattern for Identifiers. See the corresponding section for more information.

Creation

A creation is an event through which an information object (a design or an archival file) is created. The dataset reports who carried out the creation and at which location the event took place.

Creator & Role

Diagram
Application profile
NoteThe modelling of design creation activities follows the basic pattern for Actors in a Role. See the corresponding section for more information.

Location

Diagram
Application profile
NoteThe modelling of creation locations follows the basic pattern for Locations. See the corresponding section for more information.

Date

Diagram
Application profile
NoteThe modelling of creation dates follows the basic pattern for Dates. See the corresponding section for more information.

Owner

An owner is a person or organization that owns one or more xDX objects. Each owner has a name.

Name

Diagram
Application profile
NoteThe modelling of owner names follows the basic pattern for Names & Titles. See the corresponding section for more information.

Acquisition

xDX objects may have been acquired by multiple owners (people or institutions) over the years.

Diagram
Application profile
PatternDefinitionAn object has been acquired through an acquisition event.
AbstractionE22 Human-Made Object
P24 changed ownership through
E8 Acquisition
   P22 transferred title fromE39 Actor
   P22 transferred title toE39 Actor

E22 Human-Made Object
P49 has former or current keeper
E39 Actor
Applies toxDX Object. Every object has one or more acquisitions.
ValuesType of ValueUniform Resource Identifier (URI).
Expected ValuesA URI that uniquely identifies the acquisition.
A URI that uniquely identifies the owner.
AuthoritiesLINCS for the URI of the acquisition.
Virtual International Authority File, Wikidata, or LINCS for the URI of the owner(s).
Example Values<http://temp.lincsproject.ca/xdx/acquisition_of_object/2019.CU.DX.00060/by/Carleton%20University>
(Acquisition of Umbra Ah Chair)
ExamplesTypical ExampleCarleton University acquired the Umbra Ah chair from Design Exchange.
Example Abstraction<http://temp.lincsproject.ca/xdx/object/2019.CU.DX.00060> →
P24 changed ownership through
<http://temp.lincsproject.ca/xdx/acquisition_of_object/2019.CU.DX.00060/by/Carleton%20University> →
   P22 transferred title fromwikidata:Q5264264
   P22 transferred title towikidata:Q1041737

<http://temp.lincsproject.ca/xdx/object/2019.CU.DX.00060>
   P49 has former or current keeperwikidata:Q5264264
   P49 has former or current keeperwikidata:Q1041737
Generalized Pattern (Turtle)
<object> a crm:E22_Human-Made_Object ;
rdfs:label "<object>"@en ;
crm:P24i_changed_ownership_through <acquisition> ;
crm:P49_has_former_or_current_keeper <former_owner>, <current_owner> .

<acquisition> a crm:E8_Acquisition ;
rdfs:label "<acquisition>"@en ;
crm:P22_transferred_title_to <current_owner> ;
crm:P23_transferred_title_from <former_owner> .
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/object/2019.CU.DX.00060> a crm:E22_Human-Made_Object ;
rdfs:label "Umbra Ah Chair"@en ;
crm:P24i_changed_ownership_through <http://temp.lincsproject.ca/xdx/acquisition_of_object/2019.CU.DX.00059/by/Carleton%20University> ;
crm:P49_has_former_or_current_keeper wikidata:Q1041737, wikidata:Q5264264 ;

<http://temp.lincsproject.ca/xdx/acquisition_of_object/2019.CU.DX.00060/by/Carleton%20University> a crm:E8_Acquisition ;
rdfs:label "Acquisition of Umbra Ah Chair"@en ;
crm:P22_transferred_title_to wikidata:Q1041737 ;
crm:P23_transferred_title_from wikidata:Q5264264 .

Conceptual Layer

The conceptual layer of the xDX application profile involves the conceptual grouping of xDX objects into models, series, brands, work types, and classifications. Each of these concepts is represented as an instance of the CIDOC CRM class E55 Type, which allows for the creation of a hierarchy of types. Narrower terms are connected to broader terms through the CIDOC CRM property P127 has broader term, forming two separate hierarchies.

First, each object may be related to a specific model, series, or brand. Model is the narrower term, series is broader than model, and brand is broader than series. The CIDOC CRM property P127 has broader term is used to connect them together.

Second, each object may also have a work type and a classification. These are also instances of CIDOC CRM class E55 Type. The work type is the narrower term, while the classification is the broader term, and they are connected through the P127 has broader term property.

Application profile

For example, a specific Shelbern C55 Radio object is related to the Shelbern C55 Radio model (representing the conceptual grouping of all objects that are identified as Shelbern C55 Radios), and multiple models may be organized into a series such as Shelbern Radio series. At the same time, the object may be related to a work type such as radio receivers and a broader classification such as electronics.

The conceptual layer also contains the representation of object part types (e.g., Shelbern C55 Radio Antenna), and related classifications (e.g., antenna). Finally, any xDX object may also be assigned a prototype type to indicate that it is a prototype.

Model

Each object may have a specific model, such as MS-SC Stacking Chair or Umbra Ah Chair.

Diagram
Application profile
NoteThe modelling of xDX object models follows the basic pattern for Types. See also the Conceptual Object section for more information.

Series

Each object may have a specific series, intended as a grouping of models, such as Clairtone G Series.

Diagram
Application profile
NoteThe modelling of xDX object models follows the basic pattern for Types. See also the Conceptual Object section for more information.

Brand

Each object may have a specific brand, such as General Electric.

Diagram
Application profile
NoteThe modelling of xDX object brands follows the basic pattern for Types. See the corresponding section for more information.

Work Type

Each object has a specific work type, such as chair or kettle.

Diagram
Application profile
NoteThe modelling of object classifications follows the basic pattern for Types. See the corresponding section for more information.

Classification

Each object may have a general classification, such as furniture.

Diagram
Application profile
NoteThe modelling of object classifications follows the basic pattern for Types. See the corresponding section for more information.

Note

A note is a linguistic object that is attached to a certain entity. The xDX dataset contains several types of notes, such as materials notes, condition notes, dimensions notes, etc.

Type

Diagram
Application profile
NoteThe note type follows the basic pattern for Types. See the corresponding section for more information.

The table below reports the note types used in the xDX dataset along with the vocabulary terms adopted to represent them.

Note TypeVocabulariesVocabulary Terms
Colour NoteAAT & LINCSaat:300435416 (descriptive note)
temp:colour_note (colour note)
Condition NoteAAT & LINCSaat:300435416 (condition/examination description)
temp:condition_note (condition note)
Contextual Information NoteAAT & LINCSaat:300435416 (descriptive note)
temp:contextual_information_note (contextual information note)
Cultural Context NoteAAT & LINCSaat:300435428 (historical/cultural context)
temp:cultural_context_note (cultural context note)
Date NoteAAT & LINCSaat:300435416 (descriptive note)
temp:date_note (date note)
Descriptive NoteAAT & LINCShttp://vocab.getty.edu/aat/300435416 (descriptive note)
temp:descriptive_note (descriptive note)
Designer NoteAAT & LINCSaat:300435416 (descriptive note)
temp:designer_note (designer note)
Design Firm NoteAAT & LINCSaat:300435416 (descriptive note)
temp:design_firm_note (design firm note)
Dimensions NoteAAT & LINCSaat:300435430 (dimensions description)
temp:dimensions_note (dimensions note)
General NoteAAT & LINCSaat:300435416 (descriptive note)
temp:general_note (general note)
History of Use NoteAAT & LINCSaat:300435416 (descriptive note)
temp:history_of_use_note (history of use note)
Inscription NoteAAT & LINCSaat:300435416 (descriptive note)
temp:inscription_note (inscription note)
IP NoteAAT & LINCSaat:300435416 (descriptive note)
temp:ip_note (IP note)
Mark/Label NoteAAT & LINCSaat:300435416 (descriptive note)
temp:mark_label_note (mark/label note)
Materials NoteAAT & LINCSaat:300435429 (materials/technique description)
temp:materials_note (materials note)
Physical Description NoteAAT & LINCSaat:300435416 (descriptive note)
temp:physical_description_note (physical description note)
Producer NoteAAT & LINCSaat:300435416 (descriptive note)
temp:producer_note (producer note)
Production NoteAAT & LINCSaat:300435416 (descriptive note)
temp:production_note (production note)

Content

Diagram
Application profile
PatternDefinitionA note has a textual content.
AbstractionE33 Linguistic Object
P190 has symbolic content
xsd:string
Applies toNote. Every note has exactly one content.
ValuesType of Valuexsd:string
Expected ValueA string of text representing the content of the note.
AuthoritiesXSD for the datatype of the string literal.
Example Values
  • "Retail display unit, not intended to work."@en
  • "White sticker on the back labeled "this is not a toy" in English and other languages."@en
  • "Cast iron fireplace tongs. Has two rectangular handles, similar to scissors."@en
  • "Said to have inspired the creator of Twitter, Jack Dorsey, to create Twitter."@en
ExamplesTypical ExampleThe contextual information note of RIM Pager 850 has content "Said to have inspired the creator of Twitter, Jack Dorsey, to create Twitter."@en
Example Abstraction<http://temp.lincsproject.ca/xdx/contextual_information_note/2022.YU.xDX.00059> →
P190 has symbolic content
"Said to have inspired the creator of Twitter, Jack Dorsey, to create Twitter."@en
Generalized Pattern (Turtle)
<note>
a crm:E33_Linguistic_Object ;
rdfs:label "<note>"@en ;
crm:P190_has_symbolic_content "<content>".
Sample Data (Turtle)
<http://temp.lincsproject.ca/xdx/contextual_information_note/2022.YU.xDX.00059>
a crm:E33_Linguistic_Object ;
rdfs:label "Contextual information note about RIM Pager 850"@en ;
crm:P190_has_symbolic_content "Said to have inspired the creator of Twitter, Jack Dorsey, to create Twitter."@en.

Place

A place is a geographic location that is identified by spatial coordinates.

Coordinates

Diagram
Application profile
PatternDefinition

A place is identified by a geographic reference such as coordinates.

AbstractionE53 Place
P168 place is defined by
xsd:string
ValuesType of Valuexsd:string
Expected ValueA string of text representing geographic coordinates (latitude and longitude).
AuthoritiesGeoNames for the place URI.
Wikidata and GeoNames as sources of coordinates.
Example ValuePOINT(-63.29844 46.39808) (coordinates of Prince Edward Island)
ExamplesTypical ExamplePrince Edward Island has latitude 46.39808 and longitude -63.29844
Example Abstractiongeonames:6113358
P168_has_spatial_coordinates
POINT(-63.29844 46.39808)

Spatial Containment

Diagram
Application profile
PatternDefinition

A place may fall within another place.

AbstractionE53 Place
P89 falls within
E53 Place
ValuesType of ValueUniform Resource Identifier (URI).
Expected ValueA URI representing a place.
AuthoritiesGeoNames for the place URI.
Example Valuegeonames:6093943 (Ontario)
ExamplesTypical ExampleThe city of Toronto falls within the province of Ontario.
Example Abstractiongeonames:6067965
P89 falls within
geonames:6093943

Webpage

A webpage is a digital object that contains information about one or more xDX objects. Each webpage may also contain one or more images of xDX objects.

Object

Diagram
Application profile
PatternDefinitionA webpage is about an xDX object.
AbstractionD1 Digital Object (CRMdig)
P129 is about
E22 Human-Made Object
ValuesType of ValueUniform Resource Identifier (URI).
Expected ValueA URI representing an xDX object.
AuthoritiesLINCS for the URI of the object.
Example Value<http://temp.lincsproject.ca/xdx/object/2019.CU.DX.00011> (Teaching Aid Manikin)
ExamplesTypical ExampleThe webpage located at URL <https://collections.ssac.carleton.ca/index.php/Detail/objects/2870> is about the xDX object 2019.CU.DX.00011 (Teaching Aid Manikin).
Example Abstraction<https://collections.ssac.carleton.ca/index.php/Detail/objects/2870>
P129 is about
<http://temp.lincsproject.ca/xdx/object/2019.CU.DX.00011>

Image

Diagram
Application profile
PatternDefinitionA webpage incorporates an image of an xDX object.
AbstractionD1 Digital Object (CRMdig)
P165 incorporates
E36 Visual Item
ValuesType of ValueUniform Resource Identifier (URI).
Expected ValueA URI representing an image.
AuthoritiesLINCS for the URI of the image.
Example Value
ExamplesTypical ExampleThe webpage located at URL <https://collections.ssac.carleton.ca/index.php/Detail/objects/2870> incorporates an image of the xDX object 2019.CU.DX.00011 (Teaching Aid Manikin).
Example Abstraction<https://collections.ssac.carleton.ca/index.php/Detail/objects/2870>
P165 incorporates