Historical Canadians 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 Historical Canadians data is modelled for compatibility with the wider LINCS data model. This document provides patterns used in the mapping of Historical Canadians 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 Canadians 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 and vocabularies.

As part of the History of Canada project, the Historical Canadians 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 Canadians 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.

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
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 entries
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 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 .
Membership	E85 Joining	<joining> a crm:E85_Joining .
DCB Entry	D1 Digital Object (CRMdig)	<dcb_entry> a crmdig:D1_Digital_Object .
DCB Biography	E33 Linguistic Object	<image> a crm:E33_Linguistic_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 Canadians 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 Canadians 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

Basic Patterns

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

Type

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 Entry. Every entry has exactly one type. 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.
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 for DCB entries. All entries have type wikidata:Q36774.
Examples	Typical Example	The occupation event Educator activity of Margaret Eleanor Theodora Addison has types event:OccupationEvent, occupation:teacher, and wikidata:Q974144 (educator).
	Example Abstraction	<http://temp.lincsproject.ca/occupation/addison_margaret_eleanor_theodora_16/educator> → 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)	<http://temp.lincsproject.ca/occupation/addison_margaret_eleanor_theodora_16/educator> 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	Class 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
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.
Examples	Typical Example	The digital census entry for Nellie McClung has identifier 84905311.
	Example Abstraction	<http://central.bac-lac.gc.ca/.redirect?app=census&id=84905311&lang=eng&ecopy=e011748999> → P1 is identified by → <http://temp.lincsproject.ca/digital_census_entry/84905311/id> → 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 <http://temp.lincsproject.ca/digital_census_entry/84905311/id> . <http://temp.lincsproject.ca/digital_census_entry/84905311/id> 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	Class 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
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
	Example Abstraction	<http://temp.lincsproject.ca/dcb/chase_henry_pahtahquahong_12> → P1 is identified by → <http://temp.lincsproject.ca/personalname/henry_pahtahquahong_chase> → 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)	<http://temp.lincsproject.ca/dcb/chase_henry_pahtahquahong_12> a E21_Person ; rdfs:label "Henry Pahtahquahong Chase"@en ; crm:P1_is_identified_by <http://temp.lincsproject.ca/personalname/henry_pahtahquahong_chase> . <http://temp.lincsproject.ca/personalname/henry_pahtahquahong_chase> a crm:E33_E41_Linguistic_Appellation ; rdfs:label "Name of Henry Pahtahquahong Chase"@en ; crm:P190_has_symbolic_content "Henry Pahtahquahong Chase"@en .

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.
	Example Abstraction	<http://temp.lincsproject.ca/birth/aatsista_mahkan_14> → P7 took place at → <http://www.wikidata.org/entity/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)	<http://temp.lincsproject.ca/birth/aatsista_mahkan_14> a crm:E67_Birth ; rdfs:label "Birth event of Aatsista-Mahkan"@en ; crm:P7_took_place_at <http://www.wikidata.org/entity/Q189917> . <http://www.wikidata.org/entity/Q189917> a crm:E53_Place ; rdfs:label "a Blackfoot camp in Central Alberta"@en .

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.
	Example Abstraction	<http://temp.lincsproject.ca/death/brooks_harriet_16> → P4 has time-span → <http://temp.lincsproject.ca/death/brooks_harriet_16> → 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)	<http://temp.lincsproject.ca/death/brooks_harriet_16> a crm:E69_Death ; rdfs:label "Death event of Harriet Brooks"@en ; crm:P4_has_time_span <http://temp.lincsproject.ca/death/brooks_harriet_16> . <http://temp.lincsproject.ca/death/brooks_harriet_16> 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

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	Information Object (including Digital Object). An information object may be about an entity.
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 DCB biography of Ottawa Chief Pontiac is about Pontiac.
	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

Diagram
Pattern	Definition	An information object (including digital objects) mentions an entity.
	Abstraction	E73 Information object → P67 refers to → E1 CRM Entity
	Applies to	Information Object (including Digital Object). An information object may mention an entity.
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 DCB biography of Thomas Dermer mentions Tisquantum.
	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

Note

The section on attribute assignments is under construction.

Diagram
Pattern	Definition	An entity may be assigned an attribute, optionally with a certain level of uncertainty.
Note	To be completed.

Person

In this dataset, a person is an individual who is described in one or more Dictionary of Canadian Biography entries. 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

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

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	<http://temp.lincsproject.ca/birth/pitikwahanapiwiyin_11>
Examples	Typical Example	Pītikwahanapiwīyin was born in 1842 in Saskatchewan.
	Example Abstraction	viaf:106198432 → P98i_was_born → <http://temp.lincsproject.ca/birth/pitikwahanapiwiyin_11>
	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 "Pītikwahanapiwīyin"@en . <http://temp.lincsproject.ca/birth/pitikwahanapiwiyin_11> a crm:E67_Birth ; rdfs:label "Birth event of Pītikwahanapiwīyin"@en ; crm:P98_brought_into_life viaf:106198432 .

Birth 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

Diagram
Note	The modelling of birth dates follows the Date basic pattern. See the corresponding section for more information.
Diagram (Uncertain Date)
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

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	<http://temp.lincsproject.ca/death/pitikwahanapiwiyin_11>
Examples	Typical Example	Pītikwahanapiwīyin died on 4 July 1886 at Blackfoot Crossing.
	Example Abstraction	viaf:106198432 → P100i_died_in → <http://temp.lincsproject.ca/death/pitikwahanapiwiyin_11>
	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 "Pītikwahanapiwīyin"@en . <http://temp.lincsproject.ca/death/pitikwahanapiwiyin_11> a crm:E69_Death ; rdfs:label "Death event of Pītikwahanapiwīyin"@en ; crm:P100_was_death_of viaf:106198432 .

Death Place

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

Death Date

Diagram
Note	The modelling of death dates follows the basic pattern for Event Dates. See the corresponding section for more information.
Diagram (Uncertain Date)
Note	The modelling of uncertain death dates follows the basic pattern for Event Dates combined with the Attribute Assignment basic pattern. See the corresponding section for more information.

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	<http://temp.lincsproject.ca/occupation/abbott_maude_elizabeth_seymour_16/author>
Examples	Typical Example	Maude Elizabeth Seymour Abbott was an author.
	Example Abstraction	viaf:74657198 → P14i_performed → <http://temp.lincsproject.ca/occupation/abbott_maude_elizabeth_seymour_16/author>
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 . <http://temp.lincsproject.ca/occupation/abbott_maude_elizabeth_seymour_16/author> 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

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.

Membership

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	<http://temp.lincsproject.ca/marriage/zimmerman_samuel_8/margaret_ann_woodruff> (joining event) <http://temp.lincsproject.ca/marriage/zimmerman_samuel_8/margaret_ann_woodruff/group> (group)
Examples	Typical Example	Margaret Ann Woodruff joined the group Marriage of Margaret Ann Woodruff and Samuel Zimmerman in August 1848.
	Example Abstraction	<http://temp.lincsproject.ca/dcb/margaret_ann_woodruff> → P143i was joined by → <http://temp.lincsproject.ca/marriage/zimmerman_samuel_8/margaret_ann_woodruff> → P144 joined with → <http://temp.lincsproject.ca/marriage/zimmerman_samuel_8/margaret_ann_woodruff/group>

Marriage

Diagram
Note	In this dataset, marriage is modelled as a particular type of 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.

Nationality

Note

The section on nationality is under construction.

Diagram
Pattern	Definition	A person may be assigned a nationality by someone (including themselves).
	Abstraction	TBA
	Applies to	Person. Every person may be assigned one or more nationalities.
Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	A URI representing a nationality.
	Example Values	TBA
Examples	Typical Example	TBA
	Example Abstraction	TBA
Generalized Pattern (Turtle)	TBA
Sample Data (Turtle)	TBA

DCB Entry

A Dictionary of Canadian Biography entry is a webpage that reports biographical data about a historical Canadian person. Each DCB entry is primarily composed of a biography, which is the main text of the entry, but may include other information. The DCB entries are available in both English and French language.

DCB Biography

A DCB biography is the main text of a DCB entry and describes the life of the person.

Diagram
Pattern	Definition	A DCB entry is composed of a biography.
	Abstraction	D1_Digital_Object → P148_has_component → E33_Linguistic_Object→ P72_has_language→ E56_Language
Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	A URI representing the biography. A URI representing the language.
	Applies to	DCB Entry. Every DCB Entry has exactly one text (in one language). If multiple language versions exist, these are considered separate entries, each with its own text.
	Example Values	<http://www.biographi.ca/en/bio/alikomiak_15E.html>
Examples	Typical Example	The English DCB entry about Alikomiak is composed of the biography of Alikomiak.
	Example Abstraction	<TEMPORARY_URI> → P148_has_component → <http://www.biographi.ca/en/bio/alikomiak_15E.html>→ P72_has_language→ lexvo:eng

Entry Subject

Diagram
Note	The modelling of DCB entry 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 entry is always a person.

Entry Mention

Diagram
Note	The modelling of DCB entry 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

Note

The section on DCB entry annotations is under construction.

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:hasMotivation → oa:Motivation
	Applies to	DCB Entry. Every DCB entry may be annotated to connect a string of text contained in it to the entity that it references.
Values	Type of Value	xsd:string (annotated text) Uniform Resource Identifier (mentioned entity)
	Expected Value	a string of text (annotated text) a URI that identifies the mentioned entity (mentioned entity)
	Example Values	TBA
Examples	Typical Example	TBA
	Example Abstraction	TBA
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

Diagram
Pattern	Definition	The census is created by a creation event.
	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	<http://temp.lincsproject.ca/1921_census_canada/creation>
Examples	Typical Example	The 1921 Census of Canada was created on 1 June 1921.
	Example Abstraction	<http://temp.lincsproject.ca/1921_census_canada> → P94_was_created_by → <http://temp.lincsproject.ca/1921_census_canada/creation>

Creation Date

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

Census Entry

Diagram
Pattern	Definition	The census is composed of census entries, which may or may not have been digitized.
	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	<http://temp.lincsproject.ca/original_census_entry/42511930> (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	<http://temp.lincsproject.ca/original_census_entry/42511930> → P106_is_composed_of → P130i_features_are_also_found_on → <http://central.bac-lac.gc.ca/.redirect?app=census&id=42511930&lang=eng&ecopy=31228_4363979-00771>

Entry Identifier

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

Entry 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

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

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.

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

Diagram
Pattern	Definition	A place is identified by a geographic reference such as coordinates.
	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
	Example Abstraction	geonames:6113358 → P168_has_spatial_coordinates → POINT(-63.29844 46.39808)

Spatial Containment

Diagram
Pattern	Definition	A place may fall within another place.
	Abstraction	E53 Place → P89 falls within → E53 Place
Values	Type of Value	Uniform Resource Identifier (URI).
	Expected Value	A URI representing a place.
	Authorities	GeoNames for the place URI.
	Example Value	geonames:6093943 (Ontario)
Examples	Typical Example	The city of Toronto falls within the province of Ontario.
	Example Abstraction	geonames:6067965 → P89 falls within → geonames:6093943