- From: Matthew Atkinson <matkinson@tpgi.com>
- Date: Mon, 13 Jun 2022 20:08:59 +0000
- To: Sharon D Snider <snidersd@us.ibm.com>, "public-adapt@w3.org" <public-adapt@w3.org>
Hi all,
Minutes from today's call can be found at https://www.w3.org/2022/06/13-adapt-minutes.html and here they are in text form (below)...
Matthew
– DRAFT –
WAI Adapt Task Force Teleconference
13 June 2022
[2]IRC log.
[2] https://www.w3.org/2022/06/13-adapt-irc
Attendees
Present
becky, CharlesL, Lionel_Wolberger, Matthew_Atkinson
Regrets
-
Chair
Sharon
Scribe
janina, Matthew_Atkinson
Contents
1. [3]CR Status #1, spec content is ready for sharing https://
www.w3.org/TR/adapt-content/ ready for CR publication
2. [4]CR Status #2, blog post draft ready to send to Shawn
3. [5]BCI Registry Implementation: Next steps
4. [6]TPAC 12-16 September 2022
5. [7]Rewording for our Sec. 3.6 Symbol - PR 209 https://
github.com/w3c/adapt/pull/209/files (Janina)
6. [8]Editor's note for symbols (Janina action) https://
github.com/w3c/personalization-semantics/issues/203
7. [9]Content Module Implementations Status
Meeting minutes
CR Status #1, spec content is ready for sharing [10]https://
www.w3.org/TR/adapt-content/ ready for CR publication
[10] https://www.w3.org/TR/adapt-content/
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
<Roy> [11]https://www.w3.org/WAI/cc/wiki/
WAI_Announcement_Drafts#CR_publication_of_Personalization_Seman
tics_Content_Module_1.0_and_WD_of_Personalization_Semantics_Exp
lainer_announcements
[11] https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts#CR_publication_of_Personalization_Semantics_Content_Module_1.0_and_WD_of_Personalization_Semantics_Explainer_announcements
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> [12]https://lists.w3.org/Archives/Public/
public-personalization-tf/2022May/0002.html
[12] https://lists.w3.org/Archives/Public/public-personalization-tf/2022May/0002.html
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> [13]Shawn's template
[13] https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts#.5BTemplate.5D_Spec_XYZ_Announcements
Lionel_Wolberger: can have a go; what's the accepted style?
<Roy> [14]https://www.w3.org/blog/
[14] https://www.w3.org/blog/
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 (
[15]https://globalsymbols.com/ ) about that.
[15] https://globalsymbols.com/
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 [16]https://github.com/w3c/
adapt/pull/209/files (Janina)
[16] https://github.com/w3c/adapt/pull/209/files
janina: Our writeup here is confusing. Translation is covered
quite ambiguously. Started making changes, but have more to
make.
[17]https://github.com/w3c/personalization-semantics/wiki/
Best-practices-for-symbol-values
[17] https://github.com/w3c/personalization-semantics/wiki/Best-practices-for-symbol-values
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: [18]https://github.com/w3c/adapt/pull/207
[18] https://github.com/w3c/adapt/pull/207
(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) [19]https://github.com/w3c/
personalization-semantics/issues/203
[19] 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.
Minutes manually created (not a transcript), formatted by
[20]scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).
[20] https://w3c.github.io/scribe2/scribedoc.html
Diagnostics
Maybe present: janina, Roy, Sharon
--
Matthew Tylee Atkinson (he/him)
--
Principal Accessibility Engineer
TPG Interactive
https://www.tpgi.com
A Vispero Company
https://www.vispero.com
--
This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately.
Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.
On 12/06/2022, 23:46, "Sharon D Snider" <snidersd@us.ibm.com> wrote:
CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender.
Hi all,
Please review the agenda for Monday's Adapt TF call and let us know if there are any other topics that need to be added:
Chair: Lionel
* agenda+ CR Status #1, spec content is ready for sharing
https://www.w3.org/TR/adapt-content/ ready for CR publication
* agenda+ CR Status #2, blog post draft ready to send to Shawn
* agenda+ BCI Registry Implementation: Next steps
* agenda+ TPAC 12-16 September 2022
* agenda+ Editor's note for symbols (Janina action) https://github.com/w3c/personalization-semantics/issues/203
* agenda+ Content Module Implementations Status
* agenda+ Disambiguate between HTML <rel> and our newly specified "purpose." Perhaps as well, destination and action. (Lionel)
* agenda+ (on hold until following CR) Planning future COGA meetings on our other two modules
The teleconference information is at: call info - adapt <https://www.w3.org/2017/08/telecon-info_adapt>
Time:
· 10 am Eastern time
· 5 pm IS
· 3 pm UK time
IRC access
An IRC (Internet Relay Chat) channel will be available during the call at: https://irc.w3.org/?channels= <http://irc.w3.org/?channels=adapt>adapt
The server is irc.w3.org <https://irc.w3.org/>
The port number is 6665
The channel is #adapt.
You can write any name as a nickname
Resources and useful links
· Wiki <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4mKLS-4mbkbhW49Ldrp2nQ-x1W30mhG94fDYzLW1GBcSW3F6jV_W45NqmX43TBFHW3T6jkg3T1McJf4mCW9mV3&si=8000000004174048&pi=847bb923-2f8a-464b-ea70-c18f5129b0ce>; - this page has links to all our work
· mailing list archives <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj26QkH8W3T3qGX1JHM74W43Wg2w2p76z4W3T4FNJ1Lm8YzW3ZWTXk45W2z0W3SYFSb3K8R4LW41PFYp4ttcHyw43Tw4j48K2&si=8000000004174048&pi=847bb923-2f8a-464b-ea70-c18f5129b0ce>
· Personalization Semantics 1.0 <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4mKLS-4mbkbhW49Ldrl308ysDW49RkMP3zd6m0W3zhs7S41p0TNW3_R5CW3SYMZQf1Q1_Lt04&si=8000000004174048&pi=847bb923-2f8a-464b-ea70-c18f5129b0ce> (Personalization Semantics 1.0 Editors' Draft <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4mbpRl3P28X2W4hCPvp43np2_W49RkMP3zd6m0W3zhs7S41p0TNW3_R5CW3SYMZS0&si=8000000004174048&pi=847bb923-2f8a-464b-ea70-c18f5129b0ce>). See also the Adapt Task Force GitHub repository <https://github.com/w3c/adapt>.
· our home page
· Web-Based Surveys (WBS) <https://www.w3.org/2002/09/wbs/101569/>;
· adapt source repository issue tracker <https://github.com/w3c/adapt/issues>.
· Scribing and Participation Tips: http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet
· Demo: https://github.com/ayelet-seeman/coga.personalisation and https://rawgit.com/ayelet-seeman/coga.personalisation/demo/conactUs.htm <https://rawgit.com/ayelet-seeman/coga.personalisation/demo/conactUs.html>
Regards,
Sharon Snider
IBM Design ► IBM Accessibility Team
(512)965-3957
www.ibm.com/able <https://www.ibm.com/able> and w3.ibm.com/able <https://w3.ibm.com/able>
Received on Monday, 13 June 2022 20:09:15 UTC