Meeting minutes
Deadline for feedback for first public draft.
AvneeshSingh: proposed deadline november 20th
rickj: we have a number of small changes. I would love if possible to have a second public draft, asap, so we can review something more up to date.
CharlesL1: we could, yes there were a lot of impromvements.
AvneeshSingh: the question is does the editors have the bandwith?
gpellegrino: I'm travelling but i see no problem. We have a publishing script to ease the process
<gpellegrino> actual URL: https://
<rickj> +1 to end of Nov deadline
George: before thanksgiving break would be good. Too much time tends to push to backlist of todos. We want to be on the frontlist.
<rickj> modifying my +1 to agree with George on Tuesday Nov. 26
Harmonizing strings in principles, ONIX techniques and EPUB metadata techniques.
AvneeshSingh: let's publish an incremented draft and let until november 26th for feedbacks.
<AvneeshSingh> Principles: https://
<AvneeshSingh> ONIX metadata techniques: https://
<AvneeshSingh> EPUB metadata techniques: https://
George: short summary. We want to harmonize the strings in principles and techniques. We decided to have statements without period at the end. All exemples are identified by a data ID so we can have more than one per document. each data ID is a Key in the JSON with Compact and Descriptive variants.
the xlsx file is here to check that everything is aligned
AvneeshSingh: do we want to push the JSON in the next draft ?
rickj: I don't need a JSON file until it's a final one.
George: one big issue is about legal consideration. We're misisng more comments.
rickj: we assume that anything we get here will be for our internal use
gautierchomel: I think we had feedback in GitHub, saying this information should not be displayed, publishers will not use the metadata if something is displayed
… I think we had an agreement on a string proposed by Chris Saynor
ISSUE: w3c/
gautierchomel: to me the general statement is a good compromise
… and provides a good level of security
gpellegrino: proposed wording was This title benefit from an exemption or exception to legal provision of accessible publication.
rickj: US ADA Title 2 causes questions about those exemptions being too EAA oriented. We need a more neutral statement.
gautierchomel: I agree with Rick, that's why we need a string that is really neutral
… do we want multiple statements, one for each legislation?
… or one for all?
Chris_ONIX: I would argue for a very general statement, not market dedicated.
Chris_ONIX: I'll make wording proposals.
rickj: My understanding is that Title 2 has no exemption. It's WCAG AA or not.
CharlesL1: there are exceptions in title 2 like archival purpose. But we don't have it in metadata. But exceptions can exist in other markets later.
George: we need to be global in our guidance. are we thinking tthat the techniques would identify a string to trigger a suggested display, or it is a statement that a publisher could make? Is it binary or per metadata?
Chris_ONIX: three onix codes are very precise, thta's not what we want to show. It's for the use of regulatory. I would think that any of those three codes triggers one same sentence.
rickj: the purpose of those legal metadata is for enforcement. Displaying it will probably confuse the UX.
gpellegrino: it may be beneficial for users to know that before they trigger a legal action for a non accessible publication.
AvneeshSingh: concrete exemple, MTM sweden, regulator authority receive complains from consumers.
gautierchomel: as a customer i can complain even in case of exemption.
George: agree, and also agree we need a general statement.
<rickj> my suggestion: w3c/
CharlesL1: we have a placeholder in the techniques so we can easily trigger one common string or one for each.
George: so we want this in our next release.
Explain the metadata workflow in 2.2 · Issue #397
<AvneeshSingh> w3c/
<AvneeshSingh> Fixed at: https://
mgarrish: we clarified the diagram and enriched it with PDF and MARC references to make it clear it applies to any file and metadata format. This is a visualisation of how the reference and techniques work together to provide a common user experience described by the Principles. An overview of this document set. We are happy to continue to refine if someone has suggestions.
<rickj> updating the image now!
Chris_ONIX: minor thing, it should be ONIX record instead of Code LIst. Apart from that, it's good.
Issue #437: Can we add a note to mention ONIX technique is applicable to UNIMARC
<AvneeshSingh> w3c/
gautierchomel: Christofer Carr requested for a delay with this issue
ccarr: we presented ONIX mapping to IFLA commitee, editors of UNIMARC had questions, so we want to clarify with them. We get back to you as soon as.
AvneeshSingh: 14th is daisy board, we have to push our next meeting to 21th.
AvneeshSingh: it fits the feedback deadline.
AvneeshSingh: editors will work in the meanwhile.