DO NOT MERGE YET: first pass at instance graph for goals and targets

[cmungall]

Experimental approach to automatically extract an OWL representation of the goals and targets.

Opened merged.owl in Protege

The model is

goal
  --[has-part]-->
     target
       --[has-participant]--> ENVO-continuant
       --[has-part]--> ENVO-process
       --[MENTIONS]--> Anything else

As we keep adding to SDGIO, we will keep rerunning the pipeline, and
in theory the results should improve. We will also add heuristics to
refine the semantically useless MENTIONS assertions (there are useful
to indicate that we may be missing something in the ontology).

exclusions can be added directly to the prolog

TODO

ENVO has some very liberal synonyms

This can lead to:

significantly reduce illicit financial and arms flows, strengthen the recovery and return of stolen assets and combat all forms of organized crime ==> ENVO:01000696 "mass wasting flow"

due to synonyms on 'flow'

[pbuttigieg]

Looks very promising!

If I recall correctly, (@phismith please correct me if wrong) we've previously treated any given 'target' as a system which, when certain parts of it are measured, has those indicator values defined in the target text. That is, the SDG process wishes to take an existing system and transform it into a target system, which would generate specified indicator values when parts of the system are measured.

We would treat the following target...

6.4 By 2030, significantly reduce illicit financial and arms flows, 
strengthen the recovery and return of stolen assets and combat
all forms of organized crime

...as a system in which

• the rates of illicit arms flow processes and illicit financial flow processes are 'significantly' reduced relative to some baseline (@pdez90 - where would be find these baselines to compare against?)
• the rates of recovery of stolen asset and return of stolen asset processes are increased
• and processes combating organized crime are, minimally, present.

goal
  --[has-part]-->
     target
       --[has-participant]--> ENVO-continuant
       --[has-part]--> ENVO-process
       --[MENTIONS]--> Anything else

• Given the above discussion, a goal doesn't really have a target as a 'part', the target is specified by the goal (which is an objective specification). Could we create/reuse such a relation?
• Also, targets wouldn't be processes themselves, but there would be processes which would help reach the target system. Thus, the 'has-participant' link would need revision. Perhaps something towards:

goal
  --[specifies]-->
     target
       --[has-partt]--> [ENVO,SDGIO,...]-continuant
       --[achieved-by]--> [ENVO,SDGIO]-process
       --[MENTIONS]--> Anything else

The "achieved by" could be something like "output of" or "formed as a result of" some process.
Classes would probably come primarily from SDGIO or ENVO, but other ontologies (e.g. PCO) could contribute classes too.

[phismith]

This looks good to me

On Mar 17, 2016, at 10:25, Pier Luigi Buttigieg [email protected] wrote:

Looks very promising!

If I recall correctly, (@phismith please correct me if wrong) we've previously treated any given 'target' as a system which, when certain parts of it are measured, has those indicator values defined in the target text. That is, the SDG process wishes to take an existing system and transform it into a target system, which would generate specified indicator values when parts of the system are measured.

We would treat the following target...

6.4 By 2030, significantly reduce illicit financial and arms flows,
strengthen the recovery and return of stolen assets and combat
all forms of organized crime
...as a system in which

the rates of illicit arms flow processes and illicit financial flow processes are 'significantly' reduced relative to some baseline (@pdez90 - where would be find these baselines to compare against?)
the rates of recovery of stolen asset and return of stolen asset processes are increased
and processes combating organized crime are, minimally, present.
goal
--[has-part]-->
target
--[has-participant]--> ENVO-continuant
--[has-part]--> ENVO-process
--[MENTIONS]--> Anything else
Given the above discussion, a goal doesn't really have a target as a 'part', the target is specified by the goal (which is an objective specification). Could we create/reuse such a relation?
Also, targets wouldn't be processes themselves, but there would be processes which would help reach the target system. Thus, the 'has-participant' link would need revision. Perhaps something towards:
goal
--[specifies]-->
target
--[has-partt]--> [ENVO,SDGIO,...]-continuant
--[achieved-by]--> [ENVO,SDGIO]-process
--[MENTIONS]--> Anything else
The "achieved by" could be something like "output of" or "formed as a result of" some process.
Classes would probably come primarily from SDGIO or ENVO, but other ontologies (e.g. PCO) could contribute classes too.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

[cmungall]

Note to self: the hacky inst2ttl script here should be changed to parse the nice yaml provided here #105 rather than parsing the markdown.