PALplates Outline/Working Paper

We (Akhtar?, Lori?, ??) will be merging inputs from the Comments and Ideas and Questions and Issues pages here, into what will hopefully become a coherent document, and outline for a paper.

Please send Lori any suggestions/corrections you have for this document.

Why do we need PALplates?

Solve information overload by having information where/when you need it. (Currently we are forced to funnel information through our desktop)

What will PALplates do?

What won't PALplates do?

What is unique about what we're proposing?

(We need to address both user-level and technical discriminators.)

Discussion/Scenarios (along with existing alternatives for these tasks)

(We will need to make sure we can justify the need/utility of PALplates in these scenarios.)

Design Elements/Features

browser-like interface

Plan

Hardware Requirements

(Both HW and SW requirements should be driven by the task scenarios.)