reduce the use of acronyms about osdu-ontology HOT 3 CLOSED

Hi Vladimir - in large part, we stick exactly to the acronyms, naming conventions, and descriptions provided for usage in the OSDU 3.0.0 schema. It would potentially be better to be more descriptive where possible, but we keep acronym usage the same to maximize exact matches for users trying to map relational OSDU data using this ontology.

from osdu-ontology.

I see what you mean, I found them at

• https://community.opengroup.org/osdu/platform/data-flow/data-loading/open-test-data/-/blob/master/rc--3.0.0/5-templates/master_data/template_maPerforationInterval.1.0.0.json#L486
• https://community.opengroup.org/osdu/platform/data-flow/data-loading/open-test-data/-/blob/master/rc--3.0.0/3-schema/master-data/PerforationInterval.1.0.0.json#L401

However, semantic modeling is largely about explicating the meaning of things.
So perhaps you can use the full spellings in rdfs:label to make things more clear?

cCLTopShotDistance rdf:type owl:DatatypeProperty ;
  rdfs:label "Casing Collar Locator To Top Shot Distance";
  rdfs:comment "Distance from CCL to Interval Top " ;
``

from osdu-ontology.

That is a good idea, I'll mark this as a desired fix and get to it when possible

from osdu-ontology.