Closed rjyounes closed 3 months ago
DECISION:
hasSuperCategory
hadDirectSuperCategory
to hasDirectBroader
and make subproperty of hasBroader
hasUniqueSuperCategory
to hasUniqueBroader
and make subproperty of hasBroader
Taxonomy
)Maybe this is overly pedantic, but shouldn't the textual definition of broader
be something like "Relates a thing to another thing with a broader meaning that encompasses it" or "that subsumes it"? "Citrus Fruits" is broader than "Limes", and "Vertebrates" is broader than "Mammals". Now, "Limes" is a pretty narrow category and "Vertebrates" is a pretty broad category, so we could say the "Vertebrates" is broader than "Limes". But we're not meaning to talk just about broadness here; we also mean the the object encompasses the subject.
Also modify data conversion scripts to rename properties
@stevenchalem we might want to tune the definition in the future. My first impression is that people will understand the simple definition provided as it is intended (I hope so).
Maybe this is overly pedantic, but shouldn't the textual definition of
broader
be something like "Relates a thing to another thing with a broader meaning that encompasses it" or "that subsumes it"? "Citrus Fruits" is broader than "Limes", and "Vertebrates" is broader than "Mammals". Now, "Limes" is a pretty narrow category and "Vertebrates" is a pretty broad category, so we could say the "Vertebrates" is broader than "Limes". But we're not meaning to talk just about broadness here; we also mean the the object encompasses the subject.
Your point is accurate, and it would not be a bad idea to clarify as you say, for those folk who may wonder what we mean.
@stevenchalem This is a good point. Feel free to add an issue. I agree with @philblackwood that it is broadly understood - most people are familiar with the meaning from SKOS.
Since we introduce
hasBroader
in gist 13.0.0, it is now confusing that we have it in addition togist:hasSuperCategory
.hasBroader
is meant to apply to more cases, such as aspects, than ishasSuperCategory
, but it could apply equally well to categories. I propose that we:gist:hasSuperCategory
andgist:hasDirectSuperCategory
gist:hasDirectBroader
that serves the same purpose asgist:hasDirectSuperCategory