W3C

- DRAFT -

Personalization Task Force Teleconference

25 Mar 2019

Attendees

Present
present, janina, thaddeus, Becka11y, stevelee, LisaSeemanKestenbaum, MichaelC, CharlesL, Roy, JF, sharon, Lisa
Regrets
Chair
CharlesL
Scribe
becka11y

Contents


<thaddeus> +present

<scribe> scribe: becka11y

TPAC 2019 (Will there be enough TF members attending to warrant an in person meeting.)

<JF> I will NOT be there this year

<janina> I expect to be there

<LisaSeemanKestenbaum> hope to be there

<thaddeus> maybe

Charles: who will be at TPAC In September?

JF: no
... this is the area where Makoto was born

Becka11y: if I can get justification that will help the Knowbility fundraiser to get sponsor ship

Sharon: will not be able to go;

Charles: Lisa, Becky, Thaddeus are maybe; Charles and Janina are Yes; John and Sharron are not going

Janina: would have to meet Thursday, Friday to avoid weekend; hotel rate probably doesn’t kick in until Friday or Saturday so would have to take time during APA telecon for Personalization info; hope to have intergroup conversationss at TPAC; so need to put together demos and agenda topics

Lisa: if not a F2F it makes it less interesting / dersirabe to go; is there a “slow” day where we can meet during TPAC?

Janina: not likely since days are so full, especially for Janina and Charles
... probably easier / cheaper to organizae a F2F in North America since most member are there; would need to be before TPAC; need a solid agenda so we can focus
... not the week right before TPAC but at some point before

Charles: Web4all would have been an option but our paper didn’t get accepted

JF: the topic for Web4All is personalization

Janina: but our paper was declined

JF: are others going to be there? It might be a good place to have a F2F

Becka11y: Web4All is happening at the same time as Knowbility’s AccessU so I can’t go

JF: Web4All doesn’t completely overlap - AccessU starts on Wednesday

Charles: gut is TPAC won’t happen and probably not at Web4All for a personalization task force

Janina: we should have an hour to spend with Web Platforms

Charles: yes, agreed but don’t expect anyone to call in based on the time zone diff. to Japan

soliciting UA prototypes and example content for demonstrating.

charles: we want user agent prototypes and content examples
... need UA prototypes; perhaps buttons at the top of the page for different aspects, easylang, number free, etc; need proof of concept

Lisa: people here haven’t seen what we have working; it is linked in our pages but you have to install a plugin; should we have a separate call of demos to show people working examples

Charles: seems like a good idea so we can build off of those approaches

<stevelee> +1 for demos

+1

<sharon> +1

<Zakim> janina, you wanted to say it's definitely data-

<thaddeus> +1

Janina: Need to catch up on reading of HTML spec; is clear that it needs to be data- and if it gets picked up then will change to something else than data-. Seems we are reading the spec more strictly than others with our concerns over use of data-. Need to move beyond that. Agree to having demos; Need to work with a partner so we can use content that changes rather than canned demos
... the demos need to be persuasive to others and easy to understand; thus symbols should probably be our top target

Charles: yes, symbols and numberfree as well

Lisa: I think we can just move on with data- as I was the only one who did not endorse that in our last discussion

<JF> +1 to note that numbers-free demo may break layouts if the intent is to 'replace' numbers with text (suspect a better model is an onHover/onFocus tool-tip style popup with the text alternative there)

charles: hoping that with existing implementations we can just add code to parse aui to data dash.

Lisa: how long do we anticipate data dash being the way we do things? What do we tell implementors?

Janina: until we demonstrate viability in order to convince the browsers to implement additional attributes; need mainstream uptake; early implementors need to understand that we are using the accepted HTML approach to put our ideas forward;

JF: data dash attributes will validate with HTML; at TPAC Brian Kardell did mention that there is something else out there using aui - we have to be aware there is a potential conflict;

Lisa: so we have a CFC that data dash will be the implementation of choice until we become mainstream

Janina: not sure we need a CFC because using data dash (data-) is the standard HTML mechanism for extensions

Lisa: I think we need a CFC since in the past we agreed to use aui

Janina: don’t believe we need a full CFC

JF: I have concerns moving forward with aui until we know where the conflicts are; data dash I have no issues with

Charles: Do you agree to have a CFC to use data dash (data-) going forward because this is the correct approach for extending HTML as we build up mainstream support?

<LisaSeemanKestenbaum> +1

<stevelee> +1

<CharlesL> +1

<thaddeus> +1

<sharon> +1

<JF> +1 for data-dash

<janina> +1 to data-

<Roy> +1

+1

Charles: original agenda item was about UA prototypes and example content; let’s review what is existing and how we can expand that (and update to data dash)

Janina: I hope we can find someone with a larger reach that has updating content; need to look for those partners

Charles: and reaching out to existing partners
... can we get those folks to get on one of our calls and demo to us?

Lisa: some are testing custom content with people with cognitive difficulties; using some of the aria paradigms; W3C is involved - Shadi was putting together a list of web patterns for user experience
... am making a couple of test pages; the consoritum is looking towards other governments for funding an prototyping; Klaus and ICCAP are involved

Charles: would be great to get Shadi and Klaus on a future call;

Lisa: not all of their approaches will apply to this group

Charles: asks Lisa to arrange having Shadi and Klaus on a future call

review of Roy’s combination of https://raw.githack.com/w3c/personalization-semantics/rewrite-prototype/content/index.html#values for ease of understanding

Charles: is this table still the correct approach? This table with 3 columns; Roy was concerned that when completed it will be overly long

Chalres: consider repeating action/field on every row rather than as a section as it is; this will allow better sorting to find overlap

<Zakim> janina, you wanted to ask about sorting columns

Janina: how would we sort? We want to see similar ones grouped together to help users select the correct one

Stevelee: thinking that action/field/destination are sections and there are crosslinks between the items

Charles: click on attributes and get all the values like we see now, and then click on the values and see that there may be more than one add, for example - so you notice that add may be used in more than one instance/example

stevelee: how often do we have that overlap?

Charles: Lisa mentioned that developers often use the wrong value - they may not realize it could be used with destination and that was a better use than field
... I think having 3 columns is fine if you can sort on attribute and value
... can we have a sortable document?

Michael: that will require script and that is not encouraged for TR documents

<Roy> https://www.w3.org/TR/

Roy: I can try to make this a sortable document; and we can see if we can use this in Technical Report or not

Charles: any last minute items?

<thaddeus> thanks

<CharlesL> trackbot, end meeting

Summary of Action Items

Summary of Resolutions

[End of minutes]

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

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/TPAC Brian C./TPAC Brian Kardell/
Succeeded: s/destination and/destination and that/
Succeeded: s/CR/TR/
Default Present: present, janina, thaddeus, Becka11y, stevelee, LisaSeemanKestenbaum, MichaelC, CharlesL, Roy, JF, sharon
Present: present janina thaddeus Becka11y stevelee LisaSeemanKestenbaum MichaelC CharlesL Roy JF sharon Lisa
Found Scribe: becka11y
Inferring ScribeNick: Becka11y
Found Date: 25 Mar 2019
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


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]