Meeting minutes
Introductions, Logistics
Lionel_Wolberger: Hearing none, moving on to the face to face
Face to Face Planning
janina: Responses to invitations
Russell: Matthew's referring to what I have as a use case, but I do not find that label quite covers what I am doing
Annalu: Bliss symbolics is a language that can also be used or described as a symbol set
… Unicode is a means by which some of the Bliss symbols, or images, can be translated into characters
janina: We need to decide what session we want Anne in, and what session we want EA in. They are not the same topics
Annalu: A primary focus of our work is this task: converting a symbol set into unicode code points
Russell: I reiterate, Bliss/Unicode is a proposal only
… its implementation differs in significant ways from any other symbol set representation in Unicode
… Bliss has multiple code points per image (due to the fact that many concepts are composed of multiple glyphs, a 'Bliss spelling')
… any other symbol set would be a one to one mapping of glyph to Unicode code point
janina: I believe Anne is expecting the Bliss/Unicode mapping
… Our demonstration will show how this doesn't quite fit, and we have a proposal for how an implementor would do it
Annalu: Bliss as it is, is a language where words can be expressed by a sequence of Bliss characters, with each character being a unique glyph
… other symbol sets do not typically work this way
… most other symbol sets have a single, unitary image for each concept (or 'word')
… we could consider the entire spelled-out Bliss Symbolics 'word' as a single character
Russell: There is a significant number of Bliss Symbols that are a single glyph
… this can be considered a core subset, and will have good overlap with limited defined vocabularies such as Ogden's English
Annalu: We can consider this a first step
Russell: We can articulate that extensions on this basic core concepts will likely run into strings of Bliss Symbolics glyphs
<Annalu> 1992 ISO IR 169 “Codes for the Blissymbols Character Set” was published. This was a lexicallybased encoding.
<Annalu> 2004 The Fundamental Rules were published giving explicit information as to the creation of new Bliss-words, and an explanation of restrictions on the creation of new Bliss-characters with regard to the UCS.
janina: Russel reports that there was an early vocabulary of Bliss that did get expressed in Unicode
… it was abandoned as the community found it rigid
Russell: 1992 ISO IR 169 “Codes for the Blissymbols Character Set” was published. This was a lexicallybased encoding.
<Annalu> chrome-extension://
Lionel_Wolberger: This 1992 ISO IR 169 clearly was helpful in the past, as it informed the Blis Symbolics IDs
… The Adapt Task Force finds it then reasonable to take this 1992 expression of Bliss in Unicode code points
… as a good starting gate suggestion of a font
… where, if a content provider wishes to place a synmbol of their own choosing on a web page
… if they mark it as a code point in this Adapt font
… then any other user could reliably display a similar symbol, that is meaningful and personalized to their own needs
Lionel_Wolberger: Provided that the end user would have a version of this same font, with the unicode code points, but with their own personolized or localized symbols
… in the place of each code point
janina: Let's return to Anne and EA with Tuesday, and ask them if they would prefer morning or evening
<Annalu> We shouldn't forget http://
Russell: Concept coding was Andy and Matt's work
… it is reflected in Concept net as well
… https://
… frankly I am impressed with Concept Net, which does discuss its relationship to ConceptCoding
janina: I have what we need to clarify the schedules of invitees
Russell: I will do a preliminary mapping of the ISO IR 169 characters to the core vocabulary of Ogden's basic English
Lionel_Wolberger: We could add a column to the W3C Symbol registry giving the ISO IR 169 code point
Russell: Some of the ISO IR 169 may have disappeared as Bliss is a living language