Status: closed Implementation work Blocked
Source: Independent ( Leonard Levine)
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
Disposition: Resolved — LCC 1.0
Flexibility to comply with governmental & corporate guidance.
The resolution to this issue affects several clauses in the specification, including (1) clause 1, Scope, primarily in its introduction, (2) clause 4, Terms and Definitions, and (3) clause 9.3 Ontology: Country Representation. This resolution depends on the resolution to LCC-14.
Care has been taken to limit dependencies on ISO 3166, to generalize definitions, and to refactor the ontology slightly to make it easier to incorporate other code sets by combining the former country and subdivision codes into a common region identifier.
The resolution to another issue, issue
LCC-7, also provides an informative annex and related source scripts that automate the process of generate the codes themselves, which users can modify to incorporate other code sets.
Updated: Tue, 19 Dec 2017 20:01 GMT
- 1. Country Representation Class Hierarchy.svg 551 kB (image/svg+xml)
- 2. Geographic Regions.svg 816 kB (image/svg+xml)
- 3. Classifying Geographic Regions.svg 451 kB (image/svg+xml)
- 5. Definition of Country.svg 1.26 MB (image/svg+xml)
- CountryRepresentation.rdf 27 kB (application/rdf+xml)
- resolution_LCC-4.doc 347 kB (application/msword)