Meeting minutes
WCAG-ACT Joint Meeting
[self-introduction]
<addison> w3c/
<gb> Issue 572 How are rule identifiers matched to one another? (by bert-github) [i18n-needs-resolution]
addison: we did an i18n review of the ACT rules a while ago
… an open issue ^
… we have some other open issues that we might look at if there's interest and time
… it says "This identifier must be unique when the rule is part of a ruleset"
… our comment on that is uniqueness can be challenging in a Unicode context
<Wilco> https://
<gb> Pull Request 593 Qualify identifier uniqueness prose (by daniel-montalvo)
addison: ACT rule doesn't define how an ACT rule is written
… it's not a file format
… so you can write ACT rules in a number of different ways
… these are the things that you need to have in a successful ACT rule
Wilco: yeah
addison: you don't define how the identifiers are created
… the challenge is how to tell people how to meet the reqs
… we have a really long document about identifiers and checking uniqueness called charmod-norm
Wilco: we anticipated different groups writing their own rule sets potentially
addison: a weak must is a should
addison: because you don't specify what the format is
… or a rule set is, you can't say how the uniqueness is determined
… a rule set could be case insensitive, which would make uppercase and lowercase versions of English words the same
Wilco: yeah
addison: but it's up to whoever's writing the rule set to ensure the uniqueness of rule ids
… and you might want to say that straight out
<addison> > An ACT Rule <em class="rfc2119">must</em> have an identifier that is a unique string of unicode characters. The identifier can be any text, such as a lower case ascii string, URL, or a database identifier.
Wilco: I don't understand what might not work about what we're proposing in PR 593
addison: I think you want to stay out of getting too specific
… my tendency would just be it should be unique within a rule set
Wilco: yeah
Wilco: I left a comment on https://
<gb> Pull Request 593 Qualify identifier uniqueness prose (by daniel-montalvo)
addison: that looks good
JcK: you're walking along the edge of a cliff
… because the moment somebody has to start matching what appears in the rule set to something which appears somewhere else
… you suddenly jump into all the difficulties about matching a pair of Unicode identifiers
Wilco: you're right, we're aware
… if there was a thousand orgs writing rules and they were each writing a thousand rules we might have a problem here
… but it's not a thing we ever expect to happen
JcK: in reality it doesn't require 1000, it requires about three
addison: do you want a health warning?
… I think this is probably fine
<Wilco> w3c/
<gb> Issue 574 Is the ‘descriptive title’ used for matching? (by bert-github) [i18n-needs-resolution]
Daniel: I propose to close this
… We are not using the descriptive title for matching
Kathy: have you all looked at 573?
<gb> CLOSED Issue 573 ACT does not require that the language of text is indicated (by bert-github) [i18n-needs-resolution]
<addison> https://
<gb> MERGED Pull Request 592 Qualify "writing direction" statement (by daniel-montalvo)
addison: 592 closed it, we haven't reviewed that yet
Wilco: it might be good to just go over all of these too
… make sure we're all on the same page and can move forward
addison: it seems to address our comment
… you don't specify a file format, so you don't say what form the metadata takes
Wilco: so I think we covered all issues
… it depends on whatever format you implemented in
… which is a browser
xfq: should we close our tracker issues?
addison: once they merge the PR
addison: don't touch the horizontal review labels because they're how the automation works
… you just close it
Daniel: thank you for your comments
[ACT folks leave]
Agenda Review
Action Items
<addison> https://
<addison> #167
<gb> Action 167 file issue(s) against limiting-local-font-access (on aphillips) due 2025-04-24
<addison> close #167
<gb> Closed issue #167
<addison> #165
<gb> Action 165 add a conformance section to suppress the respec warning to specdev (on aphillips) due 2025-04-10
addison: #165, when you do that it causes our spec to blow up
<addison> #162
<gb> Action 162 poll I18N/CSS for new day/time (on aphillips) due 2025-03-25
<addison> #157
<gb> Action 157 write glossary proposal identifying options and next steps for those options (on aphillips) due 2025-02-20
addison: because we have all mustard in non-normative sections
<addison> #135
<gb> Action 135 follow up on XR issue 1393 about locale in session (on aphillips) due 2024-10-17
addison: so I didn't do that
<addison> #127
<gb> Action 127 make a list of shared topics of interest between TG2 and W3C-I18N (on aphillips) due 2024-09-30
<addison> #89
<gb> Action 89 update i18n specs to support dark mode (on xfq) due 2024-04-18
ACTION: xfq: add instructions on dark mode to i18n-editors
<gb> Created action #168
<addison> #33
<gb> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)
<addison> #7
<gb> Action 7 Remind shepherds to tend to their awaiting comment resolutions (Evergreen) (on aphillips, xfq, himorin, r12a, bert-github) due 18 Jul 2023
<addison> #4
<gb> Action 4 Work with respec and bikeshed to provide the character markup template as easy-to-use markup (on aphillips) due 27 Jul 2023
Info Share
r12a: how do you turn on the dark mode?
addison: in specdev if you were looking at the preview in the lower left corner there's a little icon you see the sun and moon thing
https://
r12a: all right, I see it
Review RADAR
Pending Issue Review
<addison> https://
<gb> Issue 2001 Reduce Accept-Language (by w3cbot) [pending] [tracker] [ietf] [s:http]
addison: I have a sense of wanting to escalate this with us
… any objection to making this needs-resolution?
… done
<addison> explainers-by-googlers/
<gb> Issue 10 I18N objections to reducing accept-language (by aphillips)
WebNN
webmachinelearning/
<gb> Issue 837 String metadata and localization for operator labels (by xfq) [i18n-needs-resolution]
[xfq introduces the issue]
xfq: it doesn't look like natural language string
… like "mul#1234"
<gb> Issue 1234 not found
xfq: should we ask them to add a note to clarify this?
addison: if it's an identifier then identifierish things should be applied to it
… for example Trojan Source stuff
… if you display this value you should guard against bad labels
… these are for consumption by people, but they are meant to be identifiers
xfq: yeah
Notification Email Changes
r12a: I just want to rejig things slightly
… currently if you're subscribed to the winter list you receive 0 or 2 digests a day
… one is called reviews and the other one is called something like WG issues
… I want to make it three
… a maximum of three
… one would be called review comments
… one would be called WG projects
… the other one would be called language enablement
… and then we separate out the LE stuff
… from the WG project
… splitting that out from the WG project like specdev and charmod stuff
… split i18n repos into two
… one is WG project, the other one is LE
addison: would this affect the public list?
r12a: yes
… public-i18n-core list and the winter list
addison: any objection?
… martin made a comment on this
r12a: he seemed to be barking up the wrong tree to me
… he asked how many subscribers each list has and I replied to that
… you're not getting more content in the emails
… the amount of content is still the same
… just splitting things
… which actually makes it easier for people because if you're not interested in LE you just delete that digest and you focus on the WG projects and vice versa
Specdev "isomorphic string" PR
<addison> https://
addison: I have a PR where I've started working on address the last bits of our comments with TAG about their design principles
… and I'm having a conversation with annevk in the course of doing this
… because of the weirdness of bytestring in webidl
… isomorphic string is where you take the byte and you turn it into a Unicode code point
… 0x80 becomes code point 80
… I understand why, but they don't say that anywhere
… send your comments
Bert: a couple of holidays coming up, I won't be here next week and the week after