BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20230222T204942Z
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:20230222T204942Z
SUMMARY:W3C Internationalization Working Group Teleconference
DTSTART;TZID=Europe/London:20230223T150000
DTEND;TZID=Europe/London:20230223T160000
DESCRIPTION:https://www.w3.org/events/meetings/dcb21af5-6796-49aa-9a5c-88b2
 454316a3/20230223T150000/\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 [string
 -search](https://w3c.github.io/string-search/) for potential FPWD status\n
 \n* Refresh your memory of the status of IRIs\n   * [RDF Concepts #15](htt
 ps://github.com/w3c/rdf-concepts/issues/15) raises the issue again\n   * [
 IRIStatus](https://www.w3.org/International/wiki/IRIStatus)\n\n* Review Ri
 chard's proposed definitions for ijam and taskkil\n   * [ijam](https://r12
 a.github.io/scripts/glossary/#ijam)\n   * [tashkil](https://r12a.github.io
 /scripts/glossary/#tashkil)\n\n* Review PR of qa-bidi-unicode\n   * https:
 //github.com/w3c/i18n-drafts/pull/449\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: I18N ⇔ CSS**\n_Anything to discuss?_\n\n* [M
 inutes of 2023-02-21](https://www.w3.org/2023/02/21-i18n-minutes.html)\n\n
 **Topic: ijam/tashkil definitions**\n_Review Richard's proposed new defini
 tions and approve (if appropriate) their incorporation into i18n-glossary_
 \n\n* [Richard's email](https://lists.w3.org/Archives/Public/public-i18n-c
 ore/2023JanMar/0062.html)\n* Proposed definitions [ijam](https://r12a.gith
 ub.io/scripts/glossary/#ijam) [tashkil](https://r12a.github.io/scripts/glo
 ssary/#tashkil)\n\n**Topic: Use of\, for example\, e.g. and i.e. in specs*
 *\n_Richard found folks saying we have a policy against `i.e.` and `e.g.`.
  Let's decide if we do!_\n\n* https://lists.w3.org/Archives/Public/public-
 i18n-core/2023JanMar/0065.html\n\n**Topic: Review rewrite of qa-bidi-unico
 de**\n_Richard provided a rewrite in support of his action item. Let's rev
 iew for publication_\n\n* https://github.com/w3c/i18n-drafts/pull/449\n\n*
 *Topic: Publish string-search as first public?**\n_Our document about stri
 ng-search is not in the W3C's TR space. Should we publish it as first publ
 ic\, even though we do not intend to finish it anytime soon..._\n\n* Edito
 r's copy: https://w3c.github.io/string-search/\n\n**Topic: IRIs and the UR
 L spec: what's our policy here?**\n_ RDF has raised the issue of how to re
 ference IRIs. This has been a long-standing potential issue\, given that t
 he URL spec is laser-focused on browser processing of URLs and there remai
 n some quirks in the URI/IRI space. Eight (**!!**) years ago I wrote the w
 iki linked as IRIStatus below. Note that we also have [whatwg/html#4562] o
 utstanding about EAI left-hand-side and probably some assorted other bits.
  Let's discuss!_\n\n* [RDF Concepts #15](https://github.com/w3c/rdf-concep
 ts/issues/15) raises the issue again\n* [IRIStatus](https://www.w3.org/Int
 ernational/wiki/IRIStatus)\n\n**Topic: Terms from \\*LREQ for Glossary?**\
 n_Richard compiled a list of terms that might be needed in the glossary. H
 olding a slot for discussing_\n\n* [Richard's email and my reply](https://
 lists.w3.org/Archives/Public/public-i18n-core/2023JanMar/0055.html)\n\n**T
 opic: AOB?**\n\n---\n\n#### REMINDER \nGetting too many of these notificat
 ions? Read [this](https://lists.w3.org/Archives/Member/member-i18n-core/20
 22Mar/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 reg
 rets to the chair. Volunteers to act as scribe cheerfully accepted.\n\nFel
 ix [2022-10-20]\nBert [2023-02-02]\nFuqiao [2023-02-09]\nAtsushi [2023-02-
 16]\n\n#### Chair's Link Farm\nhttps://www.w3.org/International/track/acti
 ons/open\nhttps://github.com/w3c/i18n-request/projects/1\nhttps://github.c
 om/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3Apending
STATUS:CONFIRMED
CREATED:20230216T165715Z
LAST-MODIFIED:20230222T204942Z
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:20230223T150000
END:VEVENT
END:VCALENDAR