API4KP — Need to rationalize the various properties in the ontology that employ linguistic entities

These are scattered about in the ontology, and should become subproperties of or be defined in terms of the commons 'uses' property.

This issue only impacts the ontologies, not the specification at this point.

Restructured a number of concepts and properties related to language / linguistic entities

This resolution impacts the ontologies only. Documentation for the ontologies will be addressed under API4KP-23.

Two ontologies were affected by this resolution: api4kp.rdf (the main ontology) and api4kp-lang.rdf. The changes involve a handful of updates to better align some of the properties related to language handling in API4KP, including, to the main api4KP ontology:

• separation of the dependency between hasSublanguage and embedsLanguage, including renaming embedsLanguage --> supportsEmbeddedLanguage
• making dol:Language subClassOf lcc-lr:Language rather than equivalent to it
• added api4kp:usesLanguage
• added property api4kp:supportsFormat, domain dol:Language, range api4kp-lang:metaFormat

To the api4kp-lang ontology:

• changed 'api4kp:defines some lcc-lr:language' to 'api4kp:defines some dol:formal language'
• create new 'api4kp-lang:supportsSerialization' sub-property of 'api4kp-lang:hasGrammar', with super-property of 'dol:supportsSerialization', domain dol:language and range api4kp-lang:Serialization
• create new 'api4kp-lang:supportsFormat' as a sub-property of 'api4kp-lang:hasGrammar' and sub-property of 'dol:isLinguisticallyRelatedTo', with domain dol:language and range api4kp-lang:MetaFormat