So far used EDAM, but we could also change that and mime type if nothing was found, e.g. application/geo+json

We could define some of the commonly used formats in an Ontology extension we provide like in one of the CWL examples using
the $schemas block
without schemas: https://github.com/common-workflow-language/cwl-v1.2/blob/main/tests/formattest.cwl
with schemas: https://github.com/common-workflow-language/cwl-v1.2/blob/main/tests/formattest2.cwl
with extended schema: https://github.com/common-workflow-language/cwl-v1.2/blob/main/tests/formattest3.cwl

File format ontologies may be provided in the "$schemas" metadata at the root of the document. If no ontologies are specified in $schemas, the runtime may perform exact file format matches.

https://www.commonwl.org/v1.2/CommandLineTool.html#File

Anyhow: here is an example with mime:
https://github.com/common-workflow-language/cwltool/blob/60dfe96952119f472a57524c19ed214e831b21a4/cwltool/schemas/v1.1/cwl-runner.cwl#L50

We have to run some tests and decide which ocurrences we want to consider as valid (regarding subclassOf relationship) https://github.com/fairagro/commonwl/blob/main/crates/engine/schema/format_validation.rs#L251-L279

Do we want to display file format in Studio somewhere?

maybe in brackets after the slot name or on hover

Are users allowed to change the format, e.g. in Studio through pencil? We could combine this a general step/node description that can be given by user

Maybe if we add it to the nodes themselves we can have some edition box or dropdown. See node "Ellipse Mask" -> "Mask Type"
https://docs.blender.org/manual/en/latest/_images/interface_controls_nodes_introduction_example.jpg

Do we also want to add a label to inputs/outputs, e.g. label: Aligned sequences in BAM format

Not related to that feature. label is not only tight to the format

infer file types/formats #265

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions