Research and Development Working Group Teleconference

01 Aug 2012

See also: IRC log


Shadi, Shawn, Vivienne, Simon, Peter
Klaus, Yehya, Yeliz,


for the TC4R (text customization for readability) topic, afaik, what remains is:

* Finalize co-chairs & scientific committee

* Provide HTML template(s) - decide how prescriptive to be - decide how to allow for ethnographic studies, "position papers", and other such contributions



latest list of confirmed SC: http://www.w3.org/WAI/RD/2012/text-customization/Overview.html

slh: what do we need in a co-chair?

simon: someone who can write the report
... SC judge the resaerch
... need people who can complete the work

saz: agree. need someone who will follow through
... complementary roles
... more in research side would be useful
... connect dots to other peices
... mentinoed two peole who are more developers, practioners
... one peson from research/academic, one practioner, + slh with standardization hat on

slh: I was expecting to write most of the report. so I really want complementary to my work

saz: some people might bring bigger perspective, but might not be as active. some input and review, but not a primary writier

simon: research report...

<Zakim> shadi, you wanted to mention process aspect

[ Shawn envisions a research report and a less formal guidance thingie ]

saz: chairs will need to join the group
... (so under IPR)

<Zakim> shawn, you wanted to ask only charis or also SC?

saz: only SC if actively writing stuff

simon: not be overly prescriptive

saz: can make the blurbs after the headings - expand or contexualize them for a specific heading

template: http://www.w3.org/WAI/RD/2012/mobile/template

<peter> agreed strategy->approach

shawn: not make then use these exact headings?

simon: I say yes
... good to have consistency across papers

<vivienne> does it make it easier to do the research note after the symposium if the same headings are used?

<peter> maybe "strongly encourage the use of this template outline …"

saz: (think some papers did change headings a bit.) saying "use this as a starting point" is too open

pre-call email: http://lists.w3.org/Archives/Public/w3c-wai-ig/2012AprJun/0169.html

<shadi> http://www.w3.org/WAI/RD/wiki/Topic_4_pre-call

<shadi> http://www.w3.org/WAI/RD/wiki/Topic_3_Timeline


slh: we won't have time for pre-call for E2R. Need to finalize the Symposium page

<shadi> http://www.w3.org/WAI/RD/wiki/Easy_to_Read

review process

chairs triage

send to reviewers

reviwers submit comments

(Open Conf)

after reviews in, send email to all authors. here are the reviews. you have the chance to rebut

authors usually rebut within a couple days

chairs then look at reviews & rebuttals.

meta review. chairs make decsion on accept or not. inform accepted on condition that xyz issues are addressed

one week OK

submit "camera-ready copy"

<sharper> Well Done!

<sharper> You now need to create your Camera Ready Copy for publication no later than March 16th; here is what you need to do:

<sharper> Technical papers are up to 10 pages, communications up to 4 pages, and all other papers are 2 pages;

<sharper> Take a final look at your responsibility as an author;

<sharper> Make the revisions as suggested by your reviewers and as discussed in your rebuttals (this is part of you implicit contract with us to publish);

<sharper> Make sure you have changed your copyright block to bottom left of the front page – so that the ‘Submission Type’ states either ‘Technical’, ‘Communication’, ‘Microsoft Challenge’, ‘Google Student Award’, ‘Keynote’, or ‘After Dinner’; Example: W4A2012 – Technical or W4A2012 – Communication.

<sharper> Change your ISBN to this years number of 978-1-4503-1019-2 / in word just replace the x’s on the bottom line of the block, in the LaTeX use \crdata{xxxx};

<sharper> Now you must register so we know you intend to come along and present; Notice that deadline for early bird registration is on March 12th.

<sharper> Send your completed accessible papers back via email to W4A General Chairs but in your email add a plain text version of your title, abstract, authors and their affiliations, and finally you W4A registration number;

<sharper> Take a look at your responsibility as a presenter; The W3C-WAI provides some resources to make your presentations accessible in How to Make Presentations Accessible to All.

<sharper> As a presenter you are making an implicit agreement to be filmed or recorded if the W4A decides to create Audio Visual resources as the conference proceeds;

<sharper> You will then receive an email from the ACM detailing their copyright requirements, please follow these to the letter as we cannot publish without your copyright forms;

<sharper> Find the procedures to get your visa;

<sharper> Remember to add yourself to our Lanyrd Conference.

<sharper> We are really looking forward to meeting you at W4A 2012, and you will bet more logistical information by email direct to you nearer to the conference dates.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.136 (CVS log)
$Date: 2012/08/08 07:10:48 $