UN LOCODE namespaces - Githubissues

VladimirAlexiev commented 2 years ago

ADAVL "Andorra la Vella" is published as https://service.unece.org/trade/uncefact/vocabulary/unlocode-ad/ADAVL.

All other vocabs are published at single big pages, but I guess you found https://service.unece.org/trade/uncefact/vocabulary/unlocode/ to grow too big (Wikidata says over 100k entries, see https://www.wikidata.org/wiki/Property:P1937)
Well, that's inconsistent
To resolve LOCODE to this URL, one would have to split and manipulate the first two chars

The smart people at Wikidata can do such switcheroo

see https://www.wikidata.org/wiki/Property:P3608
eg BG200356710 (Ontotext) goes to https://wikidata-externalid-url.toolforge.org, which does some splitting and results in https://ec.europa.eu/taxation_customs/vies/vatResponse.html?memberStateCode=BG&number=200356710
- (the specific toolforge URL is https://wikidata-externalid-url.toolforge.org/?p=3608&url_prefix=http://ec.europa.eu/taxation_customs/vies/vatResponse.html?memberStateCode=&id=BG200356710)

But making consumers jump through hoops just ain't right. If you do #26, that won't be necessary

nissimsan commented 2 years ago

@kshychko , this looks like a great input. Please run with this for inspiration on our dealing iwth locodes...

nissimsan commented 2 years ago

@VladimirAlexiev , @Fak3 , what would be the ideal URI you'd like to see? https://service.unece.org/trade/uncefact/vocabulary/unlocode/ADAVL?

kshychko commented 2 years ago

According to the discussion on #105 the following approach is taken:

Define RDF Classes for UNLOCODE, Subdivision, Function. For Country "schema:Country" type can be used
Because there are codes in both UN/LOCODE and Subdivision code lists, separate namespaces are used for those and other entities.
The language is set to "en" for the labels without diacritics. It's impossible to determine the language for the names with diactics so the language is not specified there. - To discuss
As countries and subdivisions are ISO 3166-1 and ISO 3166-2 code lists we might need to think about publishing them separately from UNLCODE - To discuss
UNLOCODE list items don't always have the location defined, so it is possible that it is also missing in the vocabulary.

kshychko commented 2 years ago

The current outputs for discussion are available in https://github.com/uncefact/codes-locode/tree/main/vocab

kshychko commented 2 years ago

An example of cross between LOCODE and Subdivisions: Subdiivision: "TW","TPE","Taipei","special municipality" LOCODE: ,"TW","TPE","Taipei","Taipei","TPE","1--45---","AI","1101",,"2502N 12131E",""

nissimsan commented 2 years ago

IATA codes are missing, but let's tackle that in a separate PR.

nissimsan commented 2 years ago

We did this: https://github.com/uncefact/spec-jsonld/pull/105

uncefact / spec-jsonld

UN LOCODE namespaces #27