LCC_ — The tags used on identifiers in the LCC ontologies are unnecessarily complex

There should be a single hasTag property on all identifiers (that is not functional), rather than separate hasLanguageTag, hasCountryTag, and hasSubdivisionTag properties of their respective identifiers.

The tags used on identifiers in the LCC ontologies are unnecessarily complex

In the LanguageRepresentation ontology, (1) rename the hasLanguageTag property to hasTag, (2) eliminate the isFunctional constraint (since it's possible that there might be duplication across multiple code sets), (3) revise the definition of the property to be "a unique combination of alphanumeric characters corresponding to the identifier", and (4) add a skos:note that states, "Text-valued tags are included here as they may be useful for automated transformation or encoding systems, such as those used to produce IETF compliant language tags in XML."

Also, move the domain of hasTag from LanguageIdentifier to Identifier, and move restriction LCC-13 from LanguageIdentifier to Identifier, but loosen the constraint from an exact cardinality of 1 to some values from. Move the property and restriction from the Definition of Language Identifier diagram to the Definition of Identification Schemes and Identifiers diagram, and include the "has" property on the Definition of Language Identifier diagram. It was in the model as the parent property of hasDenotation but not on a diagram.

2. In the CountryRepresentation ontology, (1) eliminate the hasCountryTag data property and restriction lcc-cr-13 on that property, and (2) eliminate the hasSubdivisionTag property (no corresponding restriction).