Although there are various community-driven developments in the Fedora ecosystem, this document describes the roughly 12-month technical focus of the core repository platform.

Technical Priorities

1. Formalize the core Fedora services Application Programming Interface (API)
   This priority is to clearly define the core services that Fedora promises as a standards-based RESTful API, accompany this API with any necessary domain-specific ontologies, and provide a Technology Compatibility Kit (TCK) for each service.
   The Fedora services are:
   1. Create/Read/Update/Delete on repository resources
      1. Standard: Linked Data Platform
      2. Include Import and Export of RDF, and option for RDF serialization to disk
   2. Versioning
      1. Standard (partial, only retrieval): Memento
   3. Transactions
      1. Standard: TBD
   4. Fixity
      1. Standard (partial, on ingest): http://tools.ietf.org/html/rfc3230#section-4.3.2
   5. Authorization
      1. Standard: WebAC
2. Formalize the core Fedora Service Provider Interfaces (SPIs)
   1. Eventing SPI
      1. Defining the interface that a Fedora repository implementation should implement to publish repository events
3. Runtime configurability
   1. Enable the update of configuration settings at runtime, e.g. changing hostname published in repository events
   2. Enable pluggability of extension modules, e.g. adding an OAI-PMH module at runtime
4. Performance and Scale
   1. Establish metrics for repository limits, including:Repository limits -
      1. number of resources
      Repository limits -
      1. number of bytes
      1. Storage optionsEstablish guidelines for storage options based on usage patterns

   Note: Items 1 and 2 define ... priorities related to "Fedora as a specification", whereas Items 3 and 4 ..relate to "Fedora as a reference implementation".