Re: Personalization Introduction

This looks great Becky and thanks Janina and JF for your edits.
So do you all think this will replace what I wrote in the Summary bullet for our Session idea<https://www.w3.org/wiki/TPAC/2018/SessionIdeas#Personalization_-_How_Should_We_Implement.3F>?  I am happy to replace what I had with this.

So for Summary I had:

  *   Summary: The personalization TF now part of the APA would like your help in deciding which implementation schema we should use for our Personalization modules we have been developing. This work came out of COGA and has been worked on previously under ARIA. Since the rechartering this past year the Personalization TF, now under APA, has 3 modules currently in editor draft status and an explainer module with a temporary implementation. Here is a Google Doc with all of the possible considerations we have come up with for implementation, as well as our explainer document and 3 modules.
     *   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>

This would be replaced with.

Summary: The Personalization TF now part of the APA would like your help in deciding which implementation schema we should use for our Personalization modules we have been developing. This work came out of COGA and has been worked on previously under ARIA. 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 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 content authors can use to identify items, and an open source symbol set is being developed through UNICEF. 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 strategies 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.

<Links to modules & Google Doc>

Thanks
EOM

Charles LaPierre
Technical Lead, DIAGRAM and Born Accessible
Twitter: @CLaPierreA11Y
Skype: charles_lapierre
Phone: 650-600-3301



On Oct 16, 2018, at 5:53 AM, Janina Sajka <janina@rednote.net<mailto:janina@rednote.net>> wrote:

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<mailto: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