W3C

- DRAFT -

Personalization Task Force Teleconference

11 Mar 2019

Attendees

Present
CharlesL, LisaSeemanKestenbaum, Roy, janina, shawn, thaddeus
Regrets
Chair
SV_MEETING_CHAIR
Scribe
janina, Jannina

Contents


<thaddeus> +present

<LisaSeemanKestenbaum> trackbot, start meeting

<trackbot> Meeting: Personalization Task Force Teleconference

<trackbot> Date: 11 March 2019

<janina> scribe: janina

<LisaSeemanKestenbaum> scribe: Jannina

review of the W3C’s webpage for ‘Personalization Overview’

<Roy> https://deploy-preview-2--wai-personalization-standards.netlify.com/standards-guidelines/personalization/

<janina> sh: Hoping to post this week, preferably even today.

<janina> sh: We can still make changes even after posting.

<janina> sh: Also want to post COGA.

<Roy> https://deploy-preview-2--wai-personalization-standards.netlify.com/standards-guidelines/personalization/

<thaddeus> i on hold on the call for 10 mins

<janina> ls: Wanting a pointer, or section of Use Cases ...

<janina> ls: 1 or 2 examples, link to wiki pages where it's being developed

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

<LisaSeemanKestenbaum> https://github.com/w3c/personalization-semantics/wiki/Use-cases

<LisaSeemanKestenbaum> https://github.com/w3c/personalization-semantics/wiki/Use-cases#severe-language-impairment

<shawn> +1 for adding brief bit in overview page and (probably) link to more

<janina> ls: Most concerned we point to augumented communication symbol users, and also to users who get lost/confused with on screen overload

<janina> ls: Notes that data overload is also a continuum in its effects, from troublesome to total show-stoppers

<LisaSeemanKestenbaum> https://github.com/w3c/personalization-semantics/wiki/Getting-started-with-personalization-semantics

<LisaSeemanKestenbaum> https://deploy-preview-2--wai-personalization-standards.netlify.com/standards-guidelines/personalization/

<thaddeus> im back

<LisaSeemanKestenbaum> https://deploy-preview-2--wai-personalization-standards.netlify.com/standards-guidelines/personalization/#who-personalization-documents-are-for

<janina> ls: Other comments?

<janina> ls: Anyone disagree to posting?

<janina> [crickets]

<janina> cl: We could use this!

<janina> Roy: SH agree to work out the mechanics

Next Meeting on March 18’th (after CSUN)

<janina> cl: Asks who is available? I will be unavailable.

<janina> I'm available

<Roy> I am not available for March 18

<janina> ls: Suggesting asking the list, looks like only 3 so far

review of Roy’s combination of Attribute/Value/Description into one table for ease of understanding

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

<janina> cl: Notes this isn't yet complete, but it's far enough along for us to determine whether the approach works

<janina> js: Find it easy to follow

<thaddeus> field is misspelled

<janina> cl: What about disjunct but related items?

<janina> ls: Depends on how we implement?

<janina> js: Suggesting cross-hyperlinks for related concepts that are disjunct in the presentation

<janina> ls: Perhaps in the description?

<LisaSeemanKestenbaum> 1

<LisaSeemanKestenbaum> +1

<thaddeus> +1

<janina> +1

<janina> roy: Notes it will be a huge table

<janina> cl; Can we make it a sortable table?

<janina> roy: Seeks clarification

<janina> cl: Sort by column

<janina> ls: Agrees that huge table may be a problem

<janina> ls: What about collapsable, accordian structure?

<janina> cl: Perhaps using html details for the description instead of the separate column

<janina> ls: Likes seeing first line of the description and then expand it

<janina> ls: Concerned that people would jump to improper conclusions about what is meant

<janina> cl; Much more work

<janina> roy: Don't think it's description that's bulking up the table, it's the value

<janina> ls: Think our problem is people seeing a term and using it in the wrong place based on what they assume

<janina> js: Likes sorting by column, but our problem remains too much bulk

<janina> cl: what about hiding description? Do we know such a design pattern?

<janina> roy: A button

<janina> cl: to hide/show description column

<janina> [head scratching]

<janina> ls: Could be good

<janina> cl: May solve the problem

Look through the prototyping with data- examples

<thaddeus> sorry i need to drop off - thad

<CharlesL> https://github.com/w3c/personalization-semantics/wiki/Protoypes-with-data-dash

<LisaSeemanKestenbaum> https://github.com/w3c/personalization-semantics/wiki/Protoypes-with-data-dash

<LisaSeemanKestenbaum> <span data-alternative-numberfree="most">92%</span>

<LisaSeemanKestenbaum> <h1 data-alternative-easylang="form to ask for money if you have a disability or if you are ill">Disability claims under CD 356 / US </h1>

<LisaSeemanKestenbaum> <span data-numberfree="most">92%</span>

<janina> ls: Meaning labels for the field -- longer and more semantic? Or short anc easier to type

<LisaSeemanKestenbaum> <h1 data-alt-easylang="form to ask for money if you have a disability or if you are ill">Disability claims under CD 356 / US </h1>

<janina> cl: So cleaner communication with developers, but doesn't disambiguiate the payload

<janina> cl: Field naming first?

<janina> ls: Thinks so

<janina> cl: Prefer to do the easy stuff first, the text based things

<janina> +1 to cl

<Roy> +1 to cl

<janina> cl: Like alt-[...]

<janina> cl: Notes the problem of multiple options after the second dash

<janina> ls: We don't have an easy way to do otherwise

<CharlesL> Nice suggestion Janina data-alt-… :)

<janina> cl: Other than numbers-free and alt, are there others?

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/11 15:04:49 $

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)

Default Present: CharlesL, janina, stevelee, Becka11y, Roy, LisaSeemanKestenbaum, sharon, present, thaddeus, JF, MichaelC, shawn
Present: CharlesL LisaSeemanKestenbaum Roy janina shawn thaddeus
Found Scribe: janina
Found Scribe: Jannina

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

Scribes: janina, Jannina

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

Found Date: 11 Mar 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]