13:52:21 RRSAgent has joined #personalization 13:52:21 logging to https://www.w3.org/2019/09/09-personalization-irc 13:52:23 RRSAgent, make logs world 13:52:23 Zakim has joined #personalization 13:52:25 Meeting: Personalization Task Force Teleconference 13:52:25 Date: 09 September 2019 13:52:26 agenda? 13:53:00 agenda+ tpac presention https://github.com/w3c/personalization-semantics/wiki/TPAC2019-WebApps-Symbols-Overview#-form-for-tpac- 13:53:16 agenda+ tpac APA joint meeting 13:53:34 agenda+ are we happy with the methodology handbook 13:54:53 agenda+ Continuing the review of the consolidated list of values at https://raw.githack.com/w3c/personalization-semantics/value-list/vocabulary-list/index.html 13:58:40 agenda? 14:00:57 CharlesL has joined #personalization 14:01:05 present+ 14:01:41 scribe: CharlesL 14:01:44 janina has joined #personalization 14:01:48 present+ 14:01:54 present+ 14:02:07 zakim, next item 14:02:07 agendum 1. "tpac presention https://github.com/w3c/personalization-semantics/wiki/TPAC2019-WebApps-Symbols-Overview#-form-for-tpac-" taken up [from LisaSeemanKest] 14:05:53 https://github.com/w3c/personalization-semantics/wiki/Use-cases 14:07:43 agenda+ is there an issue for the tag 14:08:00 agenda+ internationalization 14:08:32 zakim, close item 3 14:08:32 agendum 3, are we happy with the methodology handbook, closed 14:08:33 I see 5 items remaining on the agenda; the next one is 14:08:33 1. tpac presention https://github.com/w3c/personalization-semantics/wiki/TPAC2019-WebApps-Symbols-Overview#-form-for-tpac- [from LisaSeemanKest] 14:09:13 agenda? 14:09:36 zakim, close item 4 14:09:36 agendum 4, Continuing the review of the consolidated list of values at https://raw.githack.com/w3c/personalization-semantics/value-list/vocabulary-list/index.html, closed 14:09:39 I see 4 items remaining on the agenda; the next one is 14:09:39 1. tpac presention https://github.com/w3c/personalization-semantics/wiki/TPAC2019-WebApps-Symbols-Overview#-form-for-tpac- [from LisaSeemanKest] 14:10:18 agenda+ elivator pitch, and summarying the technology\ 14:13:09 https://www.w3.org/wiki/TPAC/2019/SessionIdeas 14:15:26 15:30 – 16:30 14:15:26 Break + W3C Groups https://www.w3.org/wiki/TPAC2019/Demos– Argos A-B-C, 1F 14:20:02 LS: solicit others for possible use-cases, we will show with the Demo we need to figure out what we are trying to achieve 14:22:15 LS: FB could use this for new markets in India potentially. 14:22:28 JS: very useful to get others ideas. 14:22:44 LS: Question what is the first sentence for our elevator pitch. 14:22:58 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. 14:22:58 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? 14:28:06 JS: transforming web content (auto-transform) and enable communication with 14:28:16 … and target audience. 14:28:31 … but how do we get folks to come. 14:29:53 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. 14:29:53 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? 14:35:59 zakim, next item 14:35:59 agendum 2. "tpac APA joint meeting" taken up [from LisaSeemanKest] 14:36:13 agenda? 14:39:01 JS: get together before APA, guidance to move our stuff fwd. 14:39:25 JS: open time late afternoon if needed. 14:40:01 https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2019 14:40:06 … meeting with TAG personalization is scheduled. 14:41:14 … TAG 3 topics, immersive Web (semantics needed), pronunciation namespace issue/need 14:42:08 … 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. 14:42:29 … do we have a question or just show them how we are using data-, 14:42:39 LS: I wasn't sure if they were OK with data-? 14:43:19 JS: we can assume that they are OK with that. do we have another architectural question? 14:43:30 CL: no I don't think so. 14:43:42 JS: we can show them the demo during that if asked 14:45:45 JS: 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. 14:46:06 JS: we may be able to refer to them in metadata with correct AAC designation. 14:46:43 LS: AAAT approached me and I told them to you Janina. language / dialect then the sign language. 14:47:02 … thought it may not be possible in the small # of digits allowed. 14:47:20 JS: that resulted in this meeting, web documents should look like. 14:48:06 … 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 14:48:39 … persenting content in a particular symbols we will want to identify the originating content with an ISO code I would think. 14:49:01 LS: Bliss has ISO # as far as I know from Russell 14:49:48 … but some of them have both english and symbols ontop of it 14:50:01 JS: this would go in the header in the metadata of the page. 14:50:23 LS: Bliss has one and has been around a long time. 30/40 years 14:50:50 … many others probably don't have this. 14:50:59 ISO 8859 is for bliss 14:51:18 ISO standards such as 7001 or 7010 but for complete pictographic/ideographic language 14:55:07 JS: how should we proceed with I18N UTF8 / ISO for this 14:55:23 agenda? 14:57:19 JS: but 8859 is the normal ISO for english language so there must be something -# added for Bliss? 14:58:43 LS: authoring tools to help this to scale, creating profiles for people etc. 14:59:38 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. 15:00:39 … animations, turning off all sounds, spacing words/ punctuation/lines, margins, between phrases, etc. 15:04:13 janina has left #personalization 15:04:40 meeting: Personalization TF TPAC Planning 15:04:51 rrsagent, make logs public 15:04:58 rrsagent, draft minutes 15:04:58 I have made the request to generate https://www.w3.org/2019/09/09-personalization-minutes.html CharlesL 15:50:02 stevelee has joined #personalization 16:00:38 trackbot, end meeting 16:00:38 Zakim, list attendees 16:00:38 As of this point the attendees have been CharlesL, janina, LisaSeemanKest 16:00:46 RRSAgent, please draft minutes 16:00:46 I have made the request to generate https://www.w3.org/2019/09/09-personalization-minutes.html trackbot 16:00:47 RRSAgent, bye 16:00:47 I see no action items