Task #4085 (new)
Opened 13 years ago
Last modified 13 years ago
Update OME-TIFF web site to reflect proposed modifications — at Initial Version
| Reported by: | curtis | Owned by: | curtis |
|---|---|---|---|
| Priority: | critical | Milestone: | Unscheduled |
| Component: | Documentation | Version: | n.a. |
| Keywords: | n.a. | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
I sent an email to the ome-devel mailing list with a list of proposed augmentations to the OME-TIFF format, arrived at through discussion with other OME developers and interested parties. In summary:
- Allow OME-TIFF datasets to use BigTIFF, rather than normal 32-bit TIFF, as appropriate.
- Update the recommended filename extension from .tif to .ome.tif, for clarity.
- Include an XML comment at the top of the OME-XML metadata block with a warning to those who would edit the block by hand.
- Store a hash (SHA1) of the pixel data associated with each TiffData? element.
- Store a hash (SHA1) of the OME-XML metadata in a custom TIFF tag.
The OME-TIFF web site needs to be updated to include these ideas, and our sample data should also reflect the recommendations as closely as possible (probably easiest to use an updated Bio-Formats to write new sample OME-TIFF files; see ticket #82).
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
