W3C home > Mailing lists > Public > public-personalization-tf@w3.org > January 2022

Re: Updating the Personalization TF Work Statement

From: Janina Sajka <janina@rednote.net>
Date: Wed, 12 Jan 2022 08:44:53 -0500
To: Roy Ran <ran@w3.org>
Cc: Personalization tf <public-personalization-tf@w3.org>, APA Chairs <group-apa-chairs@w3.org>
Message-ID: <Yd7a52QSZ9l0ownW@rednote.net>
Trying again with corrected email! Sorry for the noise!


Thanks, Roy.

May I suggest just fixing the Co-Facilitator to start? That part won't
require approval.

Updating additional parts of the document could put us into a review
mode. That's OK, but I think it would be good to do what we know doesn't
need Judy's OK first.

Best,

Janina

Roy Ran writes:
> Thanks Janina for review the statement, I will take action to fix those issues, I'll make a round of revisions first, and then we can review it again to see if there are still problems.
> 
> Best,
> 
> Roy
> 在 2022年1月12日 +0800 AM5:00,Janina Sajka <janina@rednote.net>,写道:
> > Colleagues:
> >
> > On this past Monday's Personalization teleconference the question arose
> > concerning the correct name of our Task Force. For a Task Force in a W3C
> > Working Group, this question, among many others, is defined by the Task
> > Force's Work Statement. The Personalization TF Work Statement appears
> > unupdated since 2018, when the work was migrated from the ARIA-WG to
> > APA:
> >
> > https://www.w3.org/WAI/APA/task-forces/personalization/work-statement
> >
> >
> > The correct name is:
> >
> > Personalization Task Force
> >
> > The above Work Statement needs an immediate update, please, to replace
> > one of the two Co-Facilitators. Lisa stepped down, and we appointed
> > Lionel Wolberger to that post. The above document does not yet reflect
> > this fact.
> >
> > I would further note that the Work Statement suggests a single normative
> > specification, which it calls "Personalization Semantics." Clearly, we
> > have changed our approach since the above document was last updated. We
> > may wish to bring our Work Statement up to date in this regard as well,
> > though I don't believe there's any hurry for doing so.
> >
> > Note also that the "specification" referenced by the Work Statement now
> > points to our Explainer. This is good, actually, even if it's no longer
> > strictly accurate. In other words we prefer the hyperlink to an actively
> > maintained document over a 404 error!
> >
> > Best,
> >
> > Janina
> >
> >
> > --
> >
> > Janina Sajka
> > (she/her/hers)
> > https://linkedin.com/in/jsajka
> >
> > Linux Foundation Fellow
> > Executive Chair, Accessibility Workgroup: http://a11y.org
> >
> > The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> > Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
> >
> >

-- 

Janina Sajka
(she/her/hers)
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
Received on Wednesday, 12 January 2022 13:45:36 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 12 January 2022 13:45:37 UTC