W3C home > Mailing lists > Public > public-personalization-tf@w3.org > October 2018

Re: Personalization Introduction

From: Janina Sajka <janina@rednote.net>
Date: Tue, 16 Oct 2018 08:53:41 -0400
To: public-personalization-tf@w3.org
Message-ID: <20181016125341.GB2087@rednote.net>
Thanks, Becky. This is just what we need, imo.


There's another spelling mistake in a sentence I think could benefit
from a slight expansion:

"... authors can use to idenfity items."

Suggesting:

"... authors can use to identify items, and an open source symbol set is
being developed through UNICEF."

Janina

John Foliot writes:
> Looks great. 1 spelling mistake: straregies
> 
> JF
> 
> On Mon, Oct 15, 2018, 5:17 PM Becky Gibson <becky@knowbility.org> wrote:
> 
> > Hello,
> > At today’s meeting I took the action item to draft a brief introduction to
> > the Personalization task force and our mission (our “elevator pitch”). This
> > will be used to send emails to people we hope will attend our session at
> > TPAC.  We wanted a 2-4 sentence overview and a few examples.  We also want
> > to ask people to help us evaluate the proposed implementation strategies
> > and to make recommendations.
> >
> > Here is the draft to get us started.  Please make edits and suggestions.
> > I borrowed from Charles’ TPAC Session proposal
> > <https://www.w3.org/wiki/TPAC/2018/SessionIdeas#Personalization_-_How_Should_We_Implement.3F>
> > .
> >
> > thanks,
> > -becky
> >
> > Introduction to Personalization The goal of the personalization task force
> > is to enable the adaptation of web content to user needs. Some users may
> > need simplification of text and concepts or translation into symbols.
> > Others may need content that is free of numbers, minimizes distractions, or
> > provides additional help. The web author augments the content to identify
> > options, simplications, or replacements. User agents or other technologies
> > use these semantics to augment or adapt the content based on identified
> > user preferences. Examples: The content might specify that, "9 out of 10
> > people prefer coffee over tea". The author would identify the "9 out of 10"
> > phrase and provide "almost all" as the number free alternative. Most symbol
> > sets are proprietary. People who use symbols to communicate often don't
> > understand symbols from another set. There is a need for a standard
> > vocabulary that authors can use to idenfity items. These standard tokens
> > can then be mapped to each unique symbol set. The task force has 3 modules
> > and an explainer document in editor draft status. Below are links to these
> > documents and to a Google Document comparing the implementation straregies
> > we have explored. The task force needs your help to select the best
> > implementation schema for the personalization semantics. We have eliminated
> > RDFa, HTML Microdata, and ARIA attributes as not practical at this time.
> >
> >
> >    - Comparison-of-ways-to-use-vocabulary-in-content
> >    <https://github.com/w3c/personalization-semantics/wiki/Comparison-of-ways-to-use-vocabulary-in-content>
> >    - Personalization Semantics Explainer 1.0
> >    <https://raw.githack.com/w3c/personalization-semantics/WD-explainer-and-module1-FPWD-module2-and-module3/explainer.html>
> >    - Personalization Semantics Content Module 1.0
> >    <https://raw.githack.com/w3c/personalization-semantics/WD-explainer-and-module1-FPWD-module2-and-module3/content/index.html>
> >    - Personalization Help and Support 1.0
> >    <https://raw.githack.com/w3c/personalization-semantics/WD-explainer-and-module1-FPWD-module2-and-module3/help/index.html>Personalization
> >    Tools 1.0
> >    <https://raw.githack.com/w3c/personalization-semantics/WD-explainer-and-module1-FPWD-module2-and-module3/tools/index.html>
> >
> >
> >

-- 

Janina Sajka

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

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
Received on Tuesday, 16 October 2018 12:54:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:57 UTC