<LisaSeemanKestenbaum> scribe: JF

<scribe> scribe: JF

tools module (If ready)

LSK: Becky isn't on call, but believe that what Becky did on her module is easy to follow along

worth looking at both, but the more important one is the alternative version to help

not committed to any examples, look at structure instead

this is what we had after the use-cases

here, Becky has added al the values into one table, even if they come from different places

<LisaSeemanKestenbaum> https://rawgit.com/w3c/personalization-semantics/master/help/index.html#alternative-explanation

took them out of the implementations examples

<LisaSeemanKestenbaum> https://rawgit.com/w3c/personalization-semantics/master/help/index.html#helptype-explanation

all values are being merged into one vocabulary. If this works it's good, but if it doesn't it'w bad...

LSK: do we have everything we need? Do we have all the terms/words we need?

questions around vocab numbers - somewhat arbitrary.

nuanced definitions: one says the type of help, the other is help options

one describes cognitive accessibility level, the other is the types of help we have (i.e. "human help", the other might be "FAQ")

one is accessibility features of the content (ex: types of symbols being used), the other is types of help (as above)

<LisaSeemanKestenbaum> http://w3c.github.io/apa/fast/#inventory-user-needs

<LisaSeemanKestenbaum> https://www.w3.org/wiki/WebSchemas/Accessibility

LSK: should we be looking to align with the Web Schemas effort as well
... so the big question is where do we put the Help module?

JS: sounds like a solid step forward

LSK: kind of like having the table values in the same place
... perhaps we should mark what has come as "help" types (i.e Glossary = URI to glossary page)

perhaps separate the two and look at separately

<LisaSeemanKestenbaum> https://rawgit.com/w3c/personalization-semantics/new-format-for-help-module/help/index.html#vocabulary-explanation

JF: there are many types of help, so perhaps we should be "slivering" those out - i.e. define all the types of help we can imagine

<LisaSeemanKestenbaum> overelap in module 1 :https://rawgit.com/w3c/personalization-semantics/master/semantics.html#destination

JF: this very much feels like a "Purpose, Use, or Destination" question.

LSK: suggesting overlap with Module 1
... suggest adding an Editor's note that indicates what has moved in from the Help module

3 options: 1) identify what comes from Help Types, 2) make another column after tables, 3) make it back into 2 tables (types of help, accessibility support)

<LisaSeemanKestenbaum> ACTION: lisa to add editor note identifing what comes form help type so we merge it out into seprate vocab or into https://rawgit.com/w3c/personalization-semantics/master/semantics.html#destination

Sharon: agree that the 2 table suggestion makes it easier to read. I'd also be interested in looking at the Purpose Use or Destination effort, and apply it to other terms

<LisaSeemanKestenbaum> lisa add ednot e we merge it out into seprate vocab or into https://rawgit.com/w3c/personalization-semantics/master/semantics.html#destination

<LisaSeemanKestenbaum> we mightb

RESOLUTION: will separate out the two tables (apologies to Becky) to types of help, accessibility support. Lisa will add an Editor's Note that we are not fully resolved here - this may still be re-merged together or merged with something else

<LisaSeemanKestenbaum> no merge until we fine tune it

LSK: implementation s wiki page - collecting all the data we looked at last week

this is a big task

we need to get this done however so that we can have a structured conversation

LSK: added a new row - support for the proposals we have

this is a first draft

<LisaSeemanKestenbaum> https://github.com/w3c/personalization-semantics/wiki/Comparison-of-ways-to-use-vocabulary-in-content

Task for this TF: review that page, and then add additional bullets (but do not delete). If you have concerns or issues, add to GitHub Issue tracker so that we can discuss this properly

Link Issue tracker items to the wiki page

<LisaSeemanKestenbaum> and link the git isse to the page

<LisaSeemanKestenbaum> and add link the git isse to the page

Once we are ready with this, we can have a structured discussion about approach

<LisaSeemanKestenbaum> michael?

LSK: if we add things to the implementation table, perhaps Michael can edit the summary table

don't want to mess with the structure of that for now

LSK: (we can disagree with it, but if we start messing with it we may cause additional issues)

so one of our first steps will then be to review Michael's summary

LSK: will ask Janina to add some content re: Media Queries
... this does not have to be "definitive", add what we know so that we can continue the discussion

JS: will try and get on this ASAP

trackbot, end meeting

trackbot, end meeting

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: JF Roy MichaelC janina LisaSeemanKestenbaum Sharon
Regrets: becky
Found Scribe: JF
Inferring ScribeNick: JF
Found Scribe: JF
Inferring ScribeNick: JF

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: lisa

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.)