Meeting minutes
For information:
<Avneesh Singh> https://
Avneesh Singh: we already made some changes, including access mode sufficient now mandatory, AccessMode is down graded to recommended, and formatting for date. Those are the first changes for epub accessibility 1.2, if we are making these changes we should not use version 1.1.1.
Fix the type of the certifierCredential property: Issue #2112
Avneesh Singh: to be discussed further after US holidays
<Avneesh Singh> w3c/
Gregorio Pellegrino: we are putting the URL to our website
Gregorio Pellegrino: all other certification aspects like logo are ruled through a direct contract, not thru metadata
s /nder/under/
Evaluator relationship · Issue #2721
<Avneesh Singh> w3c/
Matt Garrish: we try to determine if it is third party certification or self sertified by comparing the publisher name and the name in the certifiedBy string.
Do we need to emphasise this third party certification?
Should we have actual metadata that states this?
Gregorio Pellegrino: Self certification does not make sense. The logic is if certifier matches the publisher or creater, then it is self certified.
George Kerscher: Rick J said that it is imppossible to match it.
Avneesh Singh: What does self certification mean? Does it means an independent Q&A department inside the same company doing certification?
Matt Garrish: Somebody in your organization has certified. It is weak metadata.
Avneesh Singh: If you self certify, you should not put your company name in certifiedBy.
Gregorio Pellegrino: People are not paying much attention to the both certifiedBy and credential are not used outside of LIA and Benetech.
Matt Garrish: should we remove the string comparison information from the spec?
Gregorio agrees.
George Kerscher: I see in higher ed a lot of weight being put on third party certification.
Matt Garrish: If you put the name of the organization name in, then that is the party certified.
The people can figure it out themselves if it is self certified.
Avneesh Singh: We should remove the piece that shows the comparison. Just leave the certifier is the name of the organization. We do not need to get into these issues.
Are we OK with this? Rexolved, no objection.
Hadrien Gardeur: This has been a problem for us. Publishers are not sure what they can say.
Anything related to certifier is hard to do something with.
We only allow a single certifier.
Having more certifications makes this a complex problem.
Matt Garrish: Using refines is very difficult.
George Kerscher: Could we add a simple metadata field that is third party certified?
Matt Garrish: We will still would have an ugly mechanism for presenting the metadata.
Avneesh Singh: Can we contact the higher education folks to get their take on third party certification. I am reluctant to do major changes which effects accessibility metadata display guide also, until there is very strong need.
Hadrien Gardeur: This is better suited for ONIX.
Gregorio Pellegrino: Making significant changes in the Accessibility metadata would get pushback from the big players.
Amazon has decided to use only ONIX.
Matt Garrish: Taking the examples outdoes not change anything.
Let's take out the wishiwashie pieces.
Extended Descriptions in EPUB3: Issue #2691
Avneesh Singh: We are having this discussion inside DAISY.
If we want something inside the specifications, we should bring this up.
Gregorio Pellegrino: I will present what I have proposed.
<Gregorio Pellegrino> https://
Hadrien Gardeur: The complexity for Reading system is that there are so many ways to present the information.
What is confusing is that there are so many ways to provided additional/long/extended description.
Matt Garrish: This seems to be the domain of best practices.
Gregorio are accustom to copy what we suggest.
Gregorio Pellegrino: We want one way to provide this and have many organizations adopt.
Hadrien Gardeur: We cannot assume that a best practice will be adopted.
People will not always follow best practice.
Gregorio Pellegrino: One guideline should be for publishers.
Another document for what the reading systems should do.
George Kerscher: We have a test experimental book on go back and history also, we want reading systems to support this functionality also.
Gregorio Pellegrino: There are other best practices that we need to develop
Avneesh Singh: Next call will be July 17. Meanwhile let us continue discussion on extended descriptions.