Meeting minutes
Any other business.
Proposal from editors' for refactoring the principles document of User experience guide for accessibility metadata.
https://
This is the link with respec. We worked the Navigation Section.
AvneeshSingh: we are categorizing the metadatas to make them manageable then explaining and proposing exemples of display. We have to deal with a lot of information. Writing in a user friendly and implementable way is challenging.
gpellegrino: we've worked collectivelly, Avneesh, Charles, I, George and Gautier... the wording may change but we are proposing a structure to apply to each key informations. We started with Navigation. First paragraph is a definition, second one is refining the definition (was rationale before). Then exemples provided as extended (multiple sentences) or compacted (one sentence)...
… each sentence of the extended exemple is related to one metadata. We are interested on your feedback before writing other key informations.
CharlesL: The exemple Landmark is a great one of what is missing in metadatas.
GeorgeK: we have description that can be used to understand how to translate / localize wordings. Two different implementation exemples because diversity of realities.
AvneeshSingh: we want to know from the group if we are on the good way.
Naomi: I like the structure, it's pretty understandable. I'm just not sure of the Implementation subtitle related to ONIX / Schema.org technics. It should probably be "technical set up to trigger exemples" but to be simplified to be a heading.
GeorgeK: the concatenated seentence is nice but also the most complicated to elaborate. We have to think of absences and partiall presences. Would it be: there's no navigation tool provided? Do we say no Index?
<Zakim> gpellegrino, you wanted to say that we may call the heading "techniques"
<Naomi> +1
gpellegrino: implementation could be called technics as it referes to the names of the documents as announced in the introduction...
… on concatenated phrase I think we can find an easy way.
Madeleine: implementation I was thinking about Metadata technics.
AvneeshSingh: we can reserve one more week to give a chance to implementers who are not on this call to give a feedback.
GeorgeK: when we think about localization, the items to localize are exemples.
gpellegrino: localisation is expected for all exemples, but localisation implementers may do a choice here. I prefer separated examples so we can refer to each sentence separatly even in separated sentences example. To check how ReSpec can handle a good presentation.
AvneeshSingh: next call in 2 weeks for more feedbacks. Thank to all of you.
Hadrien: just pointing out during implementation we struggled with finding the metadata. We have a better view of market provided and file provided metadatas, we see a massive impact on this discussion. Will be presented in Madrid readmagine, at least about the work done on spanish market. To be done for other markets, we hope to have it for september. This will give us an idea of what in the display guide is actually possible to show.
Naomi: we are about a week away from using onix to epub mapping table produced by this group. Any file newly produced will have ONIX accessibility. Thank to everyone who did this mapping work, it has been crucial for us.
AvneeshSing: it's good to see real life implementation. Thank you very much!
Chris: we are updating ONIX code lists and we plan to send the proposal to that group. It's going to be a big update. If there is agrement of national groups it should be published in july. No deprecation. It's about adding details and precisions. It does not affects only list 196 but also 81 and others.
AvneeshSing: very nice informations, see you in 2 weeks.