Meeting minutes
Agenda Review, Membership & Announcements
Action Items
<matatk> Here is what we decided earlier: https://
matak: pull request coming soon
I think we wanted the TAG template for the explainer, no?
should we keep explainers discrete or have an overall one?
matatk: I've seen markdown files containing this sorts of information at various levels work well
matatk: I'll clean these up mechanically then I'll try with Roy to deprecate the documents we don't want to track any longer
… we'
… we'll deprecate #1
<gb> CLOSED Issue 1 Broken link (by tripu) [bug]
matatk: we'll deprecate #4
<gb> CLOSED Issue 4 Use Case: HTML + Microdata (by AutoSponge)
matatk: we'll deprecate 5
… explainers need to stay in lockstep with the spec
… there will be a PR for moving the gap analysis and scenarios into use cases which will leave a bit of a mess in doc 3 that we can tidy up
APA re-charter, and TF description
<matatk> https://
<matatk> Current draft text: use author-controlled markup to define precise pronunciation across environments when content authors need certainty as opposed to cross-platform heuristic variability
let's leave specific technologies out of the description (sans SSML and PLS) because people seem to get the wrong idea about our aims
PaulG: Think of someone that faces barriers such as print and learning disabilitiles - they have to deal with the scenario that what's being announced isn't what's being communicated, and they have to work around those barriers before starting to engage with the content (or having their engagement with the content interrupted).
Also, in a learning environment, this just serves to increase the burden on the person.
matak: I will reply to janina's email with this