Task #4100 (new)
Opened 16 years ago
Last modified 8 years ago
Handle mixed OME/non-OME XML blocks — at Version 2
Reported by: | curtis | Owned by: | mlinkert |
---|---|---|---|
Priority: | minor | Milestone: | OMERO-Beta4.3.2 |
Component: | Bio-Formats | Version: | n.a. |
Keywords: | n.a. | Cc: | jamoore, sbesson, mtbcarroll, rleigh |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description (last modified by ajpatterson)
When looking for OME-XML blocks, Bio-Formats assumes the entire tree will be enclosed in a root <OME> element, with no extraneous root elements or non-OME subtrees anywhere. Ideally, we would like to handle more heterogeneous cases, including:
- Non-OME block after an OME block
- Non-OME block before an OME block
- Multiple OME blocks, and/or multiple non-OME blocks
Obviously, there is not a lot we can do with arbitrary XML from a practical perspective other than ignore it, but for now the goal is merely to avoid throwing an exception in these cases.
Change History (2)
comment:1 Changed 13 years ago by jmoore
comment:2 Changed 13 years ago by ajpatterson
- Description modified (diff)
- Milestone changed from Unscheduled to OMERO-Beta4.3.2
Need to consider for validation work in 4.3.2 milestone.
imported from bio-formats:#305