volcanic feature

[cmungall]

lacks an is_a link to vocanic feature. deliberate? if so, a bit odd.

./ ENVO:00002297 ! environmental feature
..is_a ENVO:00000000 ! geographic feature
…is_a ENVO:00000012 ! hydrographic feature
….is_a ENVO:00000049 ! volcanic hydrographic feature *
…is_a ENVO:00000191 ! physiographic feature
….is_a ENVO:00000094 ! volcanic feature *

For the purposes of symmetry it seems there should be a volcanic physiographic feature, with volcanic feature subsuming volcanic {hydro,physio} feature. The multiple parentage isn’t good but eventually we’ll infer it based on has_quality links.

Currently hydrothermal vent is the only is_a child of both VF and VHF.

volcano is_a VF, but VHFs have nothing to do with volcanoes, according to ENVO

The same, with definitions shown:

./ ENVO:00002297 ! environmental feature [DEF: “A feature that is.”]
..is_a ENVO:00000000 ! geographic feature
…is_a ENVO:00000012 ! hydrographic feature [DEF: “A geographical feature associated with water.”]
….is_a ENVO:00000049 ! volcanic hydrographic feature *
…is_a ENVO:00000191 ! physiographic feature
….is_a ENVO:00000094 ! volcanic feature * [DEF: “A feature associated with a volcano, an opening, or rupture, in the Earth’s surface or crust, which allows hot, molten rock, ash and gases to escape from deep below the surface.”]

(can we do something about the definition for the root!)

some definitions for physiographic etc would be good. perhaps we could make these qualities.

note that volcano is an is_a child of volcanic feature, yet VF is defined in terms of V. Not good!

Original comment by: cmungall

[pbuttigieg]

I think 'volcanic' should be a quality and volcanic feature broken up (e.g. hydrothermal vent will go to spring and `volcanic fissure' to 'depression').

Do you think 'volcanic' will work in PATO? Roughly "a quality inhering in a bearer by virtue of the bearer being subject to (at some point) or derived from to volcanic activity". We can use ENVO process to define volcanic processes.

[cmungall]

Really the only function PATO would be serving here would be
terminologic - the ENVO material entity and process do all the heavy
lifting

On 1 Sep 2015, at 8:55, Pier Luigi Buttigieg wrote:

I think 'volcanic' should be a quality and volcanic feature broken up
(e.g. hydrothermal vent will go to spring and `volcanic fissure'
to 'depression').

Do you think 'volcanic' will work in PATO? Roughly "a quality inhering
in a bearer by virtue of the bearer being subject to (at some point)
or derived from to volcanic activity". We can use ENVO process to
define volcanic processes.

---

Reply to this email directly or view it on GitHub:
#193 (comment)

[pbuttigieg]

If we don't need the quality we can omit it, but it may come in handy for
other projects that would import PATO. A link to the ENVO process in the
PATO definition would serve to keep things in order. Thoughts?
On 5 Sep 2015 05:20, "Chris Mungall" notifications@github.com wrote:

Really the only function PATO would be serving here would be
terminologic - the ENVO material entity and process do all the heavy
lifting

On 1 Sep 2015, at 8:55, Pier Luigi Buttigieg wrote:

I think 'volcanic' should be a quality and volcanic feature broken up
(e.g. hydrothermal vent will go to spring and `volcanic fissure'
to 'depression').

Do you think 'volcanic' will work in PATO? Roughly "a quality inhering
in a bearer by virtue of the bearer being subject to (at some point)
or derived from to volcanic activity". We can use ENVO process to
define volcanic processes.

---

Reply to this email directly or view it on GitHub:

#193 (comment)

—
Reply to this email directly or view it on GitHub
#193 (comment)
.

[pbuttigieg]

Started defining and distributing using volcanic process by 3e20084.

Also created an in_subset:'environmental_hazards' AP. This will come in handy for SDGIO.