MSML Roadmap

Semantic description

• Decription of MSML format in OWL
• Description of exporter capability in OWL
• Automatic conversion of operator description to OWL/RDF
• Revision of current alphabet, e.g. logical mesh typs

Exporters

• Abaqus exporter based on ontologies: Enhance supported materials/load cases
• Exporter should declare supported functionality. If suitable for specific MSML description, best match should be found. --> Base declaration on semantic description
• FEBio, CodeAster
• Revision of current exporters: Multiple objects, contact simulation

Web services

• Restflow (beta version ready)
• Javascript wizard for MSML model generation
• Expose whole MSML as REST service
• Expose MSML operators as REST service
• XNAT? Data security?

Extended functionality

• Varadic arguments -> Better Python API instead of more XML-based functionality Shift to MSML 2.0?
• Automatic conversion operators -> Python-based VTK converters, import converters from alphabet, different conversions for different logical data types?
• Python API
• Optimize/Sweep API
• Manage debug output on Python side, messaging, error reporting, C++ outputs remain, concept for C++ error reporting

Software infrastucture

• Full VTK 6.1 & Ubuntu 14.04 compatibility
• Server für web services
• Documentation -> define what has do be documented

Issues

• MSML file validation, e.g. Ambiguous constraints -> handling?

MSML 2.0

• Exporters should be considered normal operators
• Exporters can be triggered more than once
• Multiple exporters possible