BFtools: Add option to showinf to validate TIFF vs OME-XML

[dgault]

This was a feature request raised on imagesc thread https://forum.image.sc/t/xmlvalid-check-for-omexml-vs-tiff-header-mismatch/50720/4

In the given example the OME-XML metadata does not align with the TIFF metadata and attempts to catch the mismatch in a validation step failed as the XML is only validated against the schema using the xmlvalid tool.

Showinf does perform such checks and outputs warnings but they are contained amongst the remainder of the showinf ouptut. Having a new option which would enable stricter validation and only out any validation errors or warnings for metadata mismatches would be useful in this case.

[imagesc-bot]

This issue has been mentioned on Image.sc Forum. There might be relevant details there:

https://forum.image.sc/t/xmlvalid-check-for-omexml-vs-tiff-header-mismatch/50720/6

[sbesson]

We have been discussing a similar strict option in the past. At the moment, a WARNING level logging message is used:

bioformats/components/formats-bsd/src/loci/formats/in/OMETiffReader.java

Lines 805 to 807 in 2564538

	LOGGER.warn("SamplesPerPixel mismatch: OME={}, TIFF={}",
	samples, tiffSamples);
	samples = tiffSamples;

bioformats/components/formats-bsd/src/loci/formats/in/OMETiffReader.java

Lines 1068 to 1069 in 2564538

	LOGGER.warn("SizeX mismatch: OME={}, TIFF={}",
	m.sizeX, tiffWidth);

Would a reader option that would allow to either log at the WARN level or throw a FormatException with the appropriate error message be a step in the right direction, especially in the context of QC as mentioned in the forum post?

IF so, a next question would be to know whether a single key/value pair allowing to choose between strict/lenient would be sufficient or whether more granularity might be required.

[dgault]

Throwing an exception could be beneficial and having it as an option would be nice, strict or lenient would work fine for this. Ideally you would likely want to know the full list of mismatched values so it may be best to gather the full list of warnings first.

[sbesson]

Ideally you would likely want to know the full list of mismatched values so it may be best to gather the full list of warnings first.

👍 this is certainly inline with the current behavior of xmlvalid