anyone have a good description of xsv's output format?

-- 
Bryan Rasmussen

Basically I figure that the fsm element has to mean finite state machine, if so
is there any information as to what states are what? The fsm exists as a child
of invalid, what does this fragment mean from the fsm onward, I think I
understand the text node directly descendant of invalid well enough:

<invalid char="11" code="cvc-complex-type.1.2.4" line="198"
resource="file:///C:/projects/installs/XSV/xsd/common/UBL-UnspecializedDatatypes-1.0.xsd">
  element
{urn:oasis:names:specification:ubl:schema:xsd:CoreComponentParameters-1.0}:RepresentationTerm
not allowed here (3) in element
{urn:oasis:names:specification:ubl:schema:xsd:CoreComponentParameters-1.0}:Component,
expecting
[{urn:oasis:names:specification:ubl:schema:xsd:CoreComponentParameters-1.0}:Definition,{urn:oasis:names:specification:ubl:schema:xsd:CoreComponentParameters-1.0}:Version]:

   <fsm>
      <node id="1">
        <edge dest="2"
label="{urn:oasis:names:specification:ubl:schema:xsd:CoreComponentParameters-1.0}:ComponentType"
/> 
       </node>
       <node id="2">
       <edge dest="3"
label="{urn:oasis:names:specification:ubl:schema:xsd:CoreComponentParameters-1.0}:DictionaryEntryName"
/> 
       </node>
......
        <node final="true" id="4">
         <edge dest="7"
label="{urn:oasis:names:specification:ubl:schema:xsd:CoreComponentParameters-1.0}:AlternativeBusinessTerms"
/>