Meeting minutes
Agenda Review
Action Items
<jsahleen> i18n-activity #197
<gb> Action 197 rename the repo and shortname and publish ruby accessibility document as a first draft note (on xfq, himorin) due 2025-11-18
xfq: on publication queue, expecting next week
<jsahleen> i18n-activity #196
<gb> Action 196 remind @duerst to create a list of gaps in URL standard (on aphillips, duerst) due 2025-11-17
addison: did, and he replied
… will create new one to track and remind myself
<jsahleen> i18n-actions #187
<gb> Action 187 ping GOOG again for participation (on aphillips) due 2025-10-16
addison: no conversation on #187 yet
Info Share
Review RADAR Review
[silent]
joel: went through review reuqest list
<xfq> https://
<gb> Issue 283 not found
<jsahleen> i18n-request#283
<gb> Issue 283 SHACL 1.2 Core 2025-11-03 > 2025-01-15 (by nicholascar) [REVIEW REQUESTED] [SR] [LC]
<xfq> w3c/
<gb> Issue 2062 SHACL shape and constraint messages (by jsahleen) [s:shacl] [needs-resolution] [t:bidi_strings]
<jsahleen> w3c/
<gb> Issue 724 Allow `xsd:string`, `rdf:langString`, and `rdf:dirLangString` as values for `sh:message` (by jsahleen) [i18n-needs-resolution]
joel: in terms of comment on data shapes, we talked at above
<jsahleen> w3c/
<gb> Issue 2067 Input on the treatment of non-UTF-8 content when importing text in JS/HTML (by eemeli) [pending]
joel: talked last week for 2067
<jsahleen> zakim take up item4
Review RADAR Review
<jsahleen> zakim take up item 4
joel: checked yesterday, no incoming
… moved my two into waiting comment resolution
<jsahleen> w3c/
<gb> Issue 285 rdf12-n-triples 2025-11-21 > 2026-01-22 (by ktk) [REVIEW REQUESTED] [LC]
bert: not yet done for 285
<jsahleen> w3c/
<gb> Issue 291 css-anchor-position-1 2025-12-30 > 2026-04-01 (by fantasai) [REVIEW REQUESTED] [LC]
joel: assigned myself, they said no i18n portion on this spec, but not yet done
<jsahleen> w3c/
<gb> Issue 281 Web Sustainability Guidelines 2025-10-22 > 2026-01-09 (by mgifford) [REVIEW REQUESTED] [WD]
xfq: we have issue open for web s12y
AOB?
<jsahleen> zakim take up item 8
Intl and address format articles to publish
Intl and address format articles to publish
<xfq> * https://
<xfq> * https://
xfq: two articles listed above
… related to ECMA intl spec
… wide review period ended, all review comment issues fixed
… checked and no objection seen
… I wonder if anyone have any comment for official publication?
<xfq> https://
xfq: also for ECMA script one, above link is article list, added which one is for which section
… added list for new section(s)
r12a: getting started section is for starting, I see formatting data issue
xfq: will address
Search engine crawling and indexing
joel: agenda+ from xfq
xfq: introduced during last meeting in 2025
… basically added some infomration about how lang negotiation will go
… joel and addison made some comments
<xfq> https://
<gb> Pull Request 795 Add information about search engine crawling and indexing (by xfq)
xfq: discussed with r12a on this, this document is ...
<xfq> https://
xfq: we decided to lmit context of this document into lang negotiation
… following conversation with addison, we decided to have new article about lang
… in total three documents will be prepared
addison: my article is specific to language negtiation
… lang negotiation subjective to requirement of org requirement
… disfficult to fave search engine channels, depends on upstream request of language negotiation
… also depends on how to expose language negotiation. also for performance
… and results into spam indexing
xfq: my intention is only to outline considerations
… added some paragraph and for more about these
[discussion around index with language]
addison: my article talks about something of locales
… to feed somehting into search engine
bert: article page need to have W3C logo
… most of pages uses old ones
xfq: our template has not been updated, possibly
joel: need to update template for whole our pages?
xfq: we may have three different template
<jsahleen> w3c/
<gb> Issue 203 Add new logo to templates (by jsahleen)
<r12a> https://
joel: action created as above link
Info Share
r12a: working for Korean lreq document
… getting some useful comment from Korean colleagues
… text need to be integrated into document with standard headings
<xfq> https://
<gb> Pull Request 815 Mention ruby specs in the Ruby Markup article (by xfq)
<xfq> https://
xfq: quick item, on raised one PR for our document
… added link to ruby spec
r12a: murata-san is preparting for a11y of ruby, and would want him to contribute
xfq: no objection, and will merge this PR