BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Sabre//Sabre VObject 4.5.8//EN CALSCALE:GREGORIAN LAST-MODIFIED:20230302T144450Z 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:20230302T144450Z SUMMARY:W3C Internationalization Working Group Teleconference DTSTART;TZID=Europe/London:20230302T150000 DTEND;TZID=Europe/London:20230302T160000 DESCRIPTION:https://www.w3.org/events/meetings/dcb21af5-6796-49aa-9a5c-88b2 454316a3/20230302T150000/\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* Review proposal to add items to the glossary\n\n * https://g ithub.com/w3c/i18n-glossary/issues/22\n\n#### AGENDA\n\n**Topic: Agenda Re view**\n_Send `agenda+` requests to the public-i18n-core@ list in advance of the meeting!_\n\n**Topic: Action Items**\n_Review of open action items from previous meetings_\n* [Trackbot](https://www.w3.org/International/tra ck/actions/open)\n\n**Topic: Info Share**\n_Share information of interest to the working group or pertaining to internationalization in general._\n\ n**Topic: RADAR Review**\n_Time to review new and on-going requests for sp ecification review. Incoming requests are assigned to shepherds in this pa rt of the call._\n_In addition\, we review the status of specifications th at have received comments. *Please review your issues and owned items in a dvance of the call*_\n* [RADAR](https://github.com/w3c/i18n-request/projec ts/1)\n\n**Topic: Pending Issue Review**\n_Review of new and pending issue s raised by working group members or via the various bots._\n* [Pending Is sues](https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+l abel%3Apending)\n\n**Topic: Additions to I18N Glossary (proposal)**\n_Rich ard provided a list of proposed glossary additions. Let's discuss adding t hem._\n* [Proposal](https://github.com/w3c/i18n-glossary/issues/22)\n_In a ddition\, the WHATWG Infra folks have noted some breakage when we both def ine the same terms. We need to discuss how to avoid doing that while provi ding full service to our customers. See this issue for discussion:_\n* htt ps://github.com/w3c/i18n-glossary/issues/20\n\n**Topic: IRIs and the URL s pec: what's our policy here?**\n_We re-visited our recommendations and the current 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 /#resid_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**Topic: Contact Picker API**\n_Atsushi has an issue for us to review_\n\ n* https://github.com/w3c/i18n-activity/issues/1655\n\n**Topic: Bidi named entities in HTML: now what?**\n_HTML has established a firm policy agains t having any new named entities for [reasons](https://github.com/whatwg/ht ml/issues/5121#issuecomment-719406247). Let's discuss._\n\n* https://lists .w3.org/Archives/Public/public-i18n-core/2023JanMar/0080.html\n\n**Topic: Update the W3C style guide I18N section?**\n_The section about I18N in the W3C style guide might need work..._\n\n* https://lists.w3.org/Archives/Pu blic/public-i18n-core/2023JanMar/0081.html\n* https://www.w3.org/Guide/man ual-of-style/#I18n\n\n**Topic: Review proposed changes to accept-language* *\n_Chrome is thinking of reducing accept-language values on HTTP and in n avigator.language so that only the first item is shown and the q list is n ot. Of course\, this comes from security concerns._\n* https://groups.goo gle.com/a/chromium.org/g/blink-dev/c/yAOfFp7elrw\n* https://github.com/Tan ych/accept-language\n\n_Richard notes:_\n> Seems to me that if you're worr ied about security you wouldn't add those q lists to your default\, rather than clobbering all the multilingual people out there who want accept-lan guage to work as designed.\n> What does the group think?\n\n**Topic: WoT P rofile review two draft issues**\n_Atsushi has brought us two issues for r eview!_\n\n* https://github.com/w3c/i18n-activity/issues/1664 (actually\ ,\,\, unclear text on applying UTF-8?)\n* https://github.com/w3c/i18n-acti vity/issues/1665\n\n\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/2022Mar/0013.html) email from Richard on how to m anage notifications.\n\n\n#### SCRIBE \nIf you are set to scribe and canno t make it\, please send regrets to the chair. Volunteers to act as scribe cheerfully accepted.\n\nBert [2023-02-02]\nFuqiao [2023-02-09]\nAtsushi [2 023-02-16]\nFelix [2023-02-23]\n\n#### Chair's Link Farm\nhttps://www.w3.o rg/International/track/actions/open\nhttps://github.com/w3c/i18n-request/p rojects/1\nhttps://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Ao pen+label%3Apending STATUS:CONFIRMED CREATED:20230223T161924Z LAST-MODIFIED:20230302T144450Z 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:20230302T150000 END:VEVENT END:VCALENDAR