– DRAFT –
(MEETING TITLE)

Approval for releasing the first public working draft.

AvneeshSingh: ready to publish our first public working draft. We need feedback on the EAA exceptions etc.

<AvneeshSingh> Principles: https://w3c.github.io/publ-a11y/UX-Guide-Metadata/draft/principles/?updated

<AvneeshSingh> ONIX metadata techniques: https://w3c.github.io/publ-a11y/UX-Guide-Metadata/draft/techniques/onix-metadata/index.html

<AvneeshSingh> EPUB metadata techniques: https://w3c.github.io/publ-a11y/UX-Guide-Metadata/draft/techniques/epub-metadata/index.html

AvneeshSingh: want to propose publishing these as First public working draft.

rickj: is the crosswalk also being published?

AvneeshSingh: that is not the responsible of this group but we can request it as they are part of this group :)

<AvneeshSingh> proposed: publish first working draft of the above three documents for user experience guide for accessibility metadata

<gpellegrino> +100

<rickj> +1

<Madeleine> +1

<CharlesL> +1

<Chris_edit> +1

<Hadrien> +1

<MiiaK> +1

Rick: there were some issues with syncing the principles & techniques.

AvneeshSingh: I think we should have this done as part of this larger review process.

gpellegrino: We are taking on this work on strong synchronization. We set up a spreadsheet to cross check between the principals, techniques, and json for translation.

<AvneeshSingh> approved

AvneeshSingh: Congratulations everyone! For all your participation and contributions, huge improvement from the original version.

"refines" clarification: issue #374

<AvneeshSingh> w3c/publ-a11y#374

rickj: we came across the issue with refines, in techniques there is only one refines around the date. in the principals document there are used but not reflected in the techniques, but in the EPUB specs it seems anything could have the refines.

CharlesL: gave explanation of the use of refines how it can be helpful.

rickj: this is kinda like additional information that maybe we should display like the accessibility summary

AvneeshSingh: some of these refines may be for the supply chain.

rickj: it is impractical to see if its useful, we need code for the case for what the publisher could do for the future. Since any metadata could have a refines and we should just show it and show how it is linked to another meta data field.

Hadrien: we felt what was common and useful. Readium does not expose EPUB metadata as is, we refine it "standardize" the output. a Japanese name and then refines with a different language for example.

The user experience would not be great if you show everything.

AvneeshSingh: can you send a list of which refines you prioritized.

rickj: thanks that would be great.

Any other business.

Here is Benetech's GCA metadata

<meta property="dcterms:conformsTo" id="conf"> EPUB Accessibility 1.1 - WCAG 2.1 Level AA </meta> <meta property="a11y:certifiedBy" refines="#conf" id="certifier">xyz</meta> <meta property="a11y:certifierCredential" refines="#certifier"> xxx</meta> (Optional date metadata can also be included.) <meta property="dcterms:date" refines="#certifier"> yyyy-mm-dd </meta>

AvneeshSingh: plan will send an announcement to the Publishing Working Group. Others will also send to their publishing groups.

rickj: We do a quarterly newsletter and would like to submit something to them as well.

AvneeshSingh: we will also have a posting for InclusivePublishing.

rickj: I have already been pushing it.

<rickj> (wondering where the IRC command for balloons and horns and fireworks is.... time to celebrate!!! )

MiiaK: should we spread this to the ONIX channel or would EDltEUR.

Graham: feel free to send it to your groups.