- From: Matthew Atkinson <m.atkinson@samsung.com>
- Date: Tue, 16 Jan 2024 11:28:31 -0000
- To: "'Adapt tf'" <public-adapt@w3.org>
Hi all, As we discussed on our last call, I have written a proposed comment to add to issue 240, to tease out: acceptance (or otherwise) of using Unicode in the attribute value; and to raise awareness of authoring concerns, and what we're doing about those. I've included the proposed message directly below. Four things we need to address - the first two of which depends specifically on Russell's expertise... 0. I've really tried to use correct/clear terminology, but it definitely needs review! 1. Finding examples that suitably demonstrate the different mark-up outcomes (i.e. single vs multiple glyphs needing to be composed, in some cases) - and whether/how we can accurately include those in the example. Whilst I wrote "multiple glyphs" below, I suppose they'd actually combine (as intended) and just look like one glyph in the end. Thus, maybe we will have to put HTML comments in the mark-up examples, to say something like "this apparently single glyph in the attribute value was composed of the following Unicode code points" - with apologies for any incorrect terminology. 2. I _know_ we've discussed this before, but we're approaching last call on this: do we want `adapt-symbol`, or `adapt-concept`? We should check our last discussion of it, to ensure we still feel the same. I can see good arguments for both, which we probably went over last time :-). 3. I could do with slightly more time to fix bugs in the authoring tool, but we should get this out when we can (i.e. I'll be quick, or I'll apologise for any remaining issues with it :-)). Here is my proposed comment (in Markdown)... --- Hi everyone, Thanks for your interest, suggestions, and discussion so far. It looks like there is general acceptance that it could be possible to use Unicode glyphs to refer to concepts (i.e. as the `adapt-symbol` attribute's value), where we currently have Bliss Concept IDs (integers). Let's look at how both of these would be authored. Here are a couple of examples, of the same content, marked up with Bliss Concept IDs (integers) and with the corresponding Unicode glyphs. It's important to note that the set of Bliss glyphs that were added to Unicode is a subset of the Bliss symbol set as a whole-thus, some concepts require two Unicode glyphs (which add up to one Bliss symbol) **Example 1 (something that requires only one glyph)** ```html <p>Here is some text about a <span adapt-symbol="FIXME (integer)">cup of tea</span>.</p> <p>Here is some text about a <span adapt-symbol="FIXME (glyph)">cup of tea</span>.</p> ``` **Example 2 (something that requires multiple glyphs)** ```html <p>Here is some text about a <span adapt-symbol="FIXME (integer)">elliptic curve cryptography</span>.</p> <p>Here is some text about a <span adapt-symbol="FIXME (multiple glyphs)">elliptic curve cryptography</span>.</p> ``` Note that, because with the Unicode variant, multiple glyphs may be needed to mark up a single concept. In order to assist content authors, we have two things to add: * We have a [W3C Registry spec that enumerates all known concepts, and their corresponding Bliss Concept IDs](https://www.w3.org/TR/aac-registry/)-this can be updated to include the Unicode glyph(s) that also identify the concept (by way of forming the Bliss symbol for it). * I made a (still slightly buggy!) [prototype authoring tool](https://matatk.agrip.org.uk/adaptable-content-authoring-tool/editor/) that naively demonstrates how the authoring process might work (it only supports Bliss symbols for rendering). We're very interested as to your views on this, both implementation concerns, and any thoughts you may have on the authoring side of things. --- Let's talk about it on the call later? Best regards, Matthew Atkinson Head of Web Standards Samsung R&D Institute UK Samsung Electronics +44 7733 238 020 Samsung R&D Institute (SRUK), Communications House, South Street, Staines-upon-Thames, Surrey, TW18 4QE. A division of Samsung Electronics (UK) Limited, a limited company registered in England and Wales with registered number 03086621 and whose registered address is Samsung House, 2000 Hillswood Drive, Chertsey, Surrey, KT16 0RS, UK. This email (including any attachments) is private and confidential, and may be privileged. It is for the exclusive use of the intended recipient(s). If you have received this email in error, please inform the sender immediately and then delete this email. Unless you have been given specific permission to do so, please do not distribute or copy this email or its contents. Unless the text of this email specifically states that it is a contractual offer or acceptance, the sender does not intend to create a legal relationship and this email shall not constitute an offer or acceptance which could give rise to a contract. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be the views of Samsung.
Received on Tuesday, 16 January 2024 11:28:49 UTC