<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Hi Curtis,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">For the Grid/collection stitching plugin I used the parameters<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Type: Positions from file<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Order: Defined by image metadata<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">In the next pop up screen I have all options unchecked. Here is the remainder:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Fusion method: Linear blending<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Regression Threshold: 0.30<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Max/avg displacement threshold: 2.50<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Absolute displacement threshold: 3.50<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Computation Parameters: Save memory (but be slower)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Image output: Fuse and display<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">For the Fiji + Java, I have ImageJ 2.0.0-rc-54/1.51g and for Java I have 1.8.0_66<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Michael Pinkert<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black"><ctrueden.wisc@gmail.com> on behalf of Curtis Rueden <ctrueden@wisc.edu><br>
<b>Date: </b>Thursday, November 10, 2016 at 8:34 AM<br>
<b>To: </b>OME User Support List <ome-users@lists.openmicroscopy.org.uk><br>
<b>Cc: </b>Michael Pinkert <mpinkert@wisc.edu><br>
<b>Subject: </b>Re: [ome-users] Bug report for version 2012-06 OME-XML in Fiji, seen in grid/collection stitching<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Hi Roger, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">> I've done some further testing with the submitted files.<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thank you very much for the further testing.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">> Workarounds for broken data should never compromise the handling of<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> valid data, and at some point there is a limit for what it is<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> reasonable or safe for us to correct.<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I absolutely agree 100%. However, two points in this case:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">1) I believe these files were written by Bio-Formats itself. I would argue that under no circumstances should Bio-Formats write OME-TIFFs which are later considered to be invalid or corrupt. Even dev builds of Bio-Formats should use a stable
schema version by default. If it is needed for testing to write files with "in-progress" schemas, that option should be specified via a manually triggered API call, rather than happen by default.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">2) For files with an "in-progress" schema version, making a best effort to parse using nearby stable schema versions does not introduce any possibility of compromise to valid data handling. So I am glad to hear that Bio-Formats does this.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">> I'd be interested to know why it wasn't working for you with your<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> Fiji/ImageJ installation.<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Michael: can you describe the exact steps you took? Grid/Collection Stitching? Which parameters? Which version of Fiji + Java are you using? Click the status bar to see.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Curtis<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt">--</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt">Curtis Rueden</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt">LOCI software architect - <a href="http://loci.wisc.edu/software" target="_blank">
http://loci.wisc.edu/software</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">ImageJ2 lead, Fiji maintainer - <span style="font-size:9.5pt"><a href="http://imagej.net/User:Rueden" target="_blank">http://imagej.net/User:Rueden</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Did you know ImageJ has a forum? <a href="http://forum.imagej.net/" target="_blank">
http://forum.imagej.net/</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Thu, Nov 10, 2016 at 7:32 AM, Roger Leigh <<a href="mailto:rleigh@dundee.ac.uk" target="_blank">rleigh@dundee.ac.uk</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">Dear all,<br>
<br>
I've done some further testing with the submitted files. They are<br>
technically invalid (non-validating), but I can in practice I can:<br>
<br>
- view them with showinf,<br>
- convert them to 2016-06 OME-TIFF with bfconvert (fixing the validation<br>
errors)<br>
- import into current Fiji (with the java8 update site providing<br>
bioformats 5.2.4)<br>
<br>
None of these showed any errors for me.<br>
<br>
So it looks like Bio-Formats is already doing the "best effort"<br>
transformation in this particular case. I'd be interested to know why<br>
it wasn't working for you with your Fiji/ImageJ installation. Were you<br>
using the current version of Bio-Formats (5.2.4) with the Java8 update site?<br>
<br>
I would highly recommend running bfconvert on these files to transform<br>
them into valid OME-TIFF data.<br>
<br>
A final comment about this type of "best effort" handling of invalid<br>
data. Bio-Formats already makes significant efforts to cope with<br>
various different types of invalid data and metadata so that broken,<br>
damaged and incorrect files can be read. However, this does come at a<br>
cost. As an example, a few weeks ago a fix to handle broken TiffData<br>
elements in OME-TIFF was found to corrupt *valid* OME-TIFF data due to<br>
certain assumptions being made about the structure of the data. That<br>
is, it altered the original (and correct) intent of the data.<br>
Workarounds for broken data should never compromise the handling of<br>
valid data, and at some point there is a limit for what it is reasonable<br>
or safe for us to correct. Broken data must at some point result in a<br>
hard failure. Not notifying the user that the data is incorrect is<br>
helpful from one point of view (getting the data read so we can get work<br>
done), but longer term it masks serious problems from both users and<br>
developers and delays getting them fixed. And it can also result in<br>
software using Bio-Formats unknowingly creating buggy OME-TIFFs; the<br>
workarounds result in problems not being picked up during testing<br>
because it appears to "work" while actually being broken. This is bad<br>
for interoperability, and also for the complexity of the OME-TIFF<br>
reader, which then needs to permanently retain a whole series of<br>
workarounds for every buggy file in existence rather than simply<br>
implementing the standard, and that burden is already unreasonably high.<br>
In this particular case, the workaround is (by chance) safe and<br>
functional, but development versions of the schema should never have<br>
been used for writing OME-TIFF; only published finalised versions of the<br>
schema are suitable for use in the OME-TIFF file format, and trying to<br>
use development versions for long term archival is asking for<br>
trouble--we make no guarantees these can be read back in since<br>
incompatible changes to the schema before release would result in<br>
untransformable data. The transforms are only provided for and tested<br>
with published released versions of the schema.<br>
<br>
<br>
Regards,<br>
Roger<br>
<br>
On 09/11/16 20:17, Curtis Rueden wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">Hi,<br>
<br>
Michael: This problem would occur if WiscScan was ever deployed to use a<br>
non-release version of Bio-Formats. Ask the WiscScan programmers to<br>
search the Git commit history for changes to the Bio-Formats JAR files,<br>
to see which versions were committed when.<br>
<br>
OME team: it would be nice if Bio-Formats could make a "best effort" to<br>
transform these sorts of files, by attempting to treat them as one or<br>
more released schema versions before giving up on the XSLT forward<br>
transform.<br>
<br>
Regards,<br>
Curtis<br>
<br>
--<br>
Curtis Rueden<br>
LOCI software architect - <a href="http://loci.wisc.edu/software" target="_blank">
http://loci.wisc.edu/software</a><br>
ImageJ2 lead, Fiji maintainer - <a href="http://imagej.net/User:Rueden" target="_blank">
http://imagej.net/User:Rueden</a><br>
<<a href="http://imagej.net/User:Rueden" target="_blank">http://imagej.net/User:Rueden</a>><br>
Did you know ImageJ has a forum? <a href="http://forum.imagej.net/" target="_blank">
http://forum.imagej.net/</a><br>
<br>
<br>
On Wed, Nov 9, 2016 at 2:03 PM, Michael Pinkert <<a href="mailto:mpinkert@wisc.edu" target="_blank">mpinkert@wisc.edu</a><br>
<mailto:<a href="mailto:mpinkert@wisc.edu" target="_blank">mpinkert@wisc.edu</a>>> wrote:<br>
<br>
Thanks for solving that Roger!<br>
<br>
That solution makes sense, though it is rather confusing that we<br>
would be encountering this problem now. We've been using the<br>
software for years without problems, but I guess an update either<br>
messed up the references or made the improper reference a<br>
requirement when it wasn't before.<br>
<br>
I'll have to talk to the more knowledgeable coders on this issue,<br>
and look around to see if other people are still having this problem.<br>
<br>
Best regards,<br>
Michael Pinkert<br>
<br>
-----Original Message-----<br>
From: ome-users<br>
[mailto:<a href="mailto:ome-users-bounces@lists.openmicroscopy.org.uk" target="_blank">ome-users-bounces@lists.openmicroscopy.org.uk</a><br>
<mailto:<a href="mailto:ome-users-bounces@lists.openmicroscopy.org.uk" target="_blank">ome-users-bounces@lists.openmicroscopy.org.uk</a>>] On Behalf Of<br>
Roger Leigh<br>
Sent: Wednesday, November 9, 2016 4:20 AM<br>
To: <a href="mailto:ome-users@lists.openmicroscopy.org.uk" target="_blank">ome-users@lists.openmicroscopy.org.uk</a><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"> <mailto:<a href="mailto:ome-users@lists.openmicroscopy.org.uk" target="_blank">ome-users@lists.openmicroscopy.org.uk</a>><br>
Subject: Re: [ome-users] Bug report for version 2012-06 OME-XML in<br>
Fiji, seen in grid/collection stitching<br>
<br>
On 08/11/16 19:50, Michael Pinkert wrote:<br>
> Hi Mark,<br>
><br>
> I just uploaded 9 files, from a much smaller sample image set. I<br>
tried using the ImageJ/Fiji stitching algorithm again with this<br>
smaller sample size and it ran into the same problem, with the same<br>
warning. It seems not to be reading the metadata correctly, because<br>
it was interpreting different Z-slices as different T-time points.<br>
><br>
> This problem occurred after a recent Fiji/ImageJ update and<br>
applies to older sets of images that I've already stitched; I don't<br>
think there's anything wrong with the formatting of the images.<br>
<br>
Dear Michael,<br>
<br>
I've taken a look at your files, and the problem is that the XML<br>
schema is invalid. Using bftools' xmlvalid program:<br>
<br>
% ./tools/xmlvalid ~/images/17416/FijiTester.ome.xml Parsing schema<br>
path<br>
<a href="https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd" target="_blank">
https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd</a><br>
<<a href="https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd" target="_blank">https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd</a>><br>
Validating /home/rleigh/images/17416/FijiTester.ome.xml<br>
Error parsing schema at<br>
<a href="https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd" target="_blank">
https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd</a><br>
<<a href="https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd" target="_blank">https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd</a>><br>
org.xml.sax.SAXParseException: schema_reference.4: Failed to read<br>
schema document<br>
'<a href="https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd" target="_blank">https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd</a><br>
<<a href="https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd" target="_blank">https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd</a>>',<br>
because 1) could not find the document; 2) the document could not be<br>
read; 3) the root element of the document is not <xsd:schema>.<br>
<br>
% ./tools/xmlvalid ~/images/17416/FijiTester_C0_TP0_SP0_FW0.ome.tiff<br>
Parsing schema path<br>
<a href="https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd" target="_blank">
https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd</a><br>
<<a href="https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd" target="_blank">https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd</a>><br>
Validating /home/rleigh/images/17416/FijiTester_C0_TP0_SP0_FW0.ome.tiff<br>
Error parsing schema at<br>
<a href="https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd" target="_blank">
https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd</a><br>
<<a href="https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd" target="_blank">https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd</a>><br>
org.xml.sax.SAXParseException: schema_reference.4: Failed to read<br>
schema document<br>
'<a href="https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd" target="_blank">https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd</a><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> <<a href="https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd" target="_blank">https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd</a>>',<br>
because 1) could not find the document; 2) the document could not be<br>
read; 3) the root element of the document is not <xsd:schema>.<br>
<br>
<br>
The schema which is being used here is an invalid URL, and was never<br>
a released schema. I'm not sure why any software would be using that.<br>
<br>
You can find sample files using the old 2012-06 schema here:<br>
<a href="http://downloads.openmicroscopy.org/images/OME-TIFF/2012-06/" target="_blank">
http://downloads.openmicroscopy.org/images/OME-TIFF/2012-06/</a><br>
<<a href="http://downloads.openmicroscopy.org/images/OME-TIFF/2012-06/" target="_blank">http://downloads.openmicroscopy.org/images/OME-TIFF/2012-06/</a>><br>
They are using a root element like this:<br>
<br>
<OME xmlns="<a href="http://www.openmicroscopy.org/Schemas/OME/2012-06" target="_blank">http://www.openmicroscopy.org/Schemas/OME/2012-06</a><br>
<<a href="http://www.openmicroscopy.org/Schemas/OME/2012-06" target="_blank">http://www.openmicroscopy.org/Schemas/OME/2012-06</a>>"<br>
xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance" target="_blank">http://www.w3.org/2001/XMLSchema-instance</a><br>
<<a href="http://www.w3.org/2001/XMLSchema-instance" target="_blank">http://www.w3.org/2001/XMLSchema-instance</a>>"<br>
xmlns:ROI="<a href="http://www.openmicroscopy.org/Schemas/ROI/2012-06" target="_blank">http://www.openmicroscopy.org/Schemas/ROI/2012-06</a><br>
<<a href="http://www.openmicroscopy.org/Schemas/ROI/2012-06" target="_blank">http://www.openmicroscopy.org/Schemas/ROI/2012-06</a>>"<br>
xmlns:SA="<a href="http://www.openmicroscopy.org/Schemas/SA/2012-06" target="_blank">http://www.openmicroscopy.org/Schemas/SA/2012-06</a><br>
<<a href="http://www.openmicroscopy.org/Schemas/SA/2012-06" target="_blank">http://www.openmicroscopy.org/Schemas/SA/2012-06</a>>"<br>
xmlns:SPW="<a href="http://www.openmicroscopy.org/Schemas/SPW/2012-06" target="_blank">http://www.openmicroscopy.org/Schemas/SPW/2012-06</a><br>
<<a href="http://www.openmicroscopy.org/Schemas/SPW/2012-06" target="_blank">http://www.openmicroscopy.org/Schemas/SPW/2012-06</a>>"<br>
<br>
xmlns:Bin="<a href="http://www.openmicroscopy.org/Schemas/BinaryFile/2012-06" target="_blank">http://www.openmicroscopy.org/Schemas/BinaryFile/2012-06</a><br>
<<a href="http://www.openmicroscopy.org/Schemas/BinaryFile/2012-06" target="_blank">http://www.openmicroscopy.org/Schemas/BinaryFile/2012-06</a>>"<br>
<br>
xsi:schemaLocation="<a href="http://www.openmicroscopy.org/Schemas/OME/2012-06" target="_blank">http://www.openmicroscopy.org/Schemas/OME/2012-06</a> <<a href="http://www.openmicroscopy.org/Schemas/OME/2012-06" target="_blank">http://www.openmicroscopy.org/Schemas/OME/2012-06</a>><br>
<a href="http://www.openmicroscopy.org/Schemas/OME/2012-06/ome.xsd" target="_blank">
http://www.openmicroscopy.org/Schemas/OME/2012-06/ome.xsd</a><br>
<<a href="http://www.openmicroscopy.org/Schemas/OME/2012-06/ome.xsd" target="_blank">http://www.openmicroscopy.org/Schemas/OME/2012-06/ome.xsd</a>>"><br>
<br>
while your samples do this:<br>
<br>
<OME xmlns="<a href="http://www.openmicroscopy.org/Schemas/OME/2012-06" target="_blank">http://www.openmicroscopy.org/Schemas/OME/2012-06</a><br>
<<a href="http://www.openmicroscopy.org/Schemas/OME/2012-06" target="_blank">http://www.openmicroscopy.org/Schemas/OME/2012-06</a>>"<br>
xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance" target="_blank">http://www.w3.org/2001/XMLSchema-instance</a><br>
<<a href="http://www.w3.org/2001/XMLSchema-instance" target="_blank">http://www.w3.org/2001/XMLSchema-instance</a>>"<br>
<br>
xsi:schemaLocation="<a href="http://www.openmicroscopy.org/Schemas/OME/2012-06" target="_blank">http://www.openmicroscopy.org/Schemas/OME/2012-06</a> <<a href="http://www.openmicroscopy.org/Schemas/OME/2012-06" target="_blank">http://www.openmicroscopy.org/Schemas/OME/2012-06</a>><br>
<a href="https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd" target="_blank">
https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd</a><br>
<<a href="https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd" target="_blank">https://raw.github.com/openmicroscopy/openmicroscopy/schema-2012-06/components/specification/InProgress/ome.xsd</a>>"><br>
<br>
It's the schemaLocation which is wrong, making the file invalid. If<br>
you fix that up, and the rest of the file is valid for the 2012-06<br>
schema, it should then work correctly.<br>
<br>
<br>
Kind regards,<br>
Roger<br>
<br>
--<br>
Dr Roger Leigh -- Open Microscopy Environment Wellcome Trust Centre<br>
for Gene Regulation and Expression, College of Life Sciences,<br>
University of Dundee, Dow Street,<br>
Dundee DD1 5EH Scotland UK Tel: (01382) 386364<br>
<br>
The University of Dundee is a registered Scottish Charity, No:<br>
SC015096 _______________________________________________<br>
ome-users mailing list<br>
<a href="mailto:ome-users@lists.openmicroscopy.org.uk" target="_blank">ome-users@lists.openmicroscopy.org.uk</a><br>
<mailto:<a href="mailto:ome-users@lists.openmicroscopy.org.uk" target="_blank">ome-users@lists.openmicroscopy.org.uk</a>><br>
<a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users" target="_blank">
http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users</a><br>
<<a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users" target="_blank">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users</a>><br>
_______________________________________________<br>
ome-users mailing list<br>
<a href="mailto:ome-users@lists.openmicroscopy.org.uk" target="_blank">ome-users@lists.openmicroscopy.org.uk</a><br>
<mailto:<a href="mailto:ome-users@lists.openmicroscopy.org.uk" target="_blank">ome-users@lists.openmicroscopy.org.uk</a>><br>
<a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users" target="_blank">
http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users</a><br>
<<a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users" target="_blank">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users</a>><br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
ome-users mailing list<br>
<a href="mailto:ome-users@lists.openmicroscopy.org.uk" target="_blank">ome-users@lists.openmicroscopy.org.uk</a><br>
<a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users" target="_blank">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users</a><o:p></o:p></p>
</blockquote>
<div>
<div>
<p class="MsoNormal"><br>
<br>
--<br>
Dr Roger Leigh -- Open Microscopy Environment<br>
Wellcome Trust Centre for Gene Regulation and Expression,<br>
College of Life Sciences, University of Dundee, Dow Street,<br>
Dundee DD1 5EH Scotland UK Tel: (01382) 386364<br>
<br>
The University of Dundee is a registered Scottish Charity, No: SC015096<br>
_______________________________________________<br>
ome-users mailing list<br>
<a href="mailto:ome-users@lists.openmicroscopy.org.uk" target="_blank">ome-users@lists.openmicroscopy.org.uk</a><br>
<a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users" target="_blank">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>