Meeting minutes
<janina> ppresent+
Introductions. Updates.
Symbols
matatk: Note Adapt TF did get the TPAC meetings that we have asked for: (1) Session with WHAT-WG
… to cover the Ruby implementation issues
… suggesting adding a 'type' element
… and (2) COGA meeting to discuss items that were under the Personalization umbrella
… still considering (3) meeting with CSS regarding media queries, but since this is Adapt Roadmap, we may not request that meeting
janina: We should consider a breakout for 'show and tell'
… of the revised prototype
… and support a socializing agenda, looking for implementation commitments
Lionel: Matthew is taking the action item, to go to COGA planning and get a meeting prior to TPAC
matatk: The COGA item will require the new WKD prototype to be working with the new approach
matatk: COGA's persistent request regarding WKD is understanding what will appear on the WKD
… e.g., if it says help, what kind of hlep
… does the WKD procedure need to already future-proof for that ability, to cite what kind of content will be on the WKD
Symbols (actually)
<matatk> Draft PR (still working on it) to update explainer post-workshop: w3c/
<gb> Pull Request 323 Symbols explainer post-workshop (by matatk)
Lionel: (Reading the introduction for group editing)
janina: Add an indicator on the reason we chose BCI: Long used by people committed to symbolic communication
… add a hyperlink
matatk: edit, 'We're working closely with BCI on this approach, which broadly speaking is comprised of the following:'
matatk: No need for a link to the registry below, as each of these bullets has a section below.
Lionel: (Discussing the order of the bullets)
Ruby Considerations
Russell: I found that CJK languages have homographs
… a single symbol can have multiple meanings
… a similar example in Roman characters would be 'lead' which can be 'to lead' (pronounced leed) or 'the element lead' (pronounced led)
… i also note the i18n objection to our use of ruby
… WIth my knowledge of coding, adding an attribute seems to be of similar difficulty to adding a new attribute, say 'adapt-symbol', which under the hood points to the same ruby code
… I am aware that perhaps adding a new HTML element has its own challenges
matatk: If I translate, you are saying-- the use case is, can this approach support adding a symbol to a japanese word?
… in other words, can you use 'ruby' on an element that already has 'ruby'?
… the other issue to my mind is, 'overloading'
… they feel 'ruby' has not been used enough, it is isolated to CJK
… I personally like having a seperate element
… I advocate that author's needs should come before the developers' needs
janina: If we really decide we want to advocate for a seperate element
… we need a real insider develoepr from Google perhaps, who can advocate for this
… we, as designers, cannot really opine that a seperate element is simpler
Russell: Ruby on ruby, I believe you can do that. Not sure about three layers, which could occur
janina: We need to test for that
Russell: I believe it will it