Meeting minutes
Agenda Review
Action Items
<addison> https://
<addison> #188
<gb> Action 188 convert number formatting article to html and publish to wide review (on xfq) due 2025-10-16
xfq: did it today, close
<addison> close #188
<gb> Closed issue #188
<addison> #187
<gb> Action 187 ping GOOG again for participation (on aphillips) due 2025-10-16
addison: ping but not heard back yet
… preparing other email to other companies
<addison> #185
<gb> Action 185 follow up with PLH on automating TC39 repos (on aphillips) due 2025-10-02
<addison> #135
<gb> Action 135 follow up on XR issue 1393 about locale in session (on aphillips) due 2024-10-17
<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
eemeli: submitted two breakout sessions
Review RADAR Review
<addison> https://
addison: read ECMA one
addison: we should have permission now for repository
ACTION: addison: follow up with shane carr about ecma repo automation
<gb> Created action #189
Pending Issue Review
<addison> https://
<addison> i18n-activity#2038
addison: we have two new incoming for discussion
<gb> Issue 2038 Support for Multi-language Render Templates (by w3cbot) [pending] [tracker]
addison: from VC
<addison> i18n-activity#2039
<gb> Issue 2039 Discuss adding `i18n.setAcceptLanguages` and `i18n.appendAcceptLanguage` (by w3cbot) [pending] [tracker] [s:webextensions]
addison: talking about API for managing accept language header
addison: Web extension one is early stage of incubation and discussion
ACTION: addison: add a comment to i18n issue 2039's parent to indicate interest and call for early review/engagement
<gb> Created action #190
Support for multi-language render
<addison> i18n-activity#2038
<gb> Issue 2038 Support for Multi-language Render Templates (by w3cbot) [tracker] [t:loc_localization] [s:vc-render-method]
<addison> w3c/
<gb> Issue 26 Support for Multi-language Render Templates (by vishwa-vyom) [class 4] [i18n-tracker]
addison: VC allow you to specify way to render credential, providing localization mechanizm, described
… two part for implementation, credential receiver what user locale matches with template and nagotiate to display
… credential author, provide templates with language tag
… added quick comment, as high level one
xfq: still draft in pre-FPWD phase
eemeli: could be a topic for breakout session of localization
Language tags for non-linguistic content
<addison> dapt#2032
<gb> Issue 2032 not found
<xfq> w3c/
<gb> MERGED Pull Request 322 Use `und` in place of an empty `daptm:langSrc` (by nigelmegitt)
xfq: already merged PR
<xfq> https://
xfq: and this section in spec
… basically changed default value into und
… for undetermined one
… also referenced BCP 47 for valid tag
addison: forgot to mention about well-formed
xfq: added in another one
addison: if XML lang or lang value is empty, had some meaning
… und will inherit down into, but blank is not
… und has its own meaning in cldr or else
<xfq> ... und starts to have a meaning in the CLDR land of root
joel: trigger Intl API chain
<xfq> eemeli: und means not supported, falling back to the navigator default
addison: blank could be if content is explicitly mentioned as non linguistinc content
IRI and isolates
<Eemeli Aro raised an issue with the IRI RFC>
Another way to mark normativity in the glossary
<addison> w3c/
<gb> Pull Request 85 Another way to mark normativity (by xfq)
<addison> https://
addison: PR as above
xfq: [introduce background of marking normativity work]
… previous consensus was to classify terms into categories, and transfer ones into two documents
… in preview link, you could see some terms has blue box as normative
addison: splitting would not be better, and marking as this could be good
bert: comment on readability, blue box could be adjusted
… some label could be enough
addison: basically of set of attributes on display
xfq: we could have PR against any branch, other than main
xfq: this PR is already marking normative terms, we could start discussion based on this draft
… start from normative part, and decide on other parts
xfq: will prepare next step and bring back to WG