LCC11 — The addition of the language tags (LCC-2) introduced a logical inconsistency that must be corrected

Adding the language tags to the individuals created an inconsistency when running a reasoner over the set of ontologies that include the reference data. This is due to the fact that one cannot use a language tag with a datatype property whose range is xsd:string in OWL 2 / RDF 1.1. Rather, the range must be either rdfs:Literal or rdf:langString in order to tag individuals with a particular language.

The language tags are quite useful, and were requested by the LCC user community, so the correction needs to be made to the LanguageRepresentation and CountryRepresentation ontologies to enable use of the tags.

Revise the base language and country representation ontologies to use rdfs:Literal rather than xsd:string in properties for names

The RDF 1.1 specification introduced a new type for inclusion of language tagged strings in vocabularies, called rdf:langString. This datatype is not compatible with xsd:string. In the case of properties for language and country names, the original ontologies used xsd:string in the range and in class restrictions on Language and Country that became logically inconsistent when the language tags were introduced in the individuals.

This resolution changes the property range(s) and related restrictions from using xsd:string to rdfs:Literal, which is the common parent of xsd:string and rdf:langString, thus eliminating the inconsistency.