Re: symbols - was Re: Data-* Attributes (Take 2)

 > As an alternative, I suggest that data-symbol attribute only serve as a
 > **hint* *to a symbol, in those cases when a specific symbol is not
 > already present on the end-users computer (i.e. it is/would-be a
 > fall-back symbol).

Symbols get complicated! Both in which symbol sets a user has and 
prefers and how (if) they can be accessed from a web browser on behalf 
of a website.

It is probably worth mentioning at this point that there has been 
considerable work on Concept Coding Frameworks (CCF) for symbols. The 
idea being a given concept maps to multiple symbols, eg alternative 
symbol sets, localised symbols etc. Note, the Bliss set is a little 
different as it's a language for building symbols.

Mats Lundälv has been driving CCF and Bliss in recent years. The latest 
incarnation of CCF is the Global Symbols project 
https://globalsymbols.com/ (EA Draffan)

Thus it might be better to specify the symbols 'concept' in the enhanced 
personalisation markup and something external maps that to the preferred 
symbols, as John describes. That something external may be the browser 
UA, plugins, the platform OS or AT.

This seem a closer fit the general approach being taken to 
personalisation- ie adding clues in enhanced markup which are mapped 
based on the users preferences that set on the device rendering the 
content. Not specifying exact content (eg a specific symbol) in the markup.

I recently took over the Mulberry Symbol Set 
https://mulberrysymbols.org/. It's now even more web-friendly as SVG is 
so much better supported, eg in <img> and easy to embed inline :). I've 
been trying to determine how symbols are used in order to make them 
available in the most suitable ways. So far, I don't have a clear 
picture other than for AAC devices where supporters tend to load up all 
the most useful symbols and select from them as required in 
communication charts.

Thus, I guess there's a lot to be figured out re symbols and personalisation

Steve


On 02/04/2019 15:05, John Foliot wrote:
> Hi Lisa,
> 
> On my proposal page 
> <https://github.com/w3c/personalization-semantics/wiki/Prototypes-with-data-dash-*-(Take-2)#attribute-to-provide-symbols-goal-images-to-replace-on-screen-text>, 
> I am suggesting that, yes, in fact we can likely get symbols simply via 
> the _various token values_ we've declared for data-action, data-purpose, 
> and data-destination: symbol sets will need to map-to (or otherwise 
> align with) the tokens we've documented.
> 
> As an alternative, I suggest that data-symbol attribute only serve as a 
> **hint* *to a symbol, in those cases when a specific symbol is not 
> already present on the end-users computer (i.e. it is/would-be a 
> fall-back symbol).
> 
> Make sense?
> 
> JF
> 
> 
> On Tue, Apr 2, 2019 at 4:00 AM lisa.seeman <lisa.seeman@zoho.com 
> <mailto:lisa.seeman@zoho.com>> wrote:
> 
>     __
>     I am wondering if we can use  purpose also for symbols? they are
>     very similar and we are trying to merge were we can.
> 
>     All the best
> 
>     Lisa Seeman
> 
>     LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter
>     <https://twitter.com/SeemanLisa>
> 
> 
> 
>     ---- On Tue, 02 Apr 2019 00:53:14 +0300 *James Cambron
>     <james.cambron@outlook.com <mailto:james.cambron@outlook.com>>*
>     wrote ----
> 
>         Most of what John has included is along the lines with my
>         thinking as well. It isn't clear which use cases I added to the
>         original prototype document but they were:
> 
>           * |<button data-action="undo">Revert</button>|
>           * |<a href="home.html" data-destination="homepage">our main
>             page</a>|
> 
> 
>         Best,
>         Thad
> 
>         ------------------------------------------------------------------------
> 
>         *From:* John Foliot <john.foliot@deque.com
>         <mailto:john.foliot@deque.com>>
>         *Sent:* Monday, April 1, 2019 2:13 PM
>         *To:* public-personalization-tf
>         *Subject:* Data-* Attributes (Take 2)
> 
>         Hi all,
> 
>         After today's conference call I have some very serious concerns
>         on how this is moving forward. Rather than augmenting the
>         current examples, I have instead provided an alternative
>         proposal on how to move forward, building upon existing
>         consensus (as I understand it).
> 
>         Please see:
>         https://github.com/w3c/personalization-semantics/wiki/Prototypes-with-data-dash-*-(Take-2)
>         <https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fpersonalization-semantics%2Fwiki%2FPrototypes-with-data-dash-*-(Take-2)&data=02%7C01%7C%7C157f284c154249f9080508d6b6e6fae8%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636897500497105237&sdata=sKo6jGzNbczIuahE1NJC2%2BkmdWtg%2F3qio6s%2BMpcXsjI%3D&reserved=0>
> 
>         JF
>         --
> 
>         *John Foliot* | Principal Accessibility Strategist | W3C AC
>         Representative
>         Deque Systems - Accessibility for Good
>         deque.com
>         <https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdeque.com%2F&data=02%7C01%7C%7C157f284c154249f9080508d6b6e6fae8%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636897500497115245&sdata=1OHNaeCS63OaOpVyIinh8yiMLH0ddNa98tWrXKCQW8U%3D&reserved=0>
> 
> 
> 
> 
> 
> -- 
> *​John Foliot* | Principal Accessibility Strategist | W3C AC Representative
> Deque Systems - Accessibility for Good
> deque.com <http://deque.com/>
>

Received on Monday, 8 April 2019 10:28:06 UTC