<scribe> scribe: Sharon

<janina> chair: charles

Review the changes to the Explainer that were recently added

Charles: Lisa asked the APA for formal approval.

Janina: Asked for it to be resent.
... Editorial changes are no problem. No substantial changes.

<Roy> https://raw.githack.com/w3c/personalization-semantics/master/explainer.html

<CharlesL> While the intention of this work is to introduce a new set of attributes to support Personalization, the following work items are out of scope:

<CharlesL> • Develop an API for browsers or other user-agents

<CharlesL> • Develop or produce supporting technology (browser extension, stand-alone software, etc.)

<CharlesL> • Develop or produce an authoring tool to support the new attributes

<CharlesL> • Produce a symbol set for data-symbol

Lisa: We should add a sentence that we encourage the development of these items and implementations can be found on the wiki.

<LisaSeemanKest> maybe add : We encourage a the development of these items and a list of implementations can be found on our wiki.

Charles: We have a new section for stakeholders. Any issues with that?

<CharlesL> 5. Stakeholders

<CharlesL> This document is useful for:

<CharlesL> • Content creators who want to be as usable as possible for as many people as possible, including people with learning and cognitive disabilities, and AAC users

<CharlesL> • Content creators who want to create adaptable content that meets the users preferred experience

<CharlesL> • Technology developers and providers who want to build technologies that enable more people to use the web effectively

<CharlesL> • Developers of symbol languages and related technologies

<CharlesL> • Students who wish to make a new software project for that meets a real need

<CharlesL> • Policy makers who want to know what is possible for inclusion

<CharlesL> For early implementations of content we suggest including a link to an https://github.com/w3c/personalization-semantics/wiki/Implementations-of-Semantics that can maximize the benefit for users.

<JF> Can we make a small editorial change? "...including people with learning & cognitive disabilities, and AAC users."

JF: First sentence needs editorial changes.

Charles: Call out mapping in the fourth bullet.

Lisa: If someone is making an extension, they should make a template or persona for their language.

<JF> Bullet 5: Students who wish to develop a new software project that meets a real need

<Becka11y> Content creators who want to accommodate all users, including people with learning & cognitive disabilities and AAC users.

<Becka11y> Content creators who want to accommodate as many users as possible, including people with learning & cognitive disabilities and AAC users.

Janina: Is AAC in terms section?

<Zakim> janina, you wanted to ask a few clarifying questions on the wide-review publication request

Janina: This is not a first public working draft. Draft is need for CR. Needs help with a blurb for publication.
... Standard with a publication for wide review. Why it matters and what they need to look at. We have time but need blurb for press release.

<JF> Content creators who want to accommodate as many users as possible, including people with learning & cognitive disabilities, and AAC users. [Oxford comma]

JF: Prefers Becky's second sentence. Prefer we include the comma.

<CharlesL> Policy makers who want to know what is possible for inclusion

Becky: Change the word know to understand.

<CharlesL> Content creators who want to accommodate as many users as possible, including AAC users,and people with learning &amp; cognitive disabilities.

<janina> brb

<CharlesL> https://raw.githack.com/w3c/personalization-semantics/master/explainer.html

Charles: Personalization semantics required not found. I think we need an AAC reference.

Review the changes to the Requirements document that were recently added (User Stories/Use-cases)

<CharlesL> https://raw.githack.com/w3c/personalization-semantics/master/requirements/

Charles: We have stories and use cases pulled in to requirements document.

<LisaSeemanKest> https://raw.githack.com/w3c/personalization-semantics/master/explainer.html#informative-references

<LisaSeemanKest> missing link

Charles: Asked Roy to fix reference in explainer so it links to the requirements document.

<LisaSeemanKest> thanks roy

Charles: Roy can you address broken links.
... Sections got messed up and Adding Content should be its own section.

Becky: Need to review and add the technologies we didn't pick to the explainer.

<Becka11y> https://github.com/w3c/personalization-semantics/wiki/Comparison-of-ways-to-use-vocabulary-in-content

Lisa: The explainer there is a section we discuss it already and then we link to the wiki for more. It might be enough.
... In section 4. Vocabulary Implementations has a paragraph.

Becky: An appendix or reference document we would put this in. Needs to understand how much detail.

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/wiki/Comparison-of-ways-to-use-vocabulary-in-content#overall-summary

Lisa: At the end of the document there is an overall summary, if you add data- and then have a sentence to link to the discussion.

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/wiki/Comparison-of-ways-to-use-vocabulary-in-content#-data-set-data--or-data-aui--attributes

JF: data- not included in the top of the documents under options.

Lisa: Its included as data sets. It needs to be changed to data-.
... Suggesting we complete the summary table and add an introductory paragraph.

Charles: How much work does Becky need to do, to get all of this out of a wiki and into a stable reference document?

Becky: Taking the feature list and try to paraphrase. We have to explain each of these things.

Lisa: Put a note at the top of the wiki to not delete the page.
... Include options and main considerations we looked at.

Blurb for APA Wide Review as a RC

<LisaSeemanKest> we aim to make content adaptble for groups who currently are on the wrong side of the digital deivide - Including people with cognative &learning disabilites.

<LisaSeemanKest> Further this change the user expence, alowing more user controled personlization.

<LisaSeemanKest> We have tried to incoperate feedback from other working groups and would apriate feedback

<LisaSeemanKest> We espiecial request feedback from groups involved in acc symbols, accessibility and inclusion so we can optmise the technolgy for their senarios

<LisaSeemanKest> we aim to make content adaptble for groups who currently stuggling to use the Web - Including people with cognative &learning disabilites

<JF> we aim to make content adaptble for groups who currently require alternative modalities in accessing the web

<janina> who function more effectively when content is presented to them in alternative modalities

<JF> we aim to make content adaptable for users who function more effectively when content is presented to them in alternative modalities - including people with cognative & learning disabilites.

Janina: Pin for future discussion related to a technology this group should hear about. Have a conversation with Josh and Jason so we can come up to speed.

<JF> We have incorporated earlier feedback from other working groups in this activity. We request continued feedback from groups involved in ACC symbols, accessibility and inclusion so we can optmise the technolgy for their senarios.

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)

Present: CharlesL janina LisaSeemanKest Sharon JF stevelee_ Becka11y
Found Scribe: Sharon
Inferring ScribeNick: Sharon
Found Date: 13 Jan 2020
People with action items: 

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.)