LCC 1.1 RTF Avatar
  1. OMG Issue

LCC11 — Provide capability to reference countries and regions using their code

  • Key: LCC11-4
  • Status: closed  
  • Source: 88solutions ( Pete Rivett)
  • Summary:

    Many external datasets reference countries using their 2 character code. These can be very large sets (e.g. the GLEIF dataset which covers more than a million legal entities, each with a jurisdiction and up to 5 addresses).
    To transform them to RDF referencing the Country in LCC requires a reverse lookup of the code to find the LCC URI which is based on the country name. For conversion of large sets this could be very expensive. It would be far more convenient to have a URI based on the code which could be used in the dataset with no lookup needed. I have already generated such a set of URIs with sameAs triples linking them to the normative LCC URIs.
    The problem is worse for region codes where the reverse lookup would need to be in one of 200 different ontologies (one per country). I have generated a single file of sameAs triples covering all the regions.

    Rather than people such as myself independently doing this on an ad hoc basis, these 2 files should be officially published by OMG as an optional part of LCC.

  • Reported: LCC 1.0 — Wed, 6 Feb 2019 18:18 GMT
  • Disposition: Resolved — LCC 1.1
  • Disposition Summary:

    Create new Informative adjunct ontologies and document in the spec

    The adjunct ontologies are simply created by processing the RDF files for ISO3166-1, and all the ISO3166-2 SUbdivisions and for each Country/Subdivision creating a sameAs triple linking its URI with one based on the code.
    For example :
    <lcc-cr:CountrySubdivision rdf:about="&lcc-3166-2-adj;US-DE">
    <owl:sameAs rdf:resource="http://www.omg.org/spec/LCC/Countries/Regions/ISO3166-2-SubdivisionCodes-US/Delaware"/>
    </lcc-cr:CountrySubdivision>

  • Updated: Tue, 8 Oct 2019 17:57 GMT
  • Attachments: