Skip to content

A single and easy processable representation of the OntoFlow output #18

@francescalb

Description

@francescalb

Simplify ontoconv by having a simple data structure returned by parse_ontoflow() that can be reused in all the functions for creating pipelines and declarative workchains. This means that it must contain all the needed information.

The suggestion is to represent this as a list of pre-defined tuples, like (iri, iotype, resourcetype, strategylist). Such a list is easy to iterate over and filter. The suggested fields are

  • iri: IRI of the input or output
  • iotype: Type of the resource. Either "input" or "output".
  • resourcetype: Either "datasource" or an IRI. Like the current "resourcetype" dict item.
  • strategylist: List of OTEAPI strategies configurations for the data resource.

The name of the simulation tool might also be useful for error reporting.

Originally posted by @jesper-friis in #15 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions