<Makoto> +present
scribe+
Avneesh: before UX accessibility metadata guidelines there is another discussion raised by Makoto
Makoto: topic a11y metadata for
ruby characters
... I'm director of DAISY Japan, we have been discussing a11y
metadata for the Japanese language
... one is ruby, another is horizontal or vertical writing,
last one is on adding space between words
... the first document is about requirements for the
discoverability of EPUBs containing ruby
... we need both ONIX anche Schema.org metadata for
consistency
scribe: VIPs really like ruby
both general ruby and parallel ruby
... since para-ruby is so common in Japanese textbooks
... some users are very annoyed by ruby (e.g. dislexic
people)
... an easy solution is to not display ruby
... some users don't care (e.g. partially sighted users) are ok
with ruby
... so we need different status: no-ruby, ok with ruby, ...
<CharlesL> accessibilityFeature="rubyAnnotations" is currently available. Idea is to add more
scribe: we're working on requirements docs, after that will propose metadata for Schema.org and ONIX
mgarrish: we already have "ruby-notation" in Schema.org, is it enough?
Makoto: we are discussing it, maybe we need more values
Avneesh: Makoto you can send out
proposal when it will be ready
... next topic: ONIX feedback on UX metadata guidelines
<Avneesh> https://github.com/w3c/publ-a11y/issues/23
<Avneesh> https://github.com/w3c/publ-a11y/issues/22
<Avneesh> https://github.com/w3c/publ-a11y/issues/21
<Avneesh> https://github.com/w3c/publ-a11y/issues/17
<Avneesh> https://github.com/w3c/publ-a11y/issues/15
Avneesh: brief overview #23
hazards, they have provived codes for different hazards
... #22: certified by for displaying the certifier
gpellegrino: I'm not sure we have "no hazards"
Avneesh: there are different codes "no flashing", "no sound", ...
<MadeleineRothberg> +q
CharlesL: do we have to do the
same for Schema.org? Telling "no flashing", "no sound
hazard"...
... maybe we can list both options in the crosswalk
MadeleineRothberg: yes, it is a
roundtripability issue
... we could put a warning
<Makoto> I support round-trip conversion.
Avneesh: if we want to have a code for "none" in ONIX we need request it and it takes several months
CharlesL: issue 22, I didn't realized we can have multiple certifiers
mgarrish: I think the issue is on
how ONIX can manage this field
... I think we can make more specific in next EPUB version
Avneesh: this discussion have to
happen in the Working Group
... I think that before asking ONIX we have to have it in EPUB
specs, then we can ask ONIX for adding these fields
George: what is the goal here? Do
we need multiple certifiers or do we want it to be
unique?
... maybe it depends from the jurisdiction
CharlesL: I thought about it a
lot, since publishers are improving their processes this may
make sense
... from a library o bookstore prospective it is difficult to
understand which one to show
lucaudrain: I agree we should
define EPUB accessibility specs before ONIX
... the publishing industry in France will self-certify their
publications
Avneesh: objections for adding
these issues to ONIX techniques?
... no!
<Makoto> +1
<CharlesL> +1
<lucaudrain> +1
+1
<MadeleineRothberg> +1
<Bill_Kasdorf> +1
<mgarrish> +1
<Avneesh> +1
<LauraB> +1
<George> +1
<Avneesh> https://github.com/w3c/publ-a11y/issues/20
Avneesh: it looks simple
gpellegrino: ok for me!
CharlesL: onix feed is a group of records, so fine
<Avneesh> https://github.com/w3c/publ-a11y/issues/19
Avneesh: ok, we can approve it
<MadeleineRothberg> +q
MadeleineRothberg: I added a
propose with edit to merge last sentences
... maybe we have to check it with EditEUR
mgarrish: a think we have to change first sentence "EPUB or Schema.org" since EPUB doesn't have a11y metadata
https://w3c.github.io/publ-a11y/UX-Guide-Metadata/techniques/epub-metadata.html
gpellegrino: we have discussed for naming it "EPUB Accessibility metadata", may we name it?
CharlesL: I think it is a good idea
<MadeleineRothberg> +q
CharlesL: maybe in the future we can move this metadata from EPUB to Schema.org (in long-term)
Avneesh: for now I think we need
a link to explain people what do we mean by "EPUB Accessibility
Metadata"
... is it ok to link to the techniques? Or to the vocabulary
page?
mgarrish: I'm not sure, maybe we can link to accessibility metadata
MadeleineRothberg: I'm not sure we can move all metadata to Schema.org, for political issues
Avneesh: I agree, maybe we don't need everything in Schema.org
mgarrish: Yes, I think it is something we have to discuss while writing specs, in the future
Avneesh: the recommendation is to link to EPUB accessibility metadata
<Avneesh> https://github.com/w3c/publ-a11y/issues/18
Avneesh: Matt will write a new text
+1
<lucaudrain> +1
<CharlesL> +1
<Avneesh> +1
<LauraB> +1
<MadeleineRothberg> +1
<George> qq+
<jens> +1
<Bill_Kasdorf> +1
<Zakim> George, you wanted to react to mgarrish
George: I think the existing
software that moves metadata from ONIX to MARC
... but MARC is based on Schema.org
<George> +1
<Avneesh> https://github.com/w3c/publ-a11y/issues/16
George: so it's a round-trip issue, but we don't have to manage it now
+1
<MadeleineRothberg> +1
<Bill_Kasdorf> +1
<jens> +1
CharlesL: I'm trying to understand what is the proposal
<CharlesL> +1
<George> +1
CharlesL: what George wrote was tied to the EPUB a11y metadata, so I made it more generic
Avneesh: next topic: editing
gpellegrino: I can do it
I won it!
Avneesh: Matt will add the text
in the issue tracker
... do we need another call? In two weeks?
lucaudrain: what are the next steps?
Avneesh: maybe we don't need it
George: when the documents will be updated, we can review it
lucaudrain: when we will send it
for review we can make it public
... then may I refer to it as "public"?
Avneesh: yes!
<laurent_> bye!
This is scribe.perl Revision of Date Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/rubyAnnotations/accessibilityFeature="rubyAnnotations" is currently available. Idea is to add more/ Succeeded: s/Iìm/I'm/ Succeeded: s/tidy/tied/ Present: Avneesh gpellegrino AlexGrover George CharlesL LauraB mgarrish zhengxu lucaudrain Bill_Kasdorf No ScribeNick specified. Guessing ScribeNick: gpellegrino Inferring Scribes: gpellegrino WARNING: No "Topic:" lines found. WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting 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: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report 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]