I wondered if it's planned to enable support for serving up RTI images using IIIF tiles-on-demand instead of whole images, or does that not work with the new way the RTI data is stored ? (Possibly it would need to request 3 tiles simultaneously ?)
If it is planned to do that, I wondered (longer-term) whether the data in the info.json might be something that could be integrated into the IIIF Image API as an extension, so a single info.json provides the information needs for both IIIF tile retrieval and RTI calculations.
Apologies if I've mis-understand the architecture, still getting my head round how it all works.
I wondered if it's planned to enable support for serving up RTI images using IIIF tiles-on-demand instead of whole images, or does that not work with the new way the RTI data is stored ? (Possibly it would need to request 3 tiles simultaneously ?)
If it is planned to do that, I wondered (longer-term) whether the data in the info.json might be something that could be integrated into the IIIF Image API as an extension, so a single info.json provides the information needs for both IIIF tile retrieval and RTI calculations.
Apologies if I've mis-understand the architecture, still getting my head round how it all works.