[Dev-flock] Consumer Gadget rendering test for Make IT Fair

[Lucy Mendel]

Wesa,

Cool. I especially like how readable the results are.

A couple questions:

Was the research you did manually entered, or was some aspect of node,
label, relationship or social impact issue automated in some way?
After this experience, do you have any advice or plans for automation?

Are shorter labels always shortened because of redundancy within the
context? Are there other rules? For performance we might want to store
short labels anyway, but I was just curious about the extent of logic
neede were that to be automated.

Lucy.

On Mon, Sep 29, 2008 at 8:05 AM, wesa aapro <wesa.aapro at gmail.com> wrote:
> Hi,
>
> you may be interested in the work I am doing with the Make IT Fair project
> (makeitfair.org). This weekend we managed to build a node map of issues
> related to Nokia phones, based on Make IT Fair research. A lot of hours
> spent on thinking node labels and other small issues, but we learned a lot.
>
> I also did some UI programming with pretty interesting results. There's
> still room for many new innovations, but I am starting to be happy with the
> work.
>
> http://consumergadget.org/html2.php?ean=n95 is the result page for N95,
> containing links to related nodes. The page is designed for mobile phones.
> There's quite a lot of text, but it can be read using phone. Node nodes
> types are used when the nodes are rendered as human readable node chains.
> Below them, all related ethical issues are rendered. Scoring and other extra
> information is left out at the moment.
>
> The page deals with some of the issues I wrote in the wiki. For example, a
> very interesting issue is that every node must have two labels, a short and
> a long one. The short one is used when the context is clear and the long one
> when it is not. "Nokia Phone Charger" can be just "charger", when it is
> presented under "Nokia Phone".
>
> http://consumergadget.org/xml2.php?ean=n95
> contains the same page, but in raw XML (and PHP) format.
>
> ---
>
> This work relates to BILUMI in two ways.
>
> 1) We are digging deep, trying to identify real world node and edge needs.
> We are working with NGOs who do field work, many collaboration issues
> emerge.
> 2) The rendering is an example of "consumer UI" of the BILUMI database. Many
> different views can be created using BILUMI API, but the more UI metadata
> exists, the clearer the rendering is.
>
>
>
> Best regards,
> Wesa
>
> _______________________________________________
> Dev-flock mailing list
> Dev-flock at mit.edu
> http://mailman.mit.edu/mailman/listinfo/dev-flock
>
>