There is an XSD, but it's extremely open ended because the element and
attribute names that an XMI file uses are determined by the user's
model (i.e., the type system) and not by the XMI specification.
Here's the link http://www.omg.org/spec/XMI/20071213/XMI.xsd
Thanks, Adam. I see what you mean by open-ended.
Looking at the XMI produced by UIMA for my type system, I see that
elements in the xmi namespace are a minority. There are also elements in
name spaces "cas", "tcas", and one derived from my type system.
So to produce an XSD that described everything in the file, I would need
to add definitions for all those. The schema of the cas and tcas are
fixed, however the schemas derived from the type systems deployed would
have to be dynamically generated. I suppose XmiCasSerializer should have
all the information it needs to do that...
Greg Holmberg
