BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20240325T212405Z
BEGIN:VTIMEZONE
TZID:Europe/London
X-MICROSOFT-CDO-TZID:1
BEGIN:STANDARD
DTSTART:20231029T010000
TZOFFSETFROM:+0100
TZOFFSETTO:+0000
TZNAME:GMT
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20240331T010000
TZOFFSETFROM:+0000
TZOFFSETTO:+0100
TZNAME:BST
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:6d544156-352c-46f2-b6ec-383b4e2462fb
DTSTAMP:20240325T212405Z
SUMMARY:Internationalization (I18N) WG Teleconference
DTSTART;TZID=Europe/London:20240328T150000
DTEND;TZID=Europe/London:20240328T160000
DESCRIPTION:https://www.w3.org/events/meetings/6d544156-352c-46f2-b6ec-383b
 4e2462fb/20240328T150000/\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***WHAT
  IS THIS?*** This is the regular weekly teleconference of the W3C Internat
 ionalization Working Group.\n\n***AGENDA+*** If you would like the chair t
 o consider adding an item to the agenda\, please send email to the public-
 i18n-core@ mailing list with a subject line starting `agenda+`. Here is an
  [example](https://lists.w3.org/Archives/Public/public-i18n-core/2023OctDe
 c/0007.html).\n\nAgenda\n\n#### BE PREPARED \nThings to do before the meet
 ing:\n\n* Read this section of the proposed changes to String-Meta: https:
 //deploy-preview-86--string-meta.netlify.app/#bp-producers\n* Review this 
 PR with proposed changes related to IDNs: https://github.com/w3c/bp-i18n-s
 pecdev/pull/128 \n\n#### AGENDA\n\n**Topic: Agenda Review**\n\n**Topic: Ac
 tion Items**\n_Review of open action items from previous meetings_\n* [I18
 N-ACTIONS](https://github.com/w3c/i18n-actions/issues)\n\n**Topic: Info Sh
 are**\n_Share information of interest to the working group or pertaining t
 o internationalization in general._\n\n**Topic: RADAR Review**\n_Time to r
 eview new and on-going requests for specification review. Incoming request
 s are assigned to shepherds in this part of the call._\n_In addition\, we 
 review the status of specifications that have received comments. *Please r
 eview your issues and owned items in advance of the call*_\n* [RADAR](http
 s://github.com/w3c/i18n-request/projects/1)\n\n**Topic: Pending Issue Revi
 ew**\n_Review of new and pending issues raised by working group members or
  via the various bots._\n* [Pending Issues](https://github.com/w3c/i18n-ac
 tivity/issues?q=is%3Aissue+is%3Aopen+label%3Apending)\n\n**Topic: FPWD of 
 Khmer Layout Requirements**\n_Richard is seeking approval of a first publi
 c working draft of a new LREQ document for Khmer._\n* https://lists.w3.org
 /Archives/Public/public-i18n-core/2024JanMar/0108.html\n\n**Topic: RFC9457
  and string-meta**\n_Verifiable Credentials filed a PR [2] that references
  RFC9457 in response to our comment [1]. _\n   * _RFC9457 defines a JSON (
 and alternate XML) structure for returning error information. Seems like t
 hey could follow our guidance in string-meta and include lang/dir metadata
  in the document. They do provide for localization *externally* by doing l
 anguage negotiation off of Accept-Language\, but it seems criminal not to 
 tell the recipient what language was negotiated??_\n   * _We should update
  specdev to include guidance about this._\n   * _I made a comment on VC's 
 specific text that this group should review._\n* https://lists.w3.org/Arch
 ives/Public/public-i18n-core/2024JanMar/0110.html\n* [1] https://github.co
 m/w3c/vc-bitstring-status-list/issues/140\n* [2] https://github.com/w3c/vc
 -bitstring-status-list/pull/152\n\n**Topic: String-meta best practices for
  producers**\n_The section "Guidance for Producers" was added to the PR. L
 et's review._\n* https://github.com/w3c/string-meta/pull/86\n* https://dep
 loy-preview-86--string-meta.netlify.app/#bp-producers\n\n**Topic: Specdev 
 changes to support IDNs**\n_Per last week's call\, review Fuqiao's work fo
 r inclusion this week_\n* https://github.com/w3c/bp-i18n-specdev/pull/128\
 n* https://deploy-preview-128--bp-i18n-specdev.netlify.app/#idn\n\n**Topic
 : AOB?**\n\n---\n\n#### REMINDER \nGetting too many of these notifications
 ? Read [this](https://lists.w3.org/Archives/Member/member-i18n-core/2022Ma
 r/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. Volunteers to act as scribe cheerfully accepted.\n\nAtsushi
 \n[2024-03-14] Fuqiao\n[2024-03-21] Bert\n\n#### Chair's Link Farm\nhttps:
 //github.com/w3c/i18n-actions/issues\nhttps://github.com/w3c/i18n-request/
 projects/1\nhttps://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3A
 open+label%3Apending
STATUS:CONFIRMED
CREATED:20240322T134204Z
LAST-MODIFIED:20240325T212405Z
SEQUENCE:2
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:20240328T150000
END:VEVENT
END:VCALENDAR