<h1>Proposed Changes and Additions</h1> <ul> <li><b>Higher Level Graph Library</b> (Foundation for dependancy graphs, etc)</li> </ul> <ul> <li>Use connection protocol to form N object graphs</li> </ul> <ul> <li>Include facility for optional state change notification</li> </ul> <ul> <li>Make it possible to use any conforming math library (Imath, boost, etc)</li> </ul> <ul> <li>Handle fixed size object attributes as well as variable sized array attributes</li> </ul> <ul> <li><span class="caps">GTO</span> protocol &#8220;schemes&#8221; for creating higher level tools</li> </ul> <ul> <li>Attribute/Property value constraints and other meta-data</li> </ul> <ul> <li>Programmatic file structure verification</li> </ul> <ul> <li>Some method of indicating &#8220;index&#8221; properties versus plain-old-data and what the indices refer to</li> </ul> <ul> <li>Active versus frozen graph handling</li> </ul> <ul> <li><b>Optional compacted transposable component layout</b>. Some way of having an array of identical, transposable, components that only differ in size without having a separate component header for each.</li> </ul> <ul> <li><b>Separate string tables for objects</b> &#8211; the string table merging and index rewriting you have to do when using string properties and multiple objects isn&#8217;t affecting us now, but could affect us in the future. It&#8217;d be nice if the global table was just for the strings in the header information, and there was a separate per object string table that the property indices look up into.</li> </ul> <ul> <li><b> <span class="caps">BIG</span> <span class="caps">GTO</span></b> extend the format to including 64/128 bit indices and data types</li> </ul> <ul> <li><b> Movie File Format</b> look at the viability of using <span class="caps">GTO</span> as a new movie file storage format. The existing <span class="caps">GTV</span> experiment shows it can work. Use <span class="caps">EXR</span>/Imath as a basis for the implementation and include some of the more common production codecs like photo-jpeg and H.264. This would require some changes like the compacted component idea above and possible compacted object storage (lots of similar objects get a single header)</li> </ul> 2008-07-10T11:37:39-07:00 35073 proposedchanges 32809 2008-07-10T11:42:54-07:00 16587