W3C

- DRAFT -

Personalization Task Force Teleconference

04 May 2020

Attendees

Present
CharlesL, LisaSeemanKest, JF
Regrets
Chair
SV_MEETING_CHAIR
Scribe
sharon

Contents


<LisaSeemanKest> clear agenda

<LisaSeemanKest> am I in the right zoom room?

<LisaSeemanKest> scribe: sharon

sharons edits to the expliner https://lists.w3.org/Archives/Public/public-personalization-tf/2020May/att-0000/00-part

<LisaSeemanKest> lisa: can you put in the changes?

<LisaSeemanKest> sharon: ok...

i18n issues at https://github.com/w3c/personalization-semantics/issues?q=is%3Aissue+is%3Aopen+label%3Ai18n-needs-resolution

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/issues?q=is%3Aissue+is%3Aopen+label%3Ai18n-needs-resolution

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/issues/140

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/issues/140

<LisaSeemanKest> https://www.w3.org/International/articles/definitions-characters/

<LisaSeemanKest> answer, thank you we will be useing the refrence you gave us, and will reopen this is f we find we need more discussion

<LisaSeemanKest> is this ok?

<LisaSeemanKest> +1

+1

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/issues/141

<LisaSeemanKest> we are going to have some worked examples to show how to represnt the grammer.

Janina: We do not need to respond until we have the examples.

<LisaSeemanKest> leave open while we work on it

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/issues/142

Lisa: She will assign the issue to herself so they know its being worked on.

<LisaSeemanKest> thank you, and with your permision we will be intouch when we work on module 2 , wich may be more relivent

<LisaSeemanKest> +1

Lisa: Section selection is in module 2. We will also need authoring on our wiki.

<LisaSeemanKest> maybe wwe will add authering advice / best practice

Charles: Under purpose we have section-*** to group forms together.

<LisaSeemanKest> thank you, and with your permision we will be intouch if we need user agemts to perform text semention

<LisaSeemanKest> +1

+1

<CharlesL> s/sementation/segmentation

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/issues/143

<CharlesL> +1

<LisaSeemanKest> In module 2 (if we get ther) we hope to adress simple langage alterve textx

Janina: Add that it is future work.

<LisaSeemanKest> that is future work that we hope to start on next year

<LisaSeemanKest> we agree and plan to adress easy language alternives in module to whihc we should have a working draft the end of 2020

<LisaSeemanKest> +1

Janina: The context is that it is not in the current work.

<LisaSeemanKest> Janina like it too

+1

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/issues/144

JF: I can take this on. Both lang and direction can be on any element. The direction is based on the language at the document level. We are working on the element level.

Lisa: We should wait until we have the examples. We should be considering change of direction and language.
... We will leave it open until we address grammer.

<LisaSeemanKest> leave open until we adress gramer

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/issues/145

<LisaSeemanKest> if there are no aditional question we will close it. (and close it a a few day later

<LisaSeemanKest> (a week from today)

<LisaSeemanKest> same as 145, for 146

JF: The Bliss symbol set is based on Esperanto which already has mechanisms for multi-language translation.

Janina: Its reasonable to lay this out and ask if they agree.

Lisa: Bliss created as an internalization to avoid misrepresentation of information. Its not bound to English. Do not know the extent it was based on Esperanto. Its important that it was not an English language based. It was engineered to be an international language.

<LisaSeemanKest> f there are no aditional question we will close it. BTW the refence numbers are from bliss symbolics which was designed to be an international langage similare to espeanto

<LisaSeemanKest> btw/ note that

Janina: Its import to understand rather then BTW.

<JF> NOTE: the reference numbers are from bliss symbolics, which was designed to be an international language similar to Esperanto

Lisa: Conversation with EA and Russell. Had concerns, most were addressed. We asked them for examples and we will try to include in symbols to see if we agree. We can also add the example to the spec.

tpac

<JF> <span symbol="4 8 3"> cup of tea

<JF> <span symbol="4+8+3"> cup+of+tea (="cup of tea")

<JF> <span symbol="4,3"> cup+tea (="cup of tea")

Janina: This may be a good conversation for internationalization.

<JF> IF "+" or "," symbols are present, THEN concatonate terms (when available/present), ELSE display flat symbols

JF: Problem is, even in Bliss there are phrases that they have created a concatenated symbol for. What we need is a mechanism is a way to specify concatenated numbers. Discussed issues around grammar sets. How do we annotate?

Janina: Still would like to discuss with internationalization. We are not translating among linguistic cultures. We are staying within a culture.

JF: One of the things they will look at is if there is room for schema.org which is at that document level.

Lisa: Say we are working on some examples and will post it when its done. We want them to beaware it will come in a couple of weeks.

Janina: When we have the examples we put them up.

<LisaSeemanKest> 25712 family_(female)

<LisaSeemanKest> 21094 family_(group_home)

<LisaSeemanKest> 25713 family_(male)

<JF> Grammar="Bliss"

JF: Bliss has its own grammar which has been translated to other language. We are leveraging their work.

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2020/05/04 15:19:57 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

FAILED: s/sementation/segmentation/
Present: CharlesL LisaSeemanKest JF
Found Scribe: sharon
Inferring ScribeNick: sharon

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

Found Date: 04 May 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]