BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20250506T145054Z
BEGIN:VTIMEZONE
TZID:Europe/London
X-MICROSOFT-CDO-TZID:1
BEGIN:STANDARD
DTSTART:20241027T010000
TZOFFSETFROM:+0100
TZOFFSETTO:+0000
TZNAME:GMT
END:STANDARD
BEGIN:STANDARD
DTSTART:20251026T010000
TZOFFSETFROM:+0100
TZOFFSETTO:+0000
TZNAME:GMT
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20250330T010000
TZOFFSETFROM:+0000
TZOFFSETTO:+0100
TZNAME:BST
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:a124c8bf-3982-4d0f-8862-7440d677983b
DTSTAMP:20250506T145054Z
SUMMARY:Adapt Symbols Workshop: Implementation Approach Session
DTSTART;TZID=Europe/London:20250506T160000
DTEND;TZID=Europe/London:20250506T170000
DESCRIPTION:https://www.w3.org/events/meetings/a124c8bf-3982-4d0f-8862-7440
 d677983b/\n\nThis is a specific part of the overall [Adapt Symbols Worksho
 p](https://www.w3.org/events/meetings/bbc58010-4239-4aa9-8ef2-3c05344aaed9
 /)\, where we will present a summary of the work (use cases\, implementati
 on requirements) and any specific barriers we foresee.\n\nThe goal is to h
 ighlight any specific barriers we foresee\, how we plan to address them\, 
 and seek feedback on our proposed approaches to doing so.\n\n**Note:** Som
 e important background (in our issue 240\, but recapping): Bliss has an al
 phabet of ~1\,300 characters out of ~7\,000 concepts. The Bliss 'alphabet'
  is proposed for inclusion in Unicode.\n\nWe have a [draft matrix](https:/
 /docs.google.com/spreadsheets/d/19AfygtoQ11uRFu1kBZWuwobKVa8N2GuZzvzDhOVjI
 a4/) detailing the use cases/requirements/issues we've looked at. From thi
 s\, we have the following specific questions that we'd like to cover with 
 you on the call:\n\n* Highlighting our concern around the keying scheme: w
 e intend to provide a dictionary of concepts\, but using Unicode code poin
 ts for Bliss characters is actually keying off the visual presentation of 
 the concepts (we can elaborate on the call\; there is some more detail in 
 the matrix).\n\n* **Additional question:** An alternative approach to inde
 xing off of Bliss spellings (as proposed) would be to put all Bliss concep
 ts as single code points in the PUA - what are the downsides to that?\n\n*
  Overloading of `<ruby>` / are we looking at something like `<ruby symbol>
 `\, or `type` or similar? (Can it work if we are using 'normal' rubies _an
 d_ 'symbol' rubies?)\n\n* What to do if a symbol set font doesn't have a s
 ymbol for a concept that is being used - presumed default behaviour of sho
 wing a blank square/diamond will confuse users.\n\n* Accessible name for r
 endered symbols.\n\n* Technical expertise required to personalise the font
 s vs. cascading a set of fonts - and any fingerprinting risks associated w
 ith both possible approaches.\n\n* Need for multiple `<rt>`s per `<ruby>` 
 (laid out appropriately).\n\n   - **Update:** After further research last 
 night\, we found that this does appear to be possible (including having th
 e rendered symbols horizontally laid out).\n\n   - **Additional question:*
 * We found from our meeting with AAC experts that putting the symbol inlin
 e-prior to the text being summarised by the symbol can be of help (in addi
 tion to the\, we think\, more prevalent positioning of the symbol _above_ 
 the text to which it relates). We need to make this easy for authors (need
  to check it can be easily done via CSS).\n\n**Note:** Our matrix is a dra
 ft\, and we are currently down one technical member of the group due to il
 lness alas\, so we still have some issues to look into amongst ourselves f
 irst (as noted in the matrix).\n\nAgenda: https://github.com/w3c/adapt/wik
 i/2025%E2%80%9005-Face-to-face-meeting#day-2---2025-05-06-tuesday
STATUS:CONFIRMED
CREATED:20250430T231130Z
LAST-MODIFIED:20250506T145054Z
SEQUENCE:0
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=WAI Adapt Task For
 ce:mailto:public-adapt@w3.org
END:VEVENT
END:VCALENDAR
