<LisaSeemanKestenbaum> scribe: JF
<scribe> scribe: JF
LS: getting ready to start
LS: asking Janina about update on
the draft charter(s)
... I think there may be an overlap there - we should look at
it to ensure we are comfortable
MC: have been reviewing the charter
<MichaelC> Draft APA charter
We need timelines fromthe TF to add to the Charter - hope to take it to the group this week. Runnng out of time...
<LisaSeemanKestenbaum> https://github.com/w3c/personalization-semantics/wiki
Whatever we develop should be realistic
LS: noting that the timelines may
be out of sync
... had personal reservations about moving out of ARIA to
APA
MC: believe there is no impact on our actual work by moving there
LW: moving doesn't block us from using ARIA, but it does open up other possible solutions as well
LS: dislike the branching: ARIA
is for the blind, this is for others - not comfortable with
that idea
... are there any other objections?
<thaddeus> i dont know i need to differ to people with more experience in the W3C because this is more of an organizational concern
LS: prepared to live with decisions
<thaddeus> can we move out and if it doesnt work can we move back?
<LisaSeemanKestenbaum> https://github.com/w3c/personalization-semantics/wiki
LS: draft timelines are posted in the wiki
We have been fairly close to our current timeline - a bit of slippage
next major dates may require us pushing back on some of the times
LS: how much time do we have to get timelines in?
JS: would like to get the APA Draft Charter ready by next week
and agree that we should be more generous with our timelines
we don't get in trouble finishing faster, but we do if we are late
LS: should we say in August the first WD for the first module...
JS: its a 3-year charter
MC: we need a timeline to Rec and a time-line for CR as well, with enough time between them
LS: think that Charles and I need to brainstorm this on a call, and then return to the group
CL: we have a call on Wednesday, we should look at that then?
MC: agree that you and Charles
should discuss - should have a back-up plan in case the
Wednesday call is a problem
... suggests to Charles to discuss with others at W3C for ideas
around time-lines
... maybe Janina, or Leonie, or...
[scheduling discussion]
<sgoto> FWIW, just friendly heads up, I got to leave at 10h30pm for another meeting :( so available for another 10-mins-ish
<LisaSeemanKestenbaum> https://github.com/w3c/personalization-semantics/wiki/Comparison-of-ways-to-use-vocabulary-in-content
MC: have been discussing this
with Sam
... (would like to have Sam formally join this TF)
... some of this may be excessively technical, but have been
chatting between Sam and Michael
... wiki has brief explanation of the different methods, along
with some Pros and Cons
intended for deeper discussion
MC: [reviewing pros and cons for
RDFa]
... [reviewing pros and cons for Microdata]
... [reviewing pros and cons for aria-* attributes]
... [reviewing pros and cons for aui-* attributes]
... [reviewing pros and cons for a 'single' attribute (i.e.
@purpose)]
... [reviewing pros and cons for native host language
features]
... tried to break these down with Pros and Cons, and then
provide a comparison at the end
... aria-* attributes and native semantics currently seem the
strongest possible solutions
LS: single attribute wouldn't
work for (for example) symbol(s)
... there are times when we may want free-flowing text as
well.
Fear that some of our use-cases might be lost
MC: notes that this should be added to the wiki
LW: lots of thoughts swirling...
not sure that ARIA is the way forward... we've *just* got authors around to understanding that ARIA is for screen readers, this may add confusion
still think that a single attribute may be a better way forward
LW: URI for a particular symbol - we make a token value for "foo", and then any tools that provide the symbol maps back to the token value
LS: this is the way we are going with the Bliss set - but there remain holes
<sgoto> got to run. thank you all! good stuff michael and hope we can continue working offline!
but the intent is to provide a separate URI for each symbol
LS: we don;'t have a complete set
yet, but headed in the right direction
... having a finite set of tokens may become a huge lift. What
happens when you have both simplification and symbols
MC: want to try and keep this abstract: we have a need for providing values that are unbound
<LisaSeemanKestenbaum> also support free text
LW: returning to either a single-value attribute or host languages. There is a new *** called Image Capture that has been incorporated into HTML (this is recent)
MC: worth considering is that approach, but only if we are confident that host languages will support such a move
<tink> Media Capture spec https://www.w3.org/TR/html-media-capture/
LS: think we should add the
additional suggestions, and also identify any additional pros
or cons
... want to suggest we also start working on the next two
modules, so taht we can really see if this implementation
really works
and see if we've captured all of the considerations
MC: makes some sense. Think we
should have separate parallel discussions to avoid us going off
into the weeds too soon
... reliant on minutes, but won't be able to update the wiki
for a time
... but agree we should rteturn to the vocabulary
LS: any additional comments should be added here (please)
<LisaSeemanKestenbaum> considerations include: free text support, contatination of values, any number of concepts for symbols
<LisaSeemanKestenbaum> and add a table for caoture models
LS: so next steps is update wiki, and then...
MC: check back in next week... add updates and revisit
CL: were we going to look at JSON-LD as an additional option?
MC: yes, Sam had suggested that as well, but need to grok it better
LS: always though of JASON files as user-settings
MC: it's another proposal, but
not 100% clear how it works, so want to revisit
... we should throw all the ideas we have, without a full
evaluation at this time. Add everything and filter/refine
later
Thad: only concern is about
getting work done now. Can we start looking at specific action
items, or are we on hold?...
... I have cycles now, so please let me know how I can
contribute.
MC: encourage others to add to the wiki page
LS: we want to see how to make it more understandalbe, and for others to get a grip on what's going on...
<thaddeus> yes that is correc
LS: we've divided this into three major sections (this is just a PoC - may not make full sense)
<thaddeus> my phone dropped jumping back on
first is use-cases, then vocabulary support (to ensure we have a deep enough vocabulary), but it is incomplete
often inherits from @roles, but not always
the third section is implementations
LS: hopefully this gives an
over-view, but this is still a PoC
... there is a second type of implementation examples provided
as well. Does thi smake it more understandable?
Becky: slowly starting to understand, but it wasn't obvious at the start
BG: this is confusing, because
there is no vocabulary, but there are implementations
... for example, number-free - i expected to see that in the
vocuablualry
LS: it's there
BG: but when I scroll down, it is incomplete, but under attributes it's there, but...
LS: don't have the whole table, but there are more values under Help types (which should be added)
BG: I am still unsure about next steps - how this is two topics...
MC: might suggest commenting out the examples, as they are very old
<thaddeus> Michael said what I was going to say
MC: what we're saying is the examples are old, but we are now looking at new ways of moving forward
BG: there is stuff there that needs to get moved.
Thad: Michael may have summerised that: the we put the implementations on hold, and focus on the vocabulary
LS: do you kinow what needs to be done for tools now?
Thad: yes that makes sense - I was going to look at your work and follow the styles
BG: I can work on this more, but
do we really want it in a table? (Will leave it that way for
now)
... not sure I understand all of the proposed ones, but do we
need more/others?
LS: we need to examine terms as
well
... there is a separate table for help-types, which needs to be
split out
... the goal is to ensure we have the terms we need, not
focusing on implementations now.
JF: so the examples there are illustrative only?
LS: absolutely
<thaddeus> yes
LS:
thanks all, talk next week
<thaddeus> thanks
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) Succeeded: s/tah/that/ Default Present: Léonie, MichaelC, sgoto, JF, Becka11y, thaddeus, janina Present: Léonie MichaelC sgoto JF Becka11y thaddeus janina 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: 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]