RE: Additional Detail, Requested Actions, Discussion Material RE: SIM ILE PI phone conference, 08-Aug-03 1200 EDT/1700 BST

Mick,

Attached is a preliminary write-up of the work of the SWEB programme for
SIMILE, focusing on the CY2003 demonstrator.  It's a bit long for a email
message, so I wrote an HTML page.

	Andy

-----Original Message-----
From: Bass, Mick [mailto:mick.bass@hp.com] 
Sent: 8 August 2003 16:13
To: Bass, Mick; www-rdf-dspace@w3.org
Subject: Additional Detail, Requested Actions, Discussion Material RE: SIM
ILE PI phone conference, 08-Aug-03 1200 EDT/1700 BST



Some further detail

2/ Actions to Tune Plan

In particular, I would like to continue to morph the excellent start
captured at the plenary
http://web.mit.edu/simile/www/documents/2003julyplenary/TASK_ASSIGNMENTS.htm
into a more complete and well-reviewed plan.  If we focus on this over the
next week, we should be able to get this done.

I would like this plan to result in demo-able results by the end of this
year, so as we review the plan let us keep that target in mind.

I'd therefore like to ask each of the RESPONSIBLE PIs noted on the leftmost
column of each "Major Activity" (noted in bold) to undertake or ask a
delegate to complete the following before the call next Friday:

(I note that MacKenzie is still vacationing in France, poor thing; shall we
give her a reprieve?)

- review the tasks within the major activity.  Are they necessary &
sufficient to complete the major activity?  Tune as needed.  Try to keep
similar level of granularity.

- Augment each task with a _brief_description_ (more than the six word name
of most tasks, but no longer than a paragraph or three) so others on the
team can understand the nature and completion criteria for the work.

- Under each major activity note the _KEY_DEPENDENCIES_ that you foresee.
Verify that the dependencies will be cleared by other tasks within the plan.
Add comments on dependencies that you believe will be helpful to the program
manager.

- identify any tasks or dependencies that you believe are _high_risk_ or
_in_your_critical_path_.  Propose which individuals on the team need to
discuss these items.

Please use the excel version for your markup, and note changes/additions in
a different font color, to ease merge.


3/ Urgent (Critical Path) Tasks from Plan

It is important that we make progress on the urgent tasks within the plan,
in parellel with tuning the tasks, dependencies, and key milestones.

I would like to discuss those items that you understand that we need to be
tackling right away.

Items that occur to me:
- (em) gather test corpus, including content, RDF Schemas and instance
metadata
- (mjb) complete and circulate demo "scripts"
- (mb, as, ks) early mapping demo, mapping & query capability version plan
- (rt) strawman DSpace / SIMILE architecture whitepaper
- (??) reproducible demo/code env. at MIT, CRL, HPLB, HPLPA

====
970.898.6788 office    240.536.0765 fax
617.899.3938 mobile    303.494.5202 residence
bass@alum.mit.edu      mick_bass@hp.com
====