<Roy> aganda?
<Roy> scribe: Christine
Irfan: New members for the
pronunciation task force; follow-up with potential new
member
... potential new members from New Zealand, UK, and Rutgers
University (NJ); additional follow-up required
... correction the potential new member is from New
Zealand
... Rutgers Univ has students that can contribute to user
stories
Irfan: Created tasks and assigned to team members
<Roy> https://www.w3.org/WAI/APA/task-forces/pronunciation/track/actions/open
Irfan: Tentative timeline
created; will cover documentation requirements.
... Documentation to be created on GitHub
Steve: Those responsible with the documentation will collaborate
Irfan: We can work together with Roy on version control in GitHub
Steve: Understand the requirements; need the outline and requirements on how to proceed
Irfan: Summary from last meeting regarding the documentation will be posted to GitHub
<Zakim> janina, you wanted to discuss CSS Speech
Janina: Based on experience with collaborating on document versioning; there are several ways to do this and GitHub is well established to manage versions. Examples of other WC3 gap analysis will be provided.
Irfan: Roy has some examples
Janina: Would like a more finished version of a gap analysis
<JF> https://github.com/w3c/personalization-semantics
John: to add to Janina's comment about using GitHub as the primary place to work
Janina: GitHub has 'get a copy'
feature that may support individual contributions that can then
be pushed back to the repository
... Multiple ways to update documents, with GitHub
<janina> Linkname:[css-text] text-transform's design, intent and reality resolution M-7 Issue #3775 M-7 w3c/csswg-drafts M-7 GitHub URL:https://github.com/w3c/csswg-drafts/issues/3775
Janina: CSS speech issue from APA
group - text transform design
... There may be a 'turf war' with the the APA group because
CSS is trying to figure out if this is in scope for them
... Would like to head off any conflict with the CSS team; part
of the issue is not just what appears on screen but how it is
pronounced
... We need to address this conflict sooner than later
Irfan: Some scenarios to consider but this is a use case to be considered; not necessarily a CSS issue, in particular upper case, lower case and Capitalization
Mark: Is anyone in the CSS group considering this as part of their mission?
Janina: CSS has indicated that this is part of their historic remit; they have tackled this before but without any resolution
<Zakim> JF, you wanted to suggest an olive branch versus ...
Mark: some aspects can be addressed with the CSS model, but a more international model can be addressed by our efforts. AT vendor input may provide additional requirements which addresses the CCS model or others
Janina: will propose a joint
effort with APA working group and CSS task force
... CSS may be well suited for some pronunciation but the
pronunciation task force may have greater insight based on
diversity of end user groups; gap analysis will be very
critical ti support our efforts
<janina> Last week's APA discussion minuted at:
<janina> http://www.w3.org/2019/03/27-apa-minutes.html#item03
Paul: CSS annotation can be equally addressed
Irfan: to be further discussed during the APA call
Janina: Gap analysis will provide a greater response to CSS team
Irfan: Work to start on the documentation as posted in GitHub; Let's get startted
Zakin, next item
Irfan: Several issues created by
Paul in GitHub, see link previously provided. Suggest using a
common embedded format. Ruby element provides a tool for
phoneme, but need more details/specifications
... This information can be added to user scenarios
<Irfan> cl: Sam and Christine talked about different approach to start working on this
<Irfan> js: trying to think about some document that can be useful. they are HTML and not spreadsheet.
<Irfan> js: should start jus like text document..such as user stories
Janin: specifications are available, text documents are preferred as they will then be converted to HTML
<paul_grenier> markdown renders as html in github, so it's faster if the goal is eventually html
Janina: Roy can support any style/format requirements
<paul_grenier> markdown has tables as well
Sam: If template available, that would be helpful
Janina: Publishing user scenarios are a great template to use
<janina> Web Publications Use Cases and Requirements https://www.w3.org/TR/pwp-ucr/
<Sam> Thanks, Janina! :)
Mark: Markdown can include code snippets and table structures; tools in GitHub; renders in HTML
Janina: supports Markdown;
Mark: add the .md for rendering
<Irfan> https://guides.github.com/features/mastering-markdown/
Sam: progress on user stories,
taking two prong approach collecting expertise from our
organization and other organizations including Idaho Org for
the Blind, with interviews; including practitioners and experts
but also end users
... Collection of user stories will be curated and available
for input from the team; to add/edit/comment
... Opportunity to speak with other accessibility community for
additional input to support scenarios; consider submitting a
research proposal to garner greater awareness among various
sectors
Janina: Supports Sam's efforts to get this to a larger audience; NYC event in April about UX design; URL to be provided
<Sam> https://www.meetup.com/topics/ux-design/us/ny/new_york/
Irfan: Issue List- start with use cases; can be taken from issues. Additional template to be created to begin populating with use cases
<Sam> https://www.meetup.com/NYC-UX-User-Researchers-Meetup/events/260137141/
Janina: Use cases to be cross-referenced with gap analysis
Roy: will post use case template
Janina: Paul has created issues/tickets
Paul: Same use case with different implementations; to be tied to specs, requirements and gap analysis
Janina: Also need to include best practices
Irfan: Paul to work on use case documentation
Irfan: Draft document publication - timeline
Janina: distinction between published document and editor's draft that we need to be aware of; The drafts can start anytime.
Irfan: Tentative timeline to be drafted
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 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/Netherlands/New Zealand/ Succeeded: s/historic permit/historic remit/ Default Present: paul_grenier, Irfan, Roy, janina, Sam, SteveNoble, Christine, JF, Markku Present: paul_grenier Irfan Roy janina Sam SteveNoble Christine JF Markku Found Scribe: Christine Inferring ScribeNick: Christine Found Date: 03 Apr 2019 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. 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]