DIOWG Subgroup on BFO 2020 - Revision history

Phismith: /* Relations */

2023-03-30T19:10:42Z

Relations

← Older revision		Revision as of 19:10, 30 March 2023
Line 3:		Line 3:
	The BFO 2020 Subgroup is tasked with reviewing new features in the upcoming version of BFO, BFO 2020 and recommending a policy on relation reuse to the DIOWG. To that end, we have been developing an understanding of the strengths and drawbacks of the temporalized relations strategy compared to the RO relations widely in use in the community.		The BFO 2020 Subgroup is tasked with reviewing new features in the upcoming version of BFO, BFO 2020 and recommending a policy on relation reuse to the DIOWG. To that end, we have been developing an understanding of the strengths and drawbacks of the temporalized relations strategy compared to the RO relations widely in use in the community.

	=Relations=		=Consensus on the Advantages and Disadvantages of Temporalized and Temporally Unspecified Relations=

	This section describes the BFO 2020 Subgroup's consensus on the drawbacks of Temporally Unspecified Relations and Temporalized Relations. In Background, we'll provide some background on the general problem both strategies address and a quick overview of each type of relations.		This section describes the BFO 2020 Subgroup's consensus on the drawbacks of Temporally Unspecified Relations and Temporalized Relations. In Background, we'll provide some background on the general problem both strategies address and a quick overview of each type of relations.

Phismith: /* Additional Complexity */

2023-02-24T12:33:40Z

Additional Complexity

← Older revision		Revision as of 12:33, 24 February 2023
Line 95:		Line 95:

	===Additional Complexity===		===Additional Complexity===

			Temporalized relations introduce complexity to ontologies and ontology workflows. First, when writing axioms and property chains, developers must choose the appropriate TR. This complexity is compounded when there are more than one temporalized relation in an axiom or property chain. Developers must then choose a TR for each relation in the axiom or property chain, and ensure that, taken together, the axiom has the intended interpretation. This can often be quite tricky. This complexity is an obstacle for ontology workflows that involve having non-ontologists input axioms and property chains, and will require a substantial amount of additional training and oversight.

Phismith: /* No General Use Transitive Parthood */

2023-02-24T12:28:54Z

No General Use Transitive Parthood

← Older revision		Revision as of 12:28, 24 February 2023
Line 89:		Line 89:

	===No General Use Transitive Parthood===		===No General Use Transitive Parthood===

			The three-place parthood relation, between a whole, a part, and a time, is transitive. The part-of-at-all-times relation is transitive, but the part-of-at-some-time relation is not. In many cases, part-of-at-all-times will be too strong, since objects gain and lose parts. There is no general-use temporalized relation that is both transitive and appropriate to describe parthood relations that hold for a limited period of time.

			It is possible to make a custom transitive temporalized relation that holds only in the time interval of interest ('part of in March 2023'), but these will be limited in their applicability and reuse.

	===Additional Complexity===		===Additional Complexity===

Phismith: /* Stipulative Semantics for Subclass Axioms */

2023-02-24T12:21:20Z

Stipulative Semantics for Subclass Axioms

← Older revision		Revision as of 12:21, 24 February 2023
Line 56:		Line 56:

	===Stipulative Semantics for Subclass Axioms===		===Stipulative Semantics for Subclass Axioms===

			RO Documentation says that class axioms using RO relations are to be interpreted as holding for "all snapshots in time". This is an attempt to capture permanent generic relatedness, but it's important to note that this stipulation is logically inert. Since the temporal aspect is not represented in the logic, it will have no effect on reasoning.

			The stipulative temporal semantics also compounds the ambiguity of temporally unspecified relations. RO includes an annotation property used to indicate that a given axiom holds "at all snapshots". It's unclear then, whether only annotated axioms should be interpreted in this way or whether any RO subclass axiom should be interpreted this way. Similarly, temporally unspecified relations are not only used within RO. Its not clear whether these relations, especially those that descend from RO, should be interpreted to hold at "all snapshots", despite developers not having indicated this, or whether we should restrict this interpretation to RO.

	==Temporalized Relations==		==Temporalized Relations==

Phismith: /* Current Defined Classes Cannot be Expressed */

2023-02-24T12:12:29Z

Current Defined Classes Cannot be Expressed

← Older revision		Revision as of 12:12, 24 February 2023
Line 62:		Line 62:

	Temporalized relations pose problems for many defined classes currently in use. Consider the equivalency axiom using the temporally unspecified member_of:		Temporalized relations pose problems for many defined classes currently in use. Consider the equivalency axiom using the temporally unspecified member_of:


	::::Lawyer EquivalentClass ('agent' and member_of some 'bar association')		::::Lawyer EquivalentClass ('agent' and member_of some 'bar association')


	Neither the all-times nor the some-times temporalized relation will be appropriate for this axiom. The at some times version is too broad:		Neither the all-times nor the some-times temporalized relation will be appropriate for this axiom. The at some times version is too broad:


	::::Lawyer EquivalentClass ('agent' and 'member-of-at-some-time' some 'bar association')		::::Lawyer EquivalentClass ('agent' and 'member-of-at-some-time' some 'bar association')


	This axiom will include retired and disbarred lawyers (and even future lawyers) in the Lawyer class. The at-all-times axiom, on the other hand, will exclude lawyers:		This axiom will include retired and disbarred lawyers (and even future lawyers) in the Lawyer class. The at-all-times axiom, on the other hand, will exclude lawyers:


	::::Lawyer EquivalentClass ('agent' and 'member-of-at-all-times' some 'bar association')		::::Lawyer EquivalentClass ('agent' and 'member-of-at-all-times' some 'bar association')


	Since no lawyer has always been a member of a bar association, all current lawyers will be excluded from the Lawyer class.		Since no lawyer has always been a member of a bar association, all current lawyers will be excluded from the Lawyer class.

Phismith: /* Current Defined Classes Cannot be Expressed */

2023-02-24T12:12:06Z

Current Defined Classes Cannot be Expressed

@@ Line 60: / Line 60: @@
 ===Current Defined Classes Cannot be Expressed===
 ===No General Use Transitive Parthood===
 ===Additional Complexity===

Phismith: /* Temporal Ambiguity */

2023-02-24T12:00:34Z

Temporal Ambiguity

← Older revision		Revision as of 12:00, 24 February 2023
Line 37:		Line 37:

	The primary drawback of temporally unspecified relations is that they are massively ambiguous with respect to when they hold. Consider the following statement:		The primary drawback of temporally unspecified relations is that they are massively ambiguous with respect to when they hold. Consider the following statement:


	:::Liver01 part_of Lynn		:::Liver01 part_of Lynn


	If this appears in an ontology or dataset, it's impossible know whether Liver01 has been a part of Lynn as long as it has existed, whether it became of Lynn at some later point (say, through a transplant), or whether it is still part of Lynn.		If this appears in an ontology or dataset, it's impossible know whether Liver01 has been a part of Lynn as long as it has existed, whether it became of Lynn at some later point (say, through a transplant), or whether it is still part of Lynn.

Phismith: /* Temporal Ambiguity */

2023-02-24T12:00:17Z

Temporal Ambiguity

← Older revision		Revision as of 12:00, 24 February 2023
Line 38:		Line 38:
	The primary drawback of temporally unspecified relations is that they are massively ambiguous with respect to when they hold. Consider the following statement:		The primary drawback of temporally unspecified relations is that they are massively ambiguous with respect to when they hold. Consider the following statement:

	::::Liver01 part_of Lynn		:::Liver01 part_of Lynn

	If this appears in an ontology or dataset, it's impossible know whether Liver01 has been a part of Lynn as long as it has existed, whether it became of Lynn at some later point (say, through a transplant), or whether it is still part of Lynn.		If this appears in an ontology or dataset, it's impossible know whether Liver01 has been a part of Lynn as long as it has existed, whether it became of Lynn at some later point (say, through a transplant), or whether it is still part of Lynn.

Phismith: /* Temporal Ambiguity */

2023-02-24T12:00:04Z

Temporal Ambiguity

← Older revision		Revision as of 12:00, 24 February 2023
Line 35:		Line 35:

	===Temporal Ambiguity===		===Temporal Ambiguity===

			The primary drawback of temporally unspecified relations is that they are massively ambiguous with respect to when they hold. Consider the following statement:

			::::Liver01 part_of Lynn

			If this appears in an ontology or dataset, it's impossible know whether Liver01 has been a part of Lynn as long as it has existed, whether it became of Lynn at some later point (say, through a transplant), or whether it is still part of Lynn.


			This ambiguity poses a number of interoperability and reasoning problems, particularly when aggregating data from a number of sources:

			*Failures of transitivity, which can introduce falsehoods during reasoning.

			*Property chains will not work as expected, and can also introduce falsehoods.



			The severity of these problems will depend on the use case. When aggregating data from multiple sources and using automated reasoning, especially data gathered at different times, these issues can be quite serious. On the other hand, there are common use cases for which these issues are trivial (e.g., where one is using ontology terms to specify a model or to tag data or when datasets are strictly segregated by temporal interval).

	===Stipulative Semantics for Subclass Axioms===		===Stipulative Semantics for Subclass Axioms===

Phismith: /* Temporalized Relations */

2023-02-23T22:53:09Z

Temporalized Relations

← Older revision		Revision as of 22:53, 23 February 2023
Line 39:		Line 39:

	==Temporalized Relations==		==Temporalized Relations==

			===Current Defined Classes Cannot be Expressed===

			===No General Use Transitive Parthood===

			===Additional Complexity===