Additional values for readingProgression

[mattgarrish]

readingProgression defines the values ltr and rtl. Should it also include top-to-bottom and/or bottom-to-top, as raised in #47?

[llemeurfr]

I raised this issue as a highlight of the fact that readingProgression and textual metadata direction were two different notions (even if languages that are written ltr (resp. rtl) correspond to books with a ltr (res.rtl) page progression).

IMO it is too early to add ttb and btt to the value set for readingProgression. This will come with an evolution of the standard for handling visual narratives.

[mattgarrish]

I'm not sure about bottom-to-top, as we didn't account for it in the epub metadata.

But if it's reasonable to expect a top-to-bottom progression will be needed for some publication type(s), and personally I tend to think it is, then it might be useful to add that value now.

If not, we have a bit of an extensibility problem to fix, as the manifest requires one of ltr or rtl and makes no provision for other values.

[iherman]

This issue was discussed in a meeting.

• No actions or resolutions

View the transcript

issue #51 values for readingProgression
Garth Conboy: See Issue #51
Ivan Herman: So far, the reading progression has two possible values, ltr and rtl…
… Laurent raised the possibility of whether we needed top to bottom or bottom to top…
… I don’t know if there’s a reasonable example for bottom to top. I don’t know if publications would use this, but we can add another value there if it makes sense.
Dave Cramer: I’m not expressing an opinion about the issue, but I don’t think we should make decisions here without drawing diagrams and talking about exactly what we’re expecting from user agents.
Ivan Herman: I agree, we should discuss when Laurent is around.
Dave Cramer: I’m wary of doing interesting visual things without a whiteboard around.

[iherman]

This issue was discussed in a meeting.

• RESOLVED: Defer #51 in favour of the future BDCoMa Profile, but Publication Manifest should state that we reserve other values for future work.

View the transcript

Wendy Reid: #51
Wendy Reid: additional values for RPD
… do we need more values?
Laurent Le Meur: we have a framework, we have a property, we can extend when we want
… we know a future step will introduce visual narratives, but we don’t need it yet
Dave Cramer: In the future we should not discuss this without visual aids
Wendy Reid: laurent is right; we can defer to a manga profile
Ralph Swick: this may be one place where the spec says we reserve all other values of this property for further work
… so implementations don’t crash on values that may come along
Proposed resolution: Defer #51 in favour of the future BDCoMa Profile, but Publication Manifest should state that we reserve other values for future work. (Wendy Reid)
Wendy Reid: +1
Dave Cramer: +1
Charles LaPierre: +1
Romain Deltour: +1
Brady Duga: +1
Rachel Comerford: +1
Juan Corona: 0
Gregorio Pellegrino: 0
Garth Conboy: +1
Benjamin Young: +1
Resolution #2: Defer #51 in favour of the future BDCoMa Profile, but Publication Manifest should state that we reserve other values for future work.