has_material_basis_in

[GoogleCodeExporter]

We often want to establish a relation between a disposition and the material 
entity that confers that disposition.  This manifests itself in OGMS as a 
relation between a disease and the disorder(s) that confer the disease.

After some email discussions with Barry Smith, Lindsay Cowell, Bjoern Peters, 
and Alan Ruttenberg, I believe something like this might do the trick:

has_material_basis_in 
domain: bfo:disposition
range: bfo:material entity
definition (*): d has_material_basis_in m iff
(1) d is_a bfo:disposition 
(2) m is_a bfo:material entity
(3) i is_a bfo:independent continuant and i has_disposition d because i 
has_part m

(* Note: d, m, and i are instances per RO policy)

A synonym could be 'conferred_by'.  Another proposal, 'has_physical_basis_in' I 
don't like as much because the 'physical' doesn't seem to make you think of the 
proper bfo type in the range (i.e., material entities).

Original issue reported on code.google.com by albertgo...@gmail.com on 18 Nov 2010 at 9:47

[GoogleCodeExporter]

Original comment by alanruttenberg@gmail.com on 13 Jan 2012 at 7:15

• Added labels: Type-BFO2-design
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by alanruttenberg@gmail.com on 1 May 2012 at 8:13

• Added labels: Type-BFO2-Reference
• Removed labels: Type-BFO2-design

[GoogleCodeExporter]

Original comment by alanruttenberg@gmail.com on 8 May 2012 at 4:11

[GoogleCodeExporter]

Original comment by alanruttenberg@gmail.com on 8 May 2012 at 4:46

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by alanruttenberg@gmail.com on 8 May 2012 at 4:48

• Changed state: Review-old-issue