Purpose

To formulate, discuss, and prioritize the next steps in the Fedora Roadmap.  We hope to leave this two-day meeting with a clear vision of the development priorities of the core repository service for the next year, and a good sense of who can contribute to accomplishing them. 

Where/When

• Location TBD
• Feb 23rd: 10am - ?
• Feb 24th: 10am - ?

Attendees

Many of the committers will be attending this meeting, and we are actively seeking key contributors to come and help us define the future of Fedora. This will be a relatively small group; we are planning to have space for approx. 20 attendees.

Confirmed attendees will be listed here in the coming weeks.  Currently, we are keeping track of this information here.

Topics of Discussion

This is the updated list of topics that includes input as of Jan. 19th.

• More sophisticated content modeling support
  • Asger's Enhanced Content Models (ECM)?
  • WSDL parsing
  • including full graph of relationships among objects
• Storage Pluggability
  • tiered/hierarchical and
  • multiplexed storage support
• Performance and Caching
  • very large datastream optimization
  • large numbers of objects optimization
• Relationships and Triplestore integration
  • Trippi and alternative triplestores
  • Json output for triplestore search
• Module Architecture: OSGi, Spring, etc
• Extended service execution (overlaps CMA and Module architecture)
  • simplifying service attachments to objects
  • disseminators that trigger on ingest
• Messaging
• Next Generation REST API
  • Json output for REST api results
• Workflow engine integration for the fedora-system namespace
• Creating an OWL ontology
• WebDAV support
• Better adminsitrative tools
  • Object builders for CModel, SDef and SDep objects
  • Policy editor integration
• Validation frameworks
• Security