Meeting minutes
Agenda Review
Action Items
<gb> Found actions in w3c/i18n-actions: #41, #39, #36, #35, #33, #32, #18, #16, #15, #13, #12, #11, #10, #9, #8, #7, #5, #4
<addison> #41?
<gb> Action 41 propose new specdev text on strings for xml (on aphillips) due 2023-09-07
<addison> #39?
<gb> Action 39 develop best practice guidelines for name-like fields (on aphillips) due 2023-08-31
<addison> #36?
<gb> Action 36 follow up with murata-san about wcag status (on aphillips) due 2023-08-31
<addison> #35?
<gb> Action 35 make the edits of CSS #5478 (on fantasai) due 2023-08-30
<addison> #33?
<gb> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)
addison: I've closed ~40 issues
… I've been marking issues with needs-attention
… we have ~100 issues marked 'close?'
… making progress
<addison> #32?
<gb> Action 32 Approve the character markup PR (on fantasai) due 2023-08-17
<addison> #18?
<gb> Action 18 Have informal explanation sessions about counter style translations with csswg members (on frivoal, fantasai)
<addison> #16?
<gb> Action 16 Keep track of line-breaking in Korean for i18n-discuss#11 (on aphillips)
<addison> #15?
<gb> Action 15 Get character styling into w3c stylesheet (on aphillips)
<addison> #13?
<gb> Action 13 Make sure generics are comfortable to read in the content language (on frivoal)
<addison> #12?
<gb> Action 12 Upgrade/edit the explainer to address issues raised by google (on aphillips)
<addison> #11?
<gb> Action 11 Triage all css properties to determine which are logical, physical, or na by default (on frivoal)
<addison> #10?
<gb> Action 10 With florian triage richard's article into a list of potential generics (on fantasai)
<addison> #9?
<gb> Action 9 Follow up with ecma-402 on next steps and start tc39 discussion (on aphillips)
<addison> #8?
<gb> Action 8 Create pr against canvas formatted text (on aphillips)
<addison> #7?
<gb> Action 7 Remind shepherds to tend to their awaiting comment resolutions (Evergreen) (on aphillips, xfq, himorin, r12a, bert-github)
<addison> #5
<gb> Action 5 Check into how to list questions at the top of a digest and/or improve lang enablement communications (on r12a)
<addison> #4
<gb> Action 4 Work with respec and bikeshed to provide the character markup template as easy-to-use markup (on r12a)
Info Share
RADAR Review
<addison> https://
addison: we have no new incoming requests
Pending Issue Review
addison: that's probably not suprising since there's a publishing moratorium and everyone is preparing for TPAC
<addison> https://
addison: I had a conversation with AnneVK about applying dirname to some input fields that don't currently have their name
… telephone was one
… and buttons
… passwords were the only one left
… RDF is still trying to define string again
… Verifiable Credentials Data Model really don't want to use @language in @context
… to set the default language in a JSON document
… if everybody invents their own mechanism because they don't like @context
… we end up with 12 different ways of specifying this document is in English
<addison> https://
addison: if you look at the end of the link
… you'll see that there are 20 issues
TPAC Planning
addison: r12a and xfq might want to have a look and go through these issues
<addison> https://
addison: we now have a number of meetings
… on Mon, we will meet with webapps in the afternoon
… it's confirmed
… on Tue, we will meet with RDF-star
… and with APA
… on Thursday we will meet with CSS at the end of morning
r12a: this is all great
… it would be great if we could put some links in here to give some idea of what the topic of discussion would be
… so that we can prep beforehand
… is that possible?
addison: in some cases it is
… like webapps and RDF-star
… we have a lot of open issues with CSS
… I'm going through and closing those as quickly as I can
r12a: I'm suprised it starts at 8:00
addison: I've changed the wiki page to 9 for now
<r12a> https://
r12a: this is the official schedule for TPAC 2023
… it says group meetings from 9:30 every day
addison: I did not call out Wednesday
… Eemeli has a breakout session on DOM Localization on Wednesday
… not that we're sponsoring it as a group, but it's i18n related
r12a: Monday is the biggest problem for me because we have a team event
… Tuesday for me is not such a big problem
<r12a> and on Monday people such as myself will need to register at 9am
<addison> https://
WCAG 2.2
addison: has anybody else taken a look?
r12a: as a WG we're trying to unblock it
addison: some groups claim that issues they ignored previously are now backwards compatibility
r12a: plh was on vacation when he signed off the transition and he admits that he missed
… that's a component of the problem
addison: it's a single point of failure
r12a: it has occurred to me that we're not closing a lot of stuff and yet people are flying through transitions
… and we need to look more closely at that
addison: green color doesn't mean that we put that label
addison: I'm gonna schedule some time maybe on Monday morning
<r12a> https://
RDF-star prep
addison: there are 2 things going on in that space
… one is their attempts to define what a string is
… a matter of Unicode terminology
… the other thing is the need to add directional metadata to fields
… I'll try to dig out the issues and put them in our agenda so that you can all be prepared
Verifiable Credentials localization
addison: VC is the other thing I want to bring up
… they're trying to do the right things somewhat
… although they use JSON-LD
… they want to allow people to process the credentials using regular old JSON
… regular JSON processor would not know how to apply natural language string
… problem 2 is they're concerned that @language should not be applied to non-language strings and feel that this is required by @context
r12a: if there are only 2 strings would it work just to have the language and direction that associateed with those 2 strings?
addison: yes, it would
… but they've been unwilling to encoding it for every iteration of name and description
… there *is* a way to associate metadata with the string
… but you can also just decode the string with no metadata
… because presumably they're all in the same language
… every other JSON-based format will have exactly the same set of problems
… some of them won't even be JSON-LD processors at all
AOB?
addison: I will see some of you in Seville in a few days
JcK: I wish you all pleasant travels and a wonderful and relaxing and productive meeting
addison: safe travels!