Meeting minutes
<addison> trackbot, prepare teleconference
Atsushi: [scribe missed the first part]
… ruby, Murata Makoto, discussions...
addison: Is this an agenda topic?
Action: atsushi: ensure that a summary of the ruby issue in english is forwarded to the working group
<trackbot> Created ACTION-1030 - Ensure that a summary of the ruby issue in english is forwarded to the working group [on Atsushi Shimono - due 2021-06-03].
r12a: Would be good if somebody made a summary of the Japanese e-mail discussion in English
Agenda Review
Action Items
<addison> https://
<addison> action-1027?
<trackbot> action-1027: Richard Ishida to File issue on css multi-col to clarify columns in vertical -- due 2021-05-27 -- OPEN
<addison> close action-1027
<trackbot> Closed action-1027.
<addison> action-1028?
<trackbot> action-1028: Addison Phillips to Update personalization-semantics issue with clarifying statements and questions -- due 2021-05-27 -- OPEN
<addison> close action-1028
<trackbot> Closed action-1028.
<r12a> https://
r12a: related to action-1028, I just added to the questions ^^.
<addison> action-1029?
<trackbot> action-1029: Addison Phillips to Review payment-request issues and mark for close as needed -- due 2021-05-27 -- OPEN
<addison> close action-1029
<trackbot> Closed action-1029.
Info Share
Nothing.
RADAR Review
<addison> https://
r12a: I updated all gap-analysis documents.
<xfq> r12a++
<atsushi> r12a++
r12a: That publication required working around new publication rules, which need all images in the same directory.
… Putting all images in the directory is now simple for me, but I haven't written up how I did it yet.
Rechartering status
<r12a> https://
r12a: See link ^^
… My request for charter review by the strategy team.
… contains links to the charter drafts for IG and WG.
… Period is 3 years. Updated charter template, but no real changes.
… Current charter ends 30 June, there may be a gap before the next charter starts.
… Character Model Fundamentals is part of the deliverables.
addison: We could make it a Note instead of a Rec, what it is now.
… We could also make a new document, borrowing from the Rec, and publish *that* as a Note.
I18N glossary
<r12a> https://
r12a: We talked about this previously. Is this ^^ in the right direction?
<r12a> https://
r12a: I took some definitions for time zones from an article.
addison: Is this copy-paste? Automated?
r12a: copy-paste followed by editing.
addison: Should there be links to the sources?
r12a: Quite possibly.
<xfq> https://
r12a: The a11y glossary has links, if three defintions it links to all three. Maybe not too useful.
addison: If you want more info beyond the definition, a link might be handy. But we try to make the def. somewhat stand-alone.
r12a: I decided, after thinking about it, to include String Meta.
addison: It is not all industry jargon.
r12a: It is all i18n-WG-jargon.
… My current inclination is to not include everything, but include what we may want to link to from various places. Link from a spec but also from an article.
… String Meta, and also Character Model, is largely about defining terms. But it is useful to have a succinct definition.
JcK: Yes, this is very worthwhile.
r12a: We can still decide later what we want to do with it.
addison: Who is the editor? Are you?
r12a: Happy to work on this.
… Typically, if you need a def, it is easy to add it, rather than wait for somebody else to write it.
addison: At some point we will need to decide on FPWD and such for this.
r12a: Fuqiao asked about adding links to other glossaries, such as Unicode.
… That is a good idea.
… Fuqiao also found some links hard to click. That should be fixed now.
… For the ToC, I looked at how WAI did it.
Payment-Request issues
<addison> https://
r12a: I noticed a discrepancy in the number of items...
addison: There is about three not flagged for closing.
<addison> https://
<addison> https://
<addison> https://
addison: See the three links ^^
… The last one comes from plh's tool.
r12a: I think I downgraded it from "needs-resolution" in 2017.
… It is difficult to understand these, lots of links, not clear what the actual change is.
addison: #1046, they recognized the issue, but no change in this version.
r12a: I'll put a recycle tag on it.
addison: #1040, they added something to get a language from the element in the document. But the notification is not always document-based, e.g., a push notification.
r12a: So that is an argument for adding the metadata.
addison: Totally.
Action: addison: document the state of payment-request
<trackbot> Created ACTION-1031 - Document the state of payment-request [on Addison Phillips - due 2021-06-03].
r12a: W.r.t., localizing error, we probably need to reply on their list. We say what we wanted and say that we will watch for in the next version.
addison: I'll make that part of my action of documenting payment-request.
… I'll send an email to Ian and Marcos and go through the list of issues.
one HTML issue
<r12a> https://
r12a: This ^^ talks about a datalist item and matching it to what a user is typing.
… It seems we agree on what is needed, but not sure about what is next.
… Will it be implemented? It was suggested I write a Pull Request.
addison: It doesn't seem ready. But you can write a Pull Request.
r12a: I'd like to pass it by this WG for comments.
<addison> https://
addison: We have a doc about this, ^^, but it is mostly empty.
… It serves to scare people away from writing find_text() :-)
addison: I suggest you propose some text, in an email, and we'll discuss it.
Action: richard: propose text for html 4814 (datalist find/string search)
<trackbot> Created ACTION-1032 - Propose text for html 4814 (datalist find/string search) [on Richard Ishida - due 2021-06-03].
epub issues
<xfq> https://
<xfq> https://
xfq: First issue ^^ is about normalization and case-folding.
… They added some new text.
… Text says file names in a directory must be unique after NFC norm. and case-folding.
r12a: Does it need to say which normalization?
… For matching any one is enough.
<addison> https://
addison: Just Unicode canonical case-fold is enough.
xfq: So no need to mention NFC normalization, then?
r12a: But as they reference Unicode instead of our doc, it may need to say something about norm.
addison:
… We advise them that they do not need to mention NFC, but only some canonical form?
r12a: Yes, or they can say "NFC or NFD"
… so they don't limit people to NFC.
<xfq> https://
xfq: We dicussed ^^ before about length of path names.
… We proposed to add some text.
… They say the spec does not say how to handle too long names on purpose.
r12a: OK, but a note to warn against splitting at code points.
addison: Such a health warning makes sense, even if they don't want to limit what implementations do.
xfq: Makes sense, but not sure they want to add such a note.
addison: We are asking to say, *if* an implementation truncates, then don't do this.
… Shall I write the message?
AOB?
nothing.