How should we handle references to multiple images? #9
HadrienGardeur
started this conversation in
General
Replies: 1 comment 1 reply
-
Making imgref an array would open a can of worms (not speaking about the string/array morphing I hate):
I prefer the "spread" approach, which contains an array of "imgref" and does not require a specific role to trigger a specific behavior. If a role is added, "page" is my best bet in this case (which would remove a value from #1). {
"role": ["page"],
"spread": [
"page2.jpg",
"page3.jpg"
]
"children": [
{
"role": ["panel"]
"spread": [
"page2.jpg#xywh=percent:0,0,100,20",
"page3.jpg#xywh=percent:0,0,100,20"
]
}
]
} |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently, we have at least two use cases for Guided Navigation Objects that reference two or more images at a time:
img
role in ARIA that can be used to indicate that multiple images should be presented togetherWhen I started working on this project again, I initially thought that introducing a new property (
spread
) that allows more than one URI reference would be the right way to handle this, but I'm not sure that's the case anymore. This early proposal is currently available at: https://github.com/readium/guided-navigation?tab=readme-ov-file#potential-format-for-spreadI'm increasingly tempted to just rethink what's allowed in
imgref
and provide more specific semantics usingrole
.Example 1: A manga where we display a full spread before focusing on a panel across the spread
Example 2: img role in ARIA parsed as a Guided Navigation Object for read aloud
I guess this could open up similar questions for
textref
andaudioref
, but let's just focus onimgref
for now.Beta Was this translation helpful? Give feedback.
All reactions