Meeting minutes
<JF> zakim. who's here?
<CharlesL> https://
<CharlesL> https://
Becky's Issue #160 response
<becky> https://
Becky: "Consider semantics for accessible route"
… we answered, "We agree that providing one or more accessible routes through a process is important. We discussed this briefly and agreed that it was beyond the scope of our content module. We plan to examine this more thoroughly in a future personalization module. "
Janina: +1
Sharon: +1
janina: Verifying, it has a keyword. The keyword is 'feature request'
<CharlesL> Charles +1
Becky: Keywords that are in use
… let's review it
… -- Content module #1, Help module #2, Tools module #3,
John: Help & Support are Module #2
<JF> Content Model (#1)
<JF> Help a & Support (#2)
Charles: making the changes now
<CharlesL> https://
Charles: Done.
Open actions
Charles: There is a pull request
… https://
<CharlesL> original: <p>People have very different needs. There are many people with cognitive and learning disabilities that affect their ability to interact with the web. Some people cannot process numeric information (dyscalculia), but others understand numbers better than words. Some people with severe language disabilities use symbols to represent words; some people need (or want) simplified user-interfaces. One of the main challen
<CharlesL> ges that has not been addressed on the web is transforming content for these varying needs. This specification provides a means for web technologies to address these requirements.</p>
<CharlesL> Updated: <p>People have very different needs. There are many people with cognitive and learning disabilities that affect their ability to interact with the web. Some people cannot process numeric information (dyscalculia), but others understand numbers better than words. Some people with severe language disabilities use symbols to represent words; some people need (or want) simplified user-interfaces. Different people find di
<CharlesL> fferent layouts and types of content easier to understand, and what is useable and understandable by one person can be be too complex for another. One of the main challenges is to address the varied and conflicting user needs, so that content can be understandable by the individual users. This specification provides a means for web technologies to address these requirements.</p>
John: The changes from <code> to <strong>, when it is a paragraph heading, sounds right.
John: volunteering to review the changes
<becky> https://
Charles: Suggest you pull Lisa's branch, do your changes, and commit
… then we can merge your changes in with Lisa's
<CharlesL> https://
<CharlesL> https://
Content Module 1 - Distraction values and examples need to be updated #170
<CharlesL> https://
<becky> https://
Issue #46
<CharlesL> Here is a list of Open issues related to 1) Content Module and sorted by oldest.
<CharlesL> is:open label:"1) content module" sort:created-asc
John: "ad" is no longer a distraction
janina: 170 subsumes 46?
John: We accept a token list, but is it comma separated or space separated
Becky: "a list of one or more tokens" <-- doesn't say space or comma, currently
John: ARIA is space separated, so let's inherit that for consistency
<JF> https://
Becky: (checking in ARIA) -- they have the same definition, 'a list of one or more tokens'
<becky> https://
Lionel: Just asking, will there be a need for ordering?
JF: Supported
… in this list, order doesn't really matter
Becky: With symbols, order does matter, and we handle it
JF: Do we expect another host language?
… ARIA can be used in SVG as well
janina: HTML is certainly first, then likely the education domain
JF: In editor's draft, space separated list is mentioned twice
<becky> https://
Charles: Tokens are expected to be Camel Case compressed
JF: The tokens are defined in advance
CharlesL: Double checking-- we implemented 'dash' and not CamelCase
JF: New issue found (!) says, 'symbols is a URI'
… the value is a numeric reference
<becky> https://
JF: Proposed: I will take the ARIA wording, build on it a definition of token list.
… Since personalization requires token lists, we will specify the types of lists we expect
… drafting: a token list can be either a space separated list of values, or for symbols, a conjugated list of values
becky: Thinking out loud: will we ever need to combine these two types, and then will the separator become ambiguous
Action: JF to research token list, draft definition for our spec. Also look at conjugated terms and space between + symbol?
<trackbot> Created ACTION-79 - Research token list, draft definition for our spec. also look at conjugated terms and space between + symbol? [on John Foliot - due 2021-02-15].