Search results

Typos in the specs

Status: Open.

#42 In SEMICeu/Core-Location-Vocabulary;

· EmidioStani opened on Apr 8, 2025

AdministrativeUnit lacks hierarchy property and label/description

Status: Open.

#41 In SEMICeu/Core-Location-Vocabulary;

· VladimirAlexiev opened on Mar 26, 2025

broken link in spec

Status: Open.

#40 In SEMICeu/Core-Location-Vocabulary;

· VladimirAlexiev opened on Mar 26, 2025

Core Location Vocabulary reuses legacy <code>locn</code> in spec, not in RDF

Status: Open.

#39 In SEMICeu/Core-Location-Vocabulary;

· jakubklimek opened on Feb 21, 2025

Properly referencing the vocabulary

Status: Open.

#38 In SEMICeu/Core-Location-Vocabulary;

· areleu opened on Nov 28, 2023

A structural way to represent address supplements.

Status: Open.

#37 In SEMICeu/Core-Location-Vocabulary;

· EmielPwC opened on Jul 11, 2023

How to use m8g:AdminUnit with NUTS?

Status: Open.

#36 In SEMICeu/Core-Location-Vocabulary;

· jakubklimek opened on Apr 14, 2023

Datatype for the property locn:locatorDesignator should be text (rdf:langString)?

Status: Open.

#27 In SEMICeu/Core-Location-Vocabulary;

· jimjyang opened on Oct 31, 2022

Datatypes of SEMIC-Address:Address.adminUnit and INSPIRE-Address:AddressRepresentation.adminUnit differ

Status: Open.

#25 In SEMICeu/Core-Location-Vocabulary;

· GeertThijs opened on Oct 12, 2022