Cabinet Conclusions 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 Cabinet Conclusions data is modelled for compatibility with the wider LINCS data model. This document provides patterns used in the mapping of Cabinet Conclusions 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 Cabinet Conclusions 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 Cabinet Conclusions application profile is integrated with the Historical Canadians and Historical Indian Affairs Agents application profiles. See the respective documents for more information.

Ontologies & Vocabularies

This section reports the ontologies, vocabularies, and authority files used in the Cabinet Conclusions 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.

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 & Authority Files

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

Acronym	Prefix	Vocabulary or Authority	Purpose
DCB	N/A	Dictionary of Canadian Biography	Source of URIs for DCB entries
Event	event:	LINCS Event Vocabulary	To represent event types
Identity	identity:	LINCS Identity Vocabulary	To represent people's identities
GeoNames	geo:	GeoNames	Authority for place URIs
LAC CabCon	N/A	Library and Archives Canada – Cabinet Conclusions	Source of URIs for CabCon entries
Lexvo	lexvo:	Lexvo	To represent languages
LINCS	lincs:	LINCS minted entities	To represent entities not described elsewhere
Occupation	occupation:	LINCS occupation vocabulary	To represent people's occupations
VIAF	viaf:	Virtual International Authority File	Authority for people and group URIs
Wikidata	wikidata:	Wikidata Knowledge Base	Authority for people and group URIs
XSD	xsd:	XML Schema Datatypes	For literal datatypes

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)
Cabinet Meeting	E7 Activity	<title> a crm:E7_Activity .
Ministry	E74 Group	<ministry> a crm:E74_Group .
Formation	E66 Formation	<formation> a crm:E66_Formation .
Dissolution	E68 Dissolution	<dissolution> a crm:E68_Dissolution .
Political Party	E74 Group	<party> a crm:E74_Group .
Joining	E85 Joining	<joining> a crm:E85_Joining .
Person	E21 Person	<person> a crm:E21_Person .
Occupation	E7 Activity	<occupation> a crm:E7_Activity ; crm:P2_has_type event:OccupationEvent . crm:P2_has_type <occupation_type> .
Type	E55 Type	<type> a crm:E55_Type .
Identifier	E42 Identifier	<identifier> a crm:E42_Identifier ; crm:P2_has_type <identifier_type> .
Place	E53 Place	<place> a crm:E53_Place .
CabCon Entry	E73 Information Object	<cabcon_entry> a crm:E73_Information_Object .
CabCon Page	D1 Digital Object (CRMdig)	<cabcon_page> a crmdig:D1_Digital_Object .
DCB Entry	D1 Digital Object (CRMdig)	<dcb_entry> a crmdig:D1_Digital_Object .
MIKAN Entry	E33 Linguistic Object	<note_comment> a crm:E33_Linguistic_Object ; crm:P2_has_type <note_comment_type> .
Name or Title	E33 E41 Linguistic Appellation	<name_title> a crm:E33_E41_Linguistic_Appellation ; crm:P2_has_type <name_title_type> .
Annotation	Annotation (OA)	<annotation> a oa:Annotation .

Overview

The Cabinet Conclusions dataset is a collection of Cabinet meeting minutes from the Government of Canada, covering the period from 1944 to 1979. This dataset is part of the Canadian History project along with the Historical Canadians and Department of Indian Affairs Agents datasets. See the respective application profiles for more information.

The image below shows an overview of the entire Cabinet Conclusions 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.

Nodes

Basic Patterns

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

Type

Diagram
Pattern	Definition	An entity has a type.
	Abstraction	E1 CRM Entity → P2 has type → E55 Type
	Applies to	Ministry. Every ministry has a type. CabCon Page. Every page has a type. Identifier. Every identifier has one or more types. Name & Title. Every name or title has one or more types. Occupation. Every occupation event has one or more types.
Values	Type of Value	Uniform Resource Identifier (URI).
	Expected Value	URI from vocabulary or minted by LINCS.
	Authorities	LINCS Biography for the name type. Personal names have type biography:personalName. Group names have type biography:groupName. LINCS Event. All occupation activities are assigned type event:OccupationEvent. LINCS Occupation for the specific occupation type.
Examples	Typical Example	The 18th Canadian Ministry has type wikidata:Q2458227 (Cabinet of Canada).
	Example Abstraction	wikidata:Q200217 → P2 has type → wikidata:Q2458227
	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)	wikidata:Q200217 a crm:E7_Activity ; rdfs:label "18th Canadian Ministry"@en ; crm:P2_has_type wikidata:Q2458227 . wikidata:Q2458227 a crm:E55_Type ; rdfs:label "Cabinet of Canada"@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	Cabinet Meeting. Every Cabinet meeting has exactly one ID. CabCon Entry. Every CabCon entry has exactly one ID. DCB Entry. Every DCB entry has exactly one ID. MIKAN Biography. Every biography has a MIKAN number (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 Cabinet of Canada meeting of 1 January 1970 is identified by identifier 1.
	Example Abstraction	<http://temp.lincsproject.ca/meeting/1> → P1 is identified by → <http://temp.lincsproject.ca/meeting/id/1> → P190 has symbolic content → "1"^^xsd:integer
Generalized Pattern (Turtle)	<entity> a crm:E1_CRM_Entity ; rdfs:label "<entity>" ; crm:P1_is_identified_by <identifier> . <identifier> a crm:E42_identifier ; rdfs:label "Identifier of entity <entity>"@en ; crm:P2_has_type <identifier_type> ; crm:P190_has_symbolic_content "<value>" .
Sample Data (Turtle)	<http://temp.lincsproject.ca/meeting/1> a crm:E7_Activity ; rdfs:label "Cabinet of Canada meeting on 1970-01-01" ; crm:P1_is_identified_by <http://temp.lincsproject.ca/meeting/id/1> . <http://temp.lincsproject.ca/meeting/id/1> a crm:E42_identifier ; rdfs:label "Library and Archives Canada ID for Cabinet of Canada meeting on 1970-01-01"@en ; crm:P2_has_type <http://temp.lincsproject.ca/lac/id> ; crm:P190_has_symbolic_content "1"^^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	CabCon Entry. Every entry has at least one title. DCB Entry. Every entry has at least one title. Person. Every person has at least one name. Ministry. Every ministry 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	The 1st Canadian Ministry is named "1st Canadian Ministry" (in English).
	Example Abstraction	E74 Group → P1 is identified by → E33 E41 Linguistic Appellation → P190 has symbolic content → "<ministry_name>"
Generalized Pattern (Turtle)	<entity> a crm:E1_CRM_Entity ; rdfs:label "<entity>" ; crm:P1_is_identified_by <name_or_title> . <name_or_title> a crm:E33_E41_Linguistic_Appellation ; rdfs:label "English title of the entity <name_or_title>"@en ; crm:P2_has_type <type> ; crm:P190_has_symbolic_content "<name_or_title>" .
Sample Data (Turtle)	wikidata:Q162832 a crm:E74_Group ; rdfs:label "1st Canadian Ministry"@en, "1er conseil des ministres du Canada"@fr ; crm:P1_is_identified_by <http://temp.lincsproject.ca/ministry/id/1>, <http://temp.lincsproject.ca/ministry/title/en/1>, <http://temp.lincsproject.ca/ministry/title/fr/1> ; crm:P2_has_type wikidata:Q2458227 . <http://temp.lincsproject.ca/ministry/title/en/1> a crm:E33_E41_Linguistic_Appellation ; rdfs:label "Name of 1st Canadian Ministry"@en ; crm:P190_has_symbolic_content "1st Canadian Ministry"@en ; crm:P2_has_type <http://id.lincsproject.ca/biography/groupName> .

Cabinet Meeting

A cabinet meeting is an activity carried out by a ministry and having multiple people as participants. The dataset represents basic information about the meeting, including its participants, date, location, and topic(s). Each cabinet meeting has exactly one Cabinet Conclusions (CabCon) entry that contains the minutes of the meeting.

Participant

Diagram
Pattern	Definition	A cabinet meeting has a number of participants, each with a certain role.
	Abstraction	E7_Activity → P01i_is_domain_of → PC14_Carried_Out_By → P02_has_range → E21_Person PC14_Carried_Out_By → P14.1_in_the_role_of → E55_Type
	Applies to	Meeting. Every meeting has at least one participant with a role.
Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	URI from authority file or minted by LINCS (meeting). URI from authority file or minted by LINCS (person). URI from vocabulary or minted by LINCS (role). URI minted by LINCS (person with role).
	Authorities	LINCS for the URI of the meeting. VIAF or Wikidata for the URI of the person. Wikidata for the URI of the role. LINCS for the URI of the person with role.
	Example Values	<http://temp.lincsproject.ca/meeting/100> (meeting) viaf:56618205 (person) wikidata:Q839078 (role) <TEMPORARY_PERSON_ROLE_URI> (person with role)
Examples	Typical Example	William Lyon Mackenzie King participated in the Cabinet of Canada meeting of 17 April 1945 as the Prime Minister of Canada.
	Example Abstraction	E7 Activity P01_is_domain_of → <TEMPORARY_PERSON_ROLE_URI> → P02 has range → viaf:56618205 <TEMPORARY_PERSON_ROLE_URI> → P14.1 in the role of → wikidata:Q839078
Generalized Pattern (Turtle)	<meeting> a crm:E7_Activity ; rdfs:label "<meeting>" . <person> a crm:E21_Person ; rdfs:label "<person>" . <role> a crm:E55_Type ; rdfs:label "<role>" . <person_with_role> a crm:PC14_Carried_Out_By ; rdfs:label "<person_with_role>" ; crm:P01_has_domain <meeting> ; crm:P02_has_range <person> ; crm:P14.1_in_the_role_of <role> .
Sample Data (Turtle)	<http://temp.lincsproject.ca/meeting/100> a crm:E7_Activity ; rdfs:label "Cabinet of Canada meeting on 1945-04-17"@en . viaf:56618205 a crm:E21_Person ; rdfs:label "William Lyon Mackenzie King"@en . wikidata:Q839078 a crm:E55_Type ; rdfs:label "Prime Minister of Canada"@en . <TEMPORARY_PERSON_ROLE_URI> a crm:PC14_carried_out_by ; rdfs:label "William Lyon Mackenzie King in the role of prime minister in 1945-04-17 Cabinet of Canada meeting"@en . crm:P01_has_domain <http://temp.lincsproject.ca/meeting/100> ; crm:P02_has_range viaf:56618205 ; crm:P14.1_in_the_role_of wikidata:Q839078 .
Note	The participants and their roles were extracted programmatically from attendance lists. Attendance information may be incomplete due to technical limitations of Optical Character Recognition. The extracted data was manually reviewed.

Ministry

Diagram
Pattern	Definition	A cabinet meeting is carried out by a ministry.
	Abstraction	E7_Activity → P14_carried_out_by → E74_Group
	Applies to	Cabinet Meeting. Every meeting is carred out by exactly one ministry.
Values	Type of Value	Uniform Resource Identifier (URI).
	Expected Value	URI from authority file that identifies the ministry.
	Authorities	Wikidata for the URI of the ministry.
	Example Values	wikidata:Q194658
Examples	Typical Example	The Cabinet of Canada meeting of 17 April 1945 was carried out by the 16th Canadian Ministry.
	Example Abstraction	<http://temp.lincsproject.ca/meeting/100> → P14 carried out by → wikidata:Q194658
	Generalized Pattern (Turtle)	<meeting> a crm:E7_Activity ; rdfs:label "<meeting>" ; crm:P14_carried_out_by <ministry> .
	Sample Data (Turtle)	<http://temp.lincsproject.ca/meeting/100> a crm:E7_Activity ; rdfs:label "Cabinet of Canada meeting on 1945-04-17"@en ; crm:P14_carried_out_by wikidata:Q194658 .

Topic

Diagram
Pattern	Definition	A cabinet meeting is called to discuss one or more topics.
	Abstraction	E7 Activity → P21 had general purpose → E55 Type → P127 has broader term → E55 Type
	Applies to	Cabinet Meeting. Every meeting has one or more topics.
Values	Type of Value	Uniform Resource Identifier (URI).
	Expected Value	LINCS-minted URI that identifies the topic. URI from Wikidata that identifies the broader topic.
	Authorities	LINCS for the URI of the topic. Wikidata for the URI of the broader topic.
	Example Values	<TEMPORARY_TOPIC_URI> (topic) wikidata:Q26256810 (broader topic)
Examples	Typical Example	The Cabinet of Canada meeting of 15 March 1956 discussed the administration of non-tidal fisheries in Newfoundland.
	Example Abstraction	<http://temp.lincsproject.ca/meeting/1291> → P21 had general purpose → <TEMPORARY_TOPIC_URI> → P127 has broader term → wikidata:Q26256810
	Generalized Pattern (Turtle)	<meeting> a crm:E7_Activity ; rdfs:label "<meeting>" ; crm:P21_had_general_purpose <topic> . <topic> a crm:E55_Type ; rdfs:label "<topic>" ; crm:P127_has_broader_term <broader_topic> . <broader_topic> a crm:E55_Type ; rdfs:label "<broader_topic>" .
	Sample Data (Turtle)	<http://temp.lincsproject.ca/meeting/1291> a crm:E7_Activity ; rdfs:label "Cabinet of Canada meeting on 1956-03-15"@en ; crm:P21_had_general_purpose <TEMPORARY_TOPIC_URI> . <TEMPORARY_TOPIC_URI> a crm:E55_Type ; rdfs:label "Administration of non-tidal fisheries, Newfoundland."@en ; crm:P127_has_broader_term wikidata:Q26256810 . wikidata:Q26256810 a crm:E55_Type ; rdfs:label "topic"@en .

Location

Diagram
Pattern	Definition	An Cabinet meeting happens at a certain location.
	Abstraction	E7 Activity → P7 took place at → E53 Place
	Applies to	Cabinet Meeting. Every meeting happens at a 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 Cabinet of Canada meeting of 7 March 1944 took place in Ottawa, Canada.
	Example Abstraction	<http://temp.lincsproject.ca/meeting/10> → P7 took place at → geo:6094817
Generalized Pattern (Turtle)	<event> a crm:E7_Activity ; rdfs:label "<event>" ; crm:P7_took_place_at <place> .
Sample Data (Turtle)	<http://temp.lincsproject.ca/meeting/10> a crm:E7_Activity ; rdfs:label "Cabinet of Canada meeting on 1944-03-07"@en ; crm:P7_took_place_at geo:6094817 .
Note	The location of Cabinet meetings is currently set to Ottawa, Canada by default.

Date

Diagram
Pattern	Definition	A Cabinet meeting happens on a certain date (or date range).
	Abstraction	E7 Activity → P4 has time-span → E52 Time-Span → P82 at some point within → xsd:string P82a begin of the begin → xsd:dateTime P82b end of the end → xsd:dateTime
	Applies to	Cabinet Meeting. Every meeting 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 date. A datetime value expressing the latest possible end date.
	Authorities	XSD for the datatypes.
Examples	Typical Example	The Cabinet of Canada meeting of 7 March 1944 happened on 7 March 1944.
	Example Abstraction	<http://temp.lincsproject.ca/meeting/10> → P4 has time-span → <http://temp.lincsproject.ca/meeting/date/10> → P82 at some time within → "1944-03-07"@en P82a begin of the begin → "1944-03-07T00:00:00"^^xsd:dateTime P82b end of the end → "1944-03-07T23:59:59"^^xsd:dateTime
Generalized Pattern (Turtle)	<event> a crm:E7_Activity ; 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>"^^xsd:string ; crm:P82a_begin_of_the_begin "<begin_date>"^^xsd:dateTime ; crm:P82b_end_of_the_end "<end_date>"^^xsd:dateTime .
Sample Data (Turtle)	<http://temp.lincsproject.ca/meeting/10> a crm:E7_Activity ; rdfs:label "Cabinet of Canada meeting on 1944-03-07"@en ; crm:P4_has_time-span <http://temp.lincsproject.ca/meeting/date/10> . <http://temp.lincsproject.ca/meeting/date/10> a crm:E52_Time-Span ; rdfs:label "Date of meeting Cabinet Conclusions - March 7, 1944"@en ; crm:P82_at_some_time_within "1944-03-07"@en ; crm:P82_begin_of_begin "1944-03-07T00:00:00"^^xsd:dateTime ; crm:P82_end_of_end "1944-03-07T23:59:59"^^xsd:dateTime .
Note	In this dataset we only represent meeting dates. The meeting time can be found in the source data.

Type

Diagram
Note	The modelling of cabinet meeting types follows the basic pattern for Types. See the corresponding section for more information.

Cabinet Conclusions Entry

Each Cabinet Conclusions (CabCon) entry is a digital object that is about a Cabinet meeting. Each entry has one or more pages.

Meeting

Diagram
Pattern	Definition	A CabCon entry is about a cabinet meeting.
	Abstraction	D1_Digital_Object → P129 is about → E7 Activity
	Applies to	CabCon Entry. Every entry is about exactly one meeting.
Values	Type of Value	Uniform Resource Identifier (URI).
	Expected Value	A URI identifying the Cabinet Conclusions entry.
	Authorities	LAC for the URI of the CabCon entry. LINCS for the URI of the Cabinet meeting.
	Example Values	<http://central.bac-lac.gc.ca/.redirect?app=cabcon&id=400&lang=eng>
Examples	Typical Example	CabCon entry 400 is about the Cabinet of Canada meeting held on 19 June 1947.
	Example Abstraction	D1 Digital Object → P129 is about → E7 Activity
	Generalized Pattern (Turtle)	<cabcon_entry> a crmdig:D1_Digital_Object ; rdfs:label "<cabcon_entry>" ; crm:P129_is_about <meeting> .
	Sample Data (Turtle)	<http://central.bac-lac.gc.ca/.redirect?app=cabcon&id=400&lang=eng> a crmdig:D1_Digital_Object ; rdfs:label "Library and Archives Canada record — Cabinet Conclusions - June 19, 1947"@en . crm:P129_is_about <http://temp.lincsproject.ca/meeting/400> .

Entry Page

Diagram
Pattern	Definition	A Cabinet Conclusions entry is composed of pages.
	Abstraction	D1 Digital Object → P106_is_composed_of → D1_Digital_Object
	Applies to	CabCon Entry. Every entry has one or more pages.
Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	LINCS-minted URI
	Authorities	LAC for the URI of the CabCon entry. LAC for the URIs of the entry pages.
	Example Values	<http://central.bac-lac.gc.ca/.redirect?app=cabcon&id=400&lang=eng&ecopy=e000823827>
Examples	Typical Example	CabCon entry 400 is composed of six pages.
	Example Abstraction	<http://central.bac-lac.gc.ca/.redirect?app=cabcon&id=400&lang=eng> → P106 is composed of → <http://central.bac-lac.gc.ca/.redirect?app=cabcon&id=400&lang=eng&ecopy=e000823827> <http://central.bac-lac.gc.ca/.redirect?app=cabcon&id=400&lang=eng&ecopy=e000823828> <http://central.bac-lac.gc.ca/.redirect?app=cabcon&id=400&lang=eng&ecopy=e000823829> <http://central.bac-lac.gc.ca/.redirect?app=cabcon&id=400&lang=eng&ecopy=e000823830> <http://central.bac-lac.gc.ca/.redirect?app=cabcon&id=400&lang=eng&ecopy=e000823831> <http://central.bac-lac.gc.ca/.redirect?app=cabcon&id=400&lang=eng&ecopy=e000823832>

Page Topic

Diagram
Pattern	Definition	A page may refer to a topic.
	Abstraction	D1_Digital_Object → P67_refers_to → E1_CRM_Entity
Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	A URI that identifies the mentioned topic.
	Applies to	Page. Each page may refer to one or more topics.
	Example Values	wikidata:Q8016 (Winston Churchill)
Examples	Typical Example	Page 1b of the Cabinet Conclusions entry of June 30, 1954 refers to Winston Churchill.
	Example Abstraction	<https://recherche-collection-search.bac-lac.gc.ca/eng/home/record?idnumber=1175&app=cabcon&ecopy=e000832102>> → P67_refers_to → wikidata:Q8016

Page Type

Diagram
Note	The modelling of page types follows the basic pattern for Types. See the corresponding section for more information. The page type may be Agenda, Attendance, Minutes, or Appointment.

Web Annotation

Diagram
Pattern	Definition	An annotation expresses the fact that a string of text refers to a certain entity.
	Abstraction	D1_Digital_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       oa:hasSelector → oa:Selector
	Applies to	CabCon Entry. Every Cabinet Conclusions 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	lincs:00WxWb4NdDS (string CBC in a Cabinet Conclusions entry) wikidata:Q461761 (Canadian Broadcasting Corporation)
Examples	Typical Example	The string of text CBC identifies Canadian Broadcasting Corporation in the Cabinet Conclusions entry of February 19, 1970.
	Example Abstraction	<http://central.bac-lac.gc.ca/.redirect?app=cabcon&id=2930&lang=eng&ecopy=e000002052> → P106_is_composed_of → E73_Information_Object →       P190_has_symbolic_content → CBC       P67_refers_to → wikidata:Q461761 lincs:00TmZv9kBgG →       oa:hasTarget → lincs:00WxWb4NdDS       oa:hasBody → wikidata:Q461761       oa:motivatedBy → oa:identifying       oa:hasSelector → lincs:0176i7dCzSz

Identifier

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

Title

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

Person

In this dataset, a person is an individual who has participated in one or more cabinet meetings. Each person has a name, a birth, a death (if no longer living), and one or more occupations or ministerial posts.

Occupation

Diagram
Pattern	Definition	A person has an occupation or ministerial post.
	Abstraction	E21_Person → P14i_performed → E7_Activity → P2_has_type → E55_Type
	Applies to	Person. Every person has at least one occupation or ministerial post (if known).
Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	LINCS-minted URI that identifies the occupation event. LINCS-minted URI that identifies the occupation type. event:OccupationEvent as a type for every occupation.
	Example Values	<TEMPORARY_OCCUPATION_URI> (occupation) <http://temp.lincsproject.ca/secretary_of_state_for_external_affairs> (occupation type) event:OccupationEvent (occupation type)
Examples	Typical Example	Flora Isabel MacDonald was Secretary of State for External Affairs of Canada from 4 June 1979 to 2 March 1980.
	Example Abstraction	wikidata:Q1429267 → P14i_performed → TEMPORARY_OCCUPATION_URI → P2_has_type → <http://temp.lincsproject.ca/secretary_of_state_for_external_affairs> event:OccupationEvent
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)	<TEMPORARY_OCCUPATION_URI> a crm:E7_Activity ; rdfs:label "Secretary of State for External Affairs occupation of Flora Isabel MacDonald in ministry 21"@en . crm:P14_carried_out_by wikidata:Q1429267 ; crm:P2_has_type event:OccupationEvent, <http://temp.lincsproject.ca/secretary_of_state_for_external_affairs> ; crm:P4_has_time-span <TEMPORARY_TIME_SPAN_URI> .
Note	Ministerial posts follow the same pattern as occupations and are modelled in the same way.

Name

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

Birth

Note	Birth events are not included in this dataset. Their modelling is described in the Historical Canadians application profile.

Death

Note	Death events are not included in this dataset. Their modelling is described in the Historical Canadians application profile.

Parent

Note	Parent-child relations are not included in this dataset. Their modelling is described in the Historical Canadians application profile.

Marriage

Note	Marriage relations are not included in this dataset. Their modelling is described in the Historical Canadians application profile.

DCB Entry

Note	The modelling of DCB entries is described in the Historical Canadians application profile.

Ministry

A ministry of the Canadian cabinet has a formation event, a dissolution event, and one or more members (political parties). The ministry carries out Cabinet meetings which are described in Cabinet Conclusions entries.

Formation

Diagram
Pattern	Definition	A ministry is formed through a formation event.
	Abstraction	E74_Group → P95i_was_formed_by → E66_Formation
Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	LINCS-minted URI
	Applies to	Ministry. Every ministry has exactly one formation event.
	Example Values	<http://temp.lincsproject.ca/formation/1>
Examples	Typical Example	The 1st Canadian Ministry was formed on 1 July 1867.
	Example Abstraction	wikidata:Q16283 → P95i_was_formed_by → <http://temp.lincsproject.ca/formation/1>

Dissolution

Diagram
Pattern	Definition	Formation. Every ministry has exactly one dissolution event.
	Abstraction	E74_Group → P99i_was_dissolved_by → E68_Dissolution
Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	LINCS-minted URI
	Applies to	Ministry. Every ministry has exactly one dissolution event.
	Example Values	<http://temp.lincsproject.ca/dissolution/1>
Examples	Typical Example	The 1st Canadian Ministry was dissolved on 5 November 1873.
	Example Abstraction	wikidata:Q16283 → P99_dissolved_by → <http://temp.lincsproject.ca/dissolution/1>

Membership

Diagram
Pattern	Definition	A ministry has a number of political parties as members.
	Abstraction	E74_Group → P107_has_current_or_former_member → E74_Group
Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	A URI that identifies a political party.
	Applies to	Ministry. Each ministry includes one or more political parties.
	Example Values	TBA
Examples	Typical Example	TBA
	Example Abstraction	TBA

Identifier

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

Name

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

MIKAN Entry

A MIKAN entry is a short biographical text about a person, which is part of the MIKAN database. Each entry has a content, a type, and an identifier.

Subject

lincs:GxDBKY3vsKE →
P129_is_about →
viaf:70267221

Diagram
Pattern	Definition	A MIKAN entry is about a person.
	Abstraction	E33_Linguistic_Object → P129_is_about → E21_Person
Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	LINCS-minted URI
	Applies to	Person. Every MIKAN entry is about exactly one person.
	Example Values	viaf:70267221 (John Abbott)
Examples	Typical Example	The MIKAN entry about John Abbott is about John Abbott.
	Example Abstraction

Identifier

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

Place

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

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	geo: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 → P86 falls within → E53 Place
Values	Type of Value	xsd:string
	Expected Value	A URI representing a place.
	Authorities	Geonames for the place URI.
	Example Value	TBA
Examples	Typical Example	TBA
	Example Abstraction	TBA