semanticarts/operators-ontology

Make operator object property names be verbs

Closed this issue · 3 comments

@rjyounes @sa-bpelakh
Rename:

  • specifiedValue to be specifiesValueAs
  • equalTo to be specifiesValueAsEqualTo
  • greaterOrEqualTo to be specifiesValueAsGreaterOrEqualTo
  • greaterThan to be specifiesValueAsGreaterThan
  • lessOrEqualTo to be specifiesValueAsLessOrEqualTo
  • lessrThan to be specifiesValueAsLessThan

Example:

VersionRangeSpec_GE_1_0_0_LT_2_0_0
	ops:specifiesValueAsGreaterOrEqualTo :_SemanticVersionNumber_1.0.0 ;
	ops:specifiesValueAsLessThan :_SemanticVersionNumber_2.0.0 ; 
	.

BatteryLifeSpec_GE_12Hours
        ops:specifiesValueAsGreaterOrEqualTo _Magnitude_12_Hours ;
        .

Really? Yes, that is correct grammatically, but it is so verbose. The grammar is almost obscuring meaning this way - eschew obfuscation! 😄

Yes, the names are annoyingly long. I don't have a better suggestion at the moment. Maybe we can make an exception to the verb rule. They properties always point to values, which is exactly what data properties do.

Alternate proposal:

  1. Rename: specifiedValue to be specifiesValueAs as before
  2. Leave the rest of the names as they are. They are all sub properties of specifiesValueAs so the semantics should be clear.

For example:

ops:specifiesValueAs
	a owl:ObjectProperty ;
	skos:definition "Relates a specification to a value that helps define an acceptable range for the value of a characteristic."^^xsd:string ;
	skos:prefLabel "specifies value as"^^xsd:string ;
	skos:scopeNote "This is an abstract superproperty, not intended for use in triples."^^xsd:string ;
	.

ops:lessOrEqualTo
	a owl:ObjectProperty ;
	rdfs:subPropertyOf ops:specifiesValueAs ;
	skos:definition "Relates a specification to a value that a characteristic must be less than or equal to."^^xsd:string ;
	skos:prefLabel "less or equal to"^^xsd:string ;
	.

DECISION: use the following pattern

  • hasSpecifiedValue
  • hasValueEqualTo
  • hasValueLessThan
  • hasValueGreaterOrLessThan