Meeting minutes
Content Module Implementations Status (Follow-up on i18n issue #144)
Janina: We have a zip file (the hummous recipe) to demonstrate the RTL and LTR switches will work well with Personalization's proposed <symbol> markup
... The file has English and Hebrew
... and is marked up with appropriate symbols
... We had in mind the Chrome extensions that Lisa previously
... When we have it working we will send this with a cover note to i18n, and show them how to render the Hummous recipe
... the Chrome extension is parsing the page looking for an aui- prefix rather than data- ('data dash')
... the way forward, either change the chrome extension and change the code to parse for data-
... or change the Hummous file data- to aui- (or whatever is required)
Matthew_Atkinson: I have some updates to add
Matthew_Atkinson: I changed the Hummous to aui- (since that was easiest)
... we noted a further issue
... the mappings of symbol IDs to Symbols do not exist for all the concepts referenced in the Hummous Recipe
... Matt & Lisa met this morning and confirmed this issue
... the extension does enable some control of the mappings
... We see a way forward
... hard-code, etc
... will take some time
... THe chairs and the committee thank Lisa for her time this morning
LisaSeemanKest: The symbols are loaded in a separate file to enable more symbol choices by end-users
... one use case, a user has a symbol file on their phone and another file on their computer
... the symbol file reference should be easily found
Matthew_Atkinson: The extension could support a mapping of all symbols to Bliss, and the Personalization Content module would encourage such mappings
Matthew_Atkinson: To clarify, the "Wikihow Cup of Tea" example works fine
... The Hummous recipe did not have the proper markup (no aui- markup)
Matthew_Atkinson: Janina to draft the email that we will send to i18n
... this email should bundle a procedure to allow the i18n folks to run the exatension
... with a usage stipulation, that the extension is not meant for wide distribution
... I plan to clarify what is left to complete this week
janina: I will put in the cover letter why the markup changed
LisaSeemanKest: The extension also renders "simplify"
... along with Ayeleth's github, which is an open script that authors can serve on their page
... offers a widget (overlay) approach
Matthew_Atkinson: We demo on Ayeleth's script
Lionel_Wolberger: We met with Bruce from Access Board this week and we are going ahead with the plan to mark up the
... Title: Online Architectural Barriers Act (ABA) Complaint Form
... URL: https://
... which is stored in a git for open access in the ATBCB git
... https://
... Might Google be interested in marking up something?
Defining shortnames for the modules
Personalization: Content Module
Personalization: Help and Support Module
Personalization: Tools Module
LisaSeemanKest: If we rethinkg from a blank slate, the "help and support" is more about alternatives and support
... there is a bit of ambiguity because the help icon is addressed in the Content Module
... but alternatives isn't perfect, as symbols are also alternatives
... but content is addressed in "help and support" as well
... not sure these suggested names will help guide a newbie
... Help and Support is also about content
... we may need to lean on the one sentence summary that we have written on the wiki regarding each module
Matthew_Atkinson: The discussion was regarding whether we are providing semantics or alternative content
... the differentiation between semantics and alternative content seemed significant
... these short names dont lose anything, and have a consistency, but it's worth thinking it through
ack: Matthew_Atkinson
janina: The fact that we are on the brink of CR, the most important decision is to decide on the scheme, the pattern of these names
... we don't want to have to rename the modules
... so we don't have to worry too much about the actual titles of the 2nd and 3rd modules, its the first module we need to nail, as well as the overall scheme
... I did check the original name, and the name was Personalization Semantics (no concept of three modules was present then)
LisaSeemanKest: When can COGA start brainstorming use cases for the upcoming modules
+1
LisaSeemanKest: Someone from Personalization should give an overview of the module
… the call is on Thursdays
Lionel chuckles
… allow the group to associate the conversation with the representative
What is the role of COGA in curating and bringing our next module to CR
Planning COGA January meeting on Our Other Two Modules
janina: A note is something a WG says
… a statement is something the W3C says, not just a WG
… then there is a formal way to create a registry at w3c.org
… for example, have an index number and a mapping to bliss symbols
… and discuss the details of how this registry would be defined (e.g., how many columns)
… the registry would support an API
… in the case of the symbols, it would be far more useable than the PDF of symbols
… we would need others to be in that conversation
… and might need to consult with someone from Bliss
… we may need to re-examine the terms surrounding the Bliss symbols