13:46:57 RRSAgent has joined #pcg-a11y 13:46:57 logging to https://www.w3.org/2022/05/12-pcg-a11y-irc 13:47:11 Zakim has joined #pcg-a11y 13:47:26 zakim, this will be pcg-a11y 13:47:26 ok, AvneeshSingh 13:47:42 present+ 13:47:50 chair: AvneeshSingh 13:48:20 agenda+ Update on extending crosswalk of schema.org accessibility metadata and ONIX to MARC. 13:48:40 agenda+ Issues raised by AccessibilitySummary guidance document team: 13:49:05 agenda+ Any other business. 14:00:09 MURATA has joined #pcg-a11y 14:00:34 Terence has joined #pcg-a11y 14:01:12 CharlesL has joined #pcg-a11y 14:01:16 GeorgeK has joined #pcg-a11y 14:01:19 present+ 14:01:24 present+ 14:01:32 AlexGrover_ has joined #pcg-a11y 14:01:34 g_pellegrino has joined #pcg-a11y 14:01:38 present+ 14:01:40 present+ 14:01:55 MadeleineRothberg has joined #pcg-a11y 14:02:28 present+ 14:02:34 zakim, next agendum 14:02:34 agendum 1 -- Update on extending crosswalk of schema.org accessibility metadata and ONIX to MARC. -- taken up [from AvneeshSingh] 14:02:51 scribe+ 14:03:01 https://docs.google.com/document/d/1Lh0TwYHg574WFvdIAB1-Pns3fF7oSCjD/edit?usp=sharing&ouid=110044170227731414177&rtpof=true&sd=true 14:03:21 paulgilius_ has joined #pcg-a11y 14:03:39 C_Carr has joined #pcg-a11y 14:03:43 Chris: We got some comments from Marrakech group at the June meeting to take them through the crosswalk. to get feedback 14:03:54 q? 14:04:03 Naomi_ has joined #pcg-a11y 14:04:13 present+ 14:04:44 q+ 14:04:48 …, not a lot of activity or in issue tracker. we have a question for the ONIX experts. offer to share ONIX metadata with us, we would like to map it out, the schema one is fairly clear, but ONIX is a little harder and we need real examples. 14:05:12 q+ 14:05:16 C_Carr: most NA authors has not adopted ONIX 3.0 14:05:25 ack next 14:05:35 g_pellegrino: I am available to share ONIX examples. 14:05:53 q- 14:06:25 q+ 14:06:28 …, Where would you like me to drop these? In ONIX version we have to focus on 3.0, since ONIX 2.0 is not maintained and a11y is really only been added to 3.0. and EU and is used by publishers / supply chains. 14:06:32 The same in JP 14:06:36 ack george 14:06:53 q+ 14:07:33 GeorgeK: Amazon last year started to require ONIX 3.0 to be delivered to them. this has incentivized to move to 3.0. Not sure where EDU publishers are, but most Trade are moving to 3.0 14:07:40 ack naom 14:09:03 q? 14:09:03 Naomi_: I have nothing to do with the ONIX systems, our system can provide ONIX 3 happened 3 years ago. a year ago there were some small retailers can only take 2.0. some only could take spreadsheets. in the US the Amazon thing is really making a difference. there are always a few stragglers. I can get a list if thats helpful. 14:09:16 +q 14:09:18 q? 14:09:40 ack next 14:10:06 MURATA: I know Japanese publishers has our version of ONIX 3 not sure if all books have ONIX metadata but they are trying but 3.0 is heavily used in Japan. 14:10:28 ChrisOliverOttawa__ has joined #pcg-a11y 14:10:48 q? 14:11:02 q? 14:11:12 AvneeshSingh: Gregorio, Madeleine and Charles spent a lot of time getting these into ONIX 3. 14:11:56 Chris: Chris Carr on the Canadian MARC committee in June with the official standards group to pass the mapping at that point to this wider audience to get more feedback / stability before we publish more widely. 14:12:05 AvneeshSingh: related to IFLA? 14:12:18 Michelle_ has joined #pcg-a11y 14:12:19 q? 14:12:34 q+ 14:12:38 Chris: American research libraries an implementation of the Marrakesh treaty and get metadata to support it. 14:12:39 present 14:12:47 q? 14:12:59 AvneeshSingh: Gregorio you will take on the ONIX .. 14:13:04 g_pellegrino: Yes 14:13:08 ack georg 14:13:15 GeorgeK: are you aware of the ABC? 14:14:27 Chris: Yes, this is more focused on students and faculty to launch a request, this library one direct to get the metadata into catalogs directly so no mediation can be done directly instead of via some 3rd party. 14:15:09 q? 14:15:24 GeorgeK: DAISY we have a WG EPUB in Higher Education, publishers, RS developers, etc. presentations at CSUN, AHG etc. you can join us if you want. 14:15:37 Chris: Thank you, I will mention to Victoria Owen. 14:15:47 zakim, next agendum 14:15:47 agendum 2 -- Issues raised by AccessibilitySummary guidance document team: -- taken up [from AvneeshSingh] 14:15:58 scribe+ 14:16:16 https://w3c.github.io/publ-a11y/drafts/schema-a11y-summary/ 14:16:28 George: list of issues provided. 14:16:51 #95: https://github.com/w3c/publ-a11y/issues/95 14:17:01 George: Spoke to Rachel and got corrected text for issue and merged it 14:18:46 George: Would like to clarify Gregorio's statement last week that you produce AccessibilitySummary from the ONIX. But if there is a summary in the epub, wouldn't that be carried over? 14:19:48 Gregorio: In LIA, we started certifying before there was schema.org in the epubs. So we have an internal checklist we used to create ONIX metadata. Thousands of ebooks have only ONIX, not Schema. 14:20:49 ... From last year we are starting to also create metadata in schema.org so we can use a different workflow, but we are still ONIX centric. So we generate Schema.org from ONIX 14:21:35 ...we are working on a solution to automate accessibility metadata for previous books, but it would be derived from ONIX. 14:22:30 George: So these files do not conform to EPUB Accessibility spec because they don't have embedded metadata 14:23:18 Gregorio: Yes, we conform with LIA instead, which can be stated with the conformance statement. So we conform with WCAG for the reading experience but not with the Discovery aspect. 14:23:38 q? 14:24:28 George: should we provide guidance for AccessibilitySummary about this workflow? 14:24:55 s/AccessibilitySummary/accessibilitySummary 14:24:59 Avneesh: we should keep the guidance general for summary, not specific to platform 14:25:31 Gregorio: the summary in ONIX is term 00 and the description is Accessibility Summary 14:25:52 q+ 14:26:08 ack next 14:26:19 George: maybe we should change wording in the guidance doc to "accessibility summary" to be more general rather than accessibiltySummary camel case 14:27:01 q+ 14:27:05 Gregorio: switch to description of file, then summary should say... Not if there is metadata, then summary should say.... 14:27:24 ack charl 14:27:57 q+ 14:28:13 CharlesL: we were planning to make scripts to look at schema.org metadata to draft the summary, but you are saying we should look at the file 14:28:29 CharlesL: Richard Orme is looking at this issue 14:28:40 q+ 14:28:42 q? 14:29:38 ack next 14:29:58 Naomi: Given all the different systems and tools, this will be automated in all different ways and this group can't proscribe it 14:30:37 Naomi: we have books that have javascript in them but it is never invoked and there is no interactivity, so if you scan for javascript you will get false positives 14:30:39 ack next 14:31:57 Madeleine: did Gregorio mean to scan the books, or did he mean to be more general in the language of the guidance doc to be less tied to one system 14:32:25 Gregorio: I meant to be more general in the guidance document, to avoid tying to one system 14:32:38 q? 14:33:16 Gregorio: So maybe the column header should be "is there mathML" not "is there schema.org accessibilityFeature=mathML" 14:33:39 q? 14:34:01 George: Aim document more at principles and less at metadata 14:34:51 q? 14:35:36 Gregorio: I will update the column headings to be less metadata-focused 14:35:56 George: I think we should also preserve the schema and ONIX values in the table 14:36:11 q+ 14:36:14 q? 14:36:56 q+ 14:37:20 Naomi: I would appreciate a mapping to hand off to the person who does the ONIX 14:37:43 ack char 14:38:16 CharlesL: Could have a column with the generic wording, not call out schema or onix. Or could have a table with all of it. 14:38:41 ...extra column in addition to the different metadata columns with the generic information and then what you'd expect in each metadata 14:38:54 ...puts the crosswalk right there and also guides the summary 14:39:16 ... could separate out tables if this gets too complex 14:39:29 ack next 14:40:04 Gregorio: Prefer Charles' second proposal because as we add new standards it will get huge 14:40:25 ...maintaining that table becomes the whole cross-walk but that should be a separate thing 14:40:33 q? 14:41:21 q? 14:41:29 q+ 14:41:56 Avneesh: Tzviya raised issue that we should prioritize feedback from users 14:42:38 ack charl 14:42:40 George: We could ask on various mailing lists for feedback 14:43:20 CharlesL: Vendors are starting to follow our advice on how to expose metadata. They have summary front and center and then bury all the details including hazards 14:43:28 ...so summary is very important 14:43:52 q? 14:44:04 ...do we want to create a survey to send out to ask what would be useful info in the summary? 14:44:51 q? 14:45:06 Lars: authoring guidelines should include writing summary in a clear and predictable manner 14:45:12 q+ 14:45:14 George: Yes, that's what we are working on 14:45:27 ack chris 14:45:59 ChrisOliver: IFLA has just put out a survey to libraries asking about the metadata they are using or would like to include 14:46:10 q? 14:46:39 George: We should find out what users want. Purchasers, professors and school districts that are selecting, different groups 14:46:59 ...tailor the survey to these different groups 14:47:33 ...Gregorio, when you update the tables, the first column will end up being called what? Features? Information to be communicated? 14:47:57 q? 14:48:01 Gregorio: I'm not a native speaker so maybe George you should suggest a solution 14:48:27 George: Information object, but that isn't good. Information to be communicated 14:48:35 q? 14:48:50 Charles: Facet? Hazards are not features 14:49:25 q? 14:49:38 Avneesh: The purpose is to see what is in the metadata and describe it, so it could be "accessibility metadata" even if not format-specific 14:50:23 q+ 14:50:36 George: OK. Column 1, Accessibility Metadata, Column 2, samples of summary language. Then link to crosswalks for schema and ONIX. 14:50:47 q? 14:51:06 ... do we put things in there or just link? People would appreciate the essential info and not just the link 14:51:15 ...link is canonical but this could be informative 14:51:16 ack next 14:52:01 Gregorio: question to Madeleine about crosswalk -- can we organize it with these headings? So that the link will be to the section for that piece of metadata? 14:52:09 q? 14:52:39 Madeleine: we could put in anchors for each row if needed, as long as it is HTML 14:53:04 q? 14:53:08 CharlesL: We would also need back linking to the summary document, wouldn't we? 14:53:11 q+ 14:53:21 q+ 14:53:35 q- 14:53:42 ack madel 14:53:44 q- 14:54:14 q+ 14:54:29 ack next 14:54:37 George: can we put a little bit of info in the summary table? 14:54:48 CharlesL: no, it will be too complex 14:54:57 Gregorio: agreed, too complicated 14:55:41 q? 14:56:03 CharlesL: We can put the link in the first column. Gregorio and I will work this out. 14:56:17 q+ 14:56:43 ack next 14:56:43 George: not enough time to discuss language issues and multiple summaries. 14:57:23 Naomi: was surprised to hear that Amazon is requiring ONIX 3 -- but that is only for physical books. Amazon still taking only ONIX for ebooks 14:57:38 ... correction ONIX 2 for ebooks 14:58:11 George: Action item to follow up with Amazon accessibility contact on ONIX 3 importance 14:58:21 ... sub-task force call next week at this time 14:58:28 Avneesh: Thanks to all 14:58:59 rrsagent, make logs public 14:59:10 Lars: Could use some files to test in our reader 14:59:15 rrsagent, make minutes 14:59:15 I have made the request to generate https://www.w3.org/2022/05/12-pcg-a11y-minutes.html AvneeshSingh 14:59:19 Gregorio: Sure, I can send them 15:22:04 CharlesL has left #pcg-a11y 16:30:17 GeorgeK_ has joined #pcg-a11y