Meeting minutes
<tzviya> Date: 2022-10-12
wolfgang: counterfeiting issues recap
… , ability to compare two books, perhaps blockchain technology.
AvneeshSingh: working on the same pieces, how to right good a11y summary. MARC/ONIX/Schema a Canadian group which was on holidays, should start back up in Oct. We will meet tomorrow to discuss. How to improve the user experience guide on a11y metadata.
<AvneeshSingh> document for a11y summary:
<AvneeshSingh> https://
<AvneeshSingh> Crosswalk for accessibility metadata: https://
George: the name accessibilitySummary, name is really accessibilityAddendum is more realistic. Within the next month we should be closer to having some guidance. enhances modifies clarifies other a11y metadata. Example if there was a hazard it will identify where it is.
… , not an overview anymore as this is covered by the accessibility metadata. with the EU A11y Act this other metadata will be surfaced. It would indicate it conforms to WCAG AA level, the summary would say something like this publication strives to reach WCAG AA as its difficult to 100% achieve perfection. We may look into a new schema term such as accessibilityAddendum.
Avneesh: should not repeat the machine readable accessibility Metadata.
Education TF
<Paul_B> https://
Paul: We go over draft of the Education TF Purpose document. who we want to work with for use cases
… , outlining goals, clear on how we will use the use cases. Review / determine issues raised are already addressable. maybe the solutions are not known. how to increase awareness.
… , determine which use cases we will fwd to the Working Groups. User profiles: publishers and various roles / ed-tech companies, students parents, authors. Vendors etc.
<Paul_B> https://
Paul: , Sample use case as a guide given by Charles.
… , give a rough template with just the headers. Susan Newhouse asked about a disclaimer, it may be necessary / reassuring that their responses will be anonymous etc.
… , we have the pieces in place to start gathering the use-cases, most of our time should be spent reviewing these use-cases.
AvneeshSingh: discussed the Accessibility piece with DAISY, what ever we wanted to put into the Education we have put this in already in the Accessibility 1.1
Paul: as use cases come in that are addressing a11y issues we will send this to the accessibility TF to see if these have been already addressed or how we can move this forward.
<Zakim> tzviya, you wanted to comment on use case structure
<AvneeshSingh> +1 Tzviya
tzviya: use case structure: proposed solutions might not be included, it might discourage writing a use-case. separate story and solution.
Paul: We have discussed this and there is no expectation of a solution and most cases there won't be a proposed solution.
gautier: I used a github proposed use-case template. I didn't follow the template exactly but I failed to find the Education TF template. I found difficult I had to rewrite many times, User story editorial. and a list of audience and benefit.
<tzviya> https://
gautier: easier way to restate the same thing.
Paul: yes, we discussed this and not every section needs to be filled out. Important thing is to get the right information in there.
wolfgang: get precise stories from all kinds of publishers, what is the person we are listening too, scientific publisher, student, etc.
… , why are you asking this. so we can distinguish the stakeholders. we are looking for solution from our best practices documents. We can make experiments and what is our aim in doing this.
paul: most important is to define the persona, and specific information on the pain point, problem statement is as clear as possible.
wolfgang: we can refine this use-case document, should be flexible. to categorize these use-cases.
Bill_Kasdorf: adding couple more example just the example and the pain points. With one example could bias folks. We want to encourage as many use-cases.
+1 to that bill.
wolfgang: identifying the pain points without solutions.
… , I agree
Paul: as we start getting use cases in and review with group we can modify the approach accordingly. I will create a blank template to guide the approach.
Bill_Kasdorf: Redundancy is a feature not a bug. 10 use. cases for the same thing is important to know. should not make the use cases visible initially.
wolfgang: could get different views and additional information which would be good.
<Bill_Kasdorf> I like encouraging +1s as Wendy suggests
wendyreid: Less having 10 issues for the same thing, perhaps adding to the original use-case. people can vote on these issues
… , those who can't articulate a use case they can +1 on the existing ones there which match their pain points and offer additional info they they wish.
<tzviya> +1 to wendyreid
+1 as well :)