Event Updated: W3C Internationalization Working Group Teleconference

[View this event in your browser](https://www.w3.org/events/meetings/dcb21af5-6796-49aa-9a5c-88b2454316a3/20230309T150000)

 W3C Internationalization Working Group Teleconference Upcoming Confirmed
=========================================================================

 09 March 2023, 15:00 -16:00 Europe/London

 Event is recurring every 7 days, starting from 2023-02-23, until 2023-11-03

  Location: https://www.w3.org/2017/09/i18n-meeting-info.html

[ Internationalization Working Group ](https://www.w3.org/groups/wg/i18n-core/calendar)***NOTE WELL*** This meeting is scheduled in the `Europe/London` time zone. That time zone observes Daylight Savings/Summer Time. Your local time for this call may vary due to differences in your local time zone's observation of DST/ST from that of the UK.

 Agenda
------

#### BE PREPARED

Things to do before the meeting:

- Review IRI materials for discussion:
  
  
  - Specdev: [https://w3c.github.io/bp-i18n-specdev/#resid\_misc](https://w3c.github.io/bp-i18n-specdev/#resid_misc)
  - RDF-star issue: <https://github.com/w3c/rdf-concepts/issues/15>
  - IRI Status wiki: <https://www.w3.org/International/wiki/IRIStatus>

#### AGENDA

**Topic: Agenda Review**
*Send `agenda+` requests to the public-i18n-core@ list in advance of the meeting!*

**Topic: Action Items**
*Review of open action items from previous meetings*

- [Trackbot](https://www.w3.org/International/track/actions/open)

**Topic: Info Share**
*Share information of interest to the working group or pertaining to internationalization in general.*

**Topic: RADAR Review**
*Time to review new and on-going requests for specification review. Incoming requests are assigned to shepherds in this part of the call.*
*In addition, we review the status of specifications that have received comments. *Please review your issues and owned items in advance of the call**

- [RADAR](https://github.com/w3c/i18n-request/projects/1)

**Topic: Pending Issue Review**
*Review of new and pending issues raised by working group members or via the various bots.*

- [Pending Issues](https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3Apending)

\*\*Topic: Group Meeting at TPAC \*\*
*See description below. We need to decide about how we will participate in TPAC this year*

**Topic: IRIs and the URL spec: what's our policy here?**
*We re-visited our recommendations and the current status last week. Now we need to discuss whether we're happy with our recommendations.*

- Specdev: [https://w3c.github.io/bp-i18n-specdev/#resid\_misc](https://w3c.github.io/bp-i18n-specdev/#resid_misc)
- RDF-star issue: <https://github.com/w3c/rdf-concepts/issues/15>
- IRI Status wiki: <https://www.w3.org/International/wiki/IRIStatus>

**Topic: Update the W3C style guide I18N section?**
*The section about I18N in the W3C style guide might need work...*

- <https://lists.w3.org/Archives/Public/public-i18n-core/2023JanMar/0081.html>
- <https://www.w3.org/Guide/manual-of-style/#I18n>

**Topic: Review proposed changes to accept-language**
*Chrome is thinking of reducing accept-language values on HTTP and in navigator.language so that only the first item is shown and the q list is not. Of course, this comes from security concerns.*

- <https://groups.google.com/a/chromium.org/g/blink-dev/c/yAOfFp7elrw>
- <https://github.com/Tanych/accept-language>

*Richard notes:*

> Seems to me that if you're worried about security you wouldn't add those q lists to your default, rather than clobbering all the multilingual people out there who want accept-language to work as designed.
> What does the group think?

**Topic:** I18N Glossary references
*The I18N Glossary is non-normative (because it is a WG Note) and we need to resolve changes to the instructions on how to use it and its relationship to the normative WHATWG spec "INFRA".*

- [Discussion in this issue](https://github.com/w3c/i18n-glossary/issues/20)
- Proposed text here: <https://github.com/w3c/i18n-glossary/pull/21>

**Topic: AOB?**

- - - - - -

#### REMINDER

Getting too many of these notifications? Read [this](https://lists.w3.org/Archives/Member/member-i18n-core/2022Mar/0013.html) email from Richard on how to manage notifications.

#### SCRIBE

If you are set to scribe and cannot make it, please send regrets to the chair. Volunteers to act as scribe cheerfully accepted.

Fuqiao \[2023-02-09\]
Atsushi \[2023-02-16\]
Felix \[2023-02-23\]
Bert \[2023-03-02\]

#### Chair's Link Farm

<https://www.w3.org/International/track/actions/open>
<https://github.com/w3c/i18n-request/projects/1>
<https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3Apending>

#### TPAC info

TPAC 2023 will be held from 11 to 15 September 2023, with a main in-person hub at Melia Sevilla Hotel, in Sevilla, Spain. As last year, we are adapting our format to a hybrid mode and planning to build a dynamic meeting. Here is the projected schedule (still to be confirmed):

The schedule of the week should be as follows:

- Monday 11 September: Group meetings
- Tuesday 12 September: 
  - Group meetings all day
  - AC plenary sessions in the afternoon
  - Meetup in the late afternoon
- Wednesday 13 September: Breakout sessions
- Thursday 14 September: Group meetings
- Friday 15 September: Group meetings

In order to build a dynamic meeting to bring more cross participation and interactions, we will work this year with set slots. Each group will be able to ask for 90 minute and/or 2-hour slots. If the health situation permits, all groups will break at the same time. The Melia Sevilla hotel has several outside areas, big enough to accommodate all our participants at the same time.

 Joining Instructions
--------------------

 Instructions are restricted to meeting participants. You need to [ log in](https://auth.w3.org/?url=https%3A%2F%2Fwww.w3.org%2Fevents%2Fmeetings%2Fdcb21af5-6796-49aa-9a5c-88b2454316a3%2F20230309T150000%2Fedit) to see them.

 Participants
------------

### Groups

- [Internationalization Working Group](https://www.w3.org/groups/wg/i18n-core) ([View Calendar](https://www.w3.org/groups/wg/i18n-core/calendar))

 Report feedback and issues on [ GitHub](https://github.com/w3c/calendar "W3C Calendar GitHub repository").