BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20230830T215216Z
BEGIN:VTIMEZONE
TZID:Europe/London
X-MICROSOFT-CDO-TZID:1
BEGIN:STANDARD
DTSTART:20221030T010000
TZOFFSETFROM:+0100
TZOFFSETTO:+0000
TZNAME:GMT
END:STANDARD
BEGIN:STANDARD
DTSTART:20231029T010000
TZOFFSETFROM:+0100
TZOFFSETTO:+0000
TZNAME:GMT
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20230326T010000
TZOFFSETFROM:+0000
TZOFFSETTO:+0100
TZNAME:BST
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:c5b143d1-0a5b-4adb-8d60-0f5f9bfe5a41
DTSTAMP:20230830T215216Z
SUMMARY:W3C Internationalization Working Group Teleconference
DTSTART;TZID=Europe/London:20230831T150000
DTEND;TZID=Europe/London:20230831T160000
DESCRIPTION:https://www.w3.org/events/meetings/c5b143d1-0a5b-4adb-8d60-0f5f
 9bfe5a41/20230831T150000/\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\n(This e
 vent has a new access number/link beginning 11 May 2023)\n\nAgenda\n\n####
  BE PREPARED \nThings to do before the meeting:\n\n\n#### AGENDA\n\n**Topi
 c: Agenda Review**\n_Send `agenda+` requests to the public-i18n-core@ list
  in advance of the meeting!_\n\n**Topic: Action Items**\n_Review of open a
 ction items from previous meetings_\n* [I18N-ACTIONS](https://github.com/w
 3c/i18n-actions/issues)\n\n**Topic: Info Share**\n_Share information of in
 terest to the working group or pertaining to internationalization in gener
 al._\n\n**Topic: RADAR Review**\n_Time to review new and on-going requests
  for specification review. Incoming requests are assigned to shepherds in 
 this part of the call._\n_In addition\, we review the status of specificat
 ions that have received comments. *Please review your issues and owned ite
 ms 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 pendin
 g issues raised by working group members or via the various bots._\n* [Pen
 ding Issues](https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3
 Aopen+label%3Apending)\n\n**Topic: TPAC Planning**\n_Are we ready for TPAC
 ? Let's review the schedule and our agenda_\n* https://github.com/w3c/i18n
 -actions/wiki/2023-TPAC-Planning\n\n**Topic: WCAG 2.2**\n_Review the statu
 s of their work in addressing our comments._\n\n**Topic: Backwards Deletio
 n**\n_Is this document ready for a wider review?_\n* https://aphillips.git
 hub.io/i18n-drafts/questions/qa-backwards-deletion.en.html\n* https://list
 s.w3.org/Archives/Public/public-i18n-core/2023JulSep/0103.html\n\n**Topic:
  string definitions in RDF**\n_RDF is struggling to find a definition for 
 "Unicode string" that fits their needs. Addison has made some suggestions\
 , but notes that we don't provide a string definition. In addition\, there
  is the problem that Charmod-norm doesn't provide the specific "code unit 
 vs. code point" performance out being discussed here._\n* [RDF issue](http
 s://github.com/w3c/rdf-concepts/issues/51)\n* [RDF pull request](https://g
 ithub.com/w3c/rdf-concepts/issues/59)\n* https://lists.w3.org/Archives/Pub
 lic/public-i18n-core/2023JulSep/0105.html\n* [definition discussion](https
 ://github.com/w3c/rdf-concepts/issues/51#issuecomment-1699884210)\n\n**Top
 ic: Is `@context` in JSON bad?**\n_The Verifiable Credentials folks are wo
 rking to address our request for lang/dir metadata on the `name` and `desc
 ription` (natural language text) fields. They claims that using `@language
 ` in the `@context` is bad._\n* [Addison's comment](https://github.com/w3c
 /vc-data-model/pull/1252#discussion_r1309397665)\n* [Issue](https://github
 .com/w3c/vc-data-model/issues/1264)\n* https://lists.w3.org/Archives/Publi
 c/public-i18n-core/2023JulSep/0106.html\n\n**Topic: AOB?**\n\n---\n\n#### 
 REMINDER \nGetting too many of these notifications? Read [this](https://li
 sts.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 regrets to the chair. Volunteer
 s to act as scribe cheerfully accepted.\n\n(rota)\n\n#### Chair's Link Far
 m\nhttps://github.com/w3c/i18n-actions/issues\nhttps://github.com/w3c/i18n
 -request/projects/1\nhttps://github.com/w3c/i18n-activity/issues?q=is%3Ais
 sue+is%3Aopen+label%3Apending
STATUS:CONFIRMED
CREATED:20230829T174910Z
LAST-MODIFIED:20230830T215216Z
SEQUENCE:10
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:20230831T150000
END:VEVENT
END:VCALENDAR