Meeting minutes
Review of in-progress techniques documents.
AvneeshSingh: let's start with the update on ONIx
<AvneeshSingh> https://
<Madeleine> Zoom link https://
gautierchomel: on the ONIX techniques we've added charts, diagrams, accessibility. summary and Pre-recorded audio
… for accessibility summary: in ONIX there are two codes for that (one for the "old" way to intend accessbility summary, one for the "new" way: the idea that should not say the same thing that are already expressed by machine-readable metadata)
… so our proposal is that if in a record there is both the accessibility addendum and accessibility summary, only the first should be displayed
… second thing is to identify the language in which the accessibility summary (or addendum) is written
… to pass it to the assistive technologies
AvneeshSingh: any comment?
… other items are "Charts, diagrams, and formulas" and "Pre-recorded audio"
gautierchomel: sure, all the text is there, and it can be reviewed
AvneeshSingh: yes, we can get feedback via the mailing list or via the issue tracker
AvneeshSingh: Charles do you have any update on the EPUB metadata techniques?
<AvneeshSingh> https://
CharlesL: we are using the work done for ONIX and mirroring that in the EPUB metadata world
Issue #251: Principles document examples for nonvisual reading
CharlesL: the conformance may be tricky, but let's see
<AvneeshSingh> w3c/
Madeleine: the original issue was that examples in the Principles document for nonvisual reading were not aligned
… now it's ok, so I think now we can close it
… but there is still a question about aligning examples in the principles document with examples in the non visual reading
… ok I'm closing this issue
AvneeshSingh: question: may be there cases where the order may differ from ONIX to EPUB metadata?
gpellegrino: I think that trying to align the order in the techniques and in the principles it doesn't make a lot of sense
… the goal of the documents are different
… the order may even differ from ONIX to EPUB
CharlesL: I agree
Madeleine: I agree too
… another thing is about the "unkown" value
Issue #260: Need to harmonize Principles and Techniques on Non-Visual Reading
Madeleine: is it meaningful? Do we need it?
<AvneeshSingh> w3c/
<gautierchomel> gpellegrino: Principles states that some values can be hidden if null (unknown), but techniques must provide what to say in such case for implementers who want's to display something.
<gautierchomel> CharlesL: we can addd a note in the principles to explain why order can change in techniques
AvneeshSingh: yes, I think that we can remove the "unknown" in the principles document, and leave it in the techniques
CharlesL: er may add a note about the order of the examples in the principles document
<gautierchomel> gpellegrino: i agree with Avneesh, but there may be cases where we have to say it in the principle (for the three jeys informations).
AvneeshSingh: yes for the three key information that should always be display, we'll leave the unkown
Issue #256: Align Hazards examples
<AvneeshSingh> w3c/
AvneeshSingh: so: for the key information that can be hidden, we remove the "unkown" for the principles and leave them in the techniques, with a note telling that the key information can be hidden
gautierchomel: the problem here is that we don't have examples for the extended version of all the hazards
… I made a proposal in the ticket
Madeleine: how many variants of hazards do we have?
Maybe we can elevate the flashing hazard
and then add another statement about the less common ones
CharlesL: this is tricky
… I think that if there is at least one hazard we should display all
CharlesL: yes, I think we can have information about multimedia in ebooks
… I like the idea of displaying something only if there is an hazard
AvneeshSingh: I agree we should not get in too much complex specification here
gautierchomel: Yes, I think in most cases we'll not have hazards
… I would add a note telling that hazards can be displayed both concatenated and un-concatenated (as a list)
… maybe we can also update the section about filtering
… to suggest that in some cases filtering for different types of hazards
Bill_Kasdorf: I'm about uncomfortable with under specifying, and to hide information
… I think a lot of publishers may use the "unkown" value
… and it should be displayed
AvneeshSingh: we have a problem since not all hazards are specified, for example what does it mean an audio-hazard?
gautierchomel: the proposal is not to hide hazards, is only to being able to manage this section both concatenated and as list
<gautierchomel> gpellegrino: i suggest to check techniques that are clarifying our intention. Only EPUB with no Hazard metadata will have no information displayed.
CharlesL: can we tell if there is multimedia in the ebook?
1+
<Madeleine> +1, as long as we can trust that metadata, which I guess we have to do
gautierchomel: I like this approach
… I would like to digg into it
… to check if there is multimedia before displaying it
AvneeshSingh: in ONIX there is a way to tell if there is audio or video in the EPUB
gpellegrino: we may dig into a rabbit hole
Any other business.
gautierchomel: I'm trying to setup transifex, I've asked them but they say that we cannot use it for free, since being part of W3C is not for free
AvneeshSingh: ok, let's continue with the JSON files