See also: IRC log
betty: betty purwandari
from indonesia, now in southampton for phd
developing methodology to measure impact of mobile web in dev. countries
looking in Kenya for now
and Indonesia too
should move to case studies in a year
steph: checked on the mailing-list
one person only answered
so we can stick with the current slots
<Adesina> Betty's work could be very important
stephanie: sent a mail to the group
<Stef> christelle: how difficult is the tools ?
<Stef> is it linux or windows based ?
<Adesina> Is Steph diff from stef?
<Stef> stephanie: broadening to end-user tools
<Stef> rrs reader, browser
<Stef> interesting tools for the community to recommend
<Stef> most capable browsers on a given device is important
<christellescharff> ++
<Stef> stephane: so that creates 2 categories
<betty> My point of view, tools = software, devices, netwok for MW4D. As we know there are many pilot projects to analyse.
<Stef> betty: yes, different categories
<Stef> developer, content provider, end-user
<Stef> steph: difference ?
<Stef> betty: different type of people: those providing content, those consuming content
<Stef> christelle
<Stef> :
<Stef> tools only, or the impact of the tools ?
<Stef> christelle: impact=how many users and so on
<christellescharff> scope of use of the tool
<Stef> Resolution: we should integrate tools targeted at different type of users, including those focused on end-user only (e.g. web browsers, rss reader, etc.)
<Stef> steph: goal and audience of the document
christelle: a tool for decision making to select the right tools so for e.g. ngo
also for teachers to design projects for students
stephanie: some tools works only if there is content available
like education tools
a content element should be considered
stephane: some dimension might be overlapping ?
like content creation ?
christelle: what is important too ?
how to present ?
should be clear and organized
not easy.
stephane: we should perhaps not focus on analyzing tools but just the methodology
probably not focusing on the best tools in each category ?
stephanie: at the first glance, i thought that we should recommend tools but now not sure
the way to present is key too
too much factor may kill usefullness
stephanie: specific example: mobile testharness results: very hard to understand
the results should be mobile accessible also
steph: a repository surely, the document describing the methodlogy, i'm not sure
stephane: how could-we move on ?
betty, how we are going to present document ?
<betty> Are we going to include some practitioners or potential users could be audience of the document? E.g. in m-agriculture, some smart farmers could read the document, which inspires them to try the tools analysed in the document. But they need more practical documents than lecturers or students.
betty: are the potential users of tools are
audience ?
... e.g. farmers ?
better: easier access for simpler users, more complex access to smarter/advanced users
<Adesina> mHealth applications could be the main driver for mobile web
<scribe> ACTION: stephane to create or find back the wiki page to use to drive the discussion [recorded in http://www.w3.org/2010/08/02-mw4d-minutes.html#action01]
<scribe> ACTION: stephanie to gather the different pieces expressed today and in the email thread on the wiki page [recorded in http://www.w3.org/2010/08/02-mw4d-minutes.html#action02]
<betty> Is this the link for tools wiki http://www.w3.org/2008/MW4D/wiki/Mw4d_tools?
steph: normally next date is August 16
shwetank: not good for me
<betty> 16 August sounds great to me.
<scribe> ACTION: stephane to query the group to see if any of 16 and 23 have enough participant [recorded in http://www.w3.org/2010/08/02-mw4d-minutes.html#action03]