A Semantic Web data model used for geographical names information

Overview
Figure 1. An overview of this model

1. Metadata

IRI

https://linked.data.gov.au/def/gn

Preferred Label

Geographical Names Model

Definition

A Semantic Web data model of geographical names, sometimes called place names, information. It caters specifically for Australian & New Zealand’s naming needs.

Created

2023-05-11

Modified

2023-06-12

Issued

0000-00-00 - not formally issued yet

Creator

Nicholas J. Car

Publisher

Queensland Spatial Information

History Note

This model was made for Queensland Spatial Information, a unit of the Queensland Department of Resources, to assist with their future geographical naming needs and is a development of the Place Names ontology PNO made for ICSM and should be used in its place.

Status

Beta version

Version

:0.0.1

Code Repository

https://github.com/Spatial-Information-QLD/geographical-names-model

License

Creative Commons Attribution 4.0 International (CC BY 4.0)

Copyright

© The State of Queensland (Department of Resources) 2020-2023

Machine-readable form (RDF)

https://linked.data.gov.au/def/gn.ttl

2. Preamble

2.1. Abstract

A Semantic Web data model of geographical names, sometimes called place names, information. It caters specifically for Australian & New Zealand’s naming needs.

Note
 This model was made for Queensland Spatial Information, a unit of the Queensland Department of Resources, to assist with their future geographical naming needs and is a development of the Place Names ontology PNO made for ICSM and should be used in its place.

2.2. Namespaces

This model is built on a small set of well-regarded Semantic Web models which use a variety of namespaces. Prefixes for these namespaces, used throughout this document, are listed below.

Prefix Namespace Description

:

https://linked.data.gov.au/def/gn/

This model

gpt

https://linked.data.gov.au/def/gn-part-types/

Supporting vocabulary - Geographic Name Part Types

goc

https://linked.data.gov.au/def/go-categories/

Supporting vocabulary - Geographic Object Categories

cn

https://linked.data.gov.au/def/cn/

Compound Name Model

dcterms

http://purl.org/dc/terms/

Dublin Core Terms

ex

http://example.com/

Generic examples

geo

http://www.opengis.net/ont/geosparql#

OGC GeoSPARQL model

lm

https://linked.data.gov.au/def/lifecycle/

Lifecycle Model

owl

http://www.w3.org/2002/07/owl#

Web Ontology Language ontology

rdfs

http://www.w3.org/2000/01/rdf-schema#

RDF Schema ontology

sosa

http://www.w3.org/ns/sosa/

Sensor, Observation, Sample, and Actuator ontology

skos

http://www.w3.org/2004/02/skos/core#

Simple Knowledge Organization System (SKOS) ontology

time

http://www.w3.org/2006/time#

Time Ontology in OWL

void

http://rdfs.org/ns/void#

Vocabulary of Interlinked Data (VoID) ontology

xsd

http://www.w3.org/2001/XMLSchema#

XML Schema Definitions ontology

2.3. Conformance

This model conforms to the OntPub Profile which is a specification for ontology publication that mandates certain structural and metadata properties for the model as a whole and model elements. Metadata elements for the model as a whole - the ontology - are given in the Metadata section above.

2.3.1. Figures

Figures used in this document use the following key:

Key
Figure 2. Key of elements used in this Model’s figures

2.3.2. Example Data

Example Data used in this document, for instance in model element "Example" values, are RDF data in the Turtle syntax.

3. Introduction

This model facilitates applying Geographical Name objects, sometimes called Place Names, with potentially many subcomponents, to geospatial representation of geographical objects. This style of feature name / geospatial feature modelling is informed inherited from the Compound Naming Model that this model extends.

Note
 This model does not attempt to assist with detail geospatial aspects of geographical object modelling: it only provides an association between naming components and geospatial representations of the objects established using other models and with categorisation of objects objects. This model also does not link road objects to other, related, objects, such as geographical objects they may be within or abutting. Such linking should be represented with Feature / Feature topological relations, such as those within GeoSPARQL GEO.

Data made according to this model, when stored in one of the RDF serialization formats such as TTL, is directly validatable according to this model through use of validators that are supplied, see Section Validation.

3.1. Sources of Requirements

This model was initially built to allow Queensland Government to manage geographical naming information in a manner similar to how they manage Address & Roads Name information: as a collection of Feature Names for Features which spatial information such as type categorisation, geometries and spatial relations. This introduces requirements to both facilitate complex naming and align with Address etc. modelling.

To ensure that this model implements that Feature Names / Features / Geometries pattern, it is a profile of the Compound Naming Model CNM and GeoSPARQL GEO which captures the required patterns in generic form and are also profiled by Queensland Government’s Address & Geographic Names Models. By adopting GeoSPARQL as its spatial modelling base, this model allows for detailed spatial object modelling, including spatial object categorisation and complex, multiple and even fuzzy geometry modelling.

This model also aims to handle a series long-standing known concerns specifically related to naming, in particular:

  • name changes over time

  • official/unofficial names

  • indigenous naming

  • named object categorisation

Detailed requirements for this model all stem from these top-level requirements. The individual requirements are listed in the Requirements section.

3.2. Major Modelling Principles

Major modelling principles present in this model are:

  1. Feature / Feature Naming differentiation

  2. Detailed spatial modelling

  3. Multiple names

    1. Official/unofficial names

    2. Name changes over time

    3. Indigenous / multi-lingual naming

  4. Geographical Object categorisation

3.2.1. Feature / Feature Naming differentiation

This model defines a Geographical Object and a Geographical Name class. The former is for a named spatial object, the latter for detailed naming information. The general conceptual split of spatial object/name follows the Address/AddressableObject split in ISO19160-1 ISO19160-1. Addresses there are seen as a form of complex, multi-part, label - Feature Name - for a spatial Feature and Geographical Names here are considered a form of that.

This allows for the representation, and ultimately the management, of labels - text, numbers, identifiers, references - separately to the management of spatial objects.

This Feature / Feature Naming separation applies to Roads and Administrative Areas as well as Addresses and this model’s expression of Feature / Feature Naming separation is attained by making it a formal profile of the Compound Naming Model CNM which expresses it in general terms. Other profiles of the CNM for Addresses etc. are detailed in Queensland Spatial Information’s Supermodel which is an enterprise data model for multi-model data integration.

3.2.2. Detailed spatial modelling

Historically, Place Name Gazetteers have been limited in their spatial representation of named places, usually to point locations. This is clearly not sensible for objects with significant spatial coverage, such as mountain ranges or even population centres. For this reason, this model allows for the detailed spatial modelling of Geographical Objects using powerful spatial models, in particular GeoSPARQL GEO. GeoSPARQL allows for many kinds of geometries, and even multiple geometries, to be used to characterise the spatial presence of a Feature, which a Geographical Object is a special kind of. Figure Geographical Object spatial modelling shows the general pattern of relations defined by GeoSPARQL.

Spatiality
Figure 3. Geographical Object spatial modelling

This model does not further elaborate on the detailed spatial representation or relations of Geographical Objects - for that see GeoSPARQL itself - however a specific extended use of GeoSPARQL is called out here: fuzzy geometry modelling.

Geographical Names are often not precisely defined by administrative or natural boundaries so modelling of their spatial extent should cater for this. The Extended Geometries Ontology EGO is a GeoSPARQL extension that provides mechanisms for describing fuzzy boundaries and this ontology, as well as GeoSAPRQL itself, should be used for this. The Examples section shows this.

3.2.3. Multiple names

Geographical Objects may have multiple names in one of several or even multiple, different, forms. For example, a name may have been used for a place historically but that name is no longer recommended for use. Or a place may have different names in multiple languages or concurrent official and unofficial names.

Official/unofficial names

This model conveys the officialness of a Geographical Names by indicating who is or was responsible for a name status, with statuses defined in a vocabulary, and when the status is in effect. The official status of a name may then be determined by:

  • whether one accepts the jurisdiction of the name creator/alterer

  • what the time period of interest is

For example, in the State of Queensland in 2023, the Minister for Resources has the jurisdictional authority within the State for the gazetting of place names, thus the claim that "K’gari" - the name for a Geographical Object formerly known as "Fraser Island" - is the official place name (the gazetted name) of the Object since its naming by the minister in June, 2023, must be respected within the State after the naming. It is possible that other jurisdictions do not honour that name status and use - officially or otherwise - different names for K’gari.

Name changes over time

Objects' names change over time and this model allows for them to have statues that have temporality indicated. the island "K’gari" has only officially, within the State of Queensland, been known as such since the 7th of June, 2023. From the 10th of May, 1842 until that date, it was officially known as "Fraser Island".

See the example in Examples.

Note that this model allows for names with different statuses so that the island now called "K’gari", is still called "Fraser Island" in some unofficial way - perhaps this is now a historical place name.

This model does now enforce a particular handling of names and statuses: it only supplies mechanisms for representing names and statuses over time.

Multiple names

It is easy to see how places might have multiple names over time or perhaps multiple names concurrently with different statuses. However, it is also possible that places may have multiple Names with the same status concurrently. In such cases, the different Names may need to be distinguishable via other properties, perhaps the language of the name, but perhaps not: perhaps some places may simply have more than one name at a time with the same status.

Particular rules about name concurrency will need to be created and used by model implementers.

Indigenous / multi-lingual naming

The language of a name may be indicated with a recognised language code applied to the name. For example, "Tasmania" may be indicated as being an English name with use of the ISO 639-1 2-letter language code ISO639-1 "en" or perhaps the ISO 639-2 3-letter language code ISO639-2 "eng" or similar.

Extended ISO639-like language codes may be used for indigenous languages or language variants as long as the code’s definition is discoverable.

Names in multiple languages may exist concurrently, with different or the same statuses, depending on implementer’s own rules. See Examples.

3.2.4. Geographical Object categorisation

Geographical Objects named are often categorised and Australian Place Name Gazetteer datasets have historically contained categorisation for/alongside or with the names gazetted. Here, as per the Feature / Feature Naming differentiation modelling principle above and as per the Place Names ontology PNO, object categorisation is applied to the object names, not the name itself. Thus, the object now named "K’gari" and previously named "Fraser Island" has not lost its categorisation of Island wich is applied to the Geographical Object, not either of the Geographical Names.

3.3. Model resources

This document is this model’s "Specification" which is its authoritative, human-readable, definition document. This model also contains other resources with other roles:

Resource Role Notes

Ontology

Schema

The technical, machine-readable, version of this model

Supporting Vocabularies

Vocabulary

The codelist vocabularies developed for this model and links to others defined elsewhere but used by this model

Requirements Section

Guidance

The Requirements addressed by this model

Validation Section & SHACL Validator

Validation

The machine-readable validator file used to validate data claiming conformance to this model

Templating Section

Guidance

The template logic used for Basic and Short Form templates

Examples Section & Extended example data files

Example

Examples of data conforming, and some not conforming, to this model

Code Repository

Code Repository

The online, version control, repository containing all the resources of this model

4. Model

This model is composed of Web Ontology Language (OWL) OWL Classes and Properties. While some properties are restricted in their use to various classes, the Classes and Properties are actually defined individually and both are "first class model citizens", with global identity, that can be used in isolation and together. This is in contrast to Unified Modelling Language (UML) Class Diagrams which treat Properties as sub-parts of particular classes.

This model defines only three Classes and one Property but reuses many Classes and Properties from other models. Where it does, basic details of, a reference to that Class or Properties' definition via rdfs:isDefinedBy, and a scope note about using it in this model are given.

4.1. Classes

4.1.1. Geographical Name

Property Value

IRI

:GeographicalName

Preferred Label

Geographical Name

Definition

The Geographical Name class represents structured information that allows unambiguous determination of a Geographical Object for the purposes of identification and location

Is Defined By

This model

Sub-class Of

cn:CompoundName

History Note

Specialised from CNM's Compound Name class

Expected Properties

is name for, value, additionalType, hasPart, has lifecycle stage, has pronunciation

Example

 
# Shorncliffe, a Neighbourhood
# As per Examples: Basic Use section below
ex:geographical-name-x
  a :GeographicalName ;
  cn:isNameFor ex:geographical-object-y ;
  rdf:value "Shorncliffe"@en ;
  sdo:additionalType gpt:GeographicalGivenName ;
  sdo:description "Name originally an English place name..." ;
  skos:historyNote "Originally approved by Queensland Place Names Board.." ;
  :hasPronunciation "[ʃɔrnklɪf]"^^:IPAPronunciation ;
.

ex:geographical-object-y
  a :GeographicalObject ;
  sdo:additionalType goc:Neighbourhood ;
.

4.1.2. Geographical Object

Property Value

IRI

:GeographicalObject

Preferred Label

Geographical Object

Definition

A geospatial object that is unambiguously identified by a Geographical Name.

Is Defined By

This model

Sub-class Of

geo:Feature

History Note

Specialised from GEO's Feature class, as used in CNM

Scope note

Judgement as to what makes for a permissible GeographicalObject rests with the implementer. This model’s technical requirements are only that the object is a legal geo:Feature object, thus implementers may make Geographical Objects of almost anything.

Required Properties

additionalType: Instances of this object MUST indicate a value for additionalType with a value taken from a controlled vocabulary, such as Geographical Object Categories in the section Supporting Vocabularies

Expected Properties

hasGeometry, hasPart

Example

 
ex:geographical-object-y
  a :GeographicalObject ;
  sdo:additionalType goc:Neighbourhood ;
.

4.1.3. ISA Pronunciation

Property Value

IRI

:ISAPronunciation

Preferred Label

ISA Pronunciation

Definition

A textual datatype that uses ISA Pronunciation syntax

Is Defined By

This model

Sub-class Of

rdfs:Datatype

History Note

Create in this model

Scope note

Use this to indicate that the object of the predicate :hasPronunciation uses ISA Pronunciation syntax

Example

See example for has pronunciation

4.1.4. Compound Name

Property Value

IRI

cn:CompoundName

Preferred Label

Compound Name

Definition

A Compound Name is a literal value, or objects that can be interpreted as literal values, that describe or name a Feature

Is Defined By

CNM

Scope Note

The basis for the Road Name class. This class is also used for instances of Road Name parts

4.1.5. Lifecycle Stage

Property Value

IRI

lm:LifecycleStage

Preferred Label

Compound Name

Definition

A Compound Name is a literal value, or objects that can be interpreted as literal values, that describe or name a Feature

Is Defined By

Lifecycle Model

Scope Note

Used to indicate the lifecycle stage of any Roads Model part. Different stage types may be necessary for different class instances such as Road Name and Road Object and may be sourced from different vocabularies

4.1.6. Feature

Property Value

IRI

geo:Feature

Preferred Label

Feature

Definition

A discrete spatial phenomenon in a universe of discourse

Is Defined By

GEO

Scope Note

Used as the basis for the Road Object class

4.1.7. Geometry

Property Value

IRI

geo:Geometry

Preferred Label

Geometry

Definition

A coherent set of direct positions in space. The positions are held within a Spatial Reference System (SRS).

Is Defined By

GEO

Scope Note

Used to give spatial representation information for a Road Object

4.1.8. Concept

Property Value

IRI

skos:Concept

Preferred Label

Concept

Definition

An idea or notion; a unit of thought

Is Defined By

SKOS

Scope Note

Used to indicate a value that should come from a vocabulary (modelled as a `skos:ConceptScheme)

4.1.9. Resource

Property Value

IRI

rdfs:Resource

Preferred Label

Resource

Definition

The class resource, everything

Is Defined By

RDFS

Scope Note

Used to indicate any kind of RDF value - a literal, IRI or Blank Node

4.1.10. Literal

Property Value

IRI

rdfs:Literal

Preferred Label

Literal

Definition

The class of literal values, eg. textual strings and integers

Is Defined By

RDFS

Scope Note

Used to for annotation predicate values, such as description

4.2. Properties

4.2.1. has pronunciation

Property Value

IRI

:hasPronunciation

Preferred Label

has pronunciation

Definition

Indicated a pronunciation guide for the subject’s name

Is Defined By

This model

Domain

Compound Name

Range

ISA Pronunciation

Scope Note

Used to link a name to a pronunciation guide for it

Example

 
# Shorncliffe, pronounced [ʃɔrnklɪf]
ex:geographical-name-x
  a :GeographicalName ;
  rdf:value "Shorncliffe"@en ;
  :hasPronunciation "[ʃɔrnklɪf]"^^:IPAPronunciation ;
.

4.2.2. is name for

Property Value

IRI

cn:isNameFor

Preferred Label

is name for

Definition

Inverse of sdo:name

Is Defined By

CNM

Domain

Compound Name

Range

Feature

Scope Note

Used to link a name to a feature

Example

 
# A road with a name
PREFIX ex: <http://example.com/>

ex:road-name-x
    a :RoadName ;
    cn:isNameFor ex:road-object-y ;
.

ex:road-object-y
    a :RoadObject , geo:Feature ;
    sdo:name ex:road-name-x ;
.

4.2.3. has lifecycle stage

Property Value

IRI

lm:hasLifeCycleStage

Preferred Label

has lifecycle stage

Definition

Indicates a Resources' Lifecycle Stage

Is Defined By

LM

Domain

Resource

Range

Lifecycle Stage

Scope Note

Used to indicate an object’s lifecycle stage

Example

 
# A Road Name with two Lifecycle Stages indicated:
# one current and one past
ex:road-name-x
  a :RoadName ;
  lm:hasLifeCycleStage [
    # this Stage has ceased
    time:hasTime [
      time:hasBeginning [ time:inXSDDate "1982-02-10"^^xsd:date ] ;
      time:hasEnd [ time:inXSDDate "1982-05-11"^^xsd:date ] ;
    ] ;
    sdo:additionalType lm:proposed ;
  ] ,
  [
    # this Stage is still in effect - no hasEnd given
    time:hasTime [
      time:hasBeginning [ time:inXSDDate "1982-05-11"^^xsd:date ] ;
    ] ;
    sdo:additionalType lm:current ;
  ] ,
.

4.2.4. value

Property Value

IRI

rdf:value

Preferred Label

value

Definition

Idiomatic property used for structured values

Is Defined By

RDF

Scope Note

Used to indicate literal or object values for Compound Name objects

4.2.5. additionalType

Property Value

IRI

sdo:additionalType

Preferred Label

additionalType

Definition

An additional type for the item, typically used for adding more specific types from external vocabularies

Is Defined By

SDO

Scope Note

Used to indicate a subtype for Road Name and Road Object instances

4.2.6. hasPart

Property Value

IRI

sdo:hasPart

Preferred Label

has part

Definition

Indicates a part of a whole

Is Defined By

SDO

Scope Note

Used to indicate the parts of a Road Name or of a Road Object

4.2.7. hasGeometry

Property Value

IRI

geo:hasGeometry

Preferred Label

has geometry

Definition

A spatial representation for a given Feature

Is Defined By

GEO

Domain

Feature

Range

Geometry

Scope Note

Used to indicate the Geometry of a Feature, such as a Road Object

4.2.8. description

Property Value

IRI

sdo:description

Preferred Label

description

Definition

A description of the item

Is Defined By

SDO

Scope Note

Use to indicate the main description of a Geographical Name. May also be used to annotate a Geographical Object

4.2.9. history note

Property Value

IRI

sdo:historyNote

Preferred Label

history note

Definition

A note about the past state/use/meaning of a concept

Is Defined By

SKOS

Scope Note

Use to indicate the history of a Geographical Name

5. Supporting Vocabularies

This model depends on several vocabularies to give specific values for certain theming - general classification - and sub-typing properties.

The vocabularies are all independently-published and governed Knowledge Graph artifacts and do not record any relation to this model in their own data.

The vocabularies' details are given in the table below.

Persistent IRI Name Description Model property

Geographical Objects

https://linked.data.gov.au/def/go-categories

Geographical Object Categories

A 3-level hierarchy of Geographical (Place) Object categories

sdo:additionalType for a Geographical Object

Geographical Names

https://linked.data.gov.au/def/gn-part-types

Geographical Part Types

This vocabulary describes values of name part types used in geographical naming

sdo:additionalType for a Geographical Name’s Compound Name part

https://linked.data.gov.au/def/gn-statuses

Geographical Name Statuses

This vocabulary contains classifications of how official, or otherwise, a Geographical Name is

sdo:additionalType for a Geographical Name’s Lifecycle Stage

6. Requirements

Here are the itemised Requirements referenced in the Sources of Requirements subsection of the Introduction and note for them on how this model satisfies them.

6.1. Requirements List

ID Name Description

Req01

MUST align with Address modelling

Profiles the Compound Naming Model CNM and the Lifecycle Model LM which the QSI Address Model also profiles

Req02

MUST implement the Feature Name / Feature pattern

Implements Road Name & Road Object to specialise the pattern for roads

Req03

MUST be interoperable with detailed spatial object modelling, for example of the sort implemented in the Cadastre Model

Implements Road Object as a GeoSPARQL Feature to which any GeoSPARQL spatial modelling can be applied

Req04

MUST allow for name changes over time

Allows the Lifecycle Model LM to be applied to names

Req05

MUST allow for official/unofficial names

Allows for Provenance Ontology PROV qualified attribution to be applied to names

Req06

MUST allow for indigenous naming

Allows for multiple language names

Req07

MUST allow for named object categorisation

Allows for Geographical Object categorisation using the established ICSM categories as a vocabulary

7. Validation

This section will be completed when Business Rules for Road Labels are determined - etc. June, 2023

8. Templating

To present - on screen or in print form - the consolidated name for a Geographical Object, the parts of a Geographical Name need to be assembled in a particular order and perhaps processes to make contractions etc. The logic for this is not contained in the Classes or Properties of the model but in this Templating section.

Users of this model are free to implement additional templates and template logic to suit their needs.

8.1. Basic Template

This template assembled the Geographical Name parts in the most basic manner, which is also the manner expected to be used most commonly.

The template, in EBNF form ISO-IEC-14977, is:

space = " "
extended_letters = "A" | "B" | "C" | "D" | "E" | "F" | "G"
       | "H" | "I" | "J" | "K" | "L" | "M" | "N"
       | "O" | "P" | "Q" | "R" | "S" | "T" | "U"
       | "V" | "W" | "X" | "Y" | "Z" | "a" | "b"
       | "c" | "d" | "e" | "f" | "g" | "h" | "i"
       | "j" | "k" | "l" | "m" | "n" | "o" | "p"
       | "q" | "r" | "s" | "t" | "u" | "v" | "w"
       | "x" | "y" | "z" | " " | "-" ;
prefix = extended_letters
prefix_spaced = prefix, space
given_name = extended_letters
suffix = extended_letters
suffix_spaced = space, suffix

geographical_name = [prefix_spaced], given_name, [suffix_spaced]

Consider a Geographical Name with the following parts:

  • Geographical Given Name, value text "Caboolture"

  • Geographical Name Suffix, value text "South"

The template would result in this:

space = " "
name = "Caboolture"
suffix = "South"
suffix_spaced = " South"

geographical_name = "Caboolture South"

8.2. Short Form Template

This Short Form Template is an example of an alternative template to the Basic Template above.

This template uses the same layout logic as the Basic Template but makes certain contractions:

  • Geographical Name Suffix

    • North → Nth

    • South → Sth

    • East → Est

    • West → Wst

Consider a Geographical Name with the following parts:

  • Geographical Given Name, value text "Caboolture"

  • Geographical Name Suffix, value text "South"

This template’s result for these values will be calculated as per the Basic Template example with the same input values but with the contractions from the list above applied result in:

space = " "
name = "Caboolture"
suffix = "Sth"
suffix_spaced = " Sth"

geographical_name = "Caboolture Sth"

9. Examples

9.1. Basic Use

EG 1
Figure 4. An example of basic use of this model to describe the Geographical Name "Shorncliffe"

9.2. Name Type Parts

EG 2
Figure 5. An example of basic use of this model to describe the Geographical Name "Lizard Island" which, while containing the feature-related part "Island" also has the Geographical Object categorised as an Island. The name part and categorisation need not match, for example "Nanny Goat Creek" may be the name for a Geographical Object categorised as a Watercourse, not a Creek (no such categorisation exists in the usual vocabulary used for categorisation)

9.3. Multiple Names

EG 3
Figure 6. An example for the Geographical Name "K’gari" for an island formerly known as "Fraser Island". Note that while "Fraser Island" is preserved as a Historical name, specific decisions about name statuses are not part of this model but must be handled by implementers according to their needs. This model just allows for any status sequencing and representation.

9.4. Authority

EG 4
Figure 7. An example showing use of this model indicating the Agent responsible for the name of a Geographical Place Name. Note that the role of Custodian is the preferred term for for a jurisdictional authority name issuer’s role.

Bibliography

CNM

Australian Government Linked Data Working Group. Compound Naming Model. Semantic Web data model (2023). https://linked.data.gov.au/def/cn

CONNEGP

World Wide Web Consortium, Content Negotiation by Profile, W3C Working Draft (20 March 2022). https://w3c.github.io/dx-connegp/connegp/

EGO

Nicholas Car, Extended Geometries Ontology, 2023. https://w3id.org/idn/def/ego

GEO

Open Geospatial Consortium, OGC GeoSPARQL - A Geographic Query Language for RDF Data, Version 1.1 (2021). OGC Implementation Specification. http://www.opengis.net/doc/IS/geosparql/1.1

ISO-IEC-14977

International Organization for Standardization, ISO/IEC 14977 : 1996(E): Extended Backus–Naur form. International Organization for Standardization (1996). https://www.cl.cam.ac.uk/~mgk25/iso-14977.pdf

ISO639-1

International Organization for Standardization, ISO 639-1:2002 Codes for the representation of names of languages — Part 1: Alpha-2 code. International Organization for Standardization (2002). https://www.iso.org/standard/22109.html

ISO639-2

International Organization for Standardization, ISO 639-2:1998 Codes for the representation of names of languages — Part 2: Alpha-3 code. International Organization for Standardization (1998). https://www.iso.org/standard/4767.html

ISO-IEC-14977

International Organization for Standardization, ISO/IEC 14977 : 1996(E): Extended Backus–Naur form. International Organization for Standardization (1996). https://www.cl.cam.ac.uk/~mgk25/iso-14977.pdf

ISO19101-1

International Organization for Standardization, ISO 19101-1:2014 Geographic information — Reference model — Part 1: Fundamentals (2014)

ISO19156

International Organization for Standardization, ISO 19156: Geographic information — Observations and measurements (2011)

ISO19160-1

International Organization for Standardization, ISO 19160-1: Addressing Part 1: Conceptual model (2015). https://www.iso.org/standard/61710.html

LM

Australian Government Linked Data Working Group. Lifecycle Model (2023). https://linked.data.gov.au/def/lifecycle

OWL

World Wide Web Consortium, OWL 2 Web Ontology Language Document Overview (Second Edition), W3C Recommendation (11 December 2012). https://www.w3.org/TR/owl2-overview/

PNO

Geoscience Australia, Place Names Ontology, Semantic Web model (2020). https://linked.data.gov.au/def/placenames

PROF

World Wide Web Consortium, The Profiles Vocabulary, W3C Working Group Note (18 December 2019). https://www.w3.org/TR/dx-prof/

PROV

World Wide Web Consortium, The Profiles Vocabulary, W3C Working Group Note (18 December 2019). https://www.w3.org/TR/dx-prof/

RDF

World Wide Web Consortium, RDF 1.1 Concepts and Abstract Syntax, W3C Recommendation (25 February 2014). https://www.w3.org/TR/rdf11-concepts/

RDFS

World Wide Web Consortium, RDF 1.2 Schema, W3C First Public Working Draft (16 May 2023). https://www.w3.org/TR/rdf12-schema/

SDO

W3C Schema.org Community Group, schema.org. Community ontology (2015). https://schema.org

SSN

World Wide Web Consortium, Semantic Sensor Network Ontology, W3C Recommendation (19 October 2017). https://www.w3.org/TR/vocab-ssn/

SKOS

World Wide Web Consortium, SKOS Simple Knowledge Organization System Reference, W3C Recommendation (18 August 2009). https://www.w3.org/TR/skos-reference/

TTL

World Wide Web Consortium, RDF 1.1 Turtle Terse RDF Triple Language, W3C Recommendation (25 February 2014). https://www.w3.org/TR/turtle/

XSD

World Wide Web Consortium, XML Schema Part 2: Datatypes, Second Edition, W3C Recommendation (28 October 2004). http://www.w3.org/TR/xmlschema-2/.