UN LOCODE namespaces about spec-jsonld HOT 7 CLOSED

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

from spec-jsonld.

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

from spec-jsonld.

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

1. Define RDF Classes for UNLOCODE, Subdivision, Function. For Country "schema:Country" type can be used
2. Because there are codes in both UN/LOCODE and Subdivision code lists, separate namespaces are used for those and other entities.
3. 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
4. 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
5. UNLOCODE list items don't always have the location defined, so it is possible that it is also missing in the vocabulary.

from spec-jsonld.

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

from spec-jsonld.

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",""

from spec-jsonld.

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

from spec-jsonld.

We did this: #105

from spec-jsonld.