OML => OWL,Tables conversion needs to produce the graph of ontologies

[NicolasRouquette]

The ontology.analysis used to rely on the deprecated OMF Metadata to get the directed graph of ontologies and information about the provenance of each ontology as originating from a bundle or as a result of an export from UML/SysML.

When converting from OML, it would be useful to provide this graph topology and provenance information as follows:

• Graph Nodes
• Graph Edges

A Graph Node is a tuple:

• Ontology IRI
• Ontology filename (relative to the directory where the oml.catalog.xml file is located)
• Ontology provenance (builtin, bundle, extension, other) where:
  • builtin means the ontology is part of the built-in OWL2-DL vocabulary of datatypes and annotations; this vocabulary should not be explicitly loaded using the OWLAPI (see https://github.com/JPL-IMCE/gov.nasa.jpl.omf.scala.binding.owlapi/issues/11)
  • bundle means the ontology is either a bundle itself or part of its import closure
  • extension means the ontology directly or indirectly imports a bundle ontology
  • other means the ontology is none of the above (e.g., it may be an embedding ontology).

Note that in OWL, an Ontology represents an OML module of some kind (TerminologyGraph, Bundle, DescriptionBox) which is indicated via an ontology annotation.

A Graph Edge is a tuple:

• Importing IRI
• Imported IRI

This graph topology & provenance information will be provided as a separate Json file.

[StevenJenkinsJPL]

One nit: ontology.workflow does not rely on OMF metadata.

[NicolasRouquette]

Thanks, I edited the description.