Basic Patterns Application Profile
Purpose
To document how various facets of LINCS data are modelled, along with reference authorities for the populating vocabularies. This will provide a basis for instruction for how to model data in a LINCS-compatible manner, as well as aid in navigation and discovery.
“Basic Patterns” describes patterns that are used across all facets of the data: they are general concepts that are important basic building blocks for more specific data patterns.
This document introduces the concepts as used by LINCS, and are not complete definitions of the CIDOC CRM ontology class or property concepts. Consult CIDOC CRM v. 7.1.1 documentation for full class descriptions and property descriptions.
Acronyms
Ontology Acronyms:
Vocabulary and Authority Acronyms:
- AAT - Getty Art & Architecture Thesaurus
- Biography - The LINCS Biography Vocabulary
- Context - The LINCS Context Vocabulary
- Event - The LINCS Event Vocabulary
- Identity - The LINCS Identity Vocabulary
- LINCS - LINCS minted entities
- LOC - Library of Congress
- Wikidata - Wikimedia Knowledge Base
Main Classes
Entity type | Class | Declaration Snippet (TTL) |
Identifier | crm:E42_Identifier |
|
Linguistic identifier | crm:E33_E41_Linguistic_Appellation |
|
Type | crm:E55_Type |
|
Activity | crm:E7_Activity |
|
Time-Span | crm:E52_Time-Span |
|
Place | crm:E53_Place |
|
Actors | crm:E39_Actor (subclasses E21, E74 where possible) |
|
Role | crm:PC14_carried_out_by |
|
Thing | crm:E70_Thing (subclasses where possible) |
|
Linguistic Object | crm:E33_Linguistic_Object |
|
Visual Item | crm:E36_Visual_Item |
|
Attribute Assignment | crm:E13_Attribute_Assignment |
|
Overview Diagram
Below is an image of the application profile overview diagram. Follow this link for a zoomable, more readable version. The segments below align with the document sections.
Nodes
Identifiers
Unique Identifiers
Unique identifiers are a way that a data creator or owner refers to an entity: common occurrences of this are an accession number, call number, or internal identifier field in a database. These can contain numbers, letters, and other characters, but are not linguistic in nature.
Pattern/Structure Values | Definition | This pattern declares that an entity is identified by an identifier. |
Abstraction | crm:E1_CRM_Entity → crm:P1_is_identified_by → crm:E42_Identifier
| |
Content Values | Type of Value | Uniform Resource Identifier (URI); literal value (text) |
Expected Value | URI from project dataset, existing linked data authority, or minted by LINCS; literal value from project dataset | |
Format/Requirements for the Value | URI (preferably dereferenceable); rdfs:literal | |
Case Examples | Typical Example & Abstraction | The University of Saskatchewan Art Gallery dataset states that there is an object that is identified by the accession number “2020.008.008.” <usask:3359> → crm:P1_is_identified_by → crm:E42_Identifier
|
Edge Case Example & Abstraction | N/A | |
Resource Links | The Getty Research Institute. (2017, March 7). Art & Architecture Thesaurus Online. | |
Discussion Elements Pertaining to This Pattern | Use at least two (2) E55_Types on each identifier: generic (from existing linked data vocabulary) or project-specific (minted for project). Always use the Getty AAT term for unique identifiers . Additional are optional for precision (e.g., the Getty AAT term for accession numbers ). | |
Projects Following This Pattern | All projects |
Pattern in TTL:
<entity> a crm:E1_CRM_Entity ;
rdfs:label "<entity>" ;
crm:P1_is_identified_by <entity_identifier> .
<entity_identifier> a crm:E42_Identifier ;
rdfs:label "Unique identifier of <entity>"
crm:P2_has_type <http://vocab.getty.edu/aat/300404012>,
<project_identifier_type> ;
crm:P190_has_symbolic_content "<entity_identifier>" .
<http://vocab.getty.edu/aat/300404012> a crm:E55_Type ;
rdfs:label "unique identifiers" .
<project_identifier_type> a crm:E55_Type ;
rdfs:label "<project> identifiers" .
Linguistic Identifiers (Appellations)
Identifiers that are made up of words—like titles or names—are referred to as “linguistic identifiers” or “linguistic appellations.” The class used to represent these is a combination of E41_Appellation
and E33_Linguistic_Identifier
, referred to as E33_E41_Linguistic_Appellation
in the RDF implementation of CIDOC CRM.
- For more on person names, see the relevant section of the People and Organizations Application Profile.
- For more on place names, see the relevant section of the Places Application Profile.
- For more on object and artifact titles, see the relevant section in the Physical Objects Application Profile.
- For more on titles of bibliographic records, see the relevant section in the Conceptual Objects Application Profile.
Pattern in TTL:
<entity> a crm:E1_CRM_Entity ;
rdfs:label "<entity>" ;
crm:P1_is_identified_by <entity_name_or_title> .
<entity_name_or_title> a crm:E33_E41_Linguistic_Appellation ;
rdfs:label "Linguistic identifier of <entity>" ;
crm:P2_has_type <type> ;
crm:P190_has_symbolic_content "<entity_name_or_title>" .
<type> a crm:E55_Type ;
rdfs:label "<type>" .
Identifiers as Parts of Other Identifiers
Identifiers, in particular linguistic appellations, can be made up of components that are themselves uniquely identified: for example, a full name may contain a first name and last name as its parts.
Pattern/Structure Values | Definition | This pattern declares that a linguistic identifier is made up of constituent parts. |
Abstraction | crm:E1_CRM_Entity → crm:P1_is_identified_by →
crm crm:E1_CRM_Entity → crm:P1_is_identified_by → crm 2
→ crm:P106i_forms_part_of → crm 1 | |
Content Values | Type of Value | Uniform Resource Identifier (URI) |
Expected Value | URI from project dataset, existing linked data authority, or minted by LINCS | |
Format/Requirements for the Value | URI, preferably dereferenceable | |
Case Examples | Typical Example & Abstraction | The Map of Early Modern London Personography dataset states that <https://mapoflondon.uvic.ca/BACO1> has the display name of “Sir Nicholas Bacon,” which is itself made up of “Sir,” “Nicholas,” and “Bacon.” <https://mapoflondon.uvic.ca/BACO1> → crm:P1_is_identified_by → <http://temp.lincsproject.ca/persons/foaf_name/Sir_Nicholas_Bacon> <https://mapoflondon.uvic.ca/BACO1> → crm:P1_is_identified_by → <http://temp.lincsproject.ca/persons/foaf_firstName/Nicholas>
|
Edge Case Example & Abstraction | N/A | |
Resource Links | N/A | |
Discussion Elements Pertaining to This Pattern | N/A | |
Projects Following This Pattern | AdArchive, Canadian Centre for Ethnomusicology, MoEML Persons, Orlando |
Pattern in TTL:
<entity> a crm:E1_CRM_Entity ;
rdfs:label "<entity>" ;
crm:P1_is_identified_by <entity_name_or_title_full>,
<entity_name_or_title_part_1>,
<entity_name_or_title_part_2> .
<entity_name_or_title_full> a crm:E33_E41_Linguistic_Appellation ;
rdfs:label "Linguistic identifier of <entity>" ;
crm:P106_is_composed_of <entity_name_or_title_part_1>,
<entity_name_or_title_part_2> .
<entity_name_or_title_part_1> a crm:E33_E41_Linguistic_Appellation ;
rdfs:label "<entity_name_or_title_part_1>" ;
crm:P106i_forms_part_of <entity_name_or_title_full> .
<entity_name_or_title_part_2> a crm:E33_E41_Linguistic_Appellation ;
rdfs:label "<entity_name_or_title_part_2>" ;
crm:P106i_forms_part_of <entity_name_or_title_full> .
Identifier Use Time-Spans
To say that an identifier was used by only a specific set of people or for only a specific period of time, use the Attribute Assignment pattern (see Assertions and Attributions Assignment below). The time-span connected to the assertion activity represents the time-span for which the identifier was used; the actors connected to the assertion represent the individuals or groups who used the identifier.
Types
Categorization, Classification, and Other Conceptual Groupings
All entities can be specialized, categorized, classified, or otherwise described using E55 Type.
Pattern in TTL:
<entity> a crm:E1_CRM_Entity ;
rdfs:label "<entity>" ;
crm:P2_has_type <entity_type> .
<entity_type> a crm:E55_Type ;
rdfs:label "<entity_type>" .
Type Categories
Types can have broader or narrower types; this starts the creation of a structured vocabulary. For more on vocabularies, see the following section.
Pattern/Structure Values | Definition | This pattern declares that a type has a broader concept. |
Abstraction | crm:E55_Type → crm:P127_has_broader_term → crm:E55_Type | |
Content Values | Type of Value | Uniform Resource Identifier (URI) |
Expected Value | URI from project dataset, existing linked data authority, or minted by LINCS | |
Format/Requirements for the Value | URI, preferably dereferenceable | |
Case Examples | Typical Example & Abstraction | The Anthologia graeca dataset declares that a keyword has a broader term. <lincs:keyword/1288> → crm:P127_has_broader_term →
<lincs:keyword/category/9> |
Edge Case Example & Abstraction | N/A | |
Resource Links | N/A | |
Discussion Elements Pertaining to This Pattern | N/A | |
Projects Following This Pattern | Anthologia graeca, Canadian Centre for Ethnomusicology |
Pattern in TTL:
<type> a crm:E55_Type ;
rdfs:label "<type>" ;
crm:P127_has_broader_term <type_catgeory> .
<type_catgeory> a crm:E55_Type ;
rdfs:label "<type_catgeory>" .
Vocabularies
Generally speaking, a vocabulary is a collection of terms that are used to describe a given domain. It is a generic term to refer to sets of concepts that could be concretely described in an ontology, taxonomy, or thesaurus. LINCS seeks to distinguish between the ontologies (used for structure) and the vocabularies (used for content) present in its data: while the ontology provides high-level categorization and relationships between entities, vocabularies enable semantic specificity in the label and definition for a particular type of thing.
While LINCS encourages the use of existing linked data vocabularies, in some cases, new vocabularies have been created and hosted within LINCS to provide domain-specific terms not readily available in other external authorities. In these cases, terms are classed as skos:Concept as well as crm:E55_Type, and utilize SKOS properties as well as those from CIDOC CRM. These vocabularies are made available for discovery and reuse using Skosmos.
For more on discovering and using existing linked data vocabularies, see the LINCS Vocabulary Browser.
Talking about Entities
Describing or Referencing an Entity
CIDOC CRM has two ways to model textual statements made about an entity: through a direct path using the property P3_has_note
, or a longer path through P67i_is_referred_to_by
to an E33_Linguistic_Object
. The longer path is used in the majority of cases at LINCS, as this supports other statements about the textual item to be made, such as asserting what type of statement it is and who made it. This is particularly useful when different kinds of notes are made about an entity; for example, it is necessary to differentiate a curator’s note from a conservator’s note about an object while still modeling them both as notes about the same object. By treating it as an entity, it is also possible to say further things about the text, such as who wrote it and when.
Note - Full Path
Pattern in TTL:
<entity> a crm:E1_CRM_Entity ;
rdfs:label "<entity>" ;
crm:P67i_is_referred_to_by <entity_note> .
<entity_note> a crm:E33_Linguistic_Object ;
rdfs:label "<type> statement for <entity>" ;
crm:P2_has_type <type> ;
crm:P190_has_symbolic_content "<note>" .
<type> a crm:E55_Type ;
rdfs:label "<type>" .
Note - Short Path
Pattern/Structure Values | Definition | This pattern declares that an entity has a note. |
Abstraction |
| |
Content Values | Type of Value | Literal value (text) |
Expected Value | Literal value from project dataset | |
Format/Requirements for the Value | rdfs:literal | |
Case Examples | Typical Example & Abstraction | The Orlando dataset states that there is a note associated with an entity. <cwrc_data:alcolo_BirthEvent_0> → crm:P3_has_note → “29 November 1832: LMA was born in Germantown near Philadelphia,
Pennsylvania, USA.” |
Edge Case Example & Abstraction | N/A | |
Resource Links | N/A | |
Discussion Elements Pertaining to This Pattern | When it is known, add a language tag to the rdfs:literal contents to specify the language of the text (e.g., “@en” for English). | |
Projects Following This Pattern | AdArchive, MoEML Persons, Orlando |
Pattern in TTL:
<entity> a crm:E1_CRM_Entity ;
rdfs:label "<entity>" ;
crm:P3_has_note "<note>"@en .
Visual Representations of an Entity
Pattern/Structure Values | Definition | This pattern declares that an entity is represented by an image. |
Abstraction |
| |
Content Values | Type of Value | Uniform Resource Identifier (URI) |
Expected Value | URI from project dataset, existing linked data authority, or minted by LINCS | |
Format/Requirements for the Value | URI, preferably dereferenceable | |
Case Examples | Typical Example & Abstraction | The AdArchive dataset states that the Heresies 6 Praxis advertisement (lincs:ASOL_NRr02h) is represented by an image. <lincs:ASOL_NRr02h> → crm:P138i_has_representation → |
Edge Case Example & Abstraction | N/A | |
Resource Links | IIIF Consortium. (n.d.). International Image Interoperability Framework. https://iiif.io | |
Discussion Elements Pertaining to the Pattern | N/A | |
Projects Following this Pattern | AdArchive, Anthologia graeca, HistSex, University of Saskatchewan Art Gallery |
Pattern in TTL:
<entity> a crm:E1_CRM_Entity ;
rdfs:label "<entity>" ;
crm:P138i_has_representation <image> .
<image> a crm:E36_Visual_Item ;
rdfs:label "Image of <entity>" .
Assertions and Attribution Assignment
The E13_Attribute_Assignment
class can be used to connect any assertion about an entity to the entity in question: this is a wider concept than P67i_is_referred_to_by
, which only says that a text source discusses or makes mention of an entity. This core pattern is used and extended by LINCS in three primary additional areas:
- Connecting metadata to data objects. For more on this, see the Sources & Metadata Application Profile.
- Supporting the integration of the Web Annotation Data Model for representing contextual information and nuanced data provenance. For more on this, see the Sources & Metadata Application Profile.
- Representing that statements about an actor’s identity have been made without implying anything further about the accuracy of those claims: this pattern is used to say that, for example, a biographer described Louisa May Alcott to be a woman, and not saying whether or not Louisa May Alcott is or is not a woman. For more on this, see People & Organizations Application Profile - Identities.
Pattern/Structure Values | Definition | This pattern declares that an entity has had an attribute associated with it. |
Abstraction |
| |
Content Values | Type of Value | Uniform Resource Identifier (URI); literal value (text) |
Expected Value | URI from project dataset, existing linked data authority, or minted by LINCS; literal value from project dataset | |
Format/Requirements for the Value | URI, preferably dereferenceable; rdfs:literal | |
Case Examples | Typical Example & Abstraction | The Orlando dataset states that Rosamund Marriort Watson was attributed with having a gender of woman. cwrc_data:9e381429-5019-48dd-88fd-79e8b3f4825f →
crm:P140i_was_attributed_by → crm:E13_Attribute_Assignment
|
Edge Case Example & Abstraction | N/A | |
Resource Links | Brown, S., Cummings, J., Drudge-Wilson, J., Faulkner, C., Lemak, A., Martin, K., Mo, A., Penancier, J., Simpson, J., Singh, G., Stacey, D., & Warren, R. (2020, July 14). The CWRC Ontology Specification 0.99.86. The Canadian Writing Research Collaboratory. | |
Discussion Elements Pertaining to the Pattern | To say who made the assertion, use the P14_carried_out_by pattern (see Performing below). To say that a source, such as a text, was used as the basis for the claim, use the P16_used_specific_object pattern (see Using Specific Objects below).. To say that a source, such as a text, describes the assertion (as opposed to being used for it), use the P67i_is_referred_to or P129i_is_subject_of pattern (see Describing or Referencing an Entity below). To represent the level of certainty with which the assertion was made, use the P2_has_type pattern (see Types above). | |
Projects Following this Pattern | AdArchive, Canadian Centre for Ethnomusicology, MoEML Gazetteer, Orlando, Yellow Nineties |
Pattern in TTL:
<entity> a crm:E1_CRM_Entity ;
rdfs:label "<entity>" ;
crm:P140i_was_attributed_by <assertion_activity> .
<assertion_activity> a crm:E13_Attribute_Assignment ;
rdfs:label "Attribute assignment for <entity>" ;
crm:P141_assigned <assigned> .
<assertion> a crm:E1_CRM_Entity ;
rdfs:label "<thing_asserted>" .
Activities
Events, activities, and their subclasses are the ways that people or things are brought together with other people, at points of time and in locations. Subclasses have their own unique properties, but at a high level the following categories apply to all:
- When the activity occurred (time-span)
- Where the activity occurred (location)
- Who participated in the activity (roles)
- Optionally—what was used in the activity (using things)
Events and Activities
While crm:E5_Event
is a superclass to time-based occurrences, it is not used directly in LINCS data: instead, a more specific subclass is used. In LINCS, the most generic class that is used is E7_Activity
, a direct subclass of E5_Event
. A key difference between these two classes is in their relationship to actors: E7_Activity
instances are Events that were carried out by one or more persons. While actors are able to participate and be present for instances of E5_Event
, this superclass is not within range of the crm:P14_carried_out_by
property, which is used to show active participation.
Time-Spans of Activities
Pattern/Structure Values | Definition | This pattern declares that an event occurred in a time-span. |
Abstraction | crm:E5_Event → P4_has_time_span → E52_Time-Span
| |
Content Values | Type of Value | Literal value (text); date-time value |
Expected Value | Literal value from project dataset; date-time value from project dataset | |
Format/Requirements for the Value | rdfs:literal; xsd:dateTime | |
Case Examples | Typical Example & Abstraction | The Map of Early Modern London Personography dataset declares that Sir Nicholas Bacon was born in a birth event (crm:E67_Birth, subclass of crm:E5_Event) that took place in the year 1510. <http://temp.lincsproject.ca/persons/birth/BACO1> →
crm:P4_has_time_span → crm:E52_Time_Span
|
Edge Case Example & Abstraction | Dates will not always be so precise as to be able to support a start (P82a) and end (P82b) property; sometimes only a starting or ending date may be known. For example, the Map of Early Modern London Personography dataset declares that Edward the Confessor was born in a birth event (crm:E67_Birth, subclass of crm:E5_Event) that took place after 1003. <http://temp.lincsproject.ca/persons/birth/EDWA7> →
crm:P4_has_time_span → crm:E52_Time_Span
The Map of Early Modern London Personography dataset declares that Christine Barantyn was born in a birth event (crm:E67_Birth, subclass of crm:E5_Event) that took place before 1415. <http://temp.lincsproject.ca/persons/birth/BARA2> →
crm:P4_has_time_span → crm:E52_Time_Span
| |
Resource Links | N/A | |
Discussion Elements Pertaining to This Pattern | When using E7_Activity and not a more specific subclass, use at least one (1) E55_Type on each activity specifying what it is. | |
Projects Following This Pattern | All projects |
Pattern in TTL:
<event_or_activity> a crm:E5_Event ;
rdfs:label "<event_or_activity>" ;
crm:P4_has_time-span <event_or_activity_dateTime> .
<event_or_activity_dateTime> a crm:E52_Time-Span ;
crm:P82_at_some_time_within "<event_or_activity_dateTime>" ;
crm:P82a_begin_of_the_begin
"<event_or_activityt_dateTime>"^^xsd:dateTime ;
crm:P82b_end_of_the_end
"<event_or_activity_dateTime>"^^xsd:dateTime .
Locations of Activities
For more on places, see the Places Application Profile.
Pattern in TTL:
<event_or_activity> a crm:E5_Event ;
rdfs:label "<event_or_activity>" ;
crm:P7_took_place_at <place> .
<place> a crm:E53_Place ;
rdfs:label "<place>" .
Participating in Activities
Participating
Pattern/Structure Values | Definition | This pattern declares that an actor participated in an event. |
Abstraction |
| |
Content Values | Type of Value | Uniform Resource Identifier (URI) |
Expected Value | URI from project dataset, existing linked data authority, or minted by LINCS | |
Format/Requirements for the Value | URI, preferably dereferenceable | |
Case Examples | Typical Example & Abstraction | In the Yellow Nineties Personography dataset, contribution to the creation of Yellow Nineties is identified by a string value (direct, indirect). Antonio Ferriera’s contribution is identified in this dataset as “indirect.” <y90s:ferriera-antonio/> → crm:P11i_participated_in →
<lincs:tQmPJo9trzE>
|
Edge Case Example & Abstraction | N/A | |
Resource Links | N/A | |
Discussion Elements Pertaining to This Pattern | crm:E39_Actor should be implemented through one of its subclasses: crm:E21_Person when it is one (1) person, and crm:E74_Group when it is more than one. When using E7_Activity and not a more specific subclass, use at least one (1) E55_Type on each activity specifying what it is. | |
Projects Following This Pattern | Orlando, Yellow Nineties Personography |
Pattern in TTL:
<event_or_activity> a crm:E5_Event ;
rdfs:label "<event_or_activity>" ;
crm:P11_had_participant <actor> .
<actor> a crm:E39_Actor ;
rdfs:label "<actor>" .
Performing
Pattern/Structure Values | Definition | This pattern declares that an actor performed an activity. |
Abstraction |
| |
Content Values | Type of Value | Uniform Resource Identifier (URI) |
Expected Value | URI from project dataset, existing linked data authority, or minted by LINCS | |
Format/Requirements for the Value | URI, preferably dereferenceable | |
Case Examples | Typical Example & Abstraction | The Yellow Nineties Personography dataset declares that Rosamund Marriott Watson shared a friendship with William Sharp. Their relationship is manifested as a unique crm:E7_Activity. <lincs:ZWFQzDOpYiK> → crm:P14_carried_out_by → <https://personography.1890s.ca/persons/marriott-watson-rosamund/> , |
Edge Case Example & Abstraction | When a person acts according to a certain role, such as an author or publisher in the creation of a book, the PC14 pattern is used to represent this. See Roles below. | |
Resource Links | N/A | |
Discussion Elements Pertaining to This Pattern | When using E7_Activity and not a more specific subclass, use at least one (1) E55_Type on each activity specifying what it is. crm:E39_Actor should be implemented through one of its subclasses: crm:E21_Person when it is one (1) person, and crm:E74_Group when it is more than one. | |
Projects Following This Pattern | AdArchive, Anthologia graeca, Canadian Centre for Ethnomusicology, HistSex, Orlando, University of Saskatchewan Art Gallery, Yellow Nineties Personography |
Pattern in TTL:
<activity> a crm:E7_Activity ;
rdfs:label "<activity>" ;
crm:P14_carried_out_by <actor> .
<actor> a crm:E39_Actor ;
rdfs:label "<actor>" .
Roles
LINCS implements the CIDOC CRM “Property Class” extension to represent types of participation. This is known as “reification,” in which the property P14_carried_out_by
becomes the class PC14_carried_out
.
Pattern/Structure Values | Definition | This pattern declares that an actor performed an activity by taking on a specific role. |
Abstraction | crm:E7_Activity → crm:P01i_is_domain_of → crm:PC14_carried_out_by
| |
Content Values | Type of Value | Uniform Resource Identifier (URI); literal value (text) |
Expected Value | URI from project dataset, existing linked data authority, or minted by LINCS; literal value from project dataset | |
Format/Requirements for the Value | URI, preferably dereferenceable; rdfs:literal | |
Case Examples | Typical Example & Abstraction | The Canadian Centre for Ethnomusicology dataset states that the recording of Canadian Centre for Ethnomusicology object CCE2000.2.626 was carried out by Ampex Records in the role of “record label.” <lincs:production_uri/CCE2000.2.626> → crm:P01i_is_domain_of →
<lincs:record_label_pc/CCE2000.2.626> (→ crm:P2_has_type → <wikidata:Q18127>)
|
Edge Case Example & Abstraction | This pattern can also apply to roles played in relationship activities. For more on this, see the Persons & Organizations Application Profile. The Yellow Nineties Personography dataset declares that Rosamund Marriott Watson and Andrew Lang shared a mentorship relationship wherein Marriott Watson was the mentee and Lang was the mentor. <y90s:marriott-watson-rosamund/> → crm:P02i_is_range_of
| |
Resource Links | N/A | |
Discussion Elements Pertaining to This Pattern | When using E7_Activity and not a more specific subclass, use at least one (1) E55_Type on each activity specifying what it is. crm:E39_Actor should be implemented through one of its subclasses: crm:E21_Person when it is one (1) person, and crm:E74_Group when it is more than one. LINCS identified three possible solutions for representing roles: local sub-properties; typed sub-activities; and reification through use of CIDOC CRM PC. LINCS made the decision to go with the third option as it provided the level of detail required by the data (which typed sub-activities may not have) without adding the overhead of maintaining local subproperties. | |
Projects Following This Pattern | AdArchive, Canadian Centre for Ethnomusicology, HistSex, Orlando, Yellow Nineties Personography |
Pattern in TTL:
<activity> a crm:E7_Activity ;
rdfs:label "<activity>" ;
crm:P01i_is_domain_of <reified_P14> .
<reified_P14> a crm:PC14_carried_out ;
rdfs:label "<actor> in the role of <role>" ;
crm:P02_has_range <actor> ;
crm:P14.1_in_the_role_of <role> .
<actor> a crm:E39_Actor ;
rdfs:label "<actor>" .
<role> a crm:E55:Type ;
rdfs:label "<role>" .
Using Things
Using Specific Objects
Pattern/Structure Values | Definition | This pattern declares that a thing was used in an activity. |
Abstraction | crm:E70_Thing → crm:P16i_was_used_for → crm:E7_Activity
| |
Content Values | Type of Value | Uniform Resource Identifier (URI); literal value (text) |
Expected Value | URI from project dataset, existing linked data authority, or minted by LINCS; literal value from project dataset | |
Format/Requirements for the Value | URI, preferably dereferenceable; rdfs:literal | |
Case Examples | Typical Example & Abstraction | The HistSex dataset states that a HistSex record object was used for a peer review activity. <histsex:3049> → crm:P16i_was_used_for →
<lincs:review/Sex_Worker_Film_and_Arts_Festival_Archives>
|
Edge Case Example & Abstraction | The Orlando dataset states that Rosamund Marriort Watson was attributed with having a gender of woman. <cwrc_data:9e381429-5019-48dd-88fd-79e8b3f4825f> →
crm:P140i_was_attributed_by → crm:E13_Attribute_Assignment
| |
Resource Links | Brown, S., Cummings, J., Drudge-Wilson, J., Faulkner, C., Lemak, A., Martin, K., Mo, A., Penancier, J., Simpson, J., Singh, G., Stacey, D., & Warren, R. (2020, July 14). The CWRC Ontology Specification 0.99.86. The Canadian Writing Research Collaboratory. | |
Discussion Elements Pertaining to the Pattern | crm:E70_Thing should be implemented through one of its subclasses, not used directly. When using E7_Activity and not a more specific subclass, use at least one (1) E55_Type on each activity specifying what it is. Datasets use this pattern explicitly in both directions (P16 and P16i), as reflected in the diagram and examples. LINCS uses this pattern as part of the larger Cultural Forms modeling pattern. For more on this, see People and Organizations - Identities. | |
Projects Following this Pattern | Anthologia graeca, Canadian Centre for Ethnomusicology, HistSex, Orlando, Yellow Nineties Personography |
Pattern in TTL:
<thing> a crm:E70_Thing ;
rdfs:label "<thing>" ;
crm:P16i_was_used_for <activity> .
<activity> a crm:E7_Activity ;
rdfs:label "<activity>" ;
crm:P16_used_specific_object <thing> ;
crm:P2_has_type <type> .
<type> a crm:E55_Type ;
rdfs:label "<type>" .
Using Types of Objects
Pattern/Structure Values | Definition | This pattern declares that a type of thing was used in an activity. |
Abstraction |
| |
Content Values | Type of Value | Uniform Resource Identifier (URI); literal value (text) |
Expected Value | URI from project dataset, existing linked data authority, or minted by LINCS; literal value from project dataset | |
Format/Requirements for the Value | URI, preferably dereferenceable; rdfs:literal | |
Example Values | locsubjects:sh85013057; “guitar”; “voice” | |
Case Examples | Typical Example & Abstraction | The Canadian Centre for Ethnomusicology dataset states that there is a performance (activity) that was performed using bells. <http://temp.lincsproject.ca/recordings/performance/CCE1995.2.3-1>
→ crm:P125_used_object_of_type → lcsh:sh85013057 |
Edge Case Example & Abstraction | N/A | |
Resource Links | Library of Congress. (2021, August 2). Library of Congress Subject Headings. | |
Discussion Elements Pertaining to This Pattern | When using E7_Activity and not a more specific subclass, use at least one (1) E55_Type on each activity specifying what it is. | |
Projects Following This Pattern | Canadian Centre for Ethnomusicology |
Pattern in TTL:
<activity> a crm:E7_Activity ;
rdfs:label "<activity>" ;
crm:P125_used_object_of_type <type> .
<type> a crm:E55_Type ;
rdfs:label "<type>" .
Events as Part of Other Events
Pattern/Structure Values | Definition | This pattern declares that an activity took place as part of another activity. |
Abstraction |
| |
Content Values | Type of Value | Uniform Resource Identifier (URI) |
Expected Value | URI from project dataset, existing linked data authority, or minted by LINCS | |
Format/Requirements for the Value | URI, preferably dereferenceable | |
Case Examples | Typical Example & Abstraction | The HistSex dataset states that creating a HistSex record involved a peer review of that record. <lincs:3074> → crm:P9_consists_of →
<lincs:review/Independent_Voices> |
Edge Case Example & Abstraction | N/A | |
Resource Links | N/A | |
Discussion Elements Pertaining to This Pattern | N/A | |
Projects Following This Pattern | HistSex |
Pattern in TTL:
<activity_1> a crm:E7_Activity ;
rdfs:label "<activity_1>" ;
crm:P9_consists_of <activity_2> .
<activity_2> a crm:E7_Activity ;
rdfs:label "<activity_2>" .