definition requests: lake sediment and children

[GoogleCodeExporter]

  is_a ENVO:00002007 ! sediment
   is_a ENVO:00000546 ! lake sediment *** 
    is_a ENVO:00002147 ! coal mine lake sediment
    is_a ENVO:00002209 ! saline lake sediment


Lake sediment doesn't have a definition

is it as trivial as 'sediment that is part of a lake'?

saline lake sediment is presumable lake sediment in a saline lake

what about coal mine lake sediment

Original issue reported on code.google.com by cmung...@gmail.com on 20 Feb 2015 at 1:01

[GoogleCodeExporter]

See revision r211

Original comment by cmung...@gmail.com on 20 Feb 2015 at 1:02

• Added labels: ****
• Removed labels: ****

[pbuttigieg]

@cmungall
I think these classes are intended to be quite trivial.
Should we create "coal mine lake" = 'lake that is located_in coal mine' in order to create a logical def for coal mine lake sediment?

I added some simple textual defs to these classes. We could perhaps add assertions that capture "covers the lake [bottom, bed]"...

[pbuttigieg]

@cmungall
This may be a good reason to add sediment generation processes (cosmogenous, terrigenous, biogenous, etc) to the envo process ontology. That way we can make a more useful logical definitions that is along the lines of:

sediment and 'part of' some lake (environment) and 'output of' some 'biogenous sedimentation process'

[cmungall]

Seems reasonable. We'd want to get the process hierarchy in shape a bit more before bringing it into the core. But the axioms connecting things could live purely in the process module for now