Aller au contenu principal

Historical Indian Affairs Agents 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 Indian Affairs Agents data is modelled for compatibility with the wider LINCS data model. This document provides patterns used in the mapping of Historical Indian Affairs Agents data which correspond to the categories outlined in the main LINCS Application Profiles.

This document introduces classes and properties as used in this specific context (LINCS and the Historical Indian Affairs Agents 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 Canadian History dataset collection, the Historical Indian Affairs Agents application profile is integrated with the Cabinet Conclusions and Historical Canadians application profiles. See the respective documents for more information.

Ontologies & Vocabularies

This section reports the ontologies, vocabularies, and authority files used in the Historical Indian Affairs Agents dataset. The acronyms are used throughout the document to refer to the terms defined in these ontologies. The prefixes are used to compose the URIs in Turtle code throughout the examples found below.

Ontologies

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

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

Vocabularies & Authority Files

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

AcronymPrefixVocabulary or AuthorityPurpose
Eventevent:LINCS Event VocabularyTo represent event types
GeoNamesgeo:GeoNamesAuthority for place URIs
LAC ReportsN/ALibrary and Archives Canada – Indian Affairs Annual ReportsSource of URIs for Indian Affairs reports
LINCSlincs:LINCS minted entitiesTo represent entities not described elsewhere
Occupationoccupation:LINCS occupation vocabularyTo represent people's occupations
VIAFviaf:Virtual International Authority FileAuthority for people and group URIs
Wikidatawikidata:Wikidata Knowledge BaseAuthority for people, group, and place URIs
XSDxsd:XML Schema DatatypesFor literal datatypes

Main Classes

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

Entity TypeClassDeclaration Snippet (Turtle Syntax)
AgentE21 Person
<agent> a crm:E21_Person .
NameE33 E41 Linguistic Appellation
<name_title> a crm:E33_E41_Linguistic_Appellation ;
crm:P2_has_type <name_title_type> .
BirthE67 Birth
<birth> a crm:E67_Birth .
AgencyE74 Group
<agency> a crm:E74_Group .
TypeE55 Type
<type> a crm:E55_Type .
DepartmentE74 Group
<department> a crm:E74_Group .
PlaceE53 Place
<place> a crm:E53_Place .
OccupationE7 Activity
<occupation> a crm:E7_Activity ;
crm:P2_has_type event:OccupationEvent .
crm:P2_has_type <occupation_type> .
ReportD1 Digital Object (CRMdig)
<report> a crmdig:D1_Digital_Object .
DCB EntryD1 Digital Object (CRMdig)
<report> a crmdig:D1_Digital_Object ;
crm:P2_has_type wikidata:Q36774 .

Overview Diagram

The Historical Indian Affairs Agents dataset is a collection of biographical entries about Indian affairs agents, i.e., people who worked with the agencies of the Department of Indian Affairs. This dataset is part of the Canadian History project along with the Cabinet Conclusions and Historical Canadians datasets. See the respective application profiles for more information.

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

Application profile

Nodes

Basic Patterns

This section describes basic patterns that are reused across the Historical Indian Affairs Agents dataset.

Type

Diagram
Application profile
PatternDefinitionAn entity has a type.
AbstractionE1 CRM Entity
P2 has type
E55 Type
Applies toAgency. Every agency has one or more types.
Name. Every name has one or more types.
Occupation. Every occupation has one or more types.
ValuesType of ValueUniform Resource Identifier (URI).
Expected ValueURI from vocabulary or minted by LINCS.
AuthoritiesLINCS Biography for the name type. Personal names have type biography:personalName.
LINCS Event. All occupations are assigned type event:OccupationEvent.
LINCS Occupation for the specific occupation type.
ExamplesTypical ExampleThe Assiniboine Agency was a government agency and an employer.
Example Abstractionlincs:uHpXmbg9zxY
P2 has typewikidata:Q3053337, wikidata:Q327333.
Generalized Pattern (Turtle)
<entity> a crm:E1_CRM_Entity ;  
rdfs:label "<entity>" ;
crm:P2_has_type <type> .

<type> a crm:E55_Type ;
rdfs:label "<type>"@en .
Sample Data (Turtle)
lincs:uHpXmbg9zxY a crm:E74_Group ;  
rdfs:label "Assiniboine Agency"@en ;
crm:P2_has_type wikidata:Q3053337, wikidata:Q327333 .

wikidata:Q327333 a crm:E55_Type ;
rdfs:label "government agency"@en .

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

Agent

An agent is a person who has worked with one or more agencies of the Department of Indian Affairs. Each agent has a name and one or more occupations. Agents may also have a birth event if the agent has been matched to a person with a DCB entry and their parent also has a DCB entry.

Name

Diagram
Application profile
PatternDefinitionAn agent is identified by an appellation (name).
AbstractionE21 Person
P1 is identified by
E33 E41 Linguistic Appellation
P190 has symbolic contentxsd:string
Applies toAgent. Each agent has at least one name.
ValuesType of Valuexsd:string  (a string of text).
Expected ValueA string of text that identifies the entity.
AuthoritiesXSD for the datatype.
LINCS for the appellation type.
ExamplesTypical ExampleOronhyatekha has name "Oronhyatekha".
Example Abstractionlincs:K7Eq2y5IYbi
P1 is identified by
E33 E41 Linguistic Appellation
P190 has symbolic content"Oronhyatekha"
Generalized Pattern (Turtle)
<agent> a crm:E21_Person ;  
rdfs:label "<agent>" ;
crm:P1_is_identified_by <name> .

<name> a crm:E33_E41_Linguistic_Appellation ;
rdfs:label "Name of <name>" ;
crm:P2_has_type <type> ;
crm:P190_has_symbolic_content "<name>" .
Sample Data (Turtle)
viaf:104461457 a crm:E21_Person ;
rdfs:label "Oronhyatekha"@en ;
crm:P1_is_identified_by lincs:K7Eq2y5IYbi ;
owl:sameAs wikidata:Q7103784 .

lincs:K7Eq2y5IYbi a crm:E33_E41_Linguistic_Appellation ;
rdfs:label "Name of Oronhyatekha"@en ;
crm:P190_has_symbolic_content "Oronhyatekha"@en ;
crm:P2_has_type biography:forename, biography:personalName .

Occupation

NoteFor information about the modelling of an agent's occupation, see the Employer & Employee section below.

Birth

Diagram
Application profile
PatternDefinitionAn agent is born through a birth event.
AbstractionE21_Person
P98i_was_born
E67_Birth
Applies toAgent. Every agent has exactly one birth.
ValuesType of ValueUniform Resource Identifier (URI)
Expected ValueLINCS-minted URI
Example Values<TEMPORARY_BIRTH_URI>
ExamplesTypical ExamplePītikwahanapiwīyin was born in 1842 in Saskatchewan.
Example Abstractionviaf:106198432
P98i_was_born
<http://temp.lincsproject.ca/birth/pitikwahanapiwiyin_11>
NoteIn this dataset, the birth date and place are missing because they are not found in the source data. There is also no information about people's deaths due to lack of data.

Parent

NoteThe modelling of parent-child relations is described in the Historical Canadians application profile. See that profile for more information. Agent records were manually reviewed to merge them together when they represent the same person. Variations in names remain based on how they were written in different records.

Occupation

An occupation is an activity carried out by an agent (a person) with an agency of the Department of Indian Affairs.

Employer & Employee

Diagram
Application profile
PatternDefinitionAn agent has an occupation with an agency.
AbstractionE21_Person
P14i_performed
E7_Activity
P2_has_type
E55_Type
Applies toPerson. Every agent has at least one occupation (if known).
ValuesType of ValueUniform Resource Identifier (URI)
Expected ValueLINCS-minted URI that identifies the occupation activity.
LINCS-minted URI that identifies the occupation type.
event:OccupationEvent as a type for every occupation.
Example Valueslincs:0w2KstqiD5H (occupation)
lincs:DkVxYJIb3gI (occupation type)
event:OccupationEvent (occupation type)
ExamplesTypical ExampleSister Leblanc was a hospital nurse starting in 1910.
Example Abstractionlincs:0w2KstqiD5H
P14 carried out by
lincs:OdGRhxx2WiJ
P2 has type
lincs:DkVxYJIb3gI
event:OccupationEvent
P11 had participant
lincs:2EChJkPZ4LC, lincs:U3kQTohZuA9
Generalized Pattern (Turtle)
<occupation> a crm:E7_Activity ;
rdfs:label "<occupation>" .
crm:P14_carried_out_by <person> ;
crm:P2_has_type event:OccupationEvent, <occupation_type> ;
crm:P4_has_time-span <time-span> .
Sample Data (Turtle)
 lincs:UnZeko4zabM a crm:E7_Activity ;
rdfs:label "Hospital Nurse occupation of Sister Leblanc starting in 1911"@en ;
crm:P14_carried_out_by lincs:OdGRhxx2WiJ ;
crm:P11_had_participant lincs:2EChJkPZ4LC, lincs:U3kQTohZuA9 ;
crm:P2_has_type lincs:DkVxYJIb3gI, event:OccupationEvent ;
crm:P4_has_time-span lincs:hZgsM5bAXKs ;
crm:P7_took_place_at geo:5955891 .

Place

Diagram
Application profile
PatternDefinitionAn occupation is carried out in a certain place.
AbstractionE7 Activity
P7 took place at
E53 Place
Applies toOccupation (Activity). Every occupation happens at a location.
ValuesType of ValueA URI uniquely identifying the place.
Expected ValueUniform Resource Identifier (URI).
AuthoritiesGeoNames for the place URI.
ExamplesTypical ExampleThe Senior Clerk occupation of Joseph W. Mackay took place in Victoria County, Nova Scotia.
Example Abstractionlincs:00WN9HDL4m9
P7 took place at
geo:6174034
Generalized Pattern (Turtle)
<occupation> a crm:E7_Activity ;  
rdfs:label "<occupation>" ;
crm:P7_took_place_at <place> .
Sample Data (Turtle)
lincs:QvSyTRnV9yq a crm:E7_Activity ;
rdfs:label "Senior Clerk occupation of Mackay, Joseph W. starting in 1895"@en ;
crm:P7_took_place_at geo:6174041 .

Date

Diagram
Application profile
PatternDefinitionAn occupations begins on a certain date.
AbstractionE1 CRM Entity
P4 has time-span
E52 Time-Span
P82 at some point withinxsd:string
P82a begin of the beginxsd:dateTime
P82b end of the endxsd:dateTime
Applies toOccupation (Activity). Every occupation begins on a certain date.
ValuesType of Valuexsd:string for the human-readable date.
xsd:dateTime for the date's begin of begin.
Expected ValueA string of text expressing the date of the occupation.
A datetime value expressing the earliest possible beginning time of the occupation.
AuthoritiesXSD for the datatypes.
ExamplesTypical ExampleThe Senior Clerk occupation of Joseph W. Mackay started in 1895.
Example Abstractionlincs:00WN9HDL4m9
P4 has time-span
lincs:aGgJ6C0zZs3
P82 at some time within
"1895"@en
P82a begin of the begin
"1895-01-01T00:00:00"^^xsd:dateTime
Generalized Pattern (Turtle)
<occupation> a crm:E7_Activity ;  
rdfs:label "<occupation>" ;
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>"^^xsd:string ;
crm:P82a_begin_of_the_begin "<begin_date>"^^xsd:dateTime .
Sample Data (Turtle)
lincs:QvSyTRnV9yq a crm:E7_Activity ;
rdfs:label "Senior Clerk occupation of Joseph W. Mackay starting in 1895"@en ;
crm:P4_has_time-span lincs:fhjlh9Q74Pe .

lincs:fhjlh9Q74Pe a crm:E52_Time-Span ;
rdfs:label "Occupation start date of 1895"@en ;
crm:P82_at_some_time_within "1895"@en ;
crm:P82_begin_of_begin "1895-01-01T00:00:00"^^xsd:dateTime .
NoteIn this dataset, only the starting year of each occupation is known, while the specific month or day of beginning is not found in the source data and the end date is also unknown. Therefore, the property P82b end of the end is not applicable.

Type

Diagram
Application profile
NoteThe modelling of occupation types follows the basic pattern for Types. See the corresponding section for more information. Occupation types have been kept as specific as possible and have been connected to broader terms via P127 has broader term.

Agency

An agency is a group within a department of the Canadian government. An agency has one or more Indian affairs agents as members. It also has one or more types. This dataset only includes agencies within the Department of Indian Affairs.

Membership

Diagram
Application profile
PatternDefinitionA department may have a number of agencies.
AbstractionE74_Group
P107_has_current_or_former_member
E21_Person
ValuesType of ValueUniform Resource Identifier (URI)
Expected ValueA URI identifying an agency of the Department of Indian Affairs.
Applies toAgency. Each agency employs one or more agents.
Example Valueslincs:mJ6Twv9ZEoS (John McKenzie)
ExamplesTypical ExampleJohn McKenzie was a miller for the Carlton Agency starting in 1897.
Example Abstractionlincs:8MWD2pGOkf7
P107_has_current_or_former_member
lincs:mJ6Twv9ZEoS
Generalized Pattern (Turtle)
<agency> a crm:E74_Group ;  
rdfs:label "<agency>" ;
crm:P107_has_current_or_former_member <agent> .
Sample Data (Turtle)
lincs:8MWD2pGOkf7 a crm:E74_Group ;  
rdfs:label "Carlton Agency"@en ;
crm:P107_has_current_or_former_member lincs:mJ6Twv9ZEoS .

lincs:mJ6Twv9ZEoS a crm:E21_Person ;
rdfs:label "John McKenzie"@en ;

Type

Diagram
Application profile
NoteThe modelling of department types follows the basic pattern for Types. See the corresponding section for more information. Each agency has types wikidata:Q327333 (government agency) and wikidata:Q3053337 (employer).

Department

A department is a branch of the Canadian government. A department has a number of agencies and is assigned one or more types. The only department represented in this dataset is the Department of Indian Affairs.

Membership

Diagram
Application profile
PatternDefinitionA department has a number of agencies and agents.
AbstractionE74_Group
P107_has_current_or_former_member
E39_Actor
ValuesType of ValueUniform Resource Identifier (URI)
Expected ValueA URI identifying an agency or agent of the Department of Indian Affairs.
Applies toDepartment. Each department has one or more agencies and one or more agents.
Example Valueslincs:0FCofNQkjI0 (Red Deer Industrial School)
ExamplesTypical ExampleRed Deer Industrial School was an agency of the Department of Indian Affairs.
Example Abstractionlincs:U3kQTohZuA9
P107_has_current_or_former_member
lincs:0FCofNQkjI0
Generalized Pattern (Turtle)
<department> a crm:E74_Group ;  
rdfs:label "<department>" ;
crm:P107_has_current_or_former_member <agency_or_agent> .
Sample Data (Turtle)
lincs:U3kQTohZuA9 a crm:E74_Group ;  
rdfs:label "Department of Indian Affairs"@en ;
crm:P107_has_current_or_former_member lincs:0FCofNQkjI0 .

lincs:0FCofNQkjI0 a crm:E74_Group ;
rdfs:label "Red Deer Industrial School"@en ;
NoteA department has both agencies and agents. The class E39 Actor does not actually appear in the dataset, where it is replaced by the more specific E21 Person for agents and E74 Group for agencies, using the same pattern.

Type

Diagram
Application profile
NoteThe modelling of department types follows the basic pattern for Types. See the corresponding section for more information. The Department of Indian Affairs has types wikidata:Q111190932 (Canadian federal department), wikidata:Q3053337 (employer), and wikidata:Q422404 (Government of Canada).

Report

A report is a document that contains information about the activities of one or more agencies of a governmental department. A report may mention the names of one or more agencies and one or more agents. The dataset contains Indian Affairs Annual Reports provided by Library and Archives Canada.

Mention

Diagram
Application profile
PatternDefinitionA report refers to an agency or an agent.
AbstractionD1 Digital Object
P67 refers to
E39 Actor
Applies toDepartment. Each report may refer to one or more agencies or agents.
ValuesType of ValueUniform Resource Identifier (URI)
Expected ValueA URI identifying an agency or agent of the Department of Indian Affairs.
Example Valuesviaf:16905756 (T. Mayne Daly)
wikidata:Q1585303 (James A.J. McKenna)
lincs:1pqGsL1xMjS (Caroline Reiffenstein)
AuthoritiesVIAF, Wikidata, or LINCS (agent or agency).
ExamplesTypical ExampleThe Dominion of Canada Annual Report of the Department of Indian Affairs for the Year Ended 30th June 1895 refers to Henry C. Ross.
Example Abstraction<http://central.bac-lac.gc.ca/.redirect?app=indaffannrep&id=10303&lang=eng&ecopy=1895b004>
P67 refers to
lincs:Mpg0Sh4uy0B
NoteThe class E39 Actor does not actually appear in the dataset, where it is replaced by the more specific E21 Person for agents and E74 Group for agencies.

DCB Entry

A Dictionary of Canadian Biography entry is a webpage that reports biographical data about an agent. The modelling of DCB entries is described in the Historical Canadians application profile.

Subject

Diagram
Application profile
NoteThe full modelling of DCB entries is described in the Historical Canadians application profile.

Place

A place is a geographic location that can be identified by coordinates.

Coordinates

Diagram
Application profile
PatternDefinition

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

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

Spatial Containment

Diagram
Application profile
PatternDefinition

A place may fall within another place.

AbstractionE53 Place
P86 falls within
E53 Place
Applies toPlace. A place may fall within one or more places.
ValuesType of Valuexsd:string
Expected ValueA URI representing a place.
AuthoritiesGeonames for the place URI.
Example Valuegeo:6113358 (Prince Edward Island)
ExamplesTypical ExampleTyne Valley, Prince Edward Island falls within Prince Edward Island.
Example Abstractiongeo:6171537
P86 falls within
geo:6113358