<LisaSeemanKest> clear agenda

<LisaSeemanKest> regrets, becky, sharon

<LisaSeemanKest> scribe: roy

<LisaSeemanKest> no quarum

<LisaSeemanKest> next item

<LisaSeemanKest> clear q

tpac (and i may need to step outside for 5 minuets

Lisa: who we want to meet there in TPAC
... there should be a virtual meeting
... maybe i18n

<LisaSeemanKest> tpac: intelationlization, html, wisiwig editors / authing tools

JF: 3 or 4 people who work on authoring tools,

Lisa: WCAG and Coga also need meet
... for coga, talk about what they need
... brainstorm what we could do

Janina: I don't expect much brainstorm
... Low version is fine

<LisaSeemanKest> and ui/ wot

Janina: we need specific agenda

Lisa: WCAG and Coga know what we do, we could do a short demo to AG, and to see what they think about

JF: we could do person to person talk

Lisa: we had a success demo in last TPAC

JF: I don't think schedule a call with AG or Coga is necessary
... time limited in TPAC
... we know each other

Lisa: two items, besides demo we also need coordinate with Wot

<JF> CSS WG - there's a whole bunch of personalization possibilities there

<JF> The already have "prefers-reduced-motion"

Janina: we can take with WoT when we define any a11y API

JF: if we agree with CSS WG, we should start think about issue related with them

Lisa: we could set a meeting to talk about this

<LisaSeemanKest> https://www.w3.org/TR/personalization-semantics-content-1.0/#

Lisa: the introduction is too short to be a respec
... what do people think for the introduction

<LisaSeemanKest> This document provides personalization semantics and vocabularies that can be used to annotate web content enabling user agents to augment or adapt content to various user scenarios based on the user’s personalization settings or preferences.

Charles: yes, we need more
... pointing to explainer
... adaptation, we'd better to refer other doc introduction

Janina: we have two explainer, one for general, one for tag

Lisa: introduction is important for standalone doc as Module 1 will push as rec

<LisaSeemanKest> ACTION: janina to look at induction in module 1

<trackbot> Created ACTION-57 - Look at induction in module 1 [on Janina Sajka - due 2020-05-25].

Janina: will think about introduction, but next week will be holiday in US

<LisaSeemanKest> https://lists.w3.org/Archives/Public/public-personalization-tf/2020May/0014.html

Lisa: JF wrote useful email in mailing list about data-symbol

<LisaSeemanKest> https://lists.w3.org/Archives/Public/public-personalization-tf/2020May/0009.html

Lisa: we had some discussion in tf meeting

<LisaSeemanKest> In some languages words and symbols are conjugated with sex or tense. In these case more then one value maybe need to map to a symbol (such as "you + female"). Authors must put values that may map to a single symbol in the same attribute with the subject as the first reference. "

<LisaSeemanKest> Other instructions we could include are:

<LisaSeemanKest> "Authors should join values that map to a single conjugated word with a \+\ sign"

<LisaSeemanKest> We could also add an example of a word with grammar or conjugation.

<LisaSeemanKest> We should add to the explainer that our use cases is to map between symbol sets in the same natural language. We are not enabling consistent translation for different symbol sets across different natural languages.

<LisaSeemanKest> Authors should join values that map to a single conjugated word with a \+\ sign

<LisaSeemanKest> (to the main specification

Janina: we'd better coordinate with i18n

Lisa: let's point It out to i18n

<LisaSeemanKest> janina: absolutly

<LisaSeemanKest> In some languages words and symbols are conjugated with sex or tense. In these case more then one value maybe need to map to a symbol (such as "you + female"). Authors must put values that may map to a single symbol in the same attribute with the subject as the first reference.

Charles: with examples

<LisaSeemanKest> +1

<LisaSeemanKest> Jnaina+1

<CharlesL> +1

<LisaSeemanKest> Authors should join values that map to a single conjugated word with a \+\ sign

<CharlesL> agreed, not "MUST" too restrictive.

JF: little worried, about grammar

<LisaSeemanKest> John is comftable with the word should

<LisaSeemanKest> and look at the long index first

JF: "must" looks too restrictive

<LisaSeemanKest> and link to the wiki page on best practices

<LisaSeemanKest> ACTION: put that in the spec

<trackbot> Error finding 'put'. You can review and register nicknames at <https://www.w3.org/WAI/APA/task-forces/personalization/track/users>.

<scribe> ACTION: Lisa to link to the wiki page on best practices to spec

<trackbot> Created ACTION-58 - Link to the wiki page on best practices to spec [on Lisa Seeman-Kestenbaum - due 2020-05-25].

what else do we need for CR

Lisa: we need add extra content for introduction, more example, anything else?

Charles: just make sure Michael and Judy on this board

Lisa: I will update the spec
... besides get feedback from i18n and tag, what else response should be wait?

Janina: we need clear for PR instead of CR

drfat of answers for issues

Lisa: no issues

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/must/much/
Succeeded: s/ARIA/WCAG/
Succeeded: s/date-symbol/data-symbol/
Present: JF janina CharlesL
Found Scribe: roy
Inferring ScribeNick: Roy

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

Found Date: 18 May 2020
People with action items: janina lisa put

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