<LisaSeemanKest> clear agenda
<LisaSeemanKest> scribe: janina
<scribe> scribe: janina
<LisaSeemanKest> https://raw.githack.com/w3c/personalization-semantics/edits07062020/content/index.html
ls: New version as of today
... Believe everything we discussed except Janina's changes to
the Intro
<LisaSeemanKest> https://raw.githack.com/w3c/personalization-semantics/edits07062020/content/index.html#symbol-explanation
ls: Discussion of symbols moved
up top
... also the conjugated example with the explanation
... believes we have the same info, though the changes required
slight changes
jf: Confused by the code example
ls: Hmm, think we've had that error for some time
jf: why symbols to a graphic
file? I'm unclear why?
... Don't expect we want alternative text?
ls: Old example from a working
demo ...
... Some people understand some images, others understand other
images
... Some COGa people will do better with familiar symbols, not
the picture
jf: 3 pictures describing a picture?
ls: yes
... "are not part ..." is the only new phrasing
cl: Also helpful when someone is learning a symbolic language
jf: Noting we need to clean up our markup!
ls: Indeed, how was it there so long so broken?
cl: asks about space following alt=
jf: will supply corrected code, include using png rather than gif
<JF> Example 11: <img src="cuptea.png" alt="cup of Tea" data-symbol="13621 12324 17511" alt="cup of Tea"/>
bg: generally we mean replace,
but here not?
... AT decision based on user need how it's replaced or
used
<JF> Example 12: <img src="her-name.png" alt="שמה" data-symbol="15691 + 14707"/>
jf: put it in more common authoring order, removed extra spaces, etc. etc
ls: asks if we're ok with glossary change?
cl: has a uestion before that
...
... ex 9 ^ 10; suggest change order -- oh, maybe not!
... do like the ordering
<LisaSeemanKest> When there is more than one concept that are not part of a single conjugated term, multiple concepts can be referenced by separating them with white space. The order of multiple concepts should be the same as used in typical speech in the natural language of the content.
ss: "need" should be "needed" first para
bg: also "without" sans space
jf: Asks whether full editorial
review
... volunteers
<JF> ACTION JF to do redline editorial review of https://raw.githack.com/w3c/personalization-semantics/edits07062020/content/index.html#symbol-explanation
<trackbot> Created ACTION-61 - Do redline editorial review of https://raw.githack.com/w3c/personalization-semantics/edits07062020/content/index.html#symbol-explanation [on John Foliot - due 2020-06-15].
ls: also section 2 where we have terms ...
jf: add a definition for symbolics?
js: Strong +1
jf: suggests we all read for such tweaks
cl: notes we need to add "is normative" or "is not normative" persection
js: suggests review for terms to
define based on our audience
... apologies and explains github cli confusion that prevented
my edits
... expect by wednesday
[discussion of process]
ls: notes other edits sent to
list on i18n and tag responses
... are we OK
... when to send?
js: Suggests we clean up and stabalize before forwarding to tag
ls: asks jf about time for ed review assuming content in by wednesday
jf: can do friday am
<LisaSeemanKest> ACTION: john editorial review symbols - add to glossary add :this section is non normative by friday this week
<trackbot> Created ACTION-62 - Editorial review symbols - add to glossary add :this section is non normative by friday this week [on John Foliot - due 2020-06-15].
cl: two issues
cl; ex 4 and 5
cl: entities; extra slash
<LisaSeemanKest> https://github.com/w3c/personalization-semantics/issues/144
ls: I drafted a reponse, but i see now i answered the wrong question
jf: we put metada at the element
level; they're talking doc level
... asks cl about schema.org -- can we leverage?
cl; yes; we got it added
cl: also accessmode where we might add symbols to list of values
jf: shouldn't we say 'aac'
?
... notes all we're doing in p13n is for alternative
communications
<LisaSeemanKest> This is an interesting point. we will looking into adding an access mode metadata terms like "aac".
cl: we need metadata in head per
their question; we should consider wht we need and go to
schema
... correction, we don't need schema, because they don't care
about values
... i can bring this up in dpub
<LisaSeemanKest> This is an interesting point. We will also look into adding an access mode metadata term like "aac" via digital publishing .
bg: why is this an issue? why we're not relying on underlying tech
<LisaSeemanKest> This is an interesting point. We will also look into adding an access mode metadata term like "aac" via digital publishing .
ls: suggests i18n response we're
looking into it
... then add to issues
jf: believe q is will there be an
impact when directionality is declared; so in the
translation
... will that happen with symbols? is that expected?
... seems it's about processing engines
<LisaSeemanKest> https://lists.w3.org/Archives/Public/public-personalization-tf/2020Jun/0011.html
<LisaSeemanKest> Our use cases is to map between symbol sets in the same natural language. We are not enabling consistent translation for different symbol sets across different natural languages at this time.
<LisaSeemanKest> Our use cases is to map between symbol sets in the same natural language. We are not enabling consistent translation for different symbol sets across different natural languages at this time.
jf: suggest also we're looking to add another page level value via schema.org
<JF> +1
<LisaSeemanKest> ackl
cl: want to go back to becky's
q
... for dicoverability is one reason
bg: believe some of that's already on page; so tyeing it all together?
cl: google doesn't search on element metadata
jf: becomes a search term
This is scribe.perl Revision of Date Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/3/4/ Present: JF janina becky sharon CharlesL Roy Found Scribe: janina Inferring ScribeNick: janina Found Scribe: janina Inferring ScribeNick: janina Found Date: 08 Jun 2020 People with action items: - add editorial john review symbols WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]