<LisaSeemanKest> scribe: Roy_

internationalization issues

update: explainer and requirments drafts

<Roy> scribe: Roy

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/wiki/Requirements-(draft)

Lisa: I asked Michael to help review the Requirement
... also for TAG explainer
... we also need to ask Ralph to see if we need more to do
... it's not urgent
... Michael put few changes on explainer
... I removed the stakerholder section
... we really don't want another round for tag review, I wrote to Alice offline
... I have coordinated a draft for Alice email with Janina and Michael

<JF> URL of current draft?

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/wiki/restructure-of-the-explainer

<janina> +1 to speak to some nits on the explainer

<LisaSeemanKest> +1 to john if alice asks for a new order or changes we do it

<janina> -1 to preapproving Alice

Lisa: if Alice ask some minor changes, should I just do it

<JF> If Alice believes that re-ordering content is important, then +1 to re-ordering.

Lisa: Coga doc will go to Wide Review, we should do our work
... hope glossary doc will be prepared in two week

<JF> AAC Definition: https://en.wikipedia.org/wiki/Augmentative_and_alternative_communication

Lisa: I will add sentence to explain the operators

Janina: user agent is questioning
... we should not use the words "prefer"

Lisa: changed

<LisaSeemanKest> ACTION: janina to identify words that need more info

<trackbot> Created ACTION-54 - Identify words that need more info [on Janina Sajka - due 2020-05-04].

Charles: there is old "aui-" prefix, should be changed
... we don't have link for EA

JF: that's a person, we could ask a link from her

Lisa: I will do

JF: why we point out UNICEF?

Lisa: they gave funding to coga related people, and have some join meeting

JF: we should make sure patent policy, we didn't have any interactive with them
... prefer move EA to appendix A.2
... only keep Blissymbolics Communication International and Coga in References & acknowledgements section

Lisa: agree

Janina: agree

Lisa: ok with explainer, wait for Alice's feedback

internationalization issues

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/issues

Lisa: there are i18n issues in GitHub

Becky: I will do it in 3 weeks

<LisaSeemanKest> #146, -

JF: I may take one issue, issue number?

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/issues?q=is%3Aissue+is%3Aopen+label%3Ai18n-needs-resolution

Lisa: should we try do them on the call

JF: I'd like to take some of them

<LisaSeemanKest> ACTION: john to try and take on the internationalization issues https://github.com/w3c/personalization-semantics/issues?q=is%3Aissue+is%3Aopen+label%3Ai18n-needs-resolution

<trackbot> Created ACTION-55 - Try and take on the internationalization issues https://github.com/w3c/personalization-semantics/issues?q=is%3aissue+is%3aopen+label%3ai18n-needs-resolution [on John Foliot - due 2020-05-04].

Lisa: can you try to finish next Sunday

JF: try my best

issues from coga

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/issues/149

Lisa: issue from coga

<LisaSeemanKest> the definition of critical should include a bullet point

<LisaSeemanKest> " controls necessary to continue a multi step process"

Lisa: can we add this to definition?

<LisaSeemanKest> data-spicifilation = "criticle"

Michael: we already have a related attribute in ARIA, we don't need duplicates

<LisaSeemanKest> Description

<LisaSeemanKest> critical The critical setting should be used on:

<LisaSeemanKest> Controls and content that are essential for the key function (from the user perspective) of the page. Example: The send button for an email draft in an email application.

<LisaSeemanKest> Controls and content that are sometimes critical to use the site, such as "save my work" or "emergency instructions".

<LisaSeemanKest> Controls and content that are used by over 90% of a user group (such as parents or teachers) most times they interact with the content.

JF: we already have that to support

<LisaSeemanKest> data-spicifilation = "criticle"

<LisaSeemanKest> Controls and content that are necessary to continue a multi step process"

<JF> and if it is critical for COGA users, it's likely critical for ALL users

Becky: it has already covered when you control pages

<LisaSeemanKest> who feels it is included :

<LisaSeemanKest> john feels it incldeds the usecase, Becky seas it is included

<LisaSeemanKest> +1

<JF> +1 to

<becky> +1

<JF> The Task Force believes we've already covered this use-case"

<CharlesL> +1

<janina> +1

<LisaSeemanKest> +1 to closing the issue with the comment it is included in exsisting def

<janina> +1

RESOLUTION: The Task Force believes we've already covered this use-case", close this issue

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/issues/147

<LisaSeemanKest> distressing: Content that may distress some users such as content with a violent, graphic or non-consensual sexual aspect.

JF: it is a real problem, I don't think we could use data-distraction="distressing", we could tag it

Lisa: very important use case is noice, people can't afford sudden noice or flash out
... separation different things
... it's a option to going to another module

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/I wrote Alice offline/I will write to Alice offline/
Succeeded: s/I will write to Alice offline/I wrote to Alice offline/
Present: becky CharlesL JF
Found Scribe: Roy_
Found Scribe: Roy
Inferring ScribeNick: Roy
Scribes: Roy_, Roy

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 27 Apr 2020
People with action items: janina john

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