New issue 15 by dosu...@gmail.com: domain and range of 'is preceded
by'/'precedes' too narrow?
http://code.google.com/p/bfo/issues/detail?id=15
domain and range of 'is preceded by', precedes and their child properties
is currently process. But shouldn't this be occurrent?
Here're the current definition:
occurrent: An entity that has temporal parts and that happens, unfolds or
develops through time. Sometimes also called perdurants.
process: A processual entity that is a maximally connected spatiotemporal
whole and has bona fide beginnings and endings corresponding to real
discontinuities.
SubClassOf: occurrent
----
A process must have 'bona fide beginnings and endings corresponding to real
discontinuities', but if i subdivide a process or any other occurrent into
fiat temporal parts, surely they will stand in 'is preceded by' relations
to each other.
in an axiomatisation of BFO, temporal order is primitive for time and
there are straightforward, almost trivial, and standard definitional
extensions for any temporal entity (e.g. if two occur at particular
times, the temporal order between the occurring entities follows that
between the corresponding temporal regions)
its credible that in an OWL encoding you would want to have vocabulary
that is notionally defined but for which the encoding contains no
definition
> --
> You received this message because you are subscribed to the Google Groups
> "BFO Discuss" group.
> To post to this group, send email to bfo-d...@googlegroups.com.
> To unsubscribe from this group, send email to
> bfo-discuss...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/bfo-discuss?hl=en.
>
>
Pierre Grenon replied on BFO discuss:
Selected post Jun 23, 2011; 12:22pm
Re: Issue 15 in bfo: domain and range of 'is preceded by'/'precedes' too
narrow?
Pierre Grenononline
Clairification:
- this comment refers to the version of BFO found using
http://purl.obolibrary.obo/bfo.owl , which resolves to:
http://bfo.googlecode.com/svn/trunk/src/ontology/bfo2.owl
Older versions may be better in some respects, but do not have the Foundry
compliant BFO URIs I need.
Also - I'm posting this on the BFO google code tracker
http://code.google.com/p/bfo/issues/detail?id=15. I would prefer answers
on this tracker ticket rather than on BFO discuss - or whatever other
mailing lists this might be forwarded to.
Cheers,
David O-S
Hi Pierre,
Thanks for your reply. I'm afraid I'm rather struggling to follow it. The
problem I have is a simple practical one with the domain and range defined
for this object property: http://purl.obolibrary.org/obo/BFO_0000063 (may
not resolve - probably better to browse to it in Protege after loading
http://purl.obolibrary.obo/bfo.owl). I don't understand why domain and
range are specified as process, rather than occurrent. This choice has
practical implications for my ontology of Drosophila development, for which
I would like to use this object property. I believe that the
relation/object property I am currently using is equivalent to the BFO one,
but I use it between stages. Following the BFO definition for process and
ocurrent, I classify stages as occurrents rather than processes as stages
may have fiat temporal boundaries.
Hope this is now clearer,
David
hiya, sorry for the admittedly cryptic first reply, let me try again
I think what you experience is a need for a defined term, but it is not
something that motivates modifying primitive vocabulary. In my
understanding, the file you are accessing and using is a snapshot of a
proposed reference encoding of the basic (!) BFO (BFO2 at that). So it
should contain primitive vocabulary but not all sorts of possible
definitional extensions.
Procedurally, I would argue this file should be kept minimal and if need be
an extended, distinct version with useful extensions be maintained
concurrently. It is likely such an extended version would prove more useful
to many but it is a different sort of work to find the right balance. This
being said there are obvious candidates for straightforward extension, like
the one you mention.
Meanwhile, the quick fix would be to just make this extension in your
ontology: add a super property to BFO2's 'precedes', call it something
like 'my generic precedes', and set domain and range on occurrent. You
could even set them on entity, but it'll be a bit tricky to make sense of
that and could be trickier to axiomatise in OWL.