W3C

- DRAFT -

EPUB3 CG: A11Y TF Meeting on UX A11Y Metadata

04 Sep 2019

Attendees

Present
Avneesh, gpellegrino, George, Naomi, Bill_Kasdorf, CharlesL1, romain, mattg, Madeleine, Amy, JulieBlair
Regrets
Chair
Avneesh
Scribe
George, CharlesL1

Contents


<George> scribe: George

Introductions of people present

present Amy

Madeleine has worked on Access for All, which helped to populate schema.org. She is a metadata expert.

AS: There was a need for presentation of accessibility in a user friendly way.

VitalSource started this and it was clear that a user friendly presentation was needed. This presented the schema.org metadata.

LIA brought to us the need to include ONIX. Madeleine has been working to harmonize Schema.org and ONIX.

There are also other metadata standards, such as Bibframe and MARC.

This brought forward the need to separate the layers of this document.

One for principles and one for techniques.

We can update the techniques as more metadata standards become relevant.

Views?

<CharlesL1> https://github.com/benetech/UX-Guide-EPUB-A11y-Metadata

<gpellegrino> +1 to this approach :)

<CharlesL1> Here is the link to the new W3C github new home for this work

<CharlesL1> https://github.com/w3c/publ-a11y/tree/master/UX-Guide-Metadata

<Bill_Kasdorf> +1 This is really relevant to something I'm working on right now for a client

How do we formulate the principles and the techniques.

GP: the first part explains what screen reader friendly means.

It explains the high level principles.

<gpellegrino> Sorry

In the high level principles, we explain what we need from the metadata.

In the techniques docoument we explain how to extract the documents.

AS: Should we have different techniques for the various metadata types?

Matt: we should encapuslate for each metadata type , but on the other hand you could have them together.

Bill: One comprimise is to put one primary and an appendex for others.

It is common for a publisher will need schema.org, ONIX and MARC.

Charles: To Bill's point. Who is the intended audience? Is it libraries, vendors?

If you are talking about a technique, we had the various approaches grouped together. However, because ONIX is so big it blew up in trying to do it.

Bill: Charle's point is a good one.

Charles: answering Bill's points, a simple concept in schema.org might require multiple items in ONIX.

Bill: the differentmetadata idems are very different.

GP: We can seprate the principles and referenced them saperately.

<Bill_Kasdorf> +1 to what Matt just said about the need to explain the formats

<Bill_Kasdorf> Good luck explaining MARC. . . .

providing an exampleMaatt; Add on to the idea if it is not simply then it becomes too complex to explain what ONIX or schema is doing.

use these techniques?Avneesh: Do we think Ace or SMART would

<CharlesL1> scribe: CharlesL1

GK: agree with matt, we are not here to document ONIX / Schema.

<gpellegrino> +1 to George

GK: , having a consistent first part and then having a technique for schema, and another for ONIX / MARC/Bibfram then keep it simple separate and we are providing an easy to use example of what this can be, and we are providing a user friendly translation of this.

<Bill_Kasdorf> +1 to George

<scribe> scribe: George


.Avneesh: Ace would reference the principles

Romain: We do not need to worry about the publication process, because this is a note.

We could publish as one document or we could split it.

one for ONIX and one for Schema.org.Avneesh: Let's start with two techniques documents

George: Not confirmed, but MARC may be referencing schema.org.

RESOLUTION: We will start with 2 techniques document ONIX and Schema.org

Madeleine will help Charles, and GP will take ONIX.

Matt has done a great job in setting it up. so it may be a lot of copy and pasting.

Bill: Is the principles what Charles put in? Yes.

We will probably needCharles: In the last step of presentation of everything.

Bill: What would be most useful are the principles. Can I send the link out?

Timeline and how we work.

Charles and GP can put their parts in to the document.

After TPAC we will do a pole for our next call.

<CharlesL1> title: EPUB3 CG: A11Y TF Meeting on UX A11Y Metadata

Summary of Action Items

Summary of Resolutions

  1. We will start with 2 techniques document ONIX and Schema.org
[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/09/04 16:53:09 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: Avneesh gpellegrino George Naomi Bill_Kasdorf CharlesL1 romain mattg Madeleine Amy JulieBlair
Found Scribe: George
Inferring ScribeNick: George
Found Scribe: CharlesL1
Inferring ScribeNick: CharlesL1
Found Scribe: George
Inferring ScribeNick: George
Scribes: George, CharlesL1
ScribeNicks: George, CharlesL1

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]