Friday:

• Introductions to individuals

• Introductions to participating institutions

• MONK mission statement/Users/End-user applications: What is MONK going to enable? For whom? What are the end-user tools we envisage for MONK? What tasks do they enable? What use cases will they support? How do we obtain those use cases? When and how will we evaluate usability, usefulness, etc.?

• Design principles: can we say, broadly speaking, what are some basic principles in the technical design of MONK?

• Project management & support: What are the subprojects (such as the topics above)? Who will direct them and who will work on them? How will work assignments be made? What are their interdependencies, what they will produce, and how they will communicate? How will work be designated MONK-"chargeable"? How will disagreements be reviewed and resolved? What tools do we have for communications? What are our plans for process management?

• Schedule, nature and purpose for future meetings

• Budget

• Major milestones over the next two years

• What do we do between now and the next meeting?
  • Generate documented use-cases
  • Define data model
  • Define preliminary spec for MONK architecture
  • Working pieces for at least some of these things

Saturday morning:

Data Cell: Amit (Chair)

Uses and Users Cell: Catherine (Chair)

Interface Cell: Stan (Chair)

Analytics Cell: Steve (Chair)

Collaboration Cell: John U. Chair for a day