W3C

- DRAFT -

Personalization Task Force Teleconference

09 Sep 2019

Attendees

Present
CharlesL, janina, LisaSeemanKest
Regrets
Chair
SV_MEETING_CHAIR
Scribe
CharlesL

Contents


<scribe> scribe: CharlesL

tpac presention https://github.com/w3c/personalization-semantics/wiki/TPAC2019-WebApps-Symbols-Overview#-form-for-tpac-

<LisaSeemanKest> https://github.com/w3c/personalization-semantics/wiki/Use-cases

<Roy> https://www.w3.org/wiki/TPAC/2019/SessionIdeas

15: 30 – 16:30

Break + W3C Groups https://www.w3.org/wiki/TPAC2019/Demos– Argos A-B-C, 1F

LS: solicit others for possible use-cases, we will show with the Demo we need to figure out what we are trying to achieve
... FB could use this for new markets in India potentially.

JS: very useful to get others ideas.

LS: Question what is the first sentence for our elevator pitch.

<LisaSeemanKest> People with cognative and learning disabilities have very diffrent needs. some people can not do numberic information, but others prefer numbers to words, some people with severe language disabilites use of symbols to represent words, but one of the main challenges is a lack of standard interoperability.

<LisaSeemanKest> We are working on an extreme personalization standard that let people with severe communication impairments join the online community and share informmation and comunicate accross groups. Are there more use-cases and new user groups?

JS: transforming web content (auto-transform) and enable communication with
... and target audience.
... but how do we get folks to come.

<LisaSeemanKest> Summary (one-sentence or so): 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 a lack of interoperability.

<LisaSeemanKest> We are working on an extreme personalization standard that let people with cognitive and learning disabilities join the online community and share information and communicate across groups. Are there more use-cases and new user groups for this technology?

tpac APA joint meeting

JS: get together before APA, guidance to move our stuff fwd.
... open time late afternoon if needed.

<janina> https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2019

JS: meeting with TAG personalization is scheduled.
... TAG 3 topics, immersive Web (semantics needed), pronunciation namespace issue/need
... architectural approach blessing from TAG using data- need to file an issue with TAG in github if we want to bring something to their attention.
... do we have a question or just show them how we are using data-,

LS: I wasn't sure if they were OK with data-?

JS: we can assume that they are OK with that. do we have another architectural question?

CL: no I don't think so.

JS: we can show them the demo during that if asked
... 5pm thursday i18n meeting (sign languages) issue in the past, Q? can w3c and folks on the phone path to make sure AAC ie Bliss get correct metadata and i18n paper on what they do and hyperlinked. they think a lot of this can be solved by looking at their work.
... we may be able to refer to them in metadata with correct AAC designation.

LS: AAAT approached me and I told them to you Janina. language / dialect then the sign language.
... thought it may not be possible in the small # of digits allowed.

JS: that resulted in this meeting, web documents should look like.
... I was introducing what about AAC and symbols.. lets get them in there too. there is some work in ISO on this, etc. we know some of those people
... persenting content in a particular symbols we will want to identify the originating content with an ISO code I would think.

LS: Bliss has ISO # as far as I know from Russell
... but some of them have both english and symbols ontop of it

JS: this would go in the header in the metadata of the page.

LS: Bliss has one and has been around a long time. 30/40 years
... many others probably don't have this.

<LisaSeemanKest> ISO 8859 is for bliss

<LisaSeemanKest> ISO standards such as 7001 or 7010 but for complete pictographic/ideographic language

JS: how should we proceed with I18N UTF8 / ISO for this
... but 8859 is the normal ISO for english language so there must be something -# added for Bliss?

LS: authoring tools to help this to scale, creating profiles for people etc.

JS: CSS promise user style sheet would trump everything else. seems to me what we are asking for should be done via a style sheet. even aging.
... animations, turning off all sounds, spacing words/ punctuation/lines, margins, between phrases, etc.

<scribe> meeting: Personalization TF TPAC Planning

trackbot, end meeting

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: 2019/09/09 16:00:51 $

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)

Default Present: CharlesL, janina, LisaSeemanKest
Present: CharlesL janina LisaSeemanKest
Found Scribe: CharlesL
Inferring ScribeNick: CharlesL

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

Found Date: 09 Sep 2019
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]