You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disclaimer: Participation by NIST in the creation of the documentation of mentioned software is not intended to imply a recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that any specific software is necessarily the best available for the purpose.
Is your feature request related to a problem? Please describe.
I noticed time:Instant appears in the gUFO class hierarchy, here:
rdfs:comment "An gufo:AbstractIndividual that reifies time instants. It is used as a target of the gufo:hasBeginPoint and gufo:hasEndPoint object properties."@en ;
rdfs:label "Instant"@en .
time:Instant is part of a class hierarchy with a parent and some siblings within its origin ontology OWL-Time: time:TemporalEntity is its parent, time:Interval a sibling at the same subclass depth as time:Instant, and time:ProperInterval a disjoint sibling of time:Instant, under time:Interval.
gUFO has time:Instant as a subclass of gufo:AbstractIndividual. Does this mean that time:Instant's nearby classes in the OWL-Time hierarchy are also gufo:AbstractIndividuals? E.g., is gufo:Event, as a concrete individual, automatically disjoint with time:Interval?
Describe the solution you'd like
It would be helpful to have some declared alignment with owl:Time, such as time:TemporalEntity going under gufo:AbstractClass; or, the alternative position being taken with an illustration of what under time:TemporalEntity is abstract vs. concrete; or, a stated non-commitment either way.
Describe alternatives you've considered
Alternatives are enumerated above. Either all, or some, of the time:TemporalEntity hierarchy is under gufo:AbstractIndividual.
Additional context
Knowing how gUFO treats the time:TemporalEntity hierarchy will help in understanding how the Allen relations as defined in owl:Time could relate gUFO objects.
The text was updated successfully, but these errors were encountered:
Disclaimer: Participation by NIST in the creation of the documentation of mentioned software is not intended to imply a recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that any specific software is necessarily the best available for the purpose.
Is your feature request related to a problem? Please describe.
I noticed
time:Instant
appears in the gUFO class hierarchy, here:gufo/gufo.ttl
Lines 1447 to 1451 in 6eb73ad
time:Instant
is part of a class hierarchy with a parent and some siblings within its origin ontology OWL-Time:time:TemporalEntity
is its parent,time:Interval
a sibling at the same subclass depth astime:Instant
, andtime:ProperInterval
a disjoint sibling oftime:Instant
, undertime:Interval
.gUFO has
time:Instant
as a subclass ofgufo:AbstractIndividual
. Does this mean thattime:Instant
's nearby classes in the OWL-Time hierarchy are alsogufo:AbstractIndividual
s? E.g., isgufo:Event
, as a concrete individual, automatically disjoint withtime:Interval
?Describe the solution you'd like
It would be helpful to have some declared alignment with
owl:Time
, such astime:TemporalEntity
going undergufo:AbstractClass
; or, the alternative position being taken with an illustration of what undertime:TemporalEntity
is abstract vs. concrete; or, a stated non-commitment either way.Describe alternatives you've considered
Alternatives are enumerated above. Either all, or some, of the
time:TemporalEntity
hierarchy is undergufo:AbstractIndividual
.Additional context
Knowing how gUFO treats the
time:TemporalEntity
hierarchy will help in understanding how the Allen relations as defined inowl:Time
could relate gUFO objects.The text was updated successfully, but these errors were encountered: