1. OMG Mailing List
  2. Languages, Countries and Codes 1.1 Finalization Task Force

Open Issues

  • Issues not resolved
  • Name: lcc-ftf
  • Issues Count: 11

Issues Descriptions

Need to include rdfs:isDefinedBy for every first class ontology element for cases where users load the ontology into a knowledge graph

  • Key: LCC_-12
  • Status: open  
  • Source: Thematix Partners LLC ( Elisa Kendall)
  • Summary:

    For ease of use in certain applications where "follow your nose" does not work, such as for ontologies loaded into a knowledge graph, it is helpful to have an rdfs:isDefinedBy statement for every first class entity. The object for the triple should be the IRI of the ontology that contains the entity (i.e., all classes, properties, and individuals).

  • Reported: LCC 1.0b1 — Thu, 20 Jul 2017 01:38 GMT
  • Updated: Thu, 20 Jul 2017 01:38 GMT

Including all subdivision codes in a single ontology is not workable - they should be separated into distinct namespaces / ontologies for ease of use

  • Key: LCC_-11
  • Status: open  
  • Source: Thematix Partners LLC ( Elisa Kendall)
  • Summary:

    Currently, the set of subdivision codes available in LCC (which only reflect North America) are all in one namespace and ontology. They should be split into an ontology per country containing the relevant regions for ease of use and maintenance purposes.

  • Reported: LCC 1.0b1 — Thu, 20 Jul 2017 01:24 GMT
  • Updated: Thu, 20 Jul 2017 01:33 GMT

Definition for denotes and hasDenotation should better reflect ISO 1087 / 11179

  • Key: LCC_-10
  • Status: open  
  • Source: Thematix Partners LLC ( Elisa Kendall)
  • Summary:

    The definitions for these properties are not identical to those under development for the MVF submission, which provides better correlation to the ISO standards. If the LCC definitions are revised, then MVF can simply reuse the LCC ontologies rather than creating new, incompatible definitions.

  • Reported: LCC 1.0a1 — Fri, 16 Jun 2017 20:58 GMT
  • Updated: Fri, 16 Jun 2017 21:26 GMT

The individual representing the Canadian Province of Newfoundland and Labrador is misnamed

  • Key: LCC_-8
  • Status: open  
  • Source: Thematix Partners LLC ( Elisa Kendall)
  • Summary:

    The concept in the ISO 3166-2 subdivision codes ontology for the Canadian Province of Newfoundland and Labrador is misnamed as simply Newfoundland. Also, the Canadian Territory of Nunavut should be represented and is missing.

  • Reported: LCC 1.0b1 — Tue, 21 Jun 2016 20:11 GMT
  • Updated: Thu, 6 Apr 2017 14:19 GMT

Flexibility to comply with governmental & corporate guidance.

  • Key: LCC_-4
  • Status: open   Implementation work Blocked
  • Source: Office of the Secretary of Defense ( Leonard Levine)
  • Summary:

    Many users of Language, Countries, and Codes (LCC) require flexibility to change the mappings to countries and codes to comply with governmental and corporate guidance (laws, regulations, rules, etc.). The LCC specification should clearly describe how to implement such flexibility.

    A potential solution would be to create an annex with an example that shows how this can be done, and that describes the kinds of patterns that the spec encourages people follow to ensure that the reasoning would work for them.

    From the RFC,
    "In all four (4) cases, implementers may extend any of the LCC ontologies as necessary, to add language or country codes required between releases, or to add application-specific codes needed to address various requirements. Typically such extensions will entail ontology-level conformance. We encourage implementers to submit any requirements for extension to the relevant LCC task force, as appropriate." Chapter 2, page 12.
    Others occurrences of this issue in the RFC include:

    Country is defined as "in the context of ISO 3166"; and some entities do not use ISO 3166 or not all of ISO 3166. Some use ISO 3166 only indirectly tailored to their own requirements. Similarly with CountryIdentifier and CountrySubdivision. Chapter 4. Terms and Definitions.

    The ISO 3166 Country Representations in Section 9.2, 9.3, and elsewhere may present challenges to users that do not strictly use ISO 3166 names and codes.

    Table 9-2 Country Representation Ontology Metadata is dependent on ISO 3166, esp. sm:directSource ,

    UN and other names are not universally accepted. Table 9-3 Country Representation Ontology Details

    This will probably ripple through the other normative and non-normative (informative) deliverables associated with this RFC including RDF/OWL and XMI.
    ======

    Chapter/Section (additional): 9.4 Ontology: ISO 3166-1 Country Codes

  • Reported: LCC 1.0b1 — Tue, 29 Mar 2016 18:22 GMT
  • Updated: Thu, 6 Apr 2017 14:19 GMT
  • Attachments:

Several changes from newsletter IV-14 not reflected


The spec should document the process for maintaining currency

  • Key: LCC_-7
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    There should be an annex to explain the approach to reflecting updates from ISO e.g. subscribing to ISO notifications and raising issues reflecting the changes. There should also be targets for frequency/lead time/

  • Reported: LCC 1.0b1 — Fri, 11 Nov 2016 02:28 GMT
  • Updated: Thu, 6 Apr 2017 14:19 GMT



The spec and OWL should indicate which version of ISO specs is reflected

  • Key: LCC_-2
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    People should be able to easily discover which updates have been incorporated already.

  • Reported: LCC 1.0b1 — Fri, 11 Nov 2016 02:26 GMT
  • Updated: Thu, 6 Apr 2017 14:19 GMT

The class called ApproximateCoordinates is not well defined and needs properties associated with it

  • Key: LCC_-1
  • Status: open  
  • Source: Thematix Partners LLC ( Elisa Kendall)
  • Summary:

    In fact, what this class should be called is something like GeographicArea, and then provide a means by which one can add multiple points, such as longitude and latitude to that area.

    We also need to incorporate the concept of Continent, which would be a child of GeographicArea so that we can divide the subdivisions of countries into continents to support evolution and management of those subdivisions.

  • Reported: LCC 1.0b1 — Thu, 2 Mar 2017 20:46 GMT
  • Updated: Thu, 6 Apr 2017 14:16 GMT