13:33:59 RRSAgent has joined #personalization 13:33:59 logging to https://www.w3.org/2021/06/07-personalization-irc 13:34:01 RRSAgent, make logs public 13:34:01 Zakim has joined #personalization 13:34:03 Meeting: Personalization Task Force Teleconference 13:34:03 Date: 07 June 2021 13:34:13 agenda? 13:34:33 agenda+ i18n issue #144 (Review response) - https://github.com/w3c/personalization-semantics/issues/144 13:35:17 agenda+ Diff of Content Module 1 - Working draft vs. Editors draft - https://lists.w3.org/Archives/Public/public-personalization-tf/2021Jun/att-0001/00-part (Sharon) 13:35:35 agenda+ Update on the draft document for action-destination-purpose that will be referenced with an editors note (Matthew and John) 13:35:49 agenda+ Content module 1 issues https://github.com/w3c/personalization-semantics/issues?q=is%3Aopen+is%3Aissue+label%3A%221%29+content+module%22 13:51:26 janina has joined #personalization 13:57:56 Matthew_Atkinson has joined #personalization 13:59:16 JF has joined #personalization 14:00:44 agenda? 14:01:17 Lionel_Wolberger has joined #personalization 14:01:23 Present+ 14:01:51 present+ 14:01:54 scribe: janina 14:02:01 stevelee has joined #personalization 14:02:12 present+ 14:02:21 sharon: Noting that effective immediately Lionel will be Co-Facilitator with Sharon. Lisa has stepped down. 14:02:34 zakim, take up item 3 14:02:34 agendum 3 -- Update on the draft document for action-destination-purpose that will be referenced with an editors note (Matthew and John) -- taken up [from sharon] 14:02:40 CharlesL has joined #personalization 14:02:50 present+ 14:03:13 jf: Recalls issue is whether or not to merge attributes 14:03:42 jf: We worked on use cases, possible duplication? 14:03:44 q+ 14:04:04 jf: States goal as getting as many of our attributes as possible into HTML without a prefix 14:04:15 ack ja 14:05:06 janina: Recalls that group decision had been to go with prefixed only 14:05:14 jf: Disappointed, but issue is the same 14:05:19 janina: Agree re the issue 14:05:41 jf: Matthew and I landed on that "these are research questions." 14:06:05 jf: Goal is to get feedback both from authoring and implementation 14:06:15 q+ 14:06:16 jf: Can we ask RQTF 14:07:01 Lionel scribing: 2 considerations in going to RQTF 14:07:14 ... They tend not to look at disambiguation. 14:07:30 ... They tend to support a literature-review focus, what has worked and what has not worked in the literature 14:07:49 ... Also RQTF is loaded recently. 14:08:07 Q? 14:08:07 q? 14:08:36 ... Activity in XAUR, Captcha, Sync tolerances.... Loaded. 14:08:44 ack Matthew_Atkinson 14:08:48 q+ 14:09:05 matthew: Notes he's sent email pointing to wiki 14:09:12 Document in G-Docs: https://docs.google.com/document/d/1aVnRu0tZE-hvQ4tTj1Genlno3b6H31KdAby7rrUmBRw/edit?skip_itp2_check=true&pli=1#heading=h.2ydr91se730e 14:09:20 matthew: includes proposed Ed Note to request feedback 14:09:28 matthew: Notes that would work for RQTF 14:09:30 All code examples in a single large table: https://docs.google.com/spreadsheets/d/1tdgXpteQMI5Uz9z271BhSV7W9WEit89iQzac28tPPKM/edit?skip_itp2_check=true&pli=1#gid=0 14:09:44 matthew: Not all the right formatting yet 14:09:44 ACTION: JF to add content to our wiki 14:09:45 Tells Matthew: I do not have access to the Google Doc 14:09:50 q+ 14:09:54 Error creating an ACTION: could not connect to Tracker. Please mail with details about what happened. 14:10:07 q? 14:10:19 ack Lionel_Wolberger 14:10:35 Q+ 14:10:46 lionel: Not clear about going to rQTF, though I like the direction of going for feedback 14:11:04 Lionel_Wolberger: Notes conference submission to point to our work 14:11:49 ack janina 14:12:13 Sharing my paper proposal is for this conference, https://inclusivedesign24.org/2021/ 14:12:56 q? 14:13:14 q+ 14:14:53 ack JF 14:14:59 jf: Agrees with Lionel on broadest agreement 14:15:26 jf: Recalls "white paper" is probably not right title, so it's how we ended up on "Research Questions." 14:15:45 jf: OK if RQTF can't, but it seemed colleagual to ask 14:16:14 jf: Wonders whether we want this resolved before CR. 14:16:35 q? 14:16:45 jf: Goal is to get a decision before we're too far in the process to easily adapt to a change 14:17:14 jf: Notes that he and Matthew looked at this with code examples 14:17:17 q+ 14:17:34 ack Matthew_Atkinson 14:17:48 I emailed the doc (which features the big table at the end) to the list: https://lists.w3.org/Archives/Public/public-personalization-tf/2021Jun/0004.html 14:18:01 Matthew_Atkinson: Requests post to wiki 14:18:04 jf: Can do 14:18:54 q? 14:19:38 ack janina 14:20:23 scribe: Lionel 14:20:32 q? 14:20:43 scribe: Lionel_Wolberger 14:20:44 janina: The early implementations were clearly drafts 14:21:02 ... will a second CR be too late? 14:21:53 ... this CR will be enough for WHAT-WG to give us a prefix 14:22:42 JF: Matt's code examples surface the issue very clearly 14:22:48 jf: Notes Matthew's code all about making life easier for authoring 14:22:55 q? 14:23:25 sharon: Believes we have agreed to get the paper into the wiki, and we'll look at Ed Note wording and close on it next week? 14:23:42 Q+ 14:23:45 sharon: So, we probably all need a little time to get this done 14:24:01 jf: Will post today 14:24:17 jf: Offers to add candidate Ed Note in github repo as well 14:24:19 sharon: Sure 14:24:36 zakim, next item 14:24:36 I see a speaker queue remaining and respectfully decline to close this agendum, janina 14:24:40 q? 14:24:47 ACTION: add Editor's note to Module 1 that points to Research Questions wiki page 14:24:47 Error finding 'add'. You can review and register nicknames at . 14:24:48 zakim, next item 14:24:48 I see a speaker queue remaining and respectfully decline to close this agendum, janina 14:24:52 ack jf 14:24:55 zakim, next item 14:24:55 agendum 1 -- i18n issue #144 (Review response) - https://github.com/w3c/personalization-semantics/issues/144 -- taken up [from sharon] 14:25:18 ACTION: JF to add Editor's note to Module 1 that points to Research Questions wiki page 14:25:23 Created ACTION-87 - Add editor's note to module 1 that points to research questions wiki page [on John Foliot - due 2021-06-14]. 14:26:02 sharon: Notes Addison responded on github issue 14:26:06 Lionel_Wolberger: When? 14:26:15 sharon: 12 days ago as of now 14:26:30 sharon: A long response 14:27:11 sharon: Notes also response from Richard of I18N 14:27:22 sharon: i18n unclear as to what the resolution is 14:27:30 sharon: reads some of the github 14:29:00 [i18n concerned whether direction matters] 14:29:32 sharon: Notes Richard has additional questions 14:29:44 sharon: Richard suggests graphics in specs to show what users will see 14:30:33 sharon: Also reads Richard's concern about Bliss syntax across i18n contexts 14:32:03 Q+ 14:32:17 q+ 14:33:09 q? 14:33:13 ack JF 14:33:22 jf: Believe Richard has drilled into a good question 14:33:31 jf: Believe we'll need eventually to rely on AI 14:34:22 jf: Maybe we don't have all the naswers because Bliss doesn't have them all 14:34:37 q? 14:34:41 ack CharlesL 14:34:43 jf: Bliss not always thea one to one translation 14:34:55 CharlesL: We always said we're not translating 14:34:57 Lionel found this on a Blisssymbol Canada blog, "he Hebrew language is written from right to left and, after much discussion and deliberation with the people in Canada and others from different parts of the world, it was decided to write the Blissymbols being used in Israel from right to left to correspond to the written language."" 14:35:13 CharlesL: If we have the symbols, we facilitate symbolic communication in lang X 14:35:43 CharlesL: Perhaps a note in our spec that we're not translating, just representing using symbols within a lang 14:35:49 q+ 14:35:53 CharlesL: Also suggest we ask Bliss how to respond on this 14:35:59 q? 14:36:00 +1 to asking Bliss 14:36:04 Q+ to clarify what we are using from Bliss 14:36:12 ack Lionel_Wolberger 14:36:45 Lionel_Wolberger: Have been looking, unsure whether Bliss has consensus around this 14:36:47 q? 14:37:18 Lionel_Wolberger: We're just specifying where there are symbols 14:37:21 ack JF 14:37:21 JF, you wanted to clarify what we are using from Bliss 14:37:29 jf: We're transformation, not translation 14:37:44 Or maybe "transliteration?" 14:38:00 q+ 14:38:04 jf: Notes each symbol expresses a concept plus identifier as our taxonomy 14:38:19 ack Matthew_Atkinson 14:38:46 Matthew_Atkinson: Wondering whether we can isolate ourselves -- what's essential 14:39:00 Matthew_Atkinson: Do we need to say re directionality? 14:39:10 q? 14:39:21 q+ 14:39:40 q+ 14:40:05 janina: We can acknowledge that there are gaps (as pointed out by i18n), but often, 14:40:10 q? 14:40:23 ... in accessibility, there are gaps, but putting something (flawed) out there is better than nothing. 14:40:39 q? 14:40:43 ... Suggesting having a conversation with them about that 14:40:44 +1 to Janina - don't let perfect be the enemy of good 14:40:44 ack Lionel_Wolberger 14:41:27 q? 14:41:27 Lionel_Wolberger: Asking jf would isolation also isolate us from the space/comma issue we recently looked at? 14:41:30 jf: Don't think so 14:41:52 jf: Believe we ended up with space 14:42:22 Lionel_Wolberger: So is related? 14:42:44 jf: Reason for numeric identifier 14:42:52 jf: Best choice and unencumbered 14:43:01 s/unen/IPR unen/ 14:44:43 Lionel_Wolberger: we're defining a personalization metatag, now we're getting buried by details; can we say there is a coherent personalization message there? 14:44:53 Lionel_Wolberger: Not sure, but wondering 14:44:55 ack CharlesL 14:45:11 CharlesL: Let's say we had "cup of tea" and also "a b c" symbols ... 14:45:52 CharlesL: If I'm now in Country X which is right to left, the page should display "c b a" right? I would know what. 14:45:55 Q+ 14:46:02 CharlesL: So, I'm not sure it's our issue 14:47:06 janina: There is a precedence order here: the language of the page has precedence over the language of the personalization tags and values 14:47:11 janina: Suggests Charles has a solid idea--there's a precedence order here, and the web page needs to get the i18n right before personalization transformations are applied 14:47:36 jf: Symbols will follow native lang of doc. We don't do translation 14:47:40 q? 14:48:19 janina: It is highly dependent on the page that you pull up. You might be physically in China, but reading a Hebrew page-- the page's rules are followed 14:48:57 JF: We expect the peronalization attribute to respect the lang attribute of the host page 14:49:09 sharon: recalls similar conversation last year 14:49:36 sharon: reads from Lisa's comments ... 14:49:37 Draft: our specification does not anticipate translation, but rather transformation. It is expected that the transformation tool (word to symbol) respects the language specified by the content author (using @lang) 14:50:52 Q+ to suggest we invite them to one of our calls to finally resolve this question 14:51:10 sharon: Also reads from Becky's comments ... 14:51:25 q+ 14:51:32 q? 14:51:57 ack JF 14:51:57 JF, you wanted to suggest we invite them to one of our calls to finally resolve this question 14:51:59 janina: We agree with i18n that this stuff MATTERS. 14:52:12 +1 to inviting i18N here 14:52:25 jf: Agrees that invite to call may help 14:52:37 q? 14:53:22 ack Lionel_Wolberger 14:53:24 Lionel_Wolberger: +1 on this approach 14:53:44 Lionel_Wolberger: Still a bit stuck on the alt text -- what happens? 14:53:57 Lionel_Wolberger: whoever translates the page needs to deal with i18n 14:54:20 +1 14:55:16 Lionel: an example, given an HTML page with a lang value of "english". A process translates the page into "Hebrew." This proces would translate any 'alt' tags as well 14:55:50 Issue: https://github.com/w3c/personalization-semantics/issues/144 14:55:52 https://github.com/w3c/personalization-semantics/issues/144 14:55:56 Created ISSUE-1 - Https://github.com/w3c/personalization-semantics/issues/144. Please complete additional details at . 14:56:04 ... we see our situation as similar to this example. We are in violent agreement that the 'lang' of the page takes precedence and dictates how to interpret or render the linguistic elements on the page 14:56:14 zakim, next item 14:56:14 agendum 2 -- Diff of Content Module 1 - Working draft vs. Editors draft - https://lists.w3.org/Archives/Public/public-personalization-tf/2021Jun/att-0001/00-part (Sharon) -- 14:56:17 ... taken up [from sharon] 14:56:18 ... Peronalization tags should be handled similarly. 14:56:36 sharon: Recalls being tasks to diff last working draft vs editor's draft 14:56:53 sharon: looks like none of our chages made it into the WD 14:56:55 q+ 14:57:15 +1, that appears correct Sharon 14:57:40 We've never updated the Working Draft 14:58:22 q? 14:58:39 ack ja 14:58:42 ack janina 14:58:45 jf: Offers to help! 14:58:59 sharon: Think I've noted, so will go and do the ones I found 14:59:12 jf: Have also caught a few, but never done a diff 14:59:55 jf: Believe both the module and the explainer have redline edits that need updating 15:00:33 ACTION: JF to do redline review of Modules 2 & 3 15:00:39 Created ACTION-88 - Do redline review of modules 2 & 3 [on John Foliot - due 2021-06-14]. 15:00:41 rrsagent, make minutes 15:00:41 I have made the request to generate https://www.w3.org/2021/06/07-personalization-minutes.html janina 15:00:58 becky has joined #personalization 15:01:34 RRSAgent, make logs public 15:01:40 RRSAgent, make minutes 15:01:40 I have made the request to generate https://www.w3.org/2021/06/07-personalization-minutes.html Roy 15:03:50 CharlesL has left #personalization 15:06:10 bye 15:06:36 Lionel to Sharon -- back on the Zoom for planning? 15:07:02 https://www.w3.org/2017/08/telecon-info_personalization-plan 15:07:09 Lionel_Wolberger, 15:07:09 Thanks, Roy 15:23:19 janina has left #personalization 15:27:26 RRSAgent, make log public 15:27:33 RRSAgent, make minutes 15:27:33 I have made the request to generate https://www.w3.org/2021/06/07-personalization-minutes.html Roy 15:30:29 stevelee has joined #personalization