Historical Canadian Persons Application Profile

Purpose

The purpose of this application profile is to document how Historical Canadian Persons data is modelled for compatibility with the wider LINCS data model. This document provides patterns used in the mapping of Historical Canadian Persons 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 Historical Canadian Persons 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.

As part of the History of Canada project, the Historical Canadian Persons application profile is integrated with the Cabinet Conclusions and Historical Indian Affairs Agents application profiles. See the respective documents for more information.

Dependencies

This section reports the ontologies, vocabularies, and authority files adopted in the Historical Canadian Persons 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 throughout the document.

Ontologies

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

Acronym	Prefix	Ontology	Purpose
CIDOC-CRM	`crm:`	CIDOC Conceptual Reference Model	Main reference ontology
CRMdig	`crmdig:`	CRM Digital	To represent digital objects
OA	`oa:`	Web Annotation Data Model	To represent annotations

Vocabularies

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

Acronym	Prefix	Vocabulary	Purpose
AAT	`aat:`	Getty Art and Architecture Thesaurus	To represent archival fonds
Biography	`biography:`	LINCS Biography	To represent name types.
Event	`event:`	LINCS Event Vocabulary	To represent event types
Identity	`identity:`	LINCS Identity Vocabulary	To represent people's identities
Lexvo	`lexvo:`	Lexvo	To represent languages
Occupation	`occupation:`	LINCS Occupation Vocabulary	To represent people's occupations
XSD	`xsd:`	XML Schema Datatypes	For literal datatypes

Authority Files

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

Acronym	Prefix	Authority	Purpose
Census	N/A	LAC – Census of Canada	Source of URIs for Census entries
DCB	N/A	Dictionary of Canadian Biography	Source of URIs for DCB biographies
GeoNames	`geo:`	GeoNames	Authority for place URIs
LINCS	`lincs:`	LINCS-minted entities	To represent any entities not described elsewhere.
VIAF	`viaf:`	Virtual International Authority File	Authority for people and group URIs
Wikidata	`wikidata:`	Wikidata Knowledge Base	Authority for people, group, place, and occupation type URIs

Main Classes

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

Entity Type	Class	Declaration Snippet (Turtle Syntax)
Person	E21 Person	`<person> a crm:E21_Person .`
Birth	E67 Birth	`<creation> a crm:E67_Birth .`
Death	E69 Death	`<death> a crm:E69_Death .`
Occupation	E7 Activity	`<occupation> a crm:E7_Activity ; crm:P2_has_type event:OccupationEvent . crm:P2_has_type <occupation_type> .`
Nationality	E55 Type	`<nationality> a crm:E55_Type .`
Marriage	E85 Joining	`<marriage> a crm:E85_Joining .`
Group	E74 Group	`<group> a crm:E74_Group .`
Joining	E85 Joining	`<joining> a crm:E85_Joining .`
DCB Biography	D1 Digital Object (CRMdig)	`<dcb_biography> a crmdig:D1_Digital_Object .`
Census	E73 Information Object	`<census> a crm:E73_Information_Object .`
Census Entry (original)	E73 Information Object	`<census_entry_digital> a crm:E73_Information_Object .`
Census Entry (digital)	D1 Digital Object (CRMdig)	`<census_entry_original> a crmdig:D1_Digital_Object .`
Archival Fonds	D1 Digital Object (CRMdig)	`<fonds> a crmdig:D1_Digital_Object ; crm:P2_has_type aat:300189759 .`
Type	E55 Type	`<type> a crm:E55_Type .`
Identifier	E42 Identifier	`<identifier> a crm:E42_Identifier ; crm:P2_has_type <identifier_type> .`
Name or Title	E33 E41 Linguistic Appellation	`<name_title> a crm:E33_E41_Linguistic_Appellation ; crm:P2_has_type <name_title_type> .`
Place	E53 Place	`<place> a crm:E53_Place .`
Attribute Assignment	E13 Attribute Assignment	`<annotation> a crm:E13_Attribute_Assignment .`
Annotation	Annotation (OA)	`<annotation> a oa:Annotation .`

Overview

The Historical Canadian Persons dataset is a collection of biographical entries about Canadian people. This dataset is part of the Canadian History project along with the Cabinet Conclusions and Historical Indian Affairs Agents datasets. See the respective application profiles for more information.

The image below shows an overview of the entire Historical Canadian Persons 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.

Graph Patterns

This section presents the graph patterns adopted in the Historical Canadian Persons application profile, along with examples of usage. The URI of the Historical Canadian Persons graph which can be used to query the dataset through the LINCS SPARQL endpoint is <http://graph.lincsproject.ca/hist-canada/hist-cdns>.

Basic Patterns

This section describes basic patterns that are reused across the Historical Canadian Persons dataset.

Type

An entity may have one or more types.

Diagram
Pattern	Definition	An entity has a type.
	Abstraction	`E1 CRM Entity` → `P2 has type` → `E55 Type`
	Applies to	Archival Fonds. Every fonds has exactly one type. DCB Biography. Every biography has one or more types. Identifier. Every identifier has one or more types. Name & Title. Every name or title has one or more types. Occupation. Every occupation has one or more types. Census Entry. Every census entry has exactly one type.
Values	Type of Value	Uniform Resource Identifier (URI).
	Expected Value	A URI that uniquely identifies the type.
	Authorities	AAT for archival fonds. All fonds have type `aat:300189759`. Biography for name types. Personal names have type `biography:personalName`. Group names have type `biography:groupName`. Event. All occupation activities are assigned type `event:OccupationEvent`. Occupation or Wikidata for the specific occupation type. Wikidata and LINCS for DCB biographies. All entries have type `wikidata:Q36774` and `lincs:wsm2kZqipdq`.
Examples	Typical Example	The occupation event `Educator activity of Margaret Eleanor Theodora Addison` has types `event:OccupationEvent`, `occupation:teacher`, and `wikidata:Q974144` (educator).
Examples	Example Abstraction	`lincs:oHXurMklPkF` → `P2 has type` → `event:OccupationEvent` , `occupation:teacher` , `wikidata:Q974144`
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>" .`
Sample Data (Turtle)	`lincs:oHXurMklPkF a crm:E7_Activity ; rdfs:label "Educator activity of Margaret Eleanor Theodora Addison"@en ; crm:P2_has_type event:OccupationEvent , occupation:teacher , wikidata:Q974144 . event:OccupationEvent a crm:E55_Type ; rdfs:label "Occupation Event"@en . occupation:teacher a crm:E55_Type ; rdfs:label "Teacher"@en. wikidata:Q974144 a crm:E55_Type ; rdfs:label "educator"@en.`
Note	The `E1 CRM Entity` class represents all entities, but it is not actually found in the dataset. More specific classes are applied instead (see Main Classes above).

Identifier

An entity may have one or more identifiers.

Diagram
Pattern	Definition	An entity is identified by an ID.
	Abstraction	`E1 CRM Entity` → `P1 is identified by` → `E42 Identifier` → `P190 has symbolic content` → `xsd:integer`
	Applies to	Census Entry. Every census entry has exactly one ID.
Values	Type of Value	`xsd:integer` (a positive integer number).
	Expected Value	A number that uniquely identifies the entity.
	Authorities	XSD for the datatype. LINCS for the identifier type.
Examples	Typical Example	The digital census entry for Nellie McClung has identifier `84905311`.
Examples	Example Abstraction	`<http://central.bac-lac.gc.ca/.redirect?app=census&id=84905311&lang=eng&ecopy=e011748999>` → `P1 is identified by` → `lincs:bijJo1lPRz9` → `P190 has symbolic content` → `84905311`
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>" ; crm:P190_has_symbolic_content "<value>"^^xsd:integer .`
Sample Data (Turtle)	`<http://central.bac-lac.gc.ca/.redirect?app=census&id=84905311&lang=eng&ecopy=e011748999> a crmdig:D1_Digital_Object ; rdfs:label "LAC 1931 census record for Nellie McClung"@en ; crm:P1_is_identified_by lincs:bijJo1lPRz9 . lincs:bijJo1lPRz9 a crm:E42_Identifier ; rdfs:label "Item ID number of LAC 1931 census record for Nellie McClung"@en ; crm:P190_has_symbolic_content "84905311"^^xsd:integer .`
Note	The `E1 CRM Entity` class represents all entities, but is not actually found in the dataset. More specific classes are applied instead (see Main Classes above).

Name & Title

An entity may have a name or title.

Diagram
Pattern	Definition	An entity is identified by an appellation (name or title).
	Abstraction	`E1 CRM Entity` → `P1 is identified by` → `E33 E41 Linguistic Appellation` → `P190 has symbolic content` → `xsd:string`
	Applies to	DCB Biography. Every biography has exactly one title. Person. Every person has at least one name. Place. Every place has at least one name.
Values	Type of Value	`xsd:string` (a string of text).
	Expected Value	A string of text that identifies the entity.
	Authorities	XSD< for the datatype. LINCS for the appellation type.
Examples	Typical Example	Henry Pahtahquahong Chase is identified by the name `Henry Pahtahquahong Chase`
Examples	Example Abstraction	`lincs:al2hyO3z6h5` → `P1 is identified by` → `lincs:CwN0eBlbkEC` → `P190 has symbolic content` → `"Henry Pahtahquahong Chase"@en`
Generalized Pattern (Turtle)	`<entity> a crm:E1_CRM_Entity ; rdfs:label "<entity>"@en ; crm:P1_is_identified_by <name_or_title> . <name_or_title> a crm:E33_E41_Linguistic_Appellation ; rdfs:label "<name_or_title>"@en ; crm:P190_has_symbolic_content "<value>"@en .`
Sample Data (Turtle)	`lincs:al2hyO3z6h5 a E21_Person ; rdfs:label "Henry Pahtahquahong Chase"@en ; crm:P1_is_identified_by lincs:CwN0eBlbkEC . lincs:CwN0eBlbkEC a crm:E33_E41_Linguistic_Appellation ; rdfs:label "Name of Henry Pahtahquahong Chase"@en ; crm:P190_has_symbolic_content "Henry Pahtahquahong Chase"@en .`

Location

An event happens at a location.

Diagram
Pattern	Definition	An event happens at a location.
	Abstraction	`E5 Event` → `P7 took place at` → `E53 Place`
	Applies to	Birth. Every birth happens at exactly one location. Death. Every death happens at exactly one location.
Values	Type of Value	A URI uniquely identifying the place.
	Expected Value	Uniform Resource Identifier (URI).
	Authorities	GeoNames for the place URI.
Examples	Typical Example	The birth of Aatsista-Mahkan happened at a Blackfoot camp in the region currently known as Central Alberta.
Examples	Example Abstraction	`lincs:Gst4HSToaV1` → `P7 took place at` → `wikidata:Q189917`
Generalized Pattern (Turtle)	`<event> a crm:E5_Event ; rdfs:label "<event>" ; crm:P7_took_place_at <place> . <place> a crm:E53_Place ; rdfs:label "<place>" .`
Sample Data (Turtle)	`lincs:Gst4HSToaV1 a crm:E67_Birth ; rdfs:label "Birth event of Aatsista-Mahkan"@en ; crm:P7_took_place_at wikidata:Q189917 . wikidata:Q189917 a crm:E53_Place ; rdfs:label "a Blackfoot camp in Central Alberta"@en .`

Date

An event happens on a date.

Diagram
Diagram (Uncertainty)
Pattern	Definition	An event happens on a certain date (or date range).
	Abstraction	`E5 Event` → `P4 has time-span` → `E52 Time-Span` → `P82 at some time within` → `xsd:string` `P82a begin of the begin` → `xsd:dateTime` `P82b end of the end` → `xsd:dateTime`
	Applies to	Birth. Every birth happens on a certain date (or date range). Death. Every death happens on a certain date (or date range).
Values	Type of Value	`xsd: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 Value	A 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.
	Authorities	XSD for the datatypes.
Examples	Typical Example	The death of Harriet Brooks happened on 17 April 1933.
Examples	Example Abstraction	`lincs:S8hHGt527m9` → `P4 has time-span` → `lincs:ldAsWqNfHGu` → `P82 at some time within` → `"17 April 1933"@en` `P82a begin of the begin` → `"1933-04-17T00:00:00.000Z"` `P82b end of the end` → `"1933-04-17T23:59:59.000Z"`
Generalized Pattern (Turtle)	`<event> a crm:E5_Event ; rdfs:label "<event>" ; crm:P4_has_time_span <time_span> . <time_span> a crm:E52_Time_Span ; rdfs:label "<time_span>" ; crm:P82_at_some_time_within "<date>" ; crm:P82a_begin_of_the_begin "<begin>"^^xsd:dateTime ; crm:P82b_end_of_the_end "<end>"^^xsd:dateTime .`
Sample Data (Turtle)	`lincs:S8hHGt527m9 a crm:E69_Death ; rdfs:label "Death event of Harriet Brooks"@en ; crm:P4_has_time_span lincs:ldAsWqNfHGu . lincs:ldAsWqNfHGu a crm:E52_Time_Span ; rdfs:label "Death date of Harriet Brooks"@en ; crm:P82_at_some_time_within "17 April 1933"@en ; crm:P82a_begin_of_the_begin "1933-04-17T00:00:00.000Z"^^xsd:dateTime ; crm:P82b_end_of_the_end "1933-04-17T23:59:59.000Z"^^xsd:dateTime .`

Subject

An information object is about a subject.

Diagram
Pattern	Definition	An information object (including digital objects) is about a subject.
	Abstraction	`E73 Information object` → `P129 is about` → `E1 CRM Entity`
	Applies to	Census Entry. Each census entry is about a subject (a person). DCB Biography. Each DCB biography is about a subject (a person). Archival Fonds. Each archival fonds is about one or more subjects.
Values	Type of Value	Uniform Resource Identifier (URI).
	Expected Value	A URI that identifies the entity that the information object is about.
	Authorities	Any of the authorities listed in the Vocabularies & Authorities section.
Examples	Typical Example	The English DCB biography about Ottawa Chief Pontiac is about Pontiac.
Examples	Example Abstraction	`<http://www.biographi.ca/en/bio/pontiac_3E.html>` → `P129 is about` → `viaf:52980155`
Generalized Pattern (Turtle)	`<information_object> a crm:E73_Information_Object ; rdfs:label "<information_object>" ; crm:P129_is_about <entity> . <entity> a crm:E1_CRM_Entity ; rdfs:label "<entity>" .`
Sample Data (Turtle)	`<http://www.biographi.ca/en/bio/pontiac_3E.html> a crmdig:Digital_Object, crm:E33_Linguistic_Object ; rdfs:label "English DCB biography of Pontiac"@en ; crm:P129_is_about viaf:52980155 . viaf:52980155 a crm:E21_Person ; rdfs:label "Pontiac"@en .`
Note	This pattern is used only for the primary subject(s) of the information object. For other entities that are mentioned in the information object, see Mention below.

Mention

An information object may mention one or more entities.

Diagram
Pattern	Definition	An information object (including digital objects) mentions an entity.
	Abstraction	`E73 Information object` → `P67 refers to` → `E1 CRM Entity`
	Applies to	DCB Biography. Each DCB biography may mention one or more entities. Archival Fonds. Each archival fonds may mention one or more entities.
Values	Type of Value	Uniform Resource Identifier (URI).
	Expected Value	A URI that identifies the entity that the information object mentions.
	Authorities	Any of the authorities listed in the Vocabularies & Authorities section.
Examples	Typical Example	The French DCB biography of Thomas Dermer mentions Tisquantum.
Examples	Example Abstraction	`<http://www.biographi.ca/fr/bio/dermer_thomas_1F.html>` → `P67 refers to` → `viaf:3631690`
Generalized Pattern (Turtle)	`<information_object> a crm:E73_Information_Object ; rdfs:label "<information_object>" ; crm:P67_refers_to <entity> . <entity> a crm:E1_CRM_Entity ; rdfs:label "<entity>" .`
Sample Data (Turtle)	`<http://www.biographi.ca/fr/bio/dermer_thomas_1F.html> a crmdig:Digital_Object, crm:E33_Linguistic_Object ; rdfs:label "French DCB biography of Thomas Dermer"@en ; crm:P67_refers_to viaf:3631690 . viaf:3631690 a crm:E21_Person ; rdfs:label "Tisquantum"@en .`
Note	This pattern is used for all entities that are mentioned in the information object, except its primary subject(s). For the representation of the primary subject(s), see Subject above.

Attribute Assignment

An attribute assignment assigns an attribute to a certain entity, optionally with a certain level of uncertainty.

Diagram
Pattern	Definition	An attribute assignment assigns an attribute to an entity.
	Abstraction	`E13 Attribute Assignment` → `P140 assigned attribute to` → `E1 CRM Entity` `P140 assigned` → `E1 CRM Entity` `P2 has type` → `E55 Type`
	Applies to	Person. A person may be assigned a gender (activity) and an address (appellation). Birth. A birth event may be assigned an uncertain date.
Values	Type of Value	Uniform Resource Identifier (URI).
	Expected Value	A URI that identifies the assigned attribute.
	Authorities	Any of the authorities listed in the Vocabularies & Authorities section.
Examples	Typical Example	Sara Mickle is assigned the gender identity `woman`.
Examples	Example Abstraction	`lincs:01ME4Yj8PqI` → `P140 assigned attribute to` → `lincs:ajQMBveBmmV` `P141 assigned` → `lincs:Vxn4Hs876yl`
Generalized Pattern (Turtle)	`<attribute_assignment> a crm:E13_Attribute_Assignment ; rdfs:label "<attribute_assignment>" ; crm:P140_assigned_attribute_to <entity> ; crm:P141_assigned <attribute> . <entity> a crm:E1_CRM_Entity ; rdfs:label "<entity>" . <attribute> a crm:E1_CRM_Entity ; rdfs:label "<attribute>" .`
Sample Data (Turtle)	`lincs:01ME4Yj8PqI a crm:E13_Attribute_Assignment ; rdfs:label "Sara Mickle - Gender Context - Assigning"@en ; crm:P140_assigned_attribute_to lincs:ajQMBveBmmV ; crm:P141_assigned lincs:Vxn4Hs876yl . lincs:ajQMBveBmmV a crm:E1_CRM_Entity ; rdfs:label "Sara Mickle"@en . lincs:Vxn4Hs876yl a crm:E1_CRM_Entity ; rdfs:label "Sara Mickle - Gender Label Connection"@en ; crm:P2_has_type event:GenderEvent ; crm:P16_used_specific_object identity:woman .`

Person

In this dataset, a person is an individual who is described in one or more biographies within the Dictionary of Canadian Biography. Each person has a name, a birth, a death (if no longer living), and may have one or more occupations. A person may be a member of one or more groups across their life. A person may also have one or more nationalities and one or more marriages.

Name

Each person has a name.

Diagram
Note	The modelling of person names follows the basic pattern for Names & Titles. See the corresponding section for more information.

Birth

Each person has a birth.

Diagram
Pattern	Definition	A person is born through a birth event.
	Abstraction	`E21_Person` → `P98i_was_born` → `E67_Birth`
	Applies to	Person. Every person has exactly one birth.
Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	A URI uniquely identifying the birth event.
	Example Values	`lincs:M6L8WldHvEF` (Birth event of Pītikwahanapiwīyin)
Examples	Typical Example	Pītikwahanapiwīyin was born in 1842 in Saskatchewan.
	Example Abstraction	`viaf:106198432` → `P98i_was_born` → `lincs:M6L8WldHvEF`
	Generalized Pattern (Turtle)	`<person> a crm:E21_Person ; rdfs:label "<person>" . <birth> a crm:E67_Birth ; rdfs:label "<birth>" ; crm:P98_brought_into_life <person> .`
	Sample Data (Turtle)	`viaf:106198432 a crm:E21_Person ; rdfs:label "Pītikwahanapiwīyin"@en . lincs:M6L8WldHvEF a crm:E67_Birth ; rdfs:label "Birth event of Pītikwahanapiwīyin"@en ; crm:P98_brought_into_life viaf:106198432 .`

Birth Place

Each birth happened in a certain place.

Diagram
Note	The modelling of birth places follows the Location basic pattern. See the corresponding section for more information.
Diagram (Uncertain Place)
Note	The modelling of uncertain birth places follows the Location basic pattern combined with the Attribute Assignment basic pattern. See the corresponding sections for more information.

Birth Date

Each birth happened on a certain date.

Diagram
Note	The modelling of birth dates follows the Date basic pattern. See the corresponding section for more information.

Uncertain Birth Date

The date of birth may be uncertain.

Diagram
Note	The modelling of uncertain birth dates follows the Date basic pattern combined with the Attribute Assignment basic pattern. See the corresponding sections for more information.

Death

A person may have a death.

Diagram
Pattern	Definition	A person dies through a death event.
	Abstraction	`E21_Person` → `P100i_died_in` → `E69_Death`
	Applies to	Person. Every person has at most one death.
Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	A URI uniquely identifying the death event.
	Example Values	`lincs:9a47YuJqe8Z` (Death event of Pītikwahanapiwīyin)
Examples	Typical Example	Pītikwahanapiwīyin died on 4 July 1886 at Blackfoot Crossing.
	Example Abstraction	`viaf:106198432` → `P100i_died_in` → `lincs:9a47YuJqe8Z`
	Generalized Pattern (Turtle)	`<person> a crm:E21_Person ; rdfs:label "<person>" . <death> a crm:E69_Death ; rdfs:label "<death>" ; crm:P100_was_death_of <person> .`
	Sample Data (Turtle)	`viaf:106198432 a crm:E21_Person ; rdfs:label "Pītikwahanapiwīyin"@en . lincs:9a47YuJqe8Z a crm:E69_Death ; rdfs:label "Death event of Pītikwahanapiwīyin"@en ; crm:P100_was_death_of viaf:106198432 .`

Death Place

Each death happened in a certain place.

Diagram
Note	The modelling of death places follows the Location basic pattern. See the corresponding section for more information.

Death Date

Each death happened on a certain date.

Diagram
Note	The modelling of death dates follows the basic pattern for Event Dates. See the corresponding section for more information.

Occupation

A person may have an occupation.

Diagram
Pattern	Definition	A person may have an occupation.
	Abstraction	`E21_Person` → `P14i_performed` → `E7_Activity`
	Applies to	Person. A person may have one or more occupations.
Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	A URI uniquely identifying the occupation activity.
	Example Values	`lincs:ixy8JKwjb4l` (author activity of Maude Elizabeth Seymour Abbott)
Examples	Typical Example	Maude Elizabeth Seymour Abbott was an author.
Examples	Example Abstraction	`viaf:74657198` → `P14i_performed` → `lincs:ixy8JKwjb4l`
Generalized Pattern (Turtle)	`<person> a crm:E21_Person ; rdfs:label "<person>" . <occupation> a crm:E7_Activity ; rdfs:label "<occupation>" ; crm:P14_carried_out_by <person> .`
Sample Data (Turtle)	`viaf:74657198 a crm:E21_Person ; rdfs:label "Maude Elizabeth Seymour Abbott"@en . lincs:ixy8JKwjb4l a crm:E7_Activity ; rdfs:label "author activity of Maude Elizabeth Seymour Abbott"@en ; crm:P14_carried_out_by viaf:74657198 .`
Note	Ministerial posts follow the same pattern as occupations and are modelled in the same way.

Occupation Type

Each occupation has a type.

Diagram
Note	The modelling of occupation types follows the basic pattern for Types. Each occupation is assigned type `event:OccupationEvent`, a more specific type from the LINCS Occupation Vocabulary, and optionally an additional type from Wikidata.

Group Membership

Each person may be a member of one or more groups.

Diagram
Pattern	Definition	A person may be part of a group.
	Abstraction	`E21 Person` → `P143i was joined by` → `E85 Joining` → `P144 joined with` → `E74 Group`
	Applies to	Person. A person may join one or more groups.
Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	A URI uniquely identifying the joining event. A URI uniquely identifying the group.
	Example Values	`lincs:C4heU41JGFZ` (joining event) `lincs:S6WsTFZEbDE` (group)
Examples	Typical Example	Margaret Ann Woodruff married with Samuel Zimmerman in August 1848.
	Example Abstraction	`lincs:HwsAIsQnTi4` → `P143i was joined by` → `lincs:C4heU41JGFZ` → `P144 joined with` → `lincs:S6WsTFZEbDE`
	Generalized Pattern (Turtle)	`<person> a crm:E21_Person ; rdfs:label "<person>" . <group> a crm:E74_Group ; rdfs:label "<group>" . <joining> a crm:E85_Joining ; rdfs:label "<joining>" ; crm:P143_joined <person> ; crm:P144_joined_with <group> .`
	Sample Data (Turtle)	`lincs:HwsAIsQnTi4 a crm:E21_Person ; rdfs:label "Margaret Ann Woodruff"@en . lincs:S6WsTFZEbDE a crm:E74_Group ; rdfs:label "Marriage between Margaret Ann Woodruff and Samuel Zimmerman"@en . lincs:C4heU41JGFZ a crm:E85_Joining ; rdfs:label "Marriage between Margaret Ann Woodruff and Samuel Zimmerman"@en ; crm:P143_joined lincs:HwsAIsQnTi4 ; crm:P144_joined_with lincs:S6WsTFZEbDE .`

Marriage

Each person may have been married one or more times.

Diagram
Note	In this dataset, marriage is modelled as a particular type of Group Membership. The marriage date is represented through the Date basic pattern. The marriage place is represented through the Location basic pattern. See the corresponding sections for more information.

Gender

Each person may have a gender.

Note	The modelling of genders follows the Attribute Assignment basic pattern, where the gender is modelled as an activity assigned to a person. See the corresponding section for more information.

Address

Each person may have an address.

Note	The modelling of addresses follows the Attribute Assignment basic pattern, where the address is modelled as an appellation assigned to a person. See the corresponding section for more information.

DCB Biography

A DCB biography is a webpage that reports biographical data about a historical Canadian person described in the Dictionary of Canadian Biography. DCB biographies are available in both English and French language.

Biography Language

Each DCB biography is written in a specific language.

Diagram
Pattern	Definition	A DCB biography is written in a language.
Pattern	Abstraction	`E33_Linguistic_Object`→ `P72_has_language`→ `E56_Language`
Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	A URI representing the language.
	Applies to	DCB Biography. Every DCB biography is written in exactly one language. If multiple language versions exist, these are considered separate biographies.
	Example Values	`<http://www.biographi.ca/en/bio/alikomiak_15E.html>`
Examples	Typical Example	The English DCB biography about Alikomiak is written in English.
	Example Abstraction	`<http://www.biographi.ca/en/bio/alikomiak_15E.html>` → `P72_has_language`→ `lexvo:eng`
	Generalized Pattern (Turtle)	`<dcb_biography> a crmdig:D1_Digital_Object, crm:E33_Linguistic_Object ; rdfs:label "<dcb_biography>" ; crm:P72_has_language <language> . <language> a crm:E56_Language ; rdfs:label "<language>" .`
	Sample Data (Turtle)	`<http://www.biographi.ca/en/bio/alikomiak_15E.html> a crmdig:D1_Digital_Object, crm:E33_Linguistic_Object ; rdfs:label "English DCB biography of Alikomiak"@en ; crm:P72_has_language lexvo:eng . lexvo:eng a crm:E56_Language ; rdfs:label "English"@en .`

Biography Subject

Each DCB biography is about a specific subject (a person).

Diagram
Note	The modelling of DCB biography subjects (i.e., the main person described in the biography) follows the basic pattern for Subjects. See the corresponding section for more information. Note that the subject of a DCB biography is always a person.

Biography Mention

Each DCB biography may mention one or more entities (persons, places, events, etc.).

Diagram
Note	The modelling of DCB biography mentions, applied to any entities mentioned in it except the main subject(s), follows the basic pattern for Mentions. See the corresponding section for more information. Note that mentioned entities are not only persons.

Annotation

Each annotation connects a specific string of text found in a DCB biography (the annotation target) to the entity that it refers to (the annotation body). For example, the name of a person may be annotated to connect it to the corresponding person entity.

Diagram
Pattern	Definition	An annotation expresses the fact that a string of text refers to a certain entity.
	Abstraction	`E33_Linguistic_Object` → `P106_is_composed_of` → `E73_Information_Object` → `P190_has_symbolic_content` → `xsd:string` `P67_refers_to` → `E1_CRM_Entity` `oa:Annotation` → `oa:hasTarget` → `E73_Information_Object` `oa:hasBody` → `E1_CRM_Entity` `oa:motivatedBy` → `oa:Motivation`
	Applies to	DCB Biography. Every DCB biography may be annotated to connect a string of text contained in it to the entity that it references.
Values	Type of Value	Uniform Resource Identifier (annotated text fragment) Uniform Resource Identifier (mentioned entity)
	Expected Value	A string of text (annotated text fragment) A URI that identifies the entity (mentioned entity)
	Example Values	`lincs:SO5s1S899Y6` (the string of text `Arnold`) `viaf:35249982` (the person named `Benedict Arnold`)
Examples	Typical Example	The annotation `lincs:01OTD7mnqaU` identifies the fragment of text `Arnold` in a DCB biography as referring to the person `viaf:35249982` (Benedict Arnold).
	Example Abstraction	`<http://www.biographi.ca/en/bio/panet_pierre_5E.html>` → `P106_is_composed_of` → `lincs:SO5s1S899Y6` → `P190_has_symbolic_content` → `"Arnold"@en` `P67_refers_to` → `viaf:35249982` `lincs:01OTD7mnqaU` → `oa:hasTarget` → `lincs:SO5s1S899Y6` `oa:hasBody` → `viaf:35249982` `oa:motivatedBy` → `oa:identifying`
	Generalized Pattern (Turtle)	<annotation> a oa:Annotation ; rdfs:label "<annotation>" ; oa:hasBody <body> ; oa:hasTarget <target> ; oa:motivatedBy <motivation> . <body> a crm:E1_CRM_Entity ; rdfs:label "<body>" . <target> a crm:E73_Information_Object, oa:SpecificResource ; rdfs:label "<target>" ; crm:P190_has_symbolic_content "<annotated_text>" ; crm:P67_refers_to <body> ; oa:hasSource <dcb_biography> . <motivation> a oa:Motivation ; rdfs:label "<motivation>" . <dcb_biography> a crmdig:D1_Digital_Object, crm:E33_Linguistic_Object ; rdfs:label "<dcb_biography>" ; crm:P106_is_composed_of <target> .
	Sample Data (Turtle)	lincs:01OTD7mnqaU a oa:Annotation ; rdfs:label "Arnold identifying Benedict Arnold in the DCB biography of Pierre Panet"@en ; oa:hasBody viaf:35249982 ; oa:hasTarget lincs:SO5s1S899Y6 ; oa:motivatedBy oa:identifying . viaf:35249982 a crm:E21_Person; rdfs:label "Benedict Arnold"@en . lincs:SO5s1S899Y6 a crm:E73_Information_Object, oa:SpecificResource ; rdfs:label "English DCB biography of Pierre Panet containing Arnold" ; crm:P190_has_symbolic_content "Arnold"@en ; crm:P67_refers_to viaf:35249982 ; oa:hasSource <http://www.biographi.ca/en/bio/panet_pierre_5E.html> . oa:identifying a oa:Motivation ; rdfs:label "identifying"@en . <http://www.biographi.ca/en/bio/panet_pierre_5E.html> a crmdig:D1_Digital_Object, crm:E33_Linguistic_Object ; rdfs:label "<dcb_biography>" ; crm:P106_is_composed_of lincs:SO5s1S899Y6.
Note	See the LINCS Web Annotation documentation for more detailed information about this pattern.

Census

The census is an information object composed of a number of original census entries. Some of these entries have been digitized into digital census entries.

Creation

The census is created by a creation event.

Diagram
Pattern	Definition	The census is created by a creation event.
Pattern	Abstraction	`E73_Information_Object` → `P94_was_created_by` → `E65_Creation`
Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	A URI that uniquely identifies the creation event.
	Applies to	Census. Every census is created by a creation event.
	Example Values	`lincs:bEOb7qRpLUk`
Examples	Typical Example	The 1921 Census of Canada was created on 1 June 1921.
	Example Abstraction	`lincs:csyObFwNvT6` → `P94_was_created_by` → `lincs:bEOb7qRpLUk`
	Generalized Pattern (Turtle)	`<census> a crm:E73_Information_Object ; rdfs:label "<census>" . <census_creation> a crm:E56_Creation ; rdfs:label "<census_creation>" ; crm:P94_created <census> .`
	Sample Data (Turtle)	`lincs:csyObFwNvT6 a crm:E73_Information_Object ; rdfs:label "1921 Census of Canada"@en . lincs:bEOb7qRpLUk a crm:E56_Creation ; rdfs:label "Creation of 1921 Census of Canada"@en ; crm:P94_created lincs:csyObFwNvT6 .`

Creation Date

The creation of the census happens on a date.

Diagram
Note	The modelling of census creation dates follows the Date basic pattern. See the corresponding section for more information.

Census Entry

The census is composed of census entries. The dataset distinguishes between original census entries and digital census entries (i.e., digitized versions of original census entries).

Diagram
Pattern	Definition	The census is composed of census entries, which may or may not have been digitized.
Pattern	Abstraction	`E73_Information_Object` → `P106_is_composed_of` → `P130i_features_are_also_found_on` → `E73_Information_Object`
Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	A URI that uniquely represents the original census entry. A URI that uniquely represents the digital census entry.
	Applies to	Census. Every census is composed of many census entries.
	Example Values	`lincs:n6udczR1bIQ` (original) `<http://central.bac-lac.gc.ca/.redirect?app=census&id=42511930&lang=eng&ecopy=31228_4363979-00771>` (digital)
Examples	Typical Example	The 1916 Census of the Prairie Provinces contains an entry about Nellie McClung, which has been digitized.
	Example Abstraction	`lincs:i8vXEzzIRPl` → `P106_is_composed_of` → `lincs:n6udczR1bIQ` → `P130i_features_are_also_found_on` → `<http://central.bac-lac.gc.ca/.redirect?app=census&id=42511930&lang=eng&ecopy=31228_4363979-00771>`
	Generalized Pattern (Turtle)	`<census> a crm:E73_Information_Object ; rdfs:label "<census>" ; crm:P106_is_composed_of <original_census_entry> . <original_census_entry> a crm:E73_Information_Object ; rdfs:label "<original_census_entry>" . <digital_census_entry> a crmdig:D1_Digital_Object ; rdfs:label "<digital_census_entry>" ; crm:P130_shows_features_of <original_census_entry> .`
	Sample Data (Turtle)	`lincs:i8vXEzzIRPl a crm:E73_Information_Object ; rdfs:label "1916 Census of the Prairie Provinces"@en ; crm:P106_is_composed_of lincs:n6udczR1bIQ . lincs:n6udczR1bIQ a crm:E73_Information_Object ; rdfs:label "1916 census entry for Nellie McClung"@en . <http://central.bac-lac.gc.ca/.redirect?app=census&id=42511930&lang=eng&ecopy=31228_4363979-00771> a crmdig:D1_Digital_Object ; rdfs:label "LAC 1916 census record for Nellie McClung"@en ; crm:P130_shows_features_of lincs:n6udczR1bIQ .`

Entry Identifier

Each census entry has a unique identifier.

Diagram
Note	The modelling of census entry identifiers follows the basic pattern for Identifiers. See the corresponding section for more information.

Entry Subject

Each census entry is about a subject (a person).

Diagram
Note	The modelling of census entry identifiers follows the basic pattern for Identifiers. See the corresponding section for more information.

Entry Title

Each census entry has a title.

Diagram
Note	The modelling of census entry titles follows the basic pattern for Names & Titles. See the corresponding section for more information.

Archival Fonds

An archival fonds is an information object that contains information about historical Canadian people. Each archival fonds has a title and one or more subjects. Each archival fonds may also mentions one or more entities different from the subject(s).

Fonds Subject

Each archival fonds is about one or more subjects.

Diagram
Note	The modelling of archival fonds subjects, i.e., the primary subject(s) of the fonds, follows the basic pattern for Subjects. See the corresponding section for more information.

Fonds Mention

Each archival fonds may mention one or more entities.

Diagram
Note	The modelling of archival fonds subjects, i.e., any entity described in the archival fonds except the subject(s), follows the basic pattern for Mentions. See the corresponding section for more information.

Fonds Title

Each archival fonds has a title.

Diagram
Note	The modelling of archival fonds titles follows the basic pattern for Names & Titles. See the corresponding section for more information.

Place

In this dataset, a place is a geographic location that can be identified by coordinates.

Name

Diagram
Note	The modelling of place names follows the basic pattern for Names & Titles, augmented with the basic pattern for Attribute Assignments wherever necessary. See the corresponding sections for more information.

Coordinates

A place may be identified by geographic coordinates (latitude and longitude).

Diagram
Pattern	Definition	A place is identified by a geographic reference such as coordinates.
Pattern	Abstraction	`E53 Place` → `P168 place is defined by` → `xsd:string`
Values	Type of Value	`xsd:string`
	Expected Value	A string of text representing geographic coordinates (latitude and longitude).
	Authorities	GeoNames for the place URI. Wikidata and GeoNames as sources of coordinates.
	Example Value	`POINT(-63.29844 46.39808)` (coordinates of Prince Edward Island)
Examples	Typical Example	Prince Edward Island has latitude `46.39808` and longitude `-63.29844`
Examples	Example Abstraction	`geonames:6113358` → `P168_has_spatial_coordinates` → `POINT(-63.29844 46.39808)`

Spatial Containment

A place may fall within another place.

Diagram
Pattern	Definition	A place may fall within another place.
	Abstraction	`E53 Place` → `P86 falls within` → `E53 Place`
	Applies to	Place. A place may fall within one or more places.
Values	Type of Value	`xsd:string`
	Expected Value	A URI representing a place.
	Authorities	GeoNames for the place URI.
	Example Value	`geo:6113358` (Prince Edward Island)
Examples	Typical Example	Tyne Valley, Prince Edward Island falls within Prince Edward Island.
Examples	Example Abstraction	`geo:6171537` → `P86 falls within` → `geo:6113358`

Purpose​

Dependencies​

Ontologies​

Vocabularies​

Authority Files​

Main Classes​

Overview​

Graph Patterns​

Basic Patterns​

Type​

Identifier​

Name & Title​

Location​

Date​

Subject​

Mention​

Attribute Assignment​

Person​

Name​

Birth​

Birth Place​

Birth Date​

Uncertain Birth Date​

Death​

Death Place​

Death Date​

Occupation​

Occupation Type​

Group Membership​

Marriage​

Gender​

Address​

DCB Biography​

Biography Language​

Biography Subject​

Biography Mention​

Annotation​

Census​

Creation​

Creation Date​

Census Entry​

Entry Identifier​

Entry Subject​

Entry Title​

Archival Fonds​

Fonds Subject​

Fonds Mention​

Fonds Title​

Place​

Name​

Coordinates​

Spatial Containment​

Purpose

Dependencies

Ontologies

Vocabularies

Authority Files

Main Classes

Overview

Graph Patterns

Basic Patterns

Type

Identifier

Name & Title

Location

Date

Subject

Mention

Attribute Assignment

Person

Name

Birth

Birth Place

Birth Date

Uncertain Birth Date

Death

Death Place

Death Date

Occupation

Occupation Type

Group Membership

Marriage

Gender

Address

DCB Biography

Biography Language

Biography Subject

Biography Mention

Annotation

Census

Creation

Creation Date

Census Entry

Entry Identifier

Entry Subject

Entry Title

Archival Fonds

Fonds Subject

Fonds Mention

Fonds Title

Place

Name

Coordinates

Spatial Containment