- From: lisa.seeman <lisa.seeman@zoho.com>
- Date: Mon, 29 Jul 2019 13:20:29 +0300
- To: "public-personalization-tf" <public-personalization-tf@w3.org>, "orish88" <orish88@gmail.com>
- Message-Id: <16c3d3d0c88.d8a445b5373130.8885250356441300913@zoho.com>
Hi folks basic proposal /summary of were we are: We seem to agree on using bic number as the standard reference mechanism for each concept common in symbols . for example data-symbol ="10230" A standard reference mechanism could be the number user by bliss or the common term for the concept for very commen concepts. This is like using a number for the color in CSS but you can also say "green" or another term for a limited set of very common colours. We could include the most common x term now or leave that to a separate module. references http://www.blissymbolics.net/BCI-AV_list_eng_2018-02.html with some translations at http://www.blissymbolics.org/BlissResources/Documentation/BCI-AV_2017-11-17_(en+sv+hu+de)+deriv_symbols_(bg-col).pdf Follow on proposals: If we are agreeing on the basic concept of using the bic numbers 1. Items that speed up the authoring process and make it more scalable can be moved to a seprate module. this could included: terms (or more terms) that replace very common concepts a way to associate new symbol(s) with the reference mechanism in a mapping file (phase 2 for scalability for authors if the content provider is using their own symbols?) a way to reference a mapping file to use in the content (phase 2 for scalability for authors if the content provider is using their own symbols?) 2. Are we happy with the term data-symbol (I get the impression that we are) Could data-symbol merge this with data-action ? 3. we also have to check any patent issues involved with bliss. All the best Lisa Seeman http://il.linkedin.com/in/lisaseeman/, https://twitter.com/SeemanLisa
Received on Monday, 29 July 2019 10:21:05 UTC