|9:00||Registration, introductions, opening comments and agenda setting|
|9:30||Lightning Talks: Each project gives a 5-minute talk describing the architectures and technologies used in their project, their technical orientation towards interoperability and their immediate technical roadmap. Note that materials will have been solicited from each project in advance, collated, and posted on the meeting's website.|
|10:30||Rob Sanderson: Overview of the Open Annotation Collaboration Project|
|11:00||Group Session: Discussion to identify areas of similarity and difference, and to compare both roadmaps and wish-lists. |
GOALS: To develop a preliminary conceptual framework that maps the landscape of represented repositories, tools and projects. To identify clusters of activity which take similar approaches or use similar technologies. To identify a concrete set of specific issues to address in the balance of the meeting: approaches to image-serving, metadata aggregation, etc.
|1:00||Afternoon Breakout sessions:|
Repository Group: Address architectural and functional similarities and differences. Define common approaches to exposing data and metadata to other repositories and tools. Generate a list of services repositories are built to provide, or ought to provide.
Tool Group: Tool-builders define what they require from repositories to act against the metadata and data stored in them. Generate a list of services they would subscribe to in order to collect data from repositories.
GOALS: Short documents summarizing what repositories can reliably provide, what tool-builders need, and how each group is responding to scholarly needs.
|3:30||Group session: Bringing the results of the breakout sessions to the group; brainstorming for problems presented, potential strategies, etc.|
GOAL: provide some guidelines for work to be accomplished on Saturday
|7:00||Group Dinner at the Oaxacan Kitchen in Palo Alto|
|9:00||Morning Brief Group session: Reflections on Friday’s work and agenda adjustments as necessary.|
|9:30||Use Case Breakout sessions: Each breakout group will be composed of representatives from both repositories and tool–builders and will work on a specific use case. Groups can self-select. The output will be to diagram (and explain) the interaction between repositories and tools for the given use case. The use cases should account for more than one repository and more than one tool and should also take into account specific challenges raised by metadata standards and preservation requirements. Three possible use-case scenarios are:|
|11:00||Breakout sessions (cont.)|
|1:00||Afternoon Group session: Reports from morning breakout sessions. From these
reports, consolidate requirements.|
GOAL: a draft list of requirements and/or requirements framework
|3:00||Group session or Breakout sessions: Map next steps. Identify and call-out possible near-term partnerships for model development, prototype interactions, and real-world uses.|
GOAL: a draft document outlining specific next steps and willing partners
|4:00||Wrap-up and Closing remarks|
|6:30||Group Dinner - Gordon Biersch|