Closed ajnelson-nist closed 2 years ago
Absent stronger feelings from the committee, I will assume the answer is yes, the correct subclassing for types:Thread
is core:UcoThing
, not core:UcoObject
, and adjust 430's implementation to account for this.
Answer's yes.
Issue 430 is establishing a top-level class
core:UcoThing
to give a parent class to classes that are not currently explicit subclasses of anything. (Implicitly in OWL, this makes them subclasses ofowl:Thing
.)Issue 469 asked about a few "Data structure"-style
Dictionary
classes that were not subclasses ofcore:UcoObject
, for reasons that I admit I still can't explain.Issue 393 added a new "Data structure"-style class,
types:Thread
, that I realize now serves some of the same data model role in UCO that thetypes:Dictionary
class does. However, it was defined in the implementation for 393 to be a subclass ofcore:UcoObject
.Should
types:Thread
be a subclass instead ofcore:UcoThing
like theDictionary
class?This will impact the implementation for Issue 430.