<sharon> genda?
scribe+
sharon: no link for TPAC
yet.
... less than 22 days to edit etc.
Janina: short video, probably
Lisa/Janina for APA and lisa can do the show/tell and we will
use Josh for video editing. as he did with the machine learning
video.
... , 3 minutes FIRM (2:45 would even be better.)
Sharon: next monday is a holiday. Janina can you reach out to Lisa.
Janina: Yes I can do that, we really want this because we get amazing response is over the top. Just watch this video and will really do well to get to the point. This is a BIG deal.
<sharon> https://raw.githack.com/w3c/personalization-semantics/explainer-compare/explainer.html
Janina: I read it while sending it to CSS. what they are doing is orthogonal with what we are doing. But I think we need to have at the top about COGA and why this is needed front and center. Cognitive and Learning disabilities.
Becky: 2nd sentence of the abstract.
<becky> There are many people with cognitive and learning disabilities that affect their ability to interact with the Web. So, far technology has not addressed their needs.
Janina: Web Technology, we have Bliss which is technology, we want browser based.
Becky: webtechnology is lacking in addressing these needs.
<becky> web technology has not served these needs 0r We are providing a technology for the Web to address these needs.
Janina: we are providing a means for web technologies to address these needs.
Becky: other changes we asked for, intro I added another bullet. for changes we talked about last week.
Janina: that was it, and I did read through it.
Sharon: anything else or just make those edits and get it out.
Janina: not too late for TPAC but at least the explainer which is a working draft update.
Sharon: so close so that should be easy.
sharon: where are we at with the TAG, are we waiting for Michael?
Janina: Yes Michael is wrapped up with Silver so we are waiting on him.
Roy: Yes I talked to Michael we can get an update in the planned call with him tomorrow.
Sharon: we haven't done anything on this yet?
Janina: I did send something out a week ago to the list.
Becky: looks fine, grammar issue
only. (as are instead of our)
... status and wide review…
Janina: Shawn Henry was really
good and we should keep using that.
... , I propose we get it into her template and will flag her
there is a CR coming and this is ready when the CR is ready and
hopefully there will be a video to go along with this
announcement.
Becky: will we get pushback that
we are going to CR but expect to have changes.
... , how to get peoples attention.
<becky> Anne van Kesteren
Janina: I would like to have this
in process, get Anne van Kesteren (WHAT WG guy) will be a great
ally.
... , here is the personalization we need some things from
WHAT, here is a video for it and pronunciation which will also
have a video.
Roy: I can update web page and give you a link.
Sharon: weren't we looking for feedback from them?
Roy: we are waiting for them to close all of them. if they don't reply. Before our document goes into CR, I will close all the issues.
Janina: they are usualy pretty good especially if we give them a deadline by.
Roy: we should reply to each of the issues.
Sharon: I thought we did reply, maybe there are one or two that we hadn't replied to yet.
Becky: 155 was added in
June.
... , 155 we have actions there are no up/down but we have
left/right. (Block start/end)
... , we need to address, we haven't talked about this June 22.
what he says makes sense but we need to address this.
... , there are a lot of values for this (previous/next) add a
start and end.
... , how would you use ACTION:start
action:end I guess
... , there are buttons that have buttons go beginning end/next
previous. etc. so this makes sense. CSS may change the layout
top/bottom could have vertically as well.
... , there are no up/down could still be next, direction could
be important in a game
Sharon: wonder if it's our definition.
Becky: if we have left/right we need up/down, and we need also start/end
charles: agreed
Becky: proposal add up/down/start/end
Janina: yes we can respond we agree and added up/down/start/end
Sharon: blockend/start was an
example…
... , add them first then respond and thank them.
Becky: you can assign this to me
<scribe> ACTION: becky to add up/down/start and end
<trackbot> Created ACTION-70 - Add up/down/start and end [on Becky Gibson - due 2020-09-07].
becky: should we reference data purpose for 133, but John said WCAG duplicated for their spec.
sharon: do we need to find the background discussion?
…, Lisa's response is in the issue 142 7 days ago.
scribe: , John responded to 143 are attributes supported for simplification.
becky: Not sure about the
example. John said his example is out of scope.
... , button aria label with click to submit and alt = I am
feeling lucky
... , we are providing simplification but doesn't do free text.
critical, you have to use one of our attribute values.
... , we have not addressed conflict resolution, we are only
providing semantics for further machine processing.
... , we can say that currently there is no free text. John's
example is good.
... , we agree easy lang but that is in module 2. we will
address that later, and John provided an answer and now its in
I18N's court to say if we have done enough.
sharon: any action with this?
just say is this sufficient.
... , 142 is the next one. Simplification of text.
becky: the content author just identifies text to be simplified. we think we have addressed this, but there may be some longer term needs. we don't have any user agents yet.
Sharon: this seems like its
answered and just needs to be closed.
... , 141 should grammar of symbols be defined.
Becky: symbols sets themselves
may be localized.
... , each word takes one symbol, Lisa drafted a response, but
may not be in the issue. in email somewhere
<becky> https://lists.w3.org/Archives/Public/public-personalization-tf/2020Aug/0025.html
Becky: , we have added a best practice page which may help. we are not enabling translations at this time. we also added a conjugated term. so this was drafted a week ago.
Janina: I say ship it.
Becky: this needs to be added to the issue.
sharon: we didn't make it to 141 last week.
Janina: Roy can you reply?
Roy: since this is Lisa's response then she should do it. I will ask Lisa tomorrow.
Becky: character set issue, and
Lisa responded to this as well, Becky responce to this UTF8/16
issue
... , I tried to sort this out and John added more.
... , we may want to close this as a NO-OP. just use as
reference.
... , attribute referencing, some open from me. had to do about
"purpose".
... , 139 and 138. has to do with auto complete values.
... , we just need to do that, html 5.2 in 3.3.3 we should
reference WCAG has adopted.
... , can we refer to auto complete by reference? i18n review
if we handle date time reference. not duplicate those. this is
just an open issue. do we need to close this before going to
CR.
Janina: we will resolve this by CR2 if not CR1, but we maybe should incorporate this by reference.
becky: we can assign a numeric reference. I think we can put this off, and we just refer to it.
sharon: thanks all
<scribe> Meeting: Personalization Task Force Weekly Meeting
<scribe> chair: Sharon
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: becky Roy CharlesL sajkaj Janina Regrets: Lisa No ScribeNick specified. Guessing ScribeNick: CharlesL Inferring Scribes: CharlesL Found Date: 31 Aug 2020 People with action items: becky 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]