14:17:55 RRSAgent has joined #personalization 14:17:55 logging to https://www.w3.org/2022/01/10-personalization-irc 14:17:57 RRSAgent, make logs public 14:18:00 Meeting: Personalization Task Force Teleconference 14:18:00 Date: 10 January 2022 14:18:11 agenda? 14:18:30 zakim, clear agenda 14:18:30 agenda cleared 14:18:43 chair: Sharon 14:19:19 agenda+ Work on the Rendering plug-in (Matthew) 14:20:21 agenda+ Follow-up on i18n issue #144 https://github.com/w3c/personalization-semantics/issues/144 14:20:33 agenda+ Planning COGA January meeting on Module 2.0 and 3.0 (date/time/attendees) 14:21:48 agenda+ A shortname for the modules. The numbering is confusing. 14:22:12 agenda+ Is the new W3C Registry Suitable for Bliss Symbol Lookup Functions https://www.w3.org/2021/Process-20211102/#registries 14:22:31 agenda+ Content Module Implementations Status 14:23:02 agenda+ CR draft Status (if #144 is clear or there is a renderer) 14:23:08 agenda? 14:47:45 janina has joined #personalization 14:48:09 agenda? 14:57:53 agenda+ Meeting next Monday? MLK Day? 14:58:05 zakim, reorder 8 1 2 4 3 14:58:05 I don't understand 'reorder 8 1 2 4 3', janina 14:58:56 Matthew_Atkinson has joined #personalization 14:59:02 present+ 14:59:08 agenda reorder 8 1 2 4 3 14:59:15 agenda? 15:00:37 https://www.w3.org/WAI/APA/wiki/Key_Resources_and_Links 15:00:59 agenda order 8 1 2 4 3 15:01:06 agenda? 15:03:28 JF has joined #personalization 15:03:33 Present+ 15:03:37 agenda? 15:04:09 Lionel_Wolberger has joined #personalization 15:06:26 q? 15:06:30 agenda? 15:07:42 regrets+ Becky 15:08:03 present+ 15:08:07 present+ 15:08:12 present+ 15:09:10 https://www.w3.org/WAI/APA/wiki/Key_Resources_and_Links 15:10:18 scribe: Matthew_Atkinson 15:10:29 zakim, next item 15:10:29 agendum 8 -- Meeting next Monday? MLK Day? -- taken up [from janina] 15:12:37 janina: Want to honor the holiday, but expect most of us will be here (due to covid), and we aim to reach CR as soon as possible, so suggest we meet. 15:12:55 Q+ 15:13:56 ack me 15:14:01 JF: Any news on path to CR? 15:14:05 scribe: janina 15:14:09 janina: Let's address in following items 15:14:11 zakim, next item 15:14:11 agendum 1 -- Work on the Rendering plug-in (Matthew) -- taken up [from Sharon] 15:14:28 Matthew_Atkinson: zakim, close this item 15:14:38 zakim, take up item 1 15:14:38 agendum 1 -- Work on the Rendering plug-in (Matthew) -- taken up [from Sharon] 15:15:02 zakim, close item 8 15:15:02 agendum 8, Meeting next Monday? MLK Day?, closed 15:15:03 I see 7 items remaining on the agenda; the next one is 15:15:03 1. Work on the Rendering plug-in (Matthew) [from Sharon] 15:15:35 Matthew_Atkinson: Need to have a version of the extension we can redistribute 15:15:47 Matthew_Atkinson: Need to figure out with Lisa 15:15:58 Matthew_Atkinson: Having issues getting email to her 15:16:14 janina: Do we know what the blockage is? 15:16:26 Matthew_Atkinson: Extension I have doesn't have a license clause of any kind 15:16:43 Matthew_Atkinson: It's already in the web store, but the older version 15:17:56 q? 15:18:00 janina: Expects that there would not be a license distinction from 1.0 to 1.1? 15:18:18 Lionel_Wolberger: How can I help 15:18:37 Matthew_Atkinson: Not actually sure what version is in the web store 15:19:56 CharlesL has joined #personalization 15:20:02 present+ 15:20:53 Lionel_Wolberger: we'll need instructions, if it's a file being distributed, yes? 15:21:05 Matthew_Atkinson: It's a standard process, but can do. It's easy 15:21:42 q? 15:23:32 scribe: Matthew_Atkinson 15:23:44 RRSAgent, make minutes 15:23:44 I have made the request to generate https://www.w3.org/2022/01/10-personalization-minutes.html Matthew_Atkinson 15:23:52 zakim, next item 15:23:52 agendum 2 -- Follow-up on i18n issue #144 https://github.com/w3c/personalization-semantics/issues/144 -- taken up [from Sharon] 15:24:15 Lionel_Wolberger: Checked, and no further response; we are blocked. 15:24:38 janina: Discussed with Michael and Roy; we need to clear this issue. 15:25:16 I agree lets wait for the rendering before we reach out again. 15:25:24 janina: Important to get the renderer demo sorted if we can before contacting them. 15:25:26 zakim, next item 15:25:26 agendum 4 -- A shortname for the modules. The numbering is confusing. -- taken up [from Sharon] 15:26:06 Lionel_Wolberger: As discussed briefly before; the numbering is confusing. 15:26:41 the current, Personalization Semantics Content Module 1.0 15:26:42 janina: propose module 1 is "Content" 15:26:49 JF: Propose Content Personalization Module 15:26:50 https://www.w3.org/TR/personalization-semantics-content-1.0/ 15:26:59 q+ 15:27:00 The Content Module 15:27:00 q+ 15:27:10 Content Personalization Module 15:27:37 Personalization Content Module 15:28:04 q? 15:28:26 scribe: Let's look at long names and -- regretably they're not consistent 15:28:35 personalization help and support 1.0 15:28:44 personalization tools 1.0 15:28:52 Matthew_Atkinson: Think all long names should include "Module" 15:29:03 Matt suggests that they all should contain the term, 'module' 15:29:05 Q+ 15:29:05 Matthew_Atkinson: should they all start "Personalization" 15:29:13 q? 15:29:24 ack Matthew_Atkinson 15:29:27 s/should they all start "Personalization"/should they all start "Personalization Semantics"?/ 15:29:33 https://w3c.github.io/personalization-semantics/#modules 15:29:43 CharlesL: ^ Explainer 15:30:11 Personalization Semantics Content Module 1.0: 15:30:11 +1 to Charles 15:30:14 CharlesL: Notes Explainer is more consistent; suggests we use that format everywhere 15:30:25 jf: Agree 15:30:26 CharlesL: The Explainer names should be used everywhere. 15:30:27 Personalization Help and Support Module 1.0 15:30:40 Personalization Tools Module 1.0 15:30:46 JF: Not aware of a rule that specifies the names must have a certain format. 15:30:49 q? 15:30:52 JF: Current names work quite well. 15:30:55 q+ 15:31:00 ack CharlesL 15:31:06 ack JF 15:31:19 q+ 15:31:45 scribe: janina 15:31:57 Matthew_Atkinson: Not sure about "Semantics." do we need it in there? 15:32:07 q? 15:32:25 ack Matthew_Atkinson 15:32:50 Matthew_Atkinson: Suggest "Content Semantics" if we keep the "Semantics" 15:33:05 janina: I'm more comfortable without the "Semantics" 15:33:05 https://www.w3.org/TR/personalization-semantics-help-1.0/ 15:33:08 https://www.w3.org/TR/personalization-semantics-tools-1.0/ 15:33:54 Roy: The above are the docs that are currently published. 15:34:09 janina: We can still change the names. 15:34:23 q? 15:34:30 Matthew_Atkinson: the URLs aren't consistent with the names 15:34:35 ack Roy 15:35:01 q? 15:35:10 +1 all start with Personalization 15:35:14 Lionel_Wolberger: Do we agree that they should all start with "Personalization"? 15:35:15 +1 15:35:25 +1 15:35:26 +1 15:35:29 +1 15:35:59 The Personalization Task Force will refine the Personalization Semantics specification, in consultation with the ARIA Working Group. The task force provides a focused forum for this work while the Working Group continues its work on ARIA development. Personalization Semantics was listed in the ARIA charter as "User Context" but was renamed as work progressed. 15:36:05 Lionel_Wolberger: The first is "Semantics Content" or "Content Semantics"? 15:36:31 q? 15:36:32 Lionel_Wolberger: as JF reminds us, we are bringing semantics to the element level 15:36:45 +1 to the "element-level semantics"; that is a great micro-explainer :-) 15:36:54 Agreed not the name of our TF 15:37:10 q+ 15:37:21 janina: Not sure that "Semantics" is part of our TF name. 15:38:11 janina: Not sure that "Semantics" is now important enough to put in the title. 15:38:12 q+ 15:38:22 q? 15:39:06 Q+ 15:39:14 +1 to Charles 15:39:24 CharlesL: If we take "Personalization (Content|Tools|...) Module"... we are adding semantics to each of these. Should be all or nothing. 15:39:42 CharlesL: we're not creating new tools, but adding semantics. 15:39:50 q? 15:40:00 ack CharlesL 15:40:00 CharlesL: Prefer to keep "Semantics" for all 15:40:07 Matthew_Atkinson: W3C groups says we're "Personalization" () but home page says both "Personalization Accessibilty" and "Personalization Semantics" () 15:40:09 +1 to CharlesL 15:41:02 q? 15:41:06 ack Matthew_Atkinson 15:41:17 Matthew_Atkinson: "Personalization Semantics ... Module" seem accurate to me. 15:41:34 JF: Tend to agree, but not sure where the later modules are yet. 15:41:49 ... Concerned that we are particularly concerned about the symbol attribute in the first module. 15:42:10 ... Think it's purpose that is going to see the most adoption, and that is semantic information. 15:42:22 q+ 15:42:22 JF: so +1 to semantics here; not sure if it's applicable for the other two modules. 15:42:23 q? 15:42:33 ack JF 15:42:59 q+ 15:43:10 For example, @numberfree provides alternative text for people who prefer content that does not use numerical concepts. 15:43:33 janina: The URI will stay the URI; doesn't have to match the title. We can explain how we bring semantics into help and tooling if that's the case. I can live with either, but preference to take it out of the title, as we don't fully know how those modules will devleop. 15:43:41 q? 15:43:48 Q+ 15:43:48 ack janina 15:44:04 Lionel_Wolberger: Is there anything to be gained from shorter, or longer titles? 15:44:29 CharlesL: Having a more descriptive title is better than a shorter title IMO. 15:44:46 ... Looking at the Help module, these are semantics that we're adding. 15:45:05 q? 15:45:11 ack CharlesL 15:45:25 q+ 15:46:17 JF: We may define semantics differently. Some of the attributes are about providing additional information (e.g. alt text isn't semantics; we have some attributes that are similar). Semantics is more like "the purpose of this element is a link". We are adding more specificity. 15:46:36 q? 15:46:40 ... Distraction is semantics, as we're stating relative importance, but a link to tools/help is a link. We want to classify it as a special type of link. 15:47:11 JF: I think Lionel_Wolberger's point on shortening the name is a useful consideration. There is nuance. Think our names are getting too long. 15:47:37 q? 15:47:45 Lionel_Wolberger: To summarise: JF doesn't feel there is so much in the way of semantics in the later modules. 15:48:03 q? 15:48:10 JF: Correct; it's often more about alternatives. Semantics are about the purpose of an element. 15:48:38 q? 15:48:42 ack JF 15:48:42 JF: A block of numbers with a span that has the "numberfree" attribute is providing an alternative restatement of that content. 15:48:49 scribe: janina 15:48:57 Matthew_Atkinson: Find the discussion interesting 15:49:16 +1 to Matthew 15:49:19 Matthew_Atkinson: Suggest that we'll likely agree on Personalization * Module 15:49:24 q+ 15:49:39 I think there is both, semantics and alternatives. Message-importance for example is more semantics than alternative in the tools module. 15:49:44 scribe: Matthew_Atkinson 15:49:45 q? 15:49:45 +1 to module 15:49:51 Lionel_Wolberger: Do we all agree they should end with "Module"? 15:49:53 +1 15:50:09 +1 ending wih Module 15:50:23 s/wih/with 15:50:37 +1 15:50:45 Lionel_Wolberger: Each will start with "Personalization" and end with "Module" (also don't think the URL part needs to include "module"; it does already contain "personalization-semantics") 15:51:03 +1 15:51:05 +1 15:51:05 +1 15:51:11 +1 15:51:14 Lionel_Wolberger: Do we agree with Personalization * Module in the names? 15:51:15 +1 15:52:39 RESOLUTION: Group agrees to a title schema "Personalization * Module" (with other changes to be discussed). 15:53:05 s/to a title schema/to a title scheme/ 15:53:40 -1 to the module in the URI 15:53:43 Lionel_Wolberger: Do we want "module" in the URIs? 15:53:45 -1 15:53:49 -1 15:53:58 0 15:54:09 0 15:54:36 q+ 15:54:46 q- 15:55:05 scribe: thought we'd come back to this much later -- after we establish what we're doing with 2 & 3 15:55:08 q+ 15:55:38 q+ 15:55:45 ack Matthew_Atkinson 15:55:48 Matthew_Atkinson: Can this decison on the * part be pushed back? 15:56:00 janina: We need to talk to COGA though, and thus need to not use numbers. 15:56:04 janina: Which is understandable. 15:56:19 janina: Need to be clear as to which module we're talking about, and concisely. 15:56:33 janina: We are about to go to CR with the first one, the Content one, though. 15:56:55 q? 15:57:08 janina: I'm tending towards pulling "Semantics" out of the titles. We may be talking at differnt levels of strictness. 15:57:37 s/differnt/different 15:57:56 janina: We can avoid it in the titling, even if we discuss at length in the document. 15:57:59 "Personalization: Content Module", "Personalization: Help and Support Module", "Personalization: Help Module" 15:58:10 Q+ 15:58:17 s/Personalization: Help Module/Personalization: Tools Module/ 15:58:27 Lionel_Wolberger: Agree we need simple and consistent names for these. 15:58:43 Lionel_Wolberger: We don't need shorter names, as long as they're accurate names. 15:59:02 Proposes: "Personalization: Content Module", "Personalization: Help and Support Module", "Personalization: Help Module" 15:59:03 Lionel_Wolberger: But in this case, the shorter names help to differentiate. 15:59:04 q? 15:59:18 Lionel_Wolberger: Suggest we pick this up next time. 16:00:47 JF: +1 to continuing next time 16:01:11 Lionel_Wolberger: Propose we meet next week; can cancel if need be. 16:01:16 RRSAgent, make minutes 16:01:16 I have made the request to generate https://www.w3.org/2022/01/10-personalization-minutes.html Matthew_Atkinson 16:13:35 CharlesL has left #personalization