Minutes of Personalization TF meeting of June 29

The minutes of the personalization task force meeting of June 29, 2020 are at:  https://www.w3.org/2020/06/29-personalization-minutes.html <https://www.w3.org/2020/06/29-personalization-minutes.html>

Text version is below:

 <http://www.w3.org/>
- DRAFT -

Personalization Task Force Teleconference

29 Jun 2020

Attendees <>
Present
becky, LisaSeemanKest, Roy
Regrets
Chair
SV_MEETING_CHAIR
Scribe
becky
Contents

Topics <https://www.w3.org/2020/06/29-personalization-minutes.html#agenda>
i18n issue <https://www.w3.org/2020/06/29-personalization-minutes.html#item01>
Review content module <https://www.w3.org/2020/06/29-personalization-minutes.html#item02>
i18n issue <https://www.w3.org/2020/06/29-personalization-minutes.html#item03>
Summary of Action Items <https://www.w3.org/2020/06/29-personalization-minutes.html#ActionSummary>
Summary of Resolutions <https://www.w3.org/2020/06/29-personalization-minutes.html#ResolutionSummary>
<LisaSeemanKest> trackbot, start meeting
<sharon> https://github.com/w3c/personalization-semantics/pull/156/files <https://github.com/w3c/personalization-semantics/pull/156/files>
<sharon> https://raw.githack.com/w3c/personalization-semantics/JF-Edits/content/index.html <https://raw.githack.com/w3c/personalization-semantics/JF-Edits/content/index.html>
<scribe> scribe: becky
awk Lisa
<Zakim> LisaSeemanKest, you wanted to say timlines at https://github.com/w3c/personalization-semantics/wiki/wish-list-and-priorities-for-2020--2021 <https://github.com/w3c/personalization-semantics/wiki/wish-list-and-priorities-for-2020--2021>
i18n issue

Review content module

JF: reviewing changes made to content module
... 3.1.3 - token is a broken hyperlink - seems like a vocabulary but is not in our list; need to find that definition and pull it over or remove the hyperthink
becky: suggest track down the definition
JF: section 2 has 2 terms - token doesn't seem to fit as a term there - do we want to create a glossary?
Janina: okay to link but best if W3c link - perhaps HTML
JF: COGA glossary we link to is pretty sparse
Lisa: COGA is working on that
JF: concerned about linking to such a sparse document
Lisa: concerned that the first paragraph doesn't adequately describe the topic and sentence structure is confusing
Janina: that is my rewrite - I am happy to have someone work on it and use plain language
JF: I will look at rewriting that first paragraph
<LisaSeemanKest> https://github.com/w3c/personalization-semantics/wiki/csun-draft <https://github.com/w3c/personalization-semantics/wiki/csun-draft>
Lisa: the wiki has good info about what personalization is about that we can use as background
<Roy> https://w3c.github.io/personalization-semantics/#propcharacteristic_value <https://w3c.github.io/personalization-semantics/#propcharacteristic_value>
<LisaSeemanKest> https://github.com/w3c/personalization-semantics/wiki/Getting-started-with-personalization-semantics <https://github.com/w3c/personalization-semantics/wiki/Getting-started-with-personalization-semantics>
Roy: the token broken link should work when this is merged into master
<LisaSeemanKest> https://github.com/w3c/personalization-semantics/wiki/Getting-started-with-personalization-semantics <https://github.com/w3c/personalization-semantics/wiki/Getting-started-with-personalization-semantics>
JF: just want to clarified that there is a def. for token within the explainer
<Roy> https://w3c.github.io/personalization-semantics/#propcharacteristic_value <https://w3c.github.io/personalization-semantics/#propcharacteristic_value>
<LisaSeemanKest> https://github.com/w3c/personalization-semantics/wiki/We-need-personalization-because <https://github.com/w3c/personalization-semantics/wiki/We-need-personalization-because>
<LisaSeemanKest> Summary: People have very different needs. some people can not do numeric information, but others prefer numbers to words, some people with severe language disabilities use of symbols to represent words, but one of the main challenges is transforming content for these different needs. We are working
<LisaSeemanKest> from https://github.com/w3c/personalization-semantics/wiki/TPAC2019-WebApps-Symbols-Overview <https://github.com/w3c/personalization-semantics/wiki/TPAC2019-WebApps-Symbols-Overview>
Lisa: provides links to examples of personalization overview
Janina: be careful in an normative doc that definitions are defined within a published / normative specification
Lisa: I understand that we can link to non-normative documents within a non-normative section of a normative document
<LisaSeemanKest> what number
JF: section 3.4.2 we discussed that the structure of examples was confusing - I rearranged into an ordered list
<LisaSeemanKest> are we looking at
Lisa: concerned with embedded horizontal scroll within examples
Janina: but line breaks are not always appropriate in code
JF: I will add line breaks to remove horizontal scroll
... section 3.6.1 - symbol description - broke things into a list; added <acronym> element for AAC;
... may actions are to re-write first paragraph, fix horizontal line breaks;
becky: 3.3 purpose - describes a token list but characteristics only list token
JF: could actually be a token or a token list? then we get back into definitions - how to handle
We did have this defined but took them out when moved away from ARIA - can we get these links from a previous version of the document
JF: we are showing a code example for purpose that takes a space separated list of token values. this is similar to auto-complete in HTML and that does not allow multiple values. Thus we need to define token list
Janina: we eliminated comma separated values so we need to explain that
JF: we are more specific for symbol which has two ways of doing
... symbol provides multiple examples to demonstrate the different types
... should we add another example with both token and token list to be more explicit?
Lisa: believe we have an inline example
becky: supports adding another example for consistency with symbol
Janina: agree - better not to make people hunt fo info
Lisa: agree if it makes it easier to grasp for people
JF: 3.3.3 how to handle characteristic: token - can it be left the way it is or do we need to add token, token list
<Roy> https://w3c.github.io/personalization-semantics/#propcharacteristic_value <https://w3c.github.io/personalization-semantics/#propcharacteristic_value>
JF: 3.3.6 says the value is a uri - which is also wrong
<JF> https://raw.githack.com/w3c/personalization-semantics/JF-Edits/content/index.html#characteristics-4 <https://raw.githack.com/w3c/personalization-semantics/JF-Edits/content/index.html#characteristics-4>
JF: symbol actually is a numeric identifier taken from BSI list rather than a token
Janina: BSI link destination needs to be within W3C
JF: believe that Lisa coordinated allowing us to put this list in W3C space
Lisa: perhaps we could include BSI list as an appendix
JF: but is really long
Janina: also can't update the BSI list without rev
... without revising the document that the appendix is within
... is a Roy/Michael task to get the document into W3C space as normative
JF: okay for now to refer to wiki or note but will need to be normative before CR
... can we point directly to BSI for now while this is just an editor's draft?
Janina: to work with Michael to determine long term publishing
JF: B1 - informative references - curious why some are here
<Roy> https://raw.githack.com/w3c/personalization-semantics/JF-Edits/content/index.html#characteristics-4 <https://raw.githack.com/w3c/personalization-semantics/JF-Edits/content/index.html#characteristics-4>
Roy: we reference RDFa primer in 3.6.3 and SKOS elsewhere
... I will clean up all of the links when merge
JF: will leave section B1 for Roy to clean up
becky: doc. is inconsistent about which links open in new window and others do not
Janina: we should bring that issue up in coordination call this afternoon
Janina and becky to resolve and advise JF on how links should be handled
i18n issue

SS: there is quite a long list of i18N issues
<sharon> https://github.com/w3c/personalization-semantics/issues/141 <https://github.com/w3c/personalization-semantics/issues/141>
Lisa: there is a new one - #141
... an #144 that we haven't responded to at all
... we did clarify the cup of tea example in the content module - is that sufficient to answer and close this?
<LisaSeemanKest> https://w3c.github.io/personalization-semantics/content/#symbol-example <https://w3c.github.io/personalization-semantics/content/#symbol-example>
Lisa: we did have some text to address this issue generally and that we are not translating between languages and are basing the symbols on Bliss list which is meant to be international
... good that we included hebrew which is structually different than English and other European languages
JF: I think your reference to esperanto is good to include that uses of the symbols are familiar with the language and are designed to be international
Janina: no call next week due to the US July 4th holiday
Summary of Action Items <>
Summary of Resolutions <>[End of minutes]
Minutes manually created (not a transcript), formatted by David Booth's scribe.perl <http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm> version (CVS log <http://dev.w3.org/cvsweb/2002/scribe/>)
$Date: 2020/06/29 15:01:07 $
Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ <http://dev.w3.org/cvsweb/~checkout~/2002/scribe/>

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: becky LisaSeemanKest Roy
Found Scribe: becky
Inferring ScribeNick: becky

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 29 Jun 2020
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl <http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm> diagnostic output]


Becky Gibson | Sr. Accessibility Strategist
Knowbility.org
becky@knowbility.org
Pronouns: she/her/hers