W3C

- DRAFT -

Personalization Task Force Teleconference

24 Aug 2020

Attendees

Present
janina, sharon, becky, LisaSeemanKest
Regrets
John, F
Chair
SV_MEETING_CHAIR
Scribe
Sharon

Contents


<LisaSeemanKest> clear agenda

<LisaSeemanKest> issue 139 and 138 https://github.com/w3c/personalization-semantics/issues/139 and 138

<LisaSeemanKest> scribe: Sharon

abstract

<LisaSeemanKest> https://lists.w3.org/Archives/Public/public-personalization-tf/2020Aug/0021.html

Lisa: Abstract looked good to Janina and Lisa

<LisaSeemanKest> +1

Lisa: Are we all OK with this abstract?

+1

<janina> +1

<Roy> +1

explainer https://lists.w3.org/Archives/Public/public-personalization-tf/2020Aug/0016.html

becky: Changes were to simplify and make it more action oriented.

<LisaSeemanKest> https://raw.githack.com/w3c/personalization-semantics/explainer-compare/explainer.html#introduction

Lisa: Maybe change the intro to say Personalization specification?
... I wouldn't know what starts by using data-? We could pull it out.

Janina: This is not a plan for what we are going to do. It is what we have.

Becky: Roy will look into images when its approved.

Lisa: Is the technology paragraph to long? Or maybe move it the end.
... Vocabulary Implementations is missing symbol and distraction.

Janina: Change the section be an example and not exhaustive.
... A roadmap should be documented somewhere that includes future plans.

Lisa: We can separate what is now and whats coming. So people can see what's coming in section 2.
... Section 1.4 Technology comparison summary, should it move under implementation?

Janina: Is OK to move it.

<LisaSeemanKest> move 1.4 to 4.2

Lisa: It will move to 4.2 in Vocabulary Implementation and what is existing will be 4.1.

<LisaSeemanKest> remove Other properties in the vocabulary are not yet mature enough to suggest using them in production HTML with data- attributes

<LisaSeemanKest> \Examples of those properties in the modules are to facilitate review, not to suggest implementation.

Lisa: Should we take a look at it again next week?

tag comments

<becky> This publication of personalizations semantics provides several name value pairs. These include but are not limted to:

<becky> data-action

<becky> data-destination

<becky> data- purpose

<becky> Other properties exist or will be developed as the modules mature. See the discussion of prototypes with data-.

<LisaSeemanKest> \=1

<LisaSeemanKest> +1

+1

<LisaSeemanKest> janina+1s

<LisaSeemanKest> https://lists.w3.org/Archives/Public/public-personalization-tf/2020Aug/0010.html

Lisa: This was sent to the list a couple weeks ago. Micheal was meant to review it.

<Roy> https://github.com/w3c/personalization-semantics/wiki/Explainer-for-Personalization-Semantics#non-goals

<Roy> Bliss values

Roy: Asked Michael to review. He said there needs to be a link for the Bliss values in the last value in the non-goal section

Becky: Are we looking for a link to the symbol set for Bliss values.

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/wiki/Best-practices-for-symbol-values

Janina: We need the index in TR space so it is persistent.
... We need Roy/Michael to create that for use and it is the permanent place we point to.

Lisa: We should wait for tag review until we have done that.

Janina: We should have a title. Index of what?

<becky> https://lists.w3.org/Archives/Public/public-personalization-tf/2020Jun/0022.html

Lisa: Symbol references

<LisaSeemanKest> BCI

<LisaSeemanKest> BCI Symbol references

Becky: We need to spell out BCI
... Bliss Communication International
... It is a PDF

Janina: We need to publish in HTML. Maybe we need to get the final list.

Lisa: Should I write back to Russel for the final list?
... We have a table at symbol.net from Matt in a spreadsheet for what they mean, etc.

<LisaSeemanKest> http://www.symbolnet.org/bliss/BCI-AV_2018-04-16_(en+sv+no+fi+hu+de+nl+af+ru+lv+po+fr+es+pt+it+dk)+derivations+tag-sorted.zip

<LisaSeemanKest> atts work sheet to match the material at: http://www.symbolnet.org/bliss/bliss_template+1st100+YACR-freq1000-329wl.ods

Janina: We version our copy so it is normative for our specification. Do we want to point to an evolving version?

Becky: Was hoping it was something they already had we could use.

Janina: Doesn't think we can reference an excel from our specification.

https://github.com/w3c/personalization-semantics/issues/155

Becky: Bliss does have a set of PDFs.

<becky> https://www.blissymbolics.org/index.php/symbol-files

<becky> https://www.blissymbolics.net/BCI-AV_2020-03-09/BCI-AV_2020-03-09_id_to_gloss_map.txt

<LisaSeemanKest> https://www.blissymbolics.net/BCI-AV_2020-03-09/BCI-AV_2020-03-09_id_to_gloss_map.txt

Janina: If we are going to point to symbolnet.org it needs a copyright.

<LisaSeemanKest> For a list of current reference numbers please refer to our data-symbol wiki page. The reference numbers are the same references numbers used in Bliss (BCI numbers). Here is a link to the copyright licensing from Bliss.

<LisaSeemanKest> https://www.blissymbolics.org/index.php/licensing

<becky> symbolnet.org background (http://symbolnet.org/en/background1.html) indicates they are working in conjunction with semantic web activity in W3c

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/wiki/About-Data-Symbol

Janina: Can't go to CR with an editors note.

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version (CVS log)
$Date: 2020/08/24 15:02:48 $

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/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: janina sharon becky LisaSeemanKest
Regrets: John F
Found Scribe: Sharon
Inferring ScribeNick: sharon

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

Found Date: 24 Aug 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 diagnostic output]