<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Ghislain,<br><br><blockquote type="cite">Regarding the ROI model, another point that would be nice to take into consideration for high content imaging is compactness. It would be great if the ROI schema could support chain code type registration of the ROI. Also, it would be great if some sort of compression could be added to further reduce the space required.<br></blockquote><br>We can certainly include different methods for compression:<br>I've not used chain code compression though it seems quite nice, I'm pretty certain we could move between chain code compression and polygon representations of the same element. I think maybe we should spend some time looking at possible methods for compressing mask elements.<br><br><blockquote type="cite"><br></blockquote><blockquote type="cite">Though this does not solve the "harmonization" issue, I wanted to put this suggestion out there so that it might be included in the standardized ROI schema.<br></blockquote>Your comments are very helpful, I wonder if you've any other ideas for the model?<br><br>Regards<br><br>D.<br><br><br>On Jun 10, 2010, at 5:07 PM, Ghislain Bonamy wrote:<br><br><blockquote type="cite">Hi,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Regarding the ROI model, another point that would be nice to take into consideration for high content imaging is compactness. It would be great if the ROI schema could support chain code type registration of the ROI. Also, it would be great if some sort of compression could be added to further reduce the space required.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Though this does not solve the "harmonization" issue, I wanted to put this suggestion out there so that it might be included in the standardized ROI schema.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Best,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Ghislain Bonamy, PhD<br></blockquote><blockquote type="cite">__________________________________________<br></blockquote><blockquote type="cite">Research Investigator<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Genomic Institute of the<br></blockquote><blockquote type="cite">Novartis Research<br></blockquote><blockquote type="cite">Foundation<br></blockquote><blockquote type="cite">Department of Informatics, room C117<br></blockquote><blockquote type="cite">10675 John Jay Hopkins Drive<br></blockquote><blockquote type="cite">San Diego CA 92121<br></blockquote><blockquote type="cite">USA<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">+1 (858) 812-1534 (Work & Fax)<br></blockquote><blockquote type="cite">+1 (757) 941-4194 (Home)<br></blockquote><blockquote type="cite">+1 (858) 354-7388 (Cell)<br></blockquote><blockquote type="cite"><a href="http://www.gnf.org/">www.gnf.org</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-----Original Message-----<br></blockquote><blockquote type="cite">From: <a href="mailto:ome-devel-bounces@lists.openmicroscopy.org.uk">ome-devel-bounces@lists.openmicroscopy.org.uk</a> [<a href="mailto:ome-devel-bounces@lists.openmicroscopy.org.uk">mailto:ome-devel-bounces@lists.openmicroscopy.org.uk</a>] On Behalf Of Jason Swedlow<br></blockquote><blockquote type="cite">Sent: Tuesday, June 08, 2010 7:37 AM<br></blockquote><blockquote type="cite">To: OME Development<br></blockquote><blockquote type="cite">Subject: Re: [ome-devel] ROI Meeting<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Hi all-<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">My own view is that harmonization of the ROI data model across these projects is critical, and a major priority for all. We should do whatever we need to to make this happen. The downstream pay-off for all our projects is very high. The penalties for not sorting this will be very high.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Is there a way to standardise the specification, like we already do with OME-XML, and license the implementations according to our respective preferences? If that is too hard, can we agree on some code which is shared, and that is licensed so that's compatible with all? There will invariably lots of implementation-specific stuff.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Cheers,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Jason<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Wellcome Trust Centre for Gene Regulation & Expression | University of Dundee | <a href="http://gre.lifesci.dundee.ac.uk/staff/jason_swedlow.html">http://gre.lifesci.dundee.ac.uk/staff/jason_swedlow.html</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-----Original Message-----<br></blockquote><blockquote type="cite">From: dzmacdonald <<a href="mailto:donald@lifesci.dundee.ac.uk">donald@lifesci.dundee.ac.uk</a>><br></blockquote><blockquote type="cite">Sender: <a href="mailto:ome-devel-bounces@lists.openmicroscopy.org.uk">ome-devel-bounces@lists.openmicroscopy.org.uk</a><br></blockquote><blockquote type="cite">Date: Tue, 8 Jun 2010 10:30:27<br></blockquote><blockquote type="cite">To: OME-devel mailing list<<a href="mailto:ome-devel@lists.openmicroscopy.org.uk">ome-devel@lists.openmicroscopy.org.uk</a>><br></blockquote><blockquote type="cite">Subject: [ome-devel] ROI Meeting<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Hi<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The discussion on the ROI Meeting:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The ROI model is changing too often. It will have to change to cover<br></blockquote><blockquote type="cite">3D, NDIM and maybe we should try to add these sooner rather than<br></blockquote><blockquote type="cite">later. Curtis mentioned that Bioformats will be working with NDIM data<br></blockquote><blockquote type="cite">soon, maybe we should look at their solution?<br></blockquote><blockquote type="cite">Curtis and the imageJ group are looking to develop ROI tools, possibly<br></blockquote><blockquote type="cite">using Hotdraw/JHotdraw maybe there could be a collaboration, sharing<br></blockquote><blockquote type="cite">of code between groups. The only problem with this might be licensing.<br></blockquote><blockquote type="cite">When do we wish to do this?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Regards<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">D.<br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">ome-devel mailing list<br></blockquote><blockquote type="cite"><a href="mailto:ome-devel@lists.openmicroscopy.org.uk">ome-devel@lists.openmicroscopy.org.uk</a><br></blockquote><blockquote type="cite"><a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel</a><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">ome-devel mailing list<br></blockquote><blockquote type="cite"><a href="mailto:ome-devel@lists.openmicroscopy.org.uk">ome-devel@lists.openmicroscopy.org.uk</a><br></blockquote><blockquote type="cite"><a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel</a><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">ome-devel mailing list<br></blockquote><blockquote type="cite"><a href="mailto:ome-devel@lists.openmicroscopy.org.uk">ome-devel@lists.openmicroscopy.org.uk</a><br></blockquote><blockquote type="cite"><a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel</a><br></blockquote><div><font class="Apple-style-span" color="#144FAE"><br></font></div></body></html>