Meeting minutes
<janina> Date -d 13 Jan 2026
Symbols
matatk: We intend to use Ruby for rendering
… that drove the potential need to differentiate between our use of Ruby and others' use
… there was a proposal for Ruby to have a 'type'
… as some Ruby was providing pronunciation and some Ruby was providing characters
… Pronunciation is intended to be read by the TTS (text to speech)
… but TTS's are not currently able to read and interpret such a signal
… there was discussion, then, on the introduction of such a 'type'
janina: Ruby was under-specified
… there was this built-in conflict that they had failed to address
… For clarity, this 'type' discussion has nothing to do with Adapt's use case regarding Ruby
… though there is overlap with APA WG, which is interested in Pronunciation
matatk: Florian who is proposing the Ruby 'type' attribute as already discussed
… is not indicating our need
… but to meet our needs, we do not require using 'type'
… our explainer will propose the use of lang=zbl
Discoverable Destinations
<matatk> From last time: https://
<matatk> Proposed destinations: https://
Lionel_Wolberger: The Adapt Project document is now viewable by anyone with the link
… https://
<matatk> Proposed destinations (including closed ones): https://
matatk: Leave 'sub-site' for later
Lionel_Wolberger: 'terms' sounds really strong to me, most every website has T&C for the website
… though there is sometimes confusion, as people seek the T&C of software sold on the site, and not the T&C of the site
… some companies have merged all of these
Lionel_Wolberger: Discussion is in the github issue
… we are on issue 316, social: w3c/
janina: It would be great to have an ability to hide buttons, like the 'like' button.
matatk: Contact us is a DD