<sharon> scribe: Matthew_Atkinson
<scribe> scribe: Matthew_Atkinson
Lisa: we passed this last week.
<Roy> https://github.com/w3c/personalization-semantics/pull/174
<sharon> https://github.com/w3c/personalization-semantics/wiki/actions
Becky: Roy's PR covered the notes and added horizontal table lines—we should review.
<Roy> https://raw.githack.com/w3c/personalization-semantics/action-March1st-Roy/content/index.html
Note: the PR link and comment above relate to this agendum.
Charles: good job on the table
Sharon: Looks good.
Roy: Michael may want to confirm with the low vision TF about this.
<Lionel_Wolberger> Matthew_Atkinson: Suggest going to gray, not black (on the horizontal lines)
<Lionel_Wolberger> ... also try using, from Latek (?), the ends thicker than the middles
Matthew: Looks great; maybe lighten the lines slightly and/or adopt LaTeX convetion of a thicker line to start and end the table?
<becky> https://www.w3.org/TR/coga-usable/#appendix-mapping-user-needs-persona-and-patterns
Charles, Becky: increased padding in the cells would be good too.
Becky: this example contains vertical lines, which some have warned against, but there is a lot of content in the cells so maybe valid in this case.
Charles, Lisa: This looks clear. Also better whitespacing.
Matthew: This style does look very good. Has vertical lines, but they may be lighter, and the spacing helps, will have to see how it looks in our tables. Roy's PR is already a big improvement; this may be more of one.
Roy: This PR also added a Glossary.
Janina: Michael prefers we use a reference, with a view to having a WAI-wide glossary of terms, each of which can have an HREF, so we only get the ones we need.
Becky: We could document that we're using the COGA glossary (in the body of the text, with a link).
Roy: also moved the implementation editor's note to section 1.3.
Lisa: (agreed that last week)
... The data- note should be in section 1.3.
Lionel: Some links to the explainer are broken.
Roy: This will be fixed when merged (as now using relative refs).
Lisa: One more link to the wiki; in section 1.4.
<LisaSeemanKest> what issue number?
https://github.com/w3c/personalization-semantics/issues/66
Becky: this depends on implementation: if something is implemented as link, then it is a destination, but if it's a button it's an action.
... We may need to clarify in the spec how these implementation choices affect whether something (e.g. comment) is an action or a destination.
Sharon: Have we addressed these?
Becky: We have renamed some of these, e.g. "feedback" now instead of "comment"—will review.
https://github.com/w3c/personalization-semantics/issues/68
Lionel: This refers to 3.3.4
https://w3c.github.io/personalization-semantics/content/#values-1
Becky: this related to which autocomplete values we follow: https://github.com/w3c/personalization-semantics/issues/68#issuecomment-606100220
JF: There's an ongoing discussion about having a place to provide fragment documents, such as the autocomplete values.
<becky> https://github.com/w3c/personalization-semantics/issues/68
JF: (agrees with becky's comment)
<Zakim> JF, you wanted to note the discussion about registry
becky: We need to figure out how this relates to Internationalization's issue on Personalization regarding these values.
JF: Currently the answer is that we have to keep our own copy, whilst awaiting a W3C-standard place to maintain these.
<CharlesL> +1 to remove Section****
sharon: Roy, can you remove this?
Roy: (added to TODO)
<Lionel_Wolberger> +1
<JF> +1
<becky> +1
<janina> +1
<LisaSeemanKest> +1
<sharon> Remove section-*** +1
<sharon> https://github.com/w3c/personalization-semantics/issues/46
JF: This comes under the larger action item of "how do we add multiple values to our attributes?"
... We're using HTML5's autocomplete pattern. The spec says "comma-separated" but the code samples are space-separated.
... (will raise this with HTML5)
https://github.com/w3c/personalization-semantics/issues/49
JF: This can be closed; overcome by time.
<sharon> https://github.com/w3c/personalization-semantics/issues/72
JF, becky: We've made substantial edits, considering these comments, so this issue can be closed too.
<Lionel_Wolberger> Lionel_Wolberger: blushes -- Matt, you're welcome.
https://github.com/w3c/personalization-semantics/issues/128
sharon: can we find the original version of this demo?
(nobody has found it)
Lionel_Wolberger: It's hard to find the Explainer.
janina: in theory you can start with WAI and browse, though this requires knowing Personalization is part of APA.
CharlesL: Reached out about the demo some time back; no news yet.
... (will try again)
LisaSeemanKest: There is a demo with a GitHub repo that allows site authors to include the feature in their site (so is reliant on the author of the site, rather than the user having an extension).
sharon: We should have links to implementations on the wiki?
Janina: +1 (as in this is a good idea)
becky: Should we have an implementations heading on the Wiki?
janina: +1
becky: We still don't have the video [from TPAC] on our Wiki.
Roy: The video is linked from our TF page.
<Roy> https://www.w3.org/WAI/APA/task-forces/personalization/
LisaSeemanKest: We should not change the name of the Explainer due to breaking URIs. *Takes action to find out what we have, and where, for future updates.*
<JF> +1 to janina
sharon: Did we agree to add a note to the TAG version (even if not changing name)?
janina: Need to be careful with naming. [This was the point JF +1'd I believe -scribe]
<sharon> https://github.com/w3c/personalization-semantics/issues/138
sharon: This relates to the i18n and autocomplete values discussed earlier?
becky: This is an offshoot of the previous issue (68) (and again is a larger issue within W3C).
JF: This is going to need a fairly important architectural change to TR for "normative-like" documents.
Lionel_Wolberger: I can help with the cleanup discussed above.
LisaSeemanKest: this includes links to related drafts, Explainers, etc.
<JF> ACTION: JF to get feedback re: W3C Registry discussions
Lionel_Wolberger: *takes that action*
LisaSeemanKest: *will clean up the implementations page*
<Lionel_Wolberger> Implementations page link?
<LisaSeemanKest> https://github.com/w3c/personalization-semantics/wiki/Implementations-of-Semantics