Difference between revisions of "2011 Winter Project Week:SEMXMLSchema"
From NAMIC Wiki
| Line 41: | Line 41: | ||
** Image, Geometry, Transform do not have to be '''index''' parameters | ** Image, Geometry, Transform do not have to be '''index''' parameters | ||
** ParamType, IndexParamType, TypedIndexParamType probably need clearer names | ** ParamType, IndexParamType, TypedIndexParamType probably need clearer names | ||
| − | ** Index parameters do not have to be files | + | ** Index parameters do not have to be files and hence do not need always have fileExtensions attribute |
</div> | </div> | ||
</div> | </div> | ||
Revision as of 20:54, 11 January 2011
Home < 2011 Winter Project Week:SEMXMLSchema
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
