See also: IRC log
<wolfgang> is anyone already connected to webex?
<dauwhe> No. Getting various errors still. I've emailed Ivan.
<wolfgang> thx, Dave!
<dauwhe> still no luck
<dauwhe> yeah, that link is definitely not working
<dauwhe> Sorry everyone. Romain, do you have a link or # for DAISY's?
<dauwhe> rachel and I are on the DAISY line
<Avneesh> DAISY line is in US
<rdeltour> present_
<garth> Are other folks able to dial in… is “319 436 071” really the meeting ID?
<dauwhe> Garth: we're using the DAISY number
<Terence> I tried, but it said the meeting had been cancelled or ended.
<garth> Tx! That’s what I got too.
<garth> And for Brady: dial in +1 712/432-7300 Pin: 25693#
<LauraBrady> Just dialled in successfully.
<scribe> scribenick: tzviya
<rachel> Avneesh are you able to join the line?
dauwhe: Avneesh sent an email
summarizing. BillM is working with W3M on ISO
standardization
... If things progress, we will work with CG to ISO standardize
EPUB A11y 1.0
<dauwhe> https://inclusivepublishing.org/news-and-events/news/announcing-ace-beta-release/
dauwhe: Beta testing has
begun
... You can download and install the tool to participate in
beta testing
... I got it working and it's pretty cool. It generates a JSON
file identifying accessibility problems.
... I encourage all of you to test it
rachel: I have been pressuring vendors to test it as well
rdeltour: ACE is a tool to check
conformance to EPUB Accessibility 1.0 tools. It's for power
users. The tool has 2 facets.
... It does automated checks and data extractions. Automated
checks are conservative to avoid false positives.
... data extraction is intended for later inspection of
content.
... When using the tool, it's important to remember that it
does only part of the job. Most things cannot be
autoamted.
... There is also an HTTP install for larger workflows.
<Avneesh> Sorry my screen reader crashed and I had to restart
<rdeltour> Ace's dev site: https://daisy.github.io/ace
rdeltour: For those not interested in the technical, there is also inclusivepublishing.org
<rdeltour> For higher-level news: https://inclusivepublishing.org
<rdeltour> and the issue tracker on GitHub: https://github.com/daisy/ace/issues
dauwhe: any questions for avneesh or romain?
rachel: I spent some time digging
into existing EPUB for Ed
... Especially as we discuss best practices, I think that a
significant portion of the spec is just best practices
... I am trying to come up with a recommendation for how we can
break down this profile
... Perhaps this will be best practices that differ by
genre
... There may be elements that should be merged with 3.1
spec
... Some elements should be best practices or samples.
dauwhe: It seems that one of the
only obvious things that would fit into the 3.1 spec is some of
the metadata
... some of it might be a11y metadata, and some of it might be
what type of ed material it is
rachel: that is section 8
dau
<dauwhe> https://w3c.github.io/publ-cg/education/epub-education.html
<rachel> https://w3c.github.io/publ-cg/education/epub-education.html#navigation
rachel: I was also looking at
section 7 about navigation and wondering if that might go into
3.1 as well
... what's the best way to raise this?
<rachel> Section 8 Metadata: https://w3c.github.io/publ-cg/education/epub-education.html#publication-metadata
dauwhe: github issue
... some of the navigation section is more best practices
related (it is suggested, not MUST/SHOULD)
tzviya: the navigation section includes some SSV terms "toc-brief". We need to know if there are other terms that need to go into an ARIA vocabulary
<Bill_Kasdorf> why is the sky blue?
rachel: where should we record that?
tzviya: let's start recording that in the CG and bring it to the WG after tpac
dauwhe: does anyone know status of LTI stuff?
tzviya: ask RickJ
dauwhe: One can get into a lot of
trouble
... what can be done and by whom to help with best
practices?
rachel: I was looking at epub for
ed spec. As i reach out to people for help, I've discovered
that solutions are market-specific.
... I have been thinking that best practices might be an
alternative to profiles
... This would involve working with BISG
<rachel> roles for BISG
<rachel> https://www.irccloud.com/pastebin/6A7PnYNt/
<garth> Socializing over drinks is always fine.
Bill_Kasdorf: This is on agenda for tomorrow's BISG Content Structure Committee meeting tomorrow
Evan: how generic is this best practices discussion? Is it tied to what readers will/won't support or more generic?
rachel: I am hesitant to get into
system support, especially considering how fickle they can
be
... I think it would be useful to say this is a best practice,
but bear in mind that it won't work on X platform
Evan: This topic has come up in other groups, such as JatsML - is this a potential subset of EPUB?
dauwhe: I'm remembering working
on BISG FXL guide. We had a broad set of guidelines, followed
by systems restrictions
... If we include systems, it greatly adds to the task. I am
greatly interested in what the interoperable core of EPUB
is
... finding out what the core is would be of great interest
Bill_Kasdorf: Sometimes best
practices can be about dealing with the inconsistency
... How do we publish? I recommend a web-based living document,
not a static document
<rachel> +1 to dynamic web publication
<dauwhe> tzviya: If you look successful docs we've seen in the past
<dauwhe> ... the ones that have longevity don't address the fickleness of reading systmes
<dauwhe> ... like Matt's a11y guidelines
<dauwhe> https://idpf.github.io/a11y-guidelines/
<dauwhe> ... we'll forever be updating if we deal with interop
<dauwhe> ... maybe interop is a separate project
<dauwhe> +1
<rachel> +1 to interoperability as a unique spec
<wolfgang> +1
dauwhe: I was going to bring up
Matt's a11y guide as a useful model
... I wonder if we could build from that as a model, given how
intertwined a11y and best practices already are
+1
Bill_Kasdorf: I recommend doing this in a modular fashion
+1 to Bill_Kasdorf
<rdeltour> http://kb.daisy.org/publishing/
rdeltour: Matt's guidelines have
moved to accessibility knowledgebase
... we welcome contributions
... to the a11y knowledgebase
<dauwhe> https://github.com/daisy/kb
<dauwhe> q>
rdeltour: looking for reviewers and contributors, but this is not quite ready for publicizing
dauwhe: Everyone thinks best practices are a good idea. need volunteers
I will help
<LauraBrady> I am happy to contribute and help however I can.
rachel: I have volunteered
<LauraBrady> cool
dauwhe: next steps?
rachel: we can pull in best practices from epub for ed
<JohnCosta> I am happy to contribute also - based on profile work in IEEE Actionable Data Book research (interactive epub for education)
rachel: we can pull in resources from ???
<JohnCosta> http://ieee-adb.org
<LauraBrady> Weird echo on the phone call. Makes it hard to hear everything.
rachel: other resources to recommend?
<dauwhe> q
<rachel> we can pull resources from IEEE, DAISY, Publisher specific (Macmillan), and of course the education profile
dauwhe: AOB?
<teytag> Hi there
<LauraBrady> Thank you, Dave.
<wolfgang> Thanks, Dave!
<marisa_demeglio> ( present+ )
<teytag> Hi Dave. Will you send a notes about this meeting?
<dauwhe> teytag: yes, hope to have minutes up this afternoon
<teytag> Thanks for info
<Tobias> exit+
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 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/knowledgebas/knowledgebase/ Present: toshiakikoike tzviya rachel wolfgang Avneesh dauwhe rdeltour LéoPaul Garth duga Bill_Kasdorf Tobias clapierre Found ScribeNick: tzviya Inferring Scribes: tzviya WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 19 Oct 2017 Guessing minutes URL: http://www.w3.org/2017/10/19-epub3cg-minutes.html People with action items:[End of scribe.perl diagnostic output]