<CharlesL> scribe: sharon
<CharlesL> Web4All Conference
<CharlesL> http://www.w4a.info/2019/
<CharlesL> January 27, 2019 – submissions due
<CharlesL> http://www.w4a.info/2019/submissions/technical-papers/
CharlesL: Paper needs to be ACM
style, and there is a document you can use to get the format
before its submitted.
... Also includes examples from prior years available as
downloads.
Charles: Web4All conference is in San Francisco in May. Focus on the conference is Personalization. They have had w3 talks if it is relevant to the discussion. Deadline is the end of January. One paper explaining what we are doing. Talk about the use case. During code sprint we can code up examples. Also create some implementations.
Lisa: Should we propose a
panel?
... Maybe come at it with a different angle.
Janina: Could be worth pursuing.
<Thaddeus> +present
CharlesL: Charles could chair,
Lisa could look at the cognitive side. Talk about what we are
doing, etc.
... Who wants to be a part of this. Not sure what it means when
its excepted. Are you automatically part of the agenda...
... Benetech is also getting involved in code sprints for the
hackathon.
<janina> peresent+
CharlesL: Sending out an email to ask who is interested.
CharlesL ACTION: figure out what is needed for the paper.
<scribe> ACTION: CharlesL fing out what is needed for web4all paper
<trackbot> Error finding 'CharlesL'. You can review and register nicknames at <https://www.w3.org/WAI/APA/task-forces/personalization/track/users>.
<Roy> trackbot, status?
<scribe> ACTION: Charles find out what is needed for Web4All paper.
<trackbot> Created ACTION-2 - Find out what is needed for web4all paper. [on Charles LaPierre - due 2018-12-24].
<Roy> https://www.w3.org/WAI/APA/task-forces/personalization/track/users
<CharlesL> ACTION: close item1
<trackbot> Error finding 'close'. You can review and register nicknames at <https://www.w3.org/WAI/APA/task-forces/personalization/track/users>.
<CharlesL> close action item 1
<Roy> Close action-1
<trackbot> Closed action-1.
<Roy> https://www.w3.org/WAI/APA/task-forces/personalization/track/actions/open
CharlesL: At TPAC we saw Web
Platforms who asked us to come up with a vocabulary list of
terms and the meaning. Roy copied vocabulary from all modules.
We want to send it to Web Platforms at the beginning of January
so they understand our needs. Then ask for a follow up meeting
to discuss implementation.
... Looking at the value list, there is token and actions. So
these should not be numbered? 1.1 mapped to 2.1. Does everyone
understand?
... Will this confuse anyone?
Becka11y: It does put a lot of levels.
CharlesL: What if we don't have
the value list numbered?
... Having these as numbered makes it a bit too much.
Beckya11y: Thinks its valuable to have the list.
CharlesL: Get rid of 1 altogether and go into details of categories that link down.
<janina> FYI: Our TPAC meeting with Web Platforms is logged here:
<janina> https://www.w3.org/2018/10/22-WebPlat-minutes.html#item06
CharlesL: Take a look at this document and see if it all makes sense. If we show or current thinking of how this is written up they might be bias in offering suggestions. Just give them the list of values without examples.
Steve: Where did the prefix come from?
CharlesL: aui was used for accessible user interface.
Lisa: Original it changed to ARIA, then AUI. We have some other suggestions.
Steve: Do we need a paragraph to
set a context?
... Then say examples are just one possible way to implement
it.
<Zakim> MichaelC, you wanted to say shouldn´t be formatted as TR doc and to say shouldn´t replicate info we´re saying elsewhere, except the terms
Lisa: There will be changes depending on implementation. If there is one attribute some things may become redundant. Another thing that will change is the terms. The terms will need to be longer so they are not ambiguous.
<janina> +1 to Michael.
Michael: We should keep this very focused. This is just a look up list of the modules.
<Lisa> +1 but add that to the introduction :)
CharlesL: In text section, in step indicator usage it is out of order.
Roy: Every section is this way.
He pointed to this section since. Need to figure out how to
divide it into 3 sections. We only have a little information
for this part.
... Not sure which part to implement.
CharlesL: step indicator could be
a uri, token or text.
... Where should these be?
Lisa: It is only a working draft and it has these 3 things, but the link is to step indicator that has multiple attributes.
<Roy> https://w3c.github.io/personalization-semantics/tools/index.html#all-stepindicator-explanation
Lisa: Step indicators show properties, in one section which is fine for an early working draft where we are experimenting with an idea. When we link to it we link to status, location... Maybe the link text should be different so its clear what we are looking for.
CharlesL: Everyone clear?
Anything we can do differently?
... Anyone have an opinion on if we should keep the
examples?
MichaelC: Leans toward simplicity and the examples add to much.
CharlesL: Should we have links?
MichaelC: We definitely should have links to the spec.
CharlesL: Just links to the main
item.
... Remove examples from this document and link to the
appropriate spec. Anyone disagree?
... This document is a summary where you can see it from all
specs.
MichaelC: Sees section 2 as valuable. Section 1 in each item rather then a bullet list do a paragraph or have sub items. Terms and allowed values: and have the ability to skim what the values are.
<MichaelC> <link to vocab>action</link to vocab>: add, brightness, buy, etc.
CharlesL: Thinking that the list of values... would be right at the top as a sublist under action without the definitions, just the name?
<MichaelC> <link to vocab>action</link to vocab>: 1-sentence definition
<MichaelC> values: add, brightness, buy, etc.
MichaelC: Suggest going with just a definition of the term in a single section.
CharlesL: It would make this a lot compact. I'm fine with that. Lisa what do you think?
Lisa: sounds good
<scribe> ACTION: Roy to reorganize the vocabulary list to create one line description of each topic and associated list of values without definitions.
<trackbot> Created ACTION-3 - Reorganize the vocabulary list to create one line description of each topic and associated list of values without definitions. [on Ruoxi Ran - due 2018-12-24].
CharlesL: Includes linking to the
specs.
... We need to simplify our use cases. Try to come up with
stories that show multiple uri or tokens. Lisa had one example
for a user with Dyscalia and Dislexia. We need more of these
stories with out code.
... Does everyone agree with that concept?
Janina: The Dyscalia and Dyslexia
example is a good example of the problem that is difficult to
show in code. This is fundamental to standards
development.
... Out of that we gather our requirements.
CharlesL: Would like everyone to think about use cases at that level without the coding. Is that something everyone can think about over the holidays?
Janina: Replacing symbols for text need stories for that at as well.
CharlesL: Next year is to get one of the modules to recommendation. Hopeful we can move that forward.
<CharlesL> trackbot, end meeting
<trackbot> Meeting: Personalization Task Force Teleconference
<trackbot> Meeting: Personalization Task Force Teleconference
<trackbot> Date: 17 December 2018
<CharlesL> trackbot, endmeeting
<trackbot> Sorry, CharlesL, I don't understand 'trackbot, endmeeting'. Please refer to <http://www.w3.org/2005/06/tracker/irc> for help.
<CharlesL> trackbot, end meeting
<trackbot> Meeting: Personalization Task Force Teleconference
<trackbot> Date: 17 December 2018
<CharlesL> trackbot, end meeting
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) WARNING: Replacing list of attendees. Old list: stevelee Lisa CharlesL Becka11y Roy present Thaddeus MichaelC New list: (no_one) Default Present: (no_one) Present: stevelee Lisa CharlesL Becka11y Roy present Thaddeus MichaelC Regrets: JF Found Scribe: sharon Inferring ScribeNick: sharon Found Date: 17 Dec 2018 People with action items: charles charlesl close roy 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]