Re: Your Comments are Required

I think we should at least acknowledge the relationship to EtR in the 
calls, even if just to point interested readers to the relevant wiki 
page(s). AFAIK Klaus and Andrea plan to update the EtR page and add 
related topics (such as on layout, design, and illustrations to aide 
understandability) during the next week or two.

Best,
   Shadi


On 21.5.2012 14:40, Shawn Henry wrote:
> Good to get discussion on this.
>
> I think we agreed (as we were over time in the telecon last week) to
> draft a pre-call with both topics, and then to consider whether or not
> to do a pre-call with both topics. I think it was a good exercise, and
> it has made some issues more clear.
>
> As I've been thinking more about a pre-call combining the topics, I've
> been more concerned with the issue I noted previously: if we combined
> text customization with reading level and broader issues then [I'm
> concerned] the text customization aspect would get overshadowed. As has
> been noted, text customization has not received much focused attention,
> yet is an important topic in itself.[1]
>
> Simon Harper wrote: "Further, there is no guarantee that the 4th topic
> will be 'easy to read, we've had no proposal and no vote."
>
> Then why would we do a pre-call now for easy-to-read if we haven't even
> decided that it will be the next topic?
>
> ftr, I continue to vote for going ahead with the Text Customization for
> Readability on its own now, and separately consider if we want Easy to
> Read for Topic 4. :-)
>
> ~Shawn
>
>
>
>
>
>
> [1] http://lists.w3.org/Archives/Public/public-wai-rd/2012May/0023.html
>
>
>
>
> On 5/20/2012 10:11 AM, Simon Harper wrote:
>> Hi everyone,
>> We agreed on the telecon that this would be 2 seminars with one call.
>> In this way we have the benefit of deciding which submission goes to
>> which telecon. Further, there is no guarantee that the 4th topic will
>> be 'easy to read, we've had no proposal and no vote. In addition we
>> are also assuming that there will be enough interest not just in TC
>> but also EtR to build two full telecons.
>>
>> Thus is why I vote 1 call 2 telecons.
>> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>
>> From: Peter Thiessen
>> Sent: 20/05/2012 11:07
>> To: giorgio brajnik
>> Cc: RDWG RDWG
>> Subject: Re: Your Comments are Required
>>
>> Good point about the risk of a small number submissions being minimal.
>> Also, with the plan to have Easy to Read as a future topic, I change
>> my vote to have Text Customization as a separate topic.
>>
>> cheers,
>> +peter
>>
>>
>> On 2012-05-18, at 9:33 AM, giorgio brajnik wrote:
>>
>> > I second most of Yeliz' comments.
>> >
>> > I also agree with Shawn in trying to keep Text Customization
>> separate from Easy to Read, in the pre-call and later on as well. The
>> only risk is a small number of submission, but Shawn has already done
>> a great job against it.
>> >
>> > Giorgio
>> >
>> > On 05/17/2012 08:42 PM, Yeliz Yesilada wrote:
>> >> Please see my comments below for the open issues specified
>> in<http://lists.w3.org/Archives/Public/public-wai-rd/2012May/0023.html>
>> >>
>> >>> * Relation to Easy-to-Read.
>> >>> Several weeks ago RDWG discussed the possibility of combining Text
>> Customization and Easy to Read into a one symposium, and I have since
>> exchanged e-mail with Andrea and Klaus about this. Also, Klaus has
>> ideas for additional related Symposiums.
>> >>> I would like to propose that we go ahead with the pre-call as
>> scoped, that is, focusing on text customization and not opening it up
>> broader.
>> >>
>> >>
>> >> YY: I think this would be fine, but I think once the precall is
>> released people will get the idea about the topic and even it will be
>> widened with the full call, there is a risk that people will not read
>> the full call. We can either keep this one specific to Text
>> Customisation and as it is proposed below have another seminar on easy
>> to read topic, or combine them properly and then release the call.
>> >>
>> >>> * Timing: The text customization is well defined and has been
>> reviewed by RDWG, and the Easy to Read[1] is not yet. It would will
>> take time to develop the Easy to Read information. It would be good to
>> get the pre-call for topic #3 out ASAP so people have plenty of time
>> to write up work in this area, rather than delaying it by combining
>> topics.
>> >>
>> >> YY: I think it does not have to be written fully but it would be
>> good to have a complete list of topics in the precall.
>> >>
>> >>> * Focus: I think if we combined text customization with reading
>> level and broader issues then the text customization aspect would get
>> overshadowed, if not lost all together. As has been noted, text
>> customization has not received much focused attention, yet is an
>> important topic in itself.
>> >>> * Sufficient submissions: Over the last month I have inquired of
>> several people about their interest in contributing to a symposium
>> specifically on text customization for readability and have had
>> several positive responses. So far, 10 have said they will submit, and
>> 4 said they might. If we get the pre-call out soon, we will be giving
>> over 2 months advanced notice and will likely get sufficient submissions.
>> >>
>> >> YY: This sounds great.
>> >>
>> >>> * Title.
>> >>> - The current working title is "Text Customization for Readability"
>> >>> - Ideas from previous discussions are listed here:
>> >>> http://www.w3.org/WAI/RD/wiki/Text_Customization#Title_ideas
>> >>> (of course, feel free to add other ideas and comments in the wiki)
>> >>> - I think we should settle on a title for the pre-call.
>> >>
>> >> YY: I like "Text Customization for Readability" and brainstorming
>> below!
>> >> "Text Customisation for Better User Experience"
>> >> "Text Customisation: Now and Then"
>> >> "Text Customisation: Research Challenges"
>> >> "Research Challenges in Text Customisation"
>> >>
>> >>> * Scientific Committee.
>> >>> - There are a few people I have in mind to invite. I would like
>> the group's input on the invitation letter drafted at
>> >>> http://www.w3.org/WAI/RD/wiki/SC
>> >>
>> >>
>> >> This looks good to me.
>> >>
>> >>> - Who in RDWG would like to be on the committee?
>> >>> - For the pre-call, do we want to leave off the Scientific
>> Committee list since it's still developing? Or include what we have so
>> far (which will probably be a few more after I send out the e-mail)
>> and add something like "(more to be confirmed)" at the end of the list?
>> >>
>> >> Either way is fine with me.
>> >>
>> >>> * Paper details.
>> >>> - For the pre-call can we just include limited information, e.g.,
>> that the paper limit will be 1,000 words (to give potential submitters
>> an idea of the work)? I would like to refine the rest of it (template,
>> review process, publication sections) before the complete CfP, but
>> don't want to hold up the pre-call.
>> >>
>> >> I think some broad information would be useful in the precall, not
>> specific details.
>> >>
>> >> Regards,
>> >> Yeliz.
>> >
>>
>>
>
>
>

-- 
Shadi Abou-Zahra - http://www.w3.org/People/shadi/
Activity Lead, W3C/WAI International Program Office
Evaluation and Repair Tools Working Group (ERT WG)
Research and Development Working Group (RDWG)

Received on Monday, 21 May 2012 22:43:41 UTC