Places Application Profile

Purpose

To document how various facets of LINCS data are modelled, along with reference authorities for the populating vocabularies. This will provide a basis for instruction for how to model data in a LINCS-compatible manner, as well as aid in navigation and discovery.

“Places” describes patterns that are unique or specific to representing information about places as both geographic and social concepts.

This document introduces the concepts as used by LINCS, and are not complete definitions of the CIDOC CRM ontology class or property concepts. Consult CIDOC CRM v. 7.1.1 documentation for full class descriptions and property descriptions.

Acronyms

Ontology Acronyms:

CRM - CIDOC Conceptual Reference Model

Vocabulary and Authority Acronyms:

EML - Early Modern London Place Types Vocabulary
GeoJSON - The GeoJSON Format
LINCS - LINCS minted entities
Wikidata - Wikimedia Knowledge Base

Main Classes

Entity type	Class	Declaration Snippet (TTL)
Place	crm:E53_Place	`<place> a crm:E53_Place ; rdfs:label "<place>" .`
Placename	crm:E33_E41_Linguistic_Appellation	`<place_name> a crm:E33_E41_Linguistic_Appellation ; rdfs:label "<place_name>" .`
Address	crm:E41_Appellation	`<address> a crm:E41_Appellation ; rdfs:label "<address_descriptor>" .`
Coordinates	rdfs:literal, e.g., GeoJSON string	`"<coordinates>" .`

Overview Diagram

Below is an image of the application profile overview diagram. Follow this link for a zoomable, more readable version. The segments below align with the document sections.

Nodes

Place Names

For more on identifiers, see the Identifiers section of the Basic Patterns Application Profile.

For how names are made of up parts (such as a full name having a first and last name), see the Identifiers section of the Basic Patterns Application Profile.

Different types of names are differentiated by the P2_has_type → E55_Type pattern associated with them (for more on this, see the Types section of the Basic Patterns Application Profile). For example:

Preferred name: http://vocab.getty.edu/aat/300404670

Pattern/Structure Values	Definition	This pattern declares that a place is identified by a name.
Pattern/Structure Values	Abstraction	`crm:E53_Place → crm:P1_is_identified_by → crm:E33_E41_Linguistic_Appellation → crm:P2_has_type → crm:E55_Type → crm:P190_has_symbolic_content → rdfs:Literal`
Content Values	Type of Value	Uniform Resource Identifier (URI); literal value (text)
	Expected Value	URI from project dataset, existing linked data authority, or minted by LINCS; literal value from project dataset
	Format/Requirements for the Value	URI (preferably dereferenceable); rdfs:literal
Case Examples	Typical Example & Abstraction	The Map of Early Modern London Gazetteer states that St. Saviour (Southwark) is named “St. Saviour (Southwark)” which is in English. `<moeml:STSA1> → crm:P1_is_identified_by → <moeml:St.Saviour(Southwark)> → crm:P2_has_type → <lincs:name> → crm:P72_has_language → <lincs:english> → crm:P190_has_symbolic_content → “St. Saviour (Southwark)”`
Case Examples	Edge Case Example & Abstraction	N/A
Resource Links		N/A
Discussion Elements Pertaining to This Pattern		Use at least one (1) E55_Type on each linguistic identifier specifying what it is.
Projects Following This Pattern		AdArchive, MoEML Gazetteer

Pattern in TTL:

<place> a crm:E53_Place ; 
    rdfs:label "<place>" ; 
    crm:P1_is_identified_by <name>.

<name> a crm:E33_E41_Linguistic_Appellation ; 
    rdfs:label "<name>" ; 
    crm:P2_has_type <type> ;
    crm:P190_has_symbolic_content "<name>" .

<type> a crm:E55_Type ; 
    rdfs:label "<type" .

Uses/Functions (Types)

For more on types, categorization, and classification, as well as vocabularies, see the Types section of the Basic Patterns Application Profile.

Application profile type

Pattern/Structure Values	Definition	This pattern declares that a place has a classification, including by use or function.
Pattern/Structure Values	Abstraction	crm:E53_Place → crm:P2_has_type → crm:E55_Type
Content Values	Type of Value	Uniform Resource Identifier (URI)
	Expected Value	URI from project dataset, existing linked data authority, or minted by LINCS
	Format/Requirements for the Value	URI (preferably dereferenceable)
Case Examples	Typical Example & Abstraction	The Map of Early Modern London Gazetteer states that St. Saviour (Southwark) is a type of eml:Church. `<moeml:STSA1> → crm:P2_has_type → <eml:Church>`
Case Examples	Edge Case Example & Abstraction	N/A
Resource Links		MoEML Team and Martin D. Holmes. (2022). “Locations in Early Modern London.” The Map of Early Modern London, Edition 7.0. Ed. Janelle Jenstad. University of Victoria. https://mapoflondon.uvic.ca/edition/7.0/mdtEncyclopediaLocation_subcategories.htm
Discussion Elements Pertaining to This Pattern		This pattern connects entities to vocabularies. For more on this, see the Vocabularies section of the Basic Patterns Application Profile.
Projects Following This Pattern		AdArchive, MoEML Gazetteer, Orlando

Pattern in TTL:

<place> a crm:E53_Place ;
    rdfs:label "<place>" ;
    crm:P2_has_type <type>.

<type> a crm:E55_Type ;
    rdfs:label "<type>".

Address

Pattern/Structure Values	Definition	This pattern declares that a place was identified by an address.
Pattern/Structure Values	Abstraction	`crm:E53_Place → crm:P1_is_identified_by → crm:E41_Appellation → crm:P190_has_symbolic_content → rdfs:literal → crm:P2_has_type → crm:E55_Type`
Content Values	Type of Value	Uniform Resource Identifier (URI); literal value (text)
	Expected Value	URI from project dataset, existing linked data authority, or minted by LINCS; literal value from project dataset
	Format/Requirements for the Value	URI (preferably dereferenceable); rdfs:literal
Case Examples	Typical Example & Abstraction	The AdArchive dataset states that there is a place identified by the address “WCA, 731 - 44th Avenue, San Francisco, CA 94121.” `<lincs:xijMbv6moWq> → crm:P1_is_identified_by → crm:E41_Appellation → crm:P190_has_symbolic_content → “WCA, 731 - 44th \ Avenue, San Francisco, CA 94121” → crm:P2_has_type → <wikidata:Q319608>`
Case Examples	Edge Case Example & Abstraction	N/A
Resource Links		The Wikimedia Foundation. (2021). Wikidata. https://www.wikidata.org/
Discussion Elements Pertaining to This Pattern		Use at least one (1) E55_Type on each linguistic identifier specifying what it is (e.g., full name, first name, last name, etc).
Projects Following This Pattern		AdArchive

Pattern in TTL:

<place> a crm:E53_Place ; 
    rdfs:label "<place>" ; 
    crm:P1_is_identified_by <address> .

<address> a crm:E41_Appellation ;
    rdfs:label "<address>" ;
    crm:P2_has_type <type> ; 
    crm:P190_has_symbolic_content "<address>" .

<type> a crm:E55_Type ; 
    rdfs:label "<type>" . 

Geographies and Coordinates

Application profile define by

Pattern/Structure Values	Definition	This pattern declares that a place is identified by a geographic reference.
Pattern/Structure Values	Abstraction	`crm:E53_Place → crm:P168_place_is_defined_by → rdfs:literal`
Content Values	Type of Value	literal value (text)
	Expected Value	literal value from project dataset
	Format/Requirements for the Value	rdfs:literal
Case Examples	Typical Example & Abstraction	The AdArchive dataset states that there is a place located at the coordinates “-122.505020, 37.774750.” `<wikidata:Q8030842> → crm:P74_has_current_or_former_residence → crm:E53_Place → crm:P168_place_is_defined_by → “-122.505020, 37.774750”`
Case Examples	Edge Case Example & Abstraction	The Map of Early Modern London Gazetteer states that St. Saviour (Southwark) is located at the coordinates “-0.089722,51.506111”. `<moeml:STSA1> → → crm:P168_place_is_defined_by → “POINT(51.506111 -0.089722)”`
Resource Links		H. Butler et. al. (2016). RFC 7946: The GeoJSON Format. https://www.rfc-editor.org/rfc/rfc7946 The Wikimedia Foundation. (2021). Wikidata. https://www.wikidata.org/
Discussion Elements Pertaining to This Pattern		GeoJSON can use 6 types of coordinates: Point, MultiPoint, LineString, Polygon, MultiPolygon, MultiLineString. This dataset uses all of these; most commonly used is “point.”
Projects Following This Pattern		AdArchive, Anthologia graeca, MoEML Gazetteer

Pattern in TTL:

<place> a crm:E53_Place ; 
    rdfs:label "<place>" ; 
    crm:P168_place_is_defined_by "<coordinates>" .

Places as Parts of Other Places

Application profile part of other place

Pattern/Structure Values	Definition	This pattern declares that a place is geographically within a larger space.
Pattern/Structure Values	Abstraction	`crm:E53_Place → crm:P89_falls_within → crm:E53_Place`
Content Values	Type of Value	Uniform Resource Identifier (URI); literal value (text)
	Expected Value	URI from project dataset, existing linked data authority, or minted by LINCS; literal value from project dataset
	Format/Requirements for the Value	URI (preferably dereferenceable); rdfs:literal
Case Examples	Typical Example & Abstraction	The Yellow Nineties Personography declares that the place that Rosamund Marriott Watson was born falls within the London Borough of Hackney. `<lincs:1i8nVqCadyT> → crm:P89_falls_within → <wikidata:Q205679>`
Case Examples	Edge Case Example & Abstraction	N/A
Resource Links		The Wikimedia Foundation. (2019, December 30). Wikidata: Main Page. Wikidata. https://www.wikidata.org/wiki/Wikidata:Main_Page
Discussion Elements Pertaining to the Pattern		N/A
Projects Following This Pattern		Yellow Nineties Personography

Purpose​

Acronyms​

Main Classes​

Overview Diagram​

Nodes​

Place Names​

Uses/Functions (Types)​

Address​

Geographies and Coordinates​

Places as Parts of Other Places​

Purpose

Acronyms

Main Classes

Overview Diagram

Nodes

Place Names

Uses/Functions (Types)

Address

Geographies and Coordinates

Places as Parts of Other Places