title: New embedded schema format for Parasolid v30?
body: <p>I have two binary Parasolid files from v30 (internal modeller string is 3000226, schema string is SCH_3000226_30000_13006).  In it, the embedded schema information for older types is as defined in the latest copy I have of the Parasolid XT Format Reference.  However, for entity type 204 (introduced after the 28101 schema) the embedded schema format is completely different.  Luckily, it has a lot of strings in it, so it is pretty easy to reverse engineer the basic form of it:</p>
  
  <pre><code>unsigned byte: number of fields
  short string: nodename
  short string: description
  
  then for each field
    short string: fieldname
    five bytes: maybe somehow correspond to &lt;transmit 1/0&gt; &lt;node class&gt; &lt;n_elements&gt; ?
    byte: (field) type
  
  byte: possibly &lt;variable 1/0&gt; ?
  </code></pre>
  
  <p>Then the entity proper begins as expected.</p>
  
  <p>The problem is that this seems like a workable parsing of the binary version, but without knowing what the five mystery bytes actually correspond to, I don't know how to implement support for this in a Parasolid text file.  It might be two short ints and an unsigned char, might be one 4-byte int and an unsigned char.  Heck, since in both examples I have the first three mystery bytes are zero, there might even be a string of some sort in there, which just happens to be 0 length in this case, in which case, of course, it's not really five bytes always but just happens to be five bytes in my two examples.</p>
  
  <p>Does anyone have an idea what is going on in the mystery bytes?</p>
  
  <p>Also, I'm assuming this scheme will be active for entity types 204 and up.  What I don't know about is entity type 203.  I don't believe I've ever seen a Parasolid file with that type in it.</p>
  
  <p>(Also, does anyone have any insight as to why they would make a non-backward compatible change to a feature intended solely to support backwards compatibility?)</p>