• DataFormatsPlan

Data formats for capturing MIFlowCyt encoded data and metadata

Graphical representation:

Rationale:

Since there is no known best approach for flow data formats, it's been suggested that we continue our research in all directions.

To minimize the effort, let’s split 4 undecided components and use different approaches for each one of them. Later on we can evaluate the results and possibly change the initially selected formats.

• Experiment overview: FuGE XSD based

  • Since core FuGE already has all (or almost all) data elements required in MIFlowCyt experiment overview, FuGE-ML looks like a great candidate for this component

  Experiment design: FuGEFlow XSD based

  • Creating generic format for experimental design is a great undertaking. It’s going to be a lot of work regardless of used approach. FuGEFlow extension is a good choice because core FuGE already has well-defined basic classes and we should reuse them rather than reinvent.

  Instrument settings: custom RDFS based

  • Instrument settings are expected to heavily use OBI ontology. To take advantage of this fact, it’s proposed to use RDF schema to describe this component

  Analysis results: custom RDFS based

  • In this case there is no strong reason to choose one format over another; RDF could be a good choice.

Comments:

Please let us know what you think about the approach overall and each proposed component in particular. We look forward to your feedback

Olga, Ryan, Josef