RE: Directing issue 240 towards resolution

Hello again all,

I got some coaching from Russell on terminology (thank you!) which I hope I have reflected accurately in my revised version, below. I now have a few more questions for us to go over...

1. Are the changes better? Is it more accurate, and clearer to understand? I couldn't think of how to explain it without adding the briefest of 'terminology' sections.

2. The examples will require a Unicode font that can display Bliss to be rendered properly (the attribute values will contain the glyphs resulting from the Unicode code points for the required Bliss-characters) - is there any way to make this look right on a contemporary system? If the Bliss-containing version of Unicode is not out yet, would it be possible for us to make a screengrab of how the HTML markup (text) will look?

3. We need to come up with examples that fit the criteria (one requiring only one Bliss-character; one requiring two).

4. I've added a note about the registry providing a benefit in terms of localisation to the content author's language. However, I may've over-stepped... I thought that the Unicode character descriptions were only in English, but it seems like there may be translations: <https://stackoverflow.com/questions/47656304/are-there-standardized-translations-of-unicode-character-names> - though not sure how official that is. A search didn't immediately reveal the answer to me.

I think that's it for now. Looking forward to our call.

best regards,


Matthew

==========================================

Hi everyone,

Thanks for your interest, suggestions, and discussion so far. It looks like there is general consensus that it could be possible to use Unicode code points that correspond to Bliss-characters to refer to concepts (i.e. as the `adapt-symbol` attribute's value) - currently the attribute expects Bliss Concept IDs (integers). Let's look at how both of these would be authored.

Here are a couple of examples: in each example, the same content is marked up with Bliss Concept IDs (integers) and with the corresponding Bliss-characters (which would be input via their corresponding Unicode code point(s)).

Very briefly, some terminology:

* A rendered Bliss "symbol" is, in Bliss terms, a Bliss-word.

* A single Bliss-word may be formed of one or more Bliss-characters (there's an example below).

* Therefore, some Bliss concepts will need one Unicode code point, and some will need more than one, to be identified.

It's important to note that the set of Bliss-characters that were added to Unicode is a subset of the Bliss-word set as a whole - thus, some concepts require two Bliss-characters (i.e. two Unicode code points) to be identified. They are still rendered as one visible glyph image - in the same way that Unicode code points can be combined to produce variants on a character/glyph.

**Example 1 (concept requiring a single Bliss-character to identify)**

```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 (single Bliss-character)">cup of tea</span>.</p
 ```

**Example 2 (concept requiring multiple Bliss-characters to identify)**

 ```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 Bliss-characters)">elliptic curve cryptography</span>.</p>
```

We want to make it easy for authors to find the Bliss-characters (code points) that correspond to the concept they want to convey. Remember that the set of Bliss-characters in Unicode is a subset of the whole Bliss-word set, so even looking up info on the code points (which may not be localised to the author's language) will not give them the full set of recognised concepts.

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). We also hope to have the concept descriptions localised into several different languages.

* 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.

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 Monday, 5 February 2024 20:53:12 UTC