Meeting minutes
zaki, next item
Announce that next meeting will be on IRC Channel 'adapt'
sharon: as of next week the IRC channel will be Adapt
janina: page needs to be updated. that's for Roy
sharon: Roy, can you update?
Roy: I will update
CharlesL: also the mailing list has -personalization in it
janina: will create a new archive. our Wiki will have to point out that we operated as Personalization. they're archived in a different place
Roy: will need to confirm changing the e-mail
CharlesL: the changes to github, we'll be in our specs pointing to new repos on github, right?
Roy: I think so. github will be changed by public list document
Roy: will include all URL and feedback
janina: update working draft with all changes then advance to CR
Inclusive Design 24 (Matthew)
<Matthew_Atkinson> Details: https://
Matthew_Atkinson: widely known series of talks. they archive the videos. would be a good opportunity to let people know about what we're doing
Matthew_Atkinson: present 30 minutes of Adapt and/or some APA work (XR, CAPTCHA, maturity, etc.)
janina: two questions. when's the conference?
Matthew_Atkinson: 22nd of September I believe
janina: what outcomes are we seeking?
Matthew_Atkinson: help with wide review of Adapt and encourage implementation, general publicizing of work we're doing
janina: is it typical for the conference to have prospective work? that's the stage we're in currently
Matthew_Atkinson: timing is potentially difficult. up to them to decide whether it's worthwhile.
janina: a little nervous about prospective versus the ability to implement after learning about it during the event
sharon: anyone you could talk to with those questions in mind, Matthew? or propose and see if a presentation is accepted?
Matthew_Atkinson: can always contact and ask if appropriate content. would need to decide whether we're going to go ahead with the content
janina: seems like more of a general APA opportunity as opposed to Adapt in particular. need to consider the outcomes of the presentation and what we want from it
Matthew_Atkinson: don't think an hour presentation is necessary
janina: if purpose is to introduce people to APA/W3C and what our current work is, then it becomes at least an APA if not W3C/WAI presentation
sharon: what to propose to move forward with this
janina: need more concrete sense of outcomes and what the conference is
janina: just unclear as to what we're presenting or leaving with after the presentation
Lionel_Wolberger: could do an hour if we discuss other APA work (COGA, Pronunciation, Adapt)
<Matthew_Atkinson> Abstract from the site: Inclusive Design 24 (#id24) is a free 24-hour online event for the global community. It celebrates inclusive design and shares knowledge and ideas from analogue to digital, from design to development, from planners to practitioners, and everything and everyone in between.
Matthew_Atkinson: will talk about this outside of this TF
sharon: have you do that in APA call tomorrow
APA Adapt announcement and messaging - https://lists.w3.org/Archives/Public/public-personalization-tf/2022May/0002.html
janina: I will look at it because we have a meeting that will include Shawn. want to get her involved sooner than later
sharon: updating to Adapt, added the dates, updates from previous reviews, should be the same thing we reviewed before
TPAC 12-16 September 2022 - Plan meetings; remind chairs to fill in the form before 31 May: https://www.w3.org/2002/09/wbs/1/LogisticsTPAC2022/ sharon]
sharon: planning, form to be filled out
<Matthew_Atkinson> This is the page the TF needs to add to: https://
janina: Matthew and I will do that sometime between 18th and 25th. we need each TF to decide whether the TF wants to work together or take time during TPAC to work on something
janina: COGA plans a relatively low profile, they did a lot last year and it was good
Matthew_Atkinson: link to APA wiki page. we need to fill that in as a TF.
sharon: our part is to decide who we're meeting with and presentation
Matthew_Atkinson: do we need to request a meeting with WHATWG?
janina: as soon as we pass CR we will book a meeting with them
janina: all we need is a reserved prefix
sharon: for right now, no meetings, but we will think about it
Adapt chairs, approve the Roy PR regarding renaming specification docs from Personalization to Adapt (and adding the caption) https://github.com/w3c/personalization-semantics/pull/205
Roy: can put render link in comments
janina: would be helpful as a common practice.
sharon: Lionel we need to make sure everything looks OK
janina: do an upated working draft with WAI-Adapt to move forward to CR
sharon: will merge when reviewed
PR status on issues 203 and 204 (merge) - https://github.com/w3c/personalization-semantics/issues/203, https://github.com/w3c/personalization-semantics/issues/204
<sharon> https://
sharon: start with what Matthew worked on
Matthew_Atkinson: 207, symbol examples. brief changes mentioned in PR notes.
Matthew_Atkinson: changed cuptea.png cup.png instead, used symbol for cup
Matthew_Atkinson: fixed indentation, kept example of conjugating agenda. changed rules in spec. allowed spaces around "+" symbol. not really going to work for parsing.
sharon: I see single values
Matthew_Atkinson: will get Lisa to look at this anyway.
janina: this final resolution is that we need more eyes on this and that's what we get during CR
janina: questions about meaning should not prevent us from going to CR. will prevent us from going to PR if we don't remediate during CR
janina: I am not troubled by this. we've done the best we can and will solicit more feedback during CR
Matthew_Atkinson: any thoughts on how I've marked up the "+" sign, Roy?
Roy: I think it's OK for you to fix that.
sharon: sounds like we've merged that, right
Matthew_Atkinson: yes
sharon: Lisa can look during CR
sharon: looks like we merged 203 and 204. other things to do for those two issues?
janina: have to get back to James Craig. that was an action on me. would prefer to wait until after WD
Matthew_Atkinson: PR from me. 206. talked about how we need to allay some fears about complication of rendering. did a PR to implement that issue so that it's in the same area of the document
Matthew_Atkinson: reads Editor's Note
sharon: rest of examples in PRs. should we merge the editor's note?
janina: let's go ahead and merge it
sharon: link directly to this section so whoever wants to review can do so. then we decide about changes to be made, then we can make them
Matthew_Atkinson: gonna send a link for ease of discovery
janina: James will get us a Safari implementation we hoep