W3C

- DRAFT -

SV_MEETING_TITLE

09 Oct 2017

Agenda

See also: IRC log

Attendees

Present
clapierre, janina, MichaelC, Roy, AndyHeath
Regrets
Chair
clapierre
Scribe
AndyHeath

Contents


having trouble with my audio - was on a badly-configured call earlier today and its screwed it all up - no sound so far

<lisa> scribe: AndyHeath

<lisa> (think you...)

Updates, new wiki pages, TPAC

<MichaelC> https://github.com/w3c/personalization-semantics/wiki

<clapierre> here are the architectural issues. https://github.com/w3c/personalization-semantics/wiki/Architectural-issues

Trying to scehdule a meeting with CSS and APA

Janina: Need a joint meeting with CSS - should be prepared to move ahead with Media Queries ASAP
... if we are lucky we may get 10 minutes of the joint hour

<clapierre> Meeting will be on Tues 11am - 12pm

We might need an Accessibility API mappings document

Janina and charles will pursue privately

How to treat immature sections (see the survey)

they will both pursue making arrangements with the others needed

Lisa: Note the architecture page is up on the wiki

Lisa and Charles to discuss a meeting someolace at TPAC for a perosnliation meeting

s/p13n-call/personalisation/

discussion about callins.

the APA group will have callins

<lisa> https://www.w3.org/2002/09/wbs/101569/08Oct2017immature-sections/results

<clapierre> agendum 2. "How to treat immature sections (see the survey)" taken up [from MichaelC]

Which sections should we focus on?

How to treat immature sections (see the survey)

Survey on editors notes - conclusion is yes

Michael: instead of “at risk: say something less formal

Gregg: “Section” is unclear

Michael: we will agree pragmatically

Which sections should we focus on?

Lisa: we should maybe request people for next week to flag what is immature and what mature
... there is some kind of prioritisation needed

<clapierre> https://rawgit.com/w3c/personalization-semantics/vocabulary-proposal/semantics.html

Survey for next week - one survey question for each section with what implementations they foresee - want real data not guesswork

start it as a survey then maybe copy some to wiki page later

Do we want it as a vocabulary?

<MichaelC> https://lists.w3.org/Archives/Public/public-personalization-tf/2017Oct/0006.html

<MichaelC> https://rawgit.com/w3c/personalization-semantics/vocabulary-proposal/semantics.html

Michale’s proposal: restrucrued semantics as a vocabulary

Lots of restructuiring. Michael summarised his proposal

Easiest to see the changes from the table of contents

<MichaelC> https://www.w3.org/TR/microdata/

Discussion of how the vocabularly can work with ARIA and say microdata

<clapierre> Note: Discuss at TPAC whether or not to use aria- per- coga- etc.

the meaning of the vocabulary terms is independent from the way they are implemented in different formats

+1 for this

Andy: the preffxes can come later

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

Charles: for Schema.org it is similar

Do we expect something similar for this ?

Michael: we should be compatible with Schema.org

Michael - it should be all value pairs

Discussion of the model of value pairs and scope of the work

Lisa: Logs is a problem

Michael: its do-able but no in a way that supports intrinsic validation

<lisa> https://w3c.github.io/personalization-semantics/#log-usage-examples

Michael: all this stuff can eb done with a vocab but what can’t be done is automatic validation

Topic for the next round - what can’t be done with a vocab

Gregg: what are we doing - is this for wcag or what ?
... Are we creating a technology spec ? There seem to be no implementors in the room

Lisa: Pearson and Texthelp are involved

<clapierre> EasyReader

Lisa: I also have my own project working on this

Charles: EasyReader

Survey on at risk sections for next call

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2017/10/09 18:05:09 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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/Updates on TPAC on WIki Page//
Succeeded: s/prusue/pursue/
Succeeded: s/neded/needed/
FAILED: s/p13n-call/personalisation/
Succeeded: s/servey/survey/
Succeeded: s/contatcs/contents/
Succeeded: s/The vocabulary terms are independent of the implementation/ the meaning of the vocabulary terms is independent from the way they are implemented in different formats/
Succeeded: s/Michwel/Michael/
Present: clapierre janina MichaelC Roy AndyHeath
Found Scribe: AndyHeath
Inferring ScribeNick: AndyHeath

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

Agenda: https://lists.w3.org/Archives/Public/public-personalization-tf/2017Oct/0005.html
Got date from IRC log name: 09 Oct 2017
Guessing minutes URL: http://www.w3.org/2017/10/09-personalization-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]