W3C

- DRAFT -

Personalization Task Force Teleconference

10 Jun 2019

Attendees

Present
Thaddeus, LisaSeemanKest, Roy, Becka11y, CharlesL, janina, MichaelC
Regrets
Chair
SV_MEETING_CHAIR
Scribe
roy

Contents


<Thaddeus> +present

<LisaSeemanKest> scribe: roy

List of pages at https://github.com/w3c/personalization-semantics/wiki

lisa: request from John, I made a list of pages where different docs are.
... also some useful pages
... and pages where we explored the idea.

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

lisa: would like to have everyone to review it, and tell me what missing in this wiki?

https://github.com/w3c/personalization-semantics/wiki

Missing items on autocomplete (see Charles email)

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

lisa: Charles sent the email about the missing items on autocomplete
... do we want to have them all?

<JF> https://www.w3.org/TR/WCAG21/#input-purposes

<CharlesL> I agree with John we should harmonize with auto-complete

JF: SC in 2.1, all of thing are included by 2.1, we should harmonize them.

Janina: if we have new item, we could add them in future.

Becky: we need support the same one.
... maybe link back to them

<JF> https://www.w3.org/WAI/GL/wiki/WCAG_2.1_Implementations/JF/research

JF: show a table about platform support for autocomplete

becky: impp is the thing we should talk about.
... do we want include or not?

JF: we had it in WCAG 2.1

Lisa: feel that's a issue for credit card

JF: https could figure out that.

Lisa: any objections?

<JF> Test Page: http://john.foliot.ca/demos/autofill.html

RESOLUTION: include the autocomplete that is missing

prototyping

Lisa: brief update the prototype, we have agreed first three attributes use the data-

<LisaSeemanKest> https://w3c.github.io/personalization-semantics/content/index.html

Lisa: to put it for a wide review
... what we doing now is for value set
... we will try to resolve the symbol

JF: for module 1, first three we have decided, but others we are not decided, so not a good time to wide review.

lisa: first 3 attributes would not be changed
... thaddeus, you could prototype first 3 attributes or symbol in future.

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/wiki/Options-for-symbol

Thaddeus: OK

Missing items on autocomplete (see Charles email)

continue going though list

<LisaSeemanKest> https://raw.githack.com/w3c/personalization-semantics/rewrite-prototype/content/index.html#values

lisa: going through the first 3 attributes values
... the definition for autocomplete
... I don't see any comments except Charles' email
... we sort by value, we will see what similar
... don't worry about the same value for distraction

JF: we need chang to -
... we need update the table

Lisa: destination and purpose

JF: also city in autocomplete , we could add it

becky: some countries don't use the states

JF: in autocomplete have 4 levels, we could use the city=address-level3 or something, they are samething

<Zakim> janina, you wanted to stay with localization practice

janina: i18n WG could review it and help for that
... JF have a good point for UK etc, if we do something legal, we need localization.

Lisa: @@

JF: it's different from address line with address level

<JF> Street Address Address: Line 1 Address: Line 2 Address: Line 3 Address: Line 4 Address: Level 1 Address: Level 2 Address: Level 3

JF: we create new attributes we could add thing, i18n also the idea.

Janina: we should think more about localization

<LisaSeemanKest> straw poll for having city and address-level-3

<LisaSeemanKest> -1 just adress-level 2

<JF> 0

<Becka11y> 0

<Thaddeus> 0

<CharlesL> 0

<janina> +0

Lisa: leave it to next issue
... "comment" both in purpose and destination

JF: when you submit the comment, that's an action

Becky: could we rename as feedback?

<LisaSeemanKest> resolution destination comment change to discusion

<LisaSeemanKest> +1

<JF> +1 if/when we have a better definitions

<Becka11y> +1 with update of definition as well

<Thaddeus> +1

Lisa: "email" both in purpose and destination

<JF> Proposal = Destination: Discussion (A regions or section of the page where the user can leave a comment or review prior comments)

Lisa: suggest user's email address in purpose
... it will be a link
... mailto?

JF: the destination email is the recipient

Lisa: it is the content owner

<JF> Destination: Recipient (Either a fixed list of terms, or open to a text string)

<Thaddeus> needs work i think

JF: recipient-owner something like that

<JF> a>/<a href="mailto:person@site.com" destination=+receipient">Lisa</a>/a>

Becky: would like to use email-recipient

<Thaddeus> needs work

<JF> <a href="mailto:person@site.com" destination=+receipient">Lisa</a>

<JF> <a href="mailto:person@site.com" destination="receipient">Lisa</a>

<JF> <a href="mailto:person@site.com" destination=+receipient">person@site.com</a>

<LisaSeemanKest> <a href="mailto:person@site.com" destination="email-receipient">Lisa</a>

Lisa: this is the proposal, we will keep discussion.

<Thaddeus> thank you

Summary of Action Items

Summary of Resolutions

  1. include the autocomplete that is missing
[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/06/10 15:06:12 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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/< href="mailto:___" destination+"receipient">Lisa</a>/<a href="mailto:person@site.com" destination=+receipient">Lisa</a>/
Present: Thaddeus LisaSeemanKest Roy Becka11y CharlesL janina MichaelC
Found Scribe: roy
Inferring ScribeNick: Roy

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

Found Date: 10 Jun 2019
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.)


[End of scribe.perl diagnostic output]