Class Vs Individual

aka: Type Token Distinction
Superclasses/supertypes define inheritance relationships between classes or types.
Metaclasses/metatypes classify classes
powerclasses/powertypes define properties of their classes/types; i.e. a class that classifies types of a given class, focusing on distinguishing between subclasses
- gUFO has gufo:Type which is the powerclass

Definitions

Only classes have superclasses, while other classifiers have supertypes.
- Since Class is also a Classifier, a superclass is always a supertype
powertype is a type whose instances are themselves types.

t.2024.07.11.09 after trying to formulate a comment for The Nature of Knowledge Graph Predicates, I feel a small a-ha!
- Data Scientist, as a sub-class of Occupation, requires that all its instances are occupations
2+:

just like my Dendron notes, do we have separate classes for things, or can concepts just double as classes?
- based on my experience, it's better to just have one class/concept/universal, but can be aliased from multiple places
  - t.2024.09.09.09 thinking about this more in

aka "Create a parallel hierarchy of instances as property values"
use one of the class annotation properties, e.g.
- rdfs:comment, rdfs:seeAlso, rdfs:isDefinedBy, or
- a custom annotation defined with owl:AnnotationProperty
  - used to add additional information to classes, properties, or individuals without affecting the logical structure of the ontology.
    - t.2024.05.25.14 well, kinda

maybe losing reasoning isn't important?
- transitive might be important,
  - e.g.
    - CharacterClassChoice shouldOccurBefore CharacterAbilityScoreChoice
    - CharacterAbilityScoreChoice shouldOccurBefore CharacterSkillChoice

"Punning is a simple way to provide for metamodeling that (a) does not require a major change to OWL 1.1 (DL) reasoners and (b) usually seems to satisfy the semantic requirements."
"An IRI I can be used in an OWL 2 ontology to refer to more than one type of entity. Such usage of I is often called metamodeling, because it can be used to state facts about classes and properties themselves. In such cases, the entities that share the same IRI I should be understood as different "views" of the same underlying notion identified by the IRI I."