BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20230306T163314Z
BEGIN:VTIMEZONE
TZID:Europe/London
X-MICROSOFT-CDO-TZID:1
BEGIN:DAYLIGHT
DTSTART:20220327T010000
TZOFFSETFROM:+0000
TZOFFSETTO:+0100
TZNAME:BST
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20230326T010000
TZOFFSETFROM:+0000
TZOFFSETTO:+0100
TZNAME:BST
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20221030T010000
TZOFFSETFROM:+0100
TZOFFSETTO:+0000
TZNAME:GMT
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:dcb21af5-6796-49aa-9a5c-88b2454316a3
DTSTAMP:20230306T163314Z
SUMMARY:W3C Internationalization Working Group Teleconference
DTSTART;TZID=Europe/London:20230309T150000
DTEND;TZID=Europe/London:20230309T160000
DESCRIPTION:https://www.w3.org/events/meetings/dcb21af5-6796-49aa-9a5c-88b2
 454316a3/20230309T150000/\n\n***NOTE WELL*** This meeting is scheduled in 
 the `Europe/London` time zone. That time zone observes Daylight Savings/Su
 mmer Time. Your local time for this call may vary due to differences in yo
 ur local time zone's observation of DST/ST from that of the UK.\n\nAgenda\
 n\n#### BE PREPARED \nThings to do before the meeting:\n\n* Review IRI mat
 erials for discussion:\n\n   * Specdev: https://w3c.github.io/bp-i18n-spec
 dev/#resid_misc\n   * RDF-star issue: https://github.com/w3c/rdf-concepts/
 issues/15\n   * IRI Status wiki: https://www.w3.org/International/wiki/IRI
 Status\n\n#### AGENDA\n\n**Topic: Agenda Review**\n_Send `agenda+` request
 s to the public-i18n-core@ list in advance of the meeting!_\n\n**Topic: Ac
 tion Items**\n_Review of open action items from previous meetings_\n* [Tra
 ckbot](https://www.w3.org/International/track/actions/open)\n\n**Topic: In
 fo Share**\n_Share information of interest to the working group or pertain
 ing to internationalization in general._\n\n**Topic: RADAR Review**\n_Time
  to review new and on-going requests for specification review. Incoming re
 quests are assigned to shepherds in this part of the call._\n_In addition\
 , we review the status of specifications that have received comments. *Ple
 ase review your issues and owned items in advance of the call*_\n* [RADAR]
 (https://github.com/w3c/i18n-request/projects/1)\n\n**Topic: Pending Issue
  Review**\n_Review of new and pending issues raised by working group membe
 rs or via the various bots._\n* [Pending Issues](https://github.com/w3c/i1
 8n-activity/issues?q=is%3Aissue+is%3Aopen+label%3Apending)\n\n**Topic: Gro
 up Meeting at TPAC**\n_See description below. We need to decide about how 
 we will participate in TPAC this year_\n\n**Topic: IRIs and the URL spec: 
 what's our policy here?**\n_We re-visited our recommendations and the curr
 ent status last week. Now we need to discuss whether we're happy with our 
 recommendations._\n\n* Specdev: https://w3c.github.io/bp-i18n-specdev/#res
 id_misc\n* RDF-star issue: https://github.com/w3c/rdf-concepts/issues/15\n
 * IRI Status wiki: https://www.w3.org/International/wiki/IRIStatus\n\n**To
 pic: Update the W3C style guide I18N section?**\n_The section about I18N i
 n the W3C style guide might need work..._\n\n* https://lists.w3.org/Archiv
 es/Public/public-i18n-core/2023JanMar/0081.html\n* https://www.w3.org/Guid
 e/manual-of-style/#I18n\n\n**Topic: Review proposed changes to accept-lang
 uage**\n_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._\n* https://group
 s.google.com/a/chromium.org/g/blink-dev/c/yAOfFp7elrw\n* https://github.co
 m/Tanych/accept-language\n\n_Richard notes:_\n> Seems to me that if you're
  worried about security you wouldn't add those q lists to your default\, r
 ather than clobbering all the multilingual people out there who want accep
 t-language to work as designed.\n> What does the group think?\n\n**Topic: 
 I18N Glossary references**\n_The I18N Glossary is non-normative (because i
 t 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"._\n\n*
  [Discussion in this issue](https://github.com/w3c/i18n-glossary/issues/20
 )\n* Proposed text here: https://github.com/w3c/i18n-glossary/pull/21\n\n*
 *Topic: AOB?**\n\n---\n\n#### REMINDER \nGetting too many of these notific
 ations? Read [this](https://lists.w3.org/Archives/Member/member-i18n-core/
 2022Mar/0013.html) email from Richard on how to manage notifications.\n\n\
 n#### SCRIBE \nIf you are set to scribe and cannot make it\, please send r
 egrets to the chair. Volunteers to act as scribe cheerfully accepted.\n\nF
 uqiao [2023-02-09]\nAtsushi [2023-02-16]\nFelix [2023-02-23]\nBert [2023-0
 3-02]\n\n#### Chair's Link Farm\nhttps://www.w3.org/International/track/ac
 tions/open\nhttps://github.com/w3c/i18n-request/projects/1\nhttps://github
 .com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3Apending\n\n##
 ## TPAC info\n\nTPAC 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):
 \n\nThe schedule of the week should be as follows:\n\n* Monday 11 Septembe
 r: Group meetings\n* Tuesday 12 September: \n   * Group meetings all day\n
    * AC plenary sessions in the afternoon\n   * Meetup in the late afterno
 on\n* Wednesday 13 September: Breakout sessions\n* Thursday 14 September: 
 Group meetings\n* Friday 15 September: Group meetings\n\nIn 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.
STATUS:CONFIRMED
CREATED:20230306T163224Z
LAST-MODIFIED:20230306T163314Z
SEQUENCE:9
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Internationalizati
 on Working Group:mailto:public-i18n-core@w3.org
LOCATION:Location: https://www.w3.org/2017/09/i18n-meeting-info.html
RECURRENCE-ID;TZID=Europe/London:20230309T150000
END:VEVENT
END:VCALENDAR