<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Hi Curtis...<div><br><div><div>On 16 Sep 2009, at 23:09, Curtis Rueden wrote:</div><br><blockquote type="cite"><div class="gmail_quote"><div>We definitely want to encourage this sort of thing. My group (LOCI) is in the middle of a similar effort, mapping all our acquisition metadata to OME-XML, and working to produce valid OME-TIFF files in every case.<br> <br>So yes, the documentation is supposed to help. I agree that the documentation in the schema itself could use a lot of improvement. My group has a graduate student in library sciences, Caitlin Sticco, who is currently analyzing the schema and compiling a list of suggestions and improvements; hopefully we can update the documentation as well as we work to improve the schema.<br> <br>Caitlin and I are also discussing how to make better diagrams—one idea we had is to generate them in Graphviz format from the XSD file. Any other suggestions for ways to make useful pictures would be welcome.<br></div></div></blockquote><div><br></div><div>I've been using a combination of xsl, javascript (jQuery) etc to turn the ome.xsd into a browsable hierarchy. </div><div><br></div><div><a href="http://cvs.openmicroscopy.org.uk/snapshots/omero/editor/omeXsd/ome-r373.xsd">http://cvs.openmicroscopy.org.uk/snapshots/omero/editor/omeXsd/ome-r373.xsd</a></div><div><br></div><div>Handy because it's instantly updated if you're editing the xsd, and hierarchy is easy to understand.</div><div><br></div><div>Use links on the top to expand/collapse all or show/hide docs. </div><div><br></div><div>Obviously this code could be extended to do a bunch of other stuff. E.g. JM suggested allowing the root element to be chosen, e.g. "Image" or "Instrument".</div><div><br></div><div><br></div><div> Will.</div><div><br></div><div><br></div><br><blockquote type="cite"><div class="gmail_quote"><div><br> Your idea of a list of common use cases, and how to express them in OME-XML, is a great one. We should add that to the OME-XML web site. For that, we need A) a list of which common use cases to include; and B) someone with enough time to work on writing it up. But at the least we can file a ticket about it on the OME-XML Trac at <a href="http://www.ome-xml.org/">http://www.ome-xml.org/</a>. And actually, you are welcome to file such tickets too, using the ome/ome login. :-) To be clear, we want to encourage external suggestions through that mechanism.<br></div></div></blockquote></div><br><div> <span class="Apple-style-span" style="font-size: 12px; "><div>William Moore</div><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Division of Gene Regulation and Expression</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">College of Life Sciences</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">University of Dundee</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Scotland</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">DD1 5PH</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Tel 01382 386364</div></div></span> </div><br></div></body></html>