<LisaSeemanKest_> regrets, charles

<LisaSeemanKest_> scribe: Roy_

<LisaSeemanKest_> https://raw.githack.com/w3c/personalization-semantics/rewrite-introduction/content/index.html

<Roy> Lisa: Roy and I worked for introduction, terms and privacy section

<Roy> ... Janina had some feedback before this meeting

<Roy> ... I also added the vocabulary section

<Roy> ... some links are changed

<Roy> ... some links to wiki pages

<LisaSeemanKest_> https://github.com/w3c/personalization-semantics/wiki/Best-practices-for-symbol-values

<Roy> [discuss on symbol examples]

<JF> +1 to adding an example

<Roy> Lisa: I will add an example of plus symbol

<janina> +1

<becky> +1

<LisaSeemanKest_> ACTION: add hebrew eample and sentence to the spec

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

<becky> but also agree with John's point to put the explanations together

<Roy> Lisa: all people agree to add example

<Roy> ACTION: Lisa to add hebrew example and sentence to the spec

<trackbot> Created ACTION-59 - Add hebrew example and sentence to the spec [on Lisa Seeman-Kestenbaum - due 2020-06-08].

<Roy> JF: move the explanation sentence together with example instead of at top

<LisaSeemanKest_> https://raw.githack.com/w3c/personalization-semantics/rewrite-introduction/content/index.html#privacy-and-security-considerations

<Roy> Lisa: we also changed the section 4

<Roy> ... start with the link to issue

<LisaSeemanKest_> https://raw.githack.com/w3c/personalization-semantics/rewrite-introduction/content/index.html#terms

<Roy> ... also section 2 Terms, link to coga glossary document which is not finished yet

<Roy> JF: we need refer to a complete document when we want to publish as CR

<Roy> Janina: coga glossary should be in W3C format, not a google doc

<Roy> Lisa: it will be a problem, if the glossary rely on other group's work

<Roy> ... do we need include a terms here?

<Roy> JF: we can start to find specific terms in our doc

<Roy> ... instead of depends on coga work

<Roy> https://lists.w3.org/Archives/Public/public-personalization-tf/2020Jun/0003.html

<JF> +1 to importing *some* terms now, with Editorial note that a fuller glossary is being devel;oped by COGA TF

<LisaSeemanKest_> put the values in and add ed note " we inted to incorperte by refrence with the coga glossary, when it is ready. we do not anticipate any non editorial changes to the terms included above, if there are we will use our own term.

<LisaSeemanKest_> https://www.w3.org/TR/personalization-semantics-1.0/#propcharacteristic_value

<janina> 1 as approx

<LisaSeemanKest_> lost some informtive refrences

<Roy> JF: we need more informative references

<Roy> Lisa: I will add note to glossary section

<LisaSeemanKest_> ACTION: roy to put in informive links - missing aria, acag, coga, and they all external link

<trackbot> Created ACTION-60 - Put in informive links - missing aria, acag, coga, and they all external link [on Ruoxi Ran - due 2020-06-08].

<Roy> JF: I don't think we related with ARIA

<Roy> Lisa: I think we related with ARIA, if people don't want to include it, I could live with that

<JF> +1

<janina> +1 to only referenced items

<becky> +1

<sharon_> +1

next steps

do we care about speces with the plus sine 9options

<Roy> Janina: we could follow formatting with ARIA

<LisaSeemanKest_> who want a space

<JF> +1

<janina> 1 to space delimited plus signs

<LisaSeemanKest_> -1

<becky> neutral

<sharon_> neutral

<Roy> neutral

<Roy> Lisa: we haven't consensus on this

<JF> build on existing patterns

<becky> I+1

<LisaSeemanKest_> with ed note: user agent can accspt it with the space

janina's email

<Roy> Janina's email https://lists.w3.org/Archives/Public/public-personalization-tf/2020Jun/0003.html

<Roy> Janina: first we need mention who benefits from this specification in the Abstract

<Roy> ... second, we should use the same name for Module 1

<Roy> ... third, use the plain language

<Roy> Lisa: suggest Janina edit it directly in GitHub branch

<LisaSeemanKest_> https://github.com/w3c/personalization-semantics/tree/rewrite-introduction/content

<Roy> JF: "Adaptation of content", we have some definition in WCAG

<JF> The intent of this Success Criterion is to ensure that the purpose of a form input collecting information about the user can be programmatically determined, so that user agents can extract and present this purpose to users using different modalities. The ability to programmatically declare the specific kind of data expected in a particular field makes filling out forms easier, especially for people with cognitive disabilities.

<JF> https://www.w3.org/WAI/WCAG21/Understanding/identify-input-purpose.html

<Roy> Lisa: do we want to wait longer to let i18n and tag to review?

<Roy> JF: goal of this document is to CR

<Roy> Lisa: I will draft sentence to list to let i18n responses

<LisaSeemanKest_> action

<Roy> Lisa: Sharon will be co-facilitator for this TF

<Roy> https://www.w3.org/WAI/APA/task-forces/personalization/#facilitator

<Roy> scribe: Roy

This is scribe.perl Revision of Date 
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: JF 1

WARNING: Fewer than 3 people found for Present list!

Found Scribe: Roy_
Found Scribe: Roy
Inferring ScribeNick: Roy

WARNING: 1 scribe lines found (out of 126 total lines.)
Are you sure you specified a correct ScribeNick?

Scribes: Roy_, Roy

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

Found Date: 01 Jun 2020
People with action items: add eample hebrew lisa roy sentence

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