BFO’s specific and generic dependence and generalising progress in essential and mandatory parts

The Basic Formal Ontology (BFO) version 1.1 has, compared to v1.0, the additions SpecificallyDependentContinuant (SDC) and GenericallyDependentContinuant (GDC); at least on 30 June when I downloaded it. They are defined as follows (emphasis added):
SDC = “A continuant [snap:Continuant] that inheres in or is borne by other entities. Every instance of A requires some specific instance of B which must always be the same”. To note: it subsumes Quality and RealizableEntity.
GDC = “A continuant [snap:Continuant] that is dependent on one or other independent continuant [snap:IndependentContinuant] bearers. For every instance of A requires some instance of (an independent continuant [snap:IndependentContinuant] type) B but which instance of B serves can change from time to time”.
Setting aside the lack of similarity in the formulation of the definitions, difference in constraints on the participating entities, awkward English, and absence of full formal definitions (neither in the text nor in the OWL file), the interesting bit I will zoom in on now is the mandatoryness with “same” [at all times] and “some…from time to time”. This sounds just like our work on essential versus plain mandatory parts and wholes, but then counting for an arbitrary relation that relates [in]dependent continuants as opposed to limiting it to part-whole relations. For more details, see also the previous post on essential and mandatory parts or the DL’08 paper with technical details, and the extension that specifically deals with specific and generic dependence [1], constrained to part-whole relations due to the scope of the paper.
Put differently, one needs to represent the life cycle semantics of the participating entities to be able to distinguish between “some instance—be it x1, or …, or xn—of type X must participate in a relational instance of relation of type R” and “the same instance y of type Y must participate in a relational instance of relation of type S”. More practically, and pattern-wise, given some object z that is an instance of Z (a continuant) and t0, t1, … , tn point in time, then we have for GDC
r1 : < x1, z> at t0 (at the start of active z)
r2 : < x2, z> at t1, where t1>t0, and (x1 = x2 or < x1, z> or not < x1, z> )
r3 : < x3, z> at t2, where t2 >t1 , etc… until z cease to exist as instance of Z at tn
whereas for SDC
s1 : < y1, z1> at t0 (at the start of active z)
s1 : < y1, z1> at t1, where t1>t0
s1 : < y1, z1> at t2, where t2 >t1 until z cease to exist as instance of Z at tn.
s2 : < y2, z2> at t0 (at the start of active z)
s2 : < y2, z2> at t1, where t1>t0
s2 : < y2, z2> at t2, where t2 >t1 until z cease to exist as instance of Z at tn, and where it may be that z1 = z2 or y1 = y2 or both.

Taking the GDC example from the OWL file “a certain PDF file that exists in different and in several hard drives”, then we have an example where x…xi are the distinct hard drives and z the PDF file (well, the elusive ‘contents’ of the file—clearly, there are different bits involved in the different hard drives).

The provided SDC examples, however, are somewhat more complicated: “the mass of a cloud, the smell of mozzarella, the liquidity of blood, the color of a tomato, the disposition of fish to decay, the role of being a doctor, the function of the heart in the body: to pump blood, to receive de-oxygenated and oxygenated blood”. Obviously, each cloud must have a mass, but generally not the same mass, and some mass, say, 10kg, is not necessarily related always to the same cloud as clouds can grow and decrease in volume and, thus, in amount of mass. Given the example, we only can have the specific dependence if a ‘grown’ cloud (>10kg) counts as a different cloud (which is counterintuitive). Likewise, a certain liquidity of blood can change in value (due to drinking alcoholic beverages, for instance), although blood must have some value for liquidity (which may or may not be measures and which reaches 0 if it is dried up blood in a healing wound). Vice versa, a certain liquidity value does not have to be related to the same blood for the duration of its existence. If, however, we consider instead, say, that the doctor takes a blood sample and measures the liquidity and the result of that measurement is stored in a database or written on a paper-based health record, then that measured value ‘123’ is permanent for the duration of its existence related to ‘blood sample from patient p1 taken at time hh:mm at date dd-mm-yyyy’. But the latter reading is certainly a different case from just blood & liquidity. So, overall, this seems to contradict the SDC definition—or the examples don’t quite fit the definition.

In addition, we can have variations in the life cycles of the SDC and its bearer, which I don’t think are covered. Take the following figure, where there are two principal options: we fix the lifetime of the [independent]continuant and vary the SDC’s lifetime in (A), or fix the lifetime of the SDC and vary the lifetime of the [independent]continuant in (B).

In the case of the SDC definition, one would have to focus on (B): the [independent]continuant bearer might have one or more SDCs, but given an SDC, it must always be related to the Cx, which has the same or a longer lifetime than the SDC but never a shorter lifetime. In the case of our blood sample as bearer, then we have either C2 (if the sample continues after the record of the measurement is destroyed) or C4 (if the sample is destroyed together with the recording of the taken measurement).

So, it is either me who doesn’t get it, or there is room for improvement in the SDC/GDC definitions and/or examples. Anyone has some clarifying thoughts on this?


[1] Artale, A., Guarino, N., and Keet, C.M. Formalising temporal constraints on part-whole relations. 11th International Conference on Principles of Knowledge Representation and Reasoning (KR’08). Gerhard Brewka, Jerome Lang (Eds.) AAAI Press. Sydney, Australia, September 16-19, 2008.


4 responses to “BFO’s specific and generic dependence and generalising progress in essential and mandatory parts

  1. I agree the wording is confusing. We have inheres_in, borne and depends_on when it seems the single primitive borne would suffice.

    Perhaps these proposed axioms for RO2 would help:

    non-migration principle:

    specifically_inheres_in( d, c, t) → ∀ t2[ exists_at( d, t2) → specifically_inheres_in( d, c, t2) ]

    sub-relation of the primitive inheres_in relation

    inheres_in( d, c, t) ∧ instance_of( d, specifically_dependent_continuant) ↔ specifically_inheres_in( d, c, t)

    I’m not following your cloud example – “some mass, say, 10kg, is not necessarily related always to the same cloud as clouds can grow and decrease in volume and, thus, in amount of mass”

    I believe there are two options, both consistent with clouds being SDCs. The first is that mass instances have a very short lifecycles, with mass instances being destroyed and new ones coming into being every time a cloud changes mass. The second is that the clouds mass continues to exist (and inhere_in the same cloud at t2), it just changes its type, say, from 10kg to 11kg [this is quite a small cloud…]. I don’t think BFO comes down on either side. Either way, it does not need to invoke new clouds constantly coming into being (although this may be find for clouds. I don’t know what clouds are in BFO. I prefer to think of an organism here). I think this is what you’re saying in your final paragraph – but I confess I don’t get the illustration.

    Regarding the measurement examples – I think measurements are distinct from the qualities they measure. A measurement is arguable a GDC, but it inheres in some data-bearing IC.

    See also

    A Formal Theory of Substances, Qualities,
    and Universals

    Fabian NEUHAUS
    Pierre GRENON
    Barry SMITH

  2. The very acceptance of GDC constitutes a major abdication from the straightforward trope-theoretic foundations of BFO: the fact that BFO developers have seen themselves compelled to include GDC signals, in effect, the inadequacy of trope-theory itself as a viable metaphysical position.

  3. thanks William. though I cannot (yet) comment on your statement that trope theory is inadequate. From the DL and conceptual data modeling, GDC amounts to plain, common, mandatory participation of an entity in a relation (or in DL terminology: one functionally determines the [value of an] other object); hence the SDC-only approach is at odds with that (SDC in modeling goes under the term ‘essential’ or, in the case of anti-rigid class, then ‘immutable’). It apparently being a metaphysical position, I shall look up tropes in more detail.

  4. Chris, I had emailed the link to this post to bfo-discuss, where there is further discussion going on now on tropes, qualities, values, measurements, that you may find of interest.

    As for the relation definition you provide above, I simplified that to R and S in the text. One thing that is obvious from the SDC and relational definitions you provide (where did you get them from?), is the additional time dimension to be able to define it. That is in the direction of the way we address the “specific dependence” as well; more precisely, with a temporal description logic DLRus to do it elegantly. One could also add modal operators. Neither one can be dealt with adequately with OWL though.
    (the GDC constraints can be done easily)

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s