Has_participant is a primitive instance-level relation between a process, a continuant, and a time at which the continuant participates in some way in the process. The relation obtains, for example, when this particular process of oxygen exchange across this particular alveolar membrane has_participantthis particular sample of hemoglobin at this particular time.
To define the class-level counterpart of the participation relation we set:
P has_participant C = [definition] for all p, if Pp then there is some c, t such that Cct and p has_participant c at t.
--
You received this message because you are subscribed to the Google Groups "bfo-owl-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bfo-owl-deve...@googlegroups.com.
To post to this group, send email to bfo-ow...@googlegroups.com.
Visit this group at http://groups.google.com/group/bfo-owl-devel.
For more options, visit https://groups.google.com/d/optout.
I agree with the proposal regarding participation. However, I expect that in OWL ontologies the relation has_participant is much more frequently used, because having participants of a certain type is a necessary condition for most processes (e.g. phosphorylation subClassOf has_participant some Phosphate), whereas being participant of a certain type of process is much less frequently a necessary condition for continuants (e.g. Phosphate subClassOf participates_in some ???).Regarding concretization, could you explain why at-some-time always implies at-all-times ?