<scribe> scribe: sharon
<CharlesL> Congrats all!
<CharlesL> ACTION: CharlesL to add a new GitHub issue to define "personalization" in explainer re: Janina's email responce
<trackbot> Error finding 'CharlesL'. You can review and register nicknames at <https://www.w3.org/WAI/APA/task-forces/personalization/track/users>.
<CharlesL> ACTION: Charles to add a new GitHub issue to define "personalization" in explainer re: Janina's email responce
<trackbot> Created ACTION-37 - Add a new github issue to define "personalization" in explainer re: janina's email responce [on Charles LaPierre - due 2020-02-10].
Janina: Discussed main things we
want to accomplish. Use this page, its a start. Personalization
should be in it. Publishing will be on the list.
... Two specific things to nail down. Are we ready to ask HTML
WG / WCAG, we've done what you ask. We need to move forward.
Can we replace it with a prefix?
... We can work with them on what the prefix should be. We need
to lock down a prefix.
... Second point, what is the minimum ask we have from the main
stream browsers?
... Suggesting we want to be in the DOM. We need to decide
early so we can understand what we are asking from the
browsers.
becky: Do we have enough of an implementation to take to HTML?
Charles: John feeling too. He
would like to see someone pick up and use it (i.e. Bank, or
Weather...) So we can see it working on a real Web site.
... Has some control at Benetech where he could put somethings
in with help from this TF.
Steve: Not sure if we need an attribute rather then sticking with data-. Can we enumerate what the reasons are?
Charles: Something that John sent to the group that had to do with the definition of what data- is used for.
Janina: Should we move away to
data- to development prefix and ensure its accessible in the
DOM.
... What do we need to achieve before we make a request to
replace data-. We can't move to PR on data-.
Charles: Pronunciation is missing from the list.
Janina: It will be added.
<CharlesL> https://w3c.github.io/i18n-drafts/techniques/shortchecklist
Charles: The attributes can be english, and we do have some values.
Janina: Ask them to take a look and let us know if they have a problem.
Charles: Whatever format they want for review, we just need to do that.
Becky: We might need to add some id refs.
Charles: i18n labels are in
GitHub. We'll need to inform the internalization working
group.
... Does everyone think we can update the request issue and put
the documents we want.
Janina: They may want to read the explainer before looking at the module.
Charles: Review request is a tag, with working draft, PR, etc... It looks like they want that as well. Should we do 3 separate?
Janina: All documents or just specifications. It might be worth an email for clarification.
<CharlesL> ACTION: Charles to contact i18n chairs asking about Normative documents only vs. supporting document (cc michael and Janina.
<trackbot> Created ACTION-38 - Contact i18n chairs asking about normative documents only vs. supporting document (cc michael and janina. [on Charles LaPierre - due 2020-02-10].
Charles: We are ready for tag
review.
... Janina will take it up with Michael to understand what to
do.
... Lets get internalization, tag, and security to sign off.
Then we can go on to module 2.
... We also need to support WCAG SC.
Janina: That should be a priority.
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) Present: CharlesL stevelee Becka11y janina Roy Found Scribe: sharon Inferring ScribeNick: sharon Found Date: 03 Feb 2020 People with action items: charles charlesl 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]