2011 Winter Project Week:SEMXMLSchema

From NAMIC

Jump to: navigation, search

Key Investigators

  • UIowa: Hans Johnson
  • GE: Jim Miller
  • Tim Olsen

Objective

Create a formal schema for the SEM xml so that eternal tools (i.e. nipype) can validate the xml

Approach, Plan

Define what should be valid SEM XML. The current SEM parser and Slicer CommandLineModule may currently only support a subset of the ultimate specification.

  • Use XML tools to grok a schema from current SEM XML files.
  • Use this schema as a guide to identify what the SEM schema should be
  • Check schema against Slicer CommandLineModule gui/logic. Attributes like reference, multiple, type should be generalized where it makes sense.
  • Update the SEM XML parser
  • Update the CommandLineModule in Slicer

Progress

An XML schema has already been written part of CTK (unofficial yet): slicerModuleDescription.xsd

  • Issues with initial schema
    • Image, Geometry, Transform do not have to be index parameters
    • ParamType, IndexParamType, TypedIndexParamType probably need clearer names
    • Index parameters do not have to be files and hence do not need always have fileExtensions attribute
  • Perl script to validate XML using LibXML
  • Issues against current CLI's XML
    • xxx


Current Parser

hiddenreferencefileExtensiontypecoordinateSystemmultipleaggregate
boolean.....x.
integer.....x.
float.....x.
double.....x.
string.....x.
imagexxxx.x.
geometry..xx.xx
transform.xxx.x.
tablexxxx.x.
measurementxxxx.x.
file..x..x.
directory.....x.
point....xx.
region....xx.

All other parameters (integer-vector, float-vector, double-vector, string-vector, integer-enumeration, float-enumeration, double-enumeration, string-enumeration) have no attributes currently

Current XML against initial schema

xxx

xxx


Personal tools