Open GoogleCodeExporter opened 9 years ago
See revision r211
Original comment by cmung...@gmail.com
on 20 Feb 2015 at 1:02
@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]"...
@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'
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
Original issue reported on code.google.com by
cmung...@gmail.com
on 20 Feb 2015 at 1:01