Meeting minutes
CR Status #1, spec content is ready for sharing https://www.w3.org/TR/adapt-content/ ready for CR publication
Sharon: There are other items on the agenda relating to specific aspects of CR, but any general news/reviews?
janina: We need to click through links, as well as checking general language use. 3.6 discussion upcoming later in agenda.
Sharon: We need to hammer away at reviewing the document.
CR Status #2, blog post draft ready to send to Shawn
Sharon: I made a draft according to the template. This didn't include a full blog post.
janina: It's worth making a blog post, as this is transformative technology.
Roy: Added a link above, but the access is only for chairs and facilitators.
<Roy> https://
janina: The procoess for Shawn is to fill in the wiki, once we've agreed on our announcement, and then let Shanw know it's ready.
Sharon: Will fill in wiki.
Sharon: We'll still need to draft the blog post.
janina: Can probably take this largely from the abstract and intro; re-read this morning; it's pretty good.
Lionel_Wolberger: [screen shares wiki draft announcement]
Lionel_Wolberger: Need to rename.
Sharon: We need to take the updates from the email and apply those (and link corrections) to the wiki page.
Matthew_Atkinson: Asks whether wiki should be group readable, if not writable?
[ Note: it is editable by us all, which has largely been agreed to be a good thing. ]
janina: Let's check against Shawn's latest template.
<Roy> Shawn's template
Lionel_Wolberger: can have a go; what's the accepted style?
<Roy> https://
janina: Catch developer and consumer interest; fairly light; slightly technical; we want to reach beyond accessibility news interest eventually at least. Can point to examples, though I think the wiki page does that.
Lionel_Wolberger: I have been evangelizing and socializing this, so have some language suggestions. Can help towards a blog post. Will take first pass, possibly with UserWay colleagues.
janina: Roy posted another link, which is Shawn's latest template; that's where it goes. Block copy and put it there.
Lionel_Wolberger: Deadline?
janina: These aren't necessariily synced to CR pub, but best to be ready to go when it does.
janina: The current WD says "comments until July 10" so we are boxed in. I hope we'll be ready for CR on the 11th.
BCI Registry Implementation: Next steps
janina: Had a good conversation with Russell from BCI last week (as minuted then). We'll write another spec, for the W3C Registry, that enshrines how we'll do the mapping (possibly with multiple languages; maybe also for symbol sets to map to the concepts). Should the relatively easy. Want to find some people who've been there before to help us do it. Russell will become an invited expert (IE) to APA.
janina: What we're moving to CR will have a dependency on the Registry spec. We don't want to have to refer people to the PDF we have so far.
janina: Not necessarily a good idea to use w3.org as a lookup for symbols itself (potentially too much load). May want to see if a CDN wants to loan us some space in the interests of the common good.
janina: We probably want a defined URI, so may register one, like ARIA did for the implementation guide.
Matthew_Atkinson: Not that concerned if we don't have a real-time symbol look-up; seems most efficient to use local symbol sets with a mapping anyway.
janina: Yes, though may be good to have a means to get symbols the user doesn't yet have.
Matthew_Atkinson: Maybe we could talk to Global Symbols ( https://
Sharon: Can this wait until after CR?
janina: Yes, but probably want to have the Registry by the time we get to PR (i.e. at least 60, probably closer to 120, days).
TPAC 12-16 September 2022
Rewording for our Sec. 3.6 Symbol - PR 209 https://github.com/w3c/adapt/pull/209/files (Janina)
janina: Our writeup here is confusing. Translation is covered quite ambiguously. Started making changes, but have more to make.
https://
janina: correct grammatical terms for parts of language aren't being used.
janina: The referenced (GitHub) wiki page needs updating.
janina: Should we reference it?
Roy: we can update it in the new repo if we want to.
Matthew_Atkinson: I was wondering, when doing my PR, if we should leave it historical, and not update it any more, and not reference it any more from the spec, or keep it updated.
janina: Agree about not referencing from the spec.
janina: we still use "Personalization" along with "User Agent"
Lionel_Wolberger: I noticed this too.
Lionel_Wolberger: This comes up very close to the start. However, mindful that we can make further changes after CR.
Lionel_Wolberger: We probably don't want to call it just "User Agent". In one place we have "Adaptive User Agent" which is interesting.
janina: agree we should leave the ones you mentioned for now; they seem OK.
Lionel_Wolberger: so "Personalization Agent" can be as it is, as the others.
Roy: we shouldn't delete the page just yet, due to being referenced by the current WD, but could do afterwards.
janina: I'll make additional changes on top of #209 and post to the list.
You can see how to craft HTML preview URIs via the examples on my PR: https://
(the "before" and "after" examples)
Sharon: Matthew_Atkinson: can you put a deprecation notice on the wiki page?
Matthew_Atkinson: yes
Editor's note for symbols (Janina action) https://github.com/w3c/personalization-semantics/issues/203
janina: as soon as we have edits accepted on section 3.6 I'll let James Craig know.
Content Module Implementations Status
Lionel_Wolberger: (several in progress, but no confirmed commitment from them yet)
Lionel_Wolberger: (several in progress, but no additional confirmed commitment from them yet)
janina: Being in CR may be helpful here.
Lionel_Wolberger: Really want to get browsers involved.