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.

    type key summary assignee reporter priority status resolution created updated due

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.


    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

      3. type key summary assignee reporter priority status resolution created updated due

        Unable to locate Jira server for this macro. It may be due to Application Link configuration.

    2. Versioning
      1. Standard (partial, only retrieval): Memento

      2. type key summary assignee reporter priority status resolution created updated due

        Unable to locate Jira server for this macro. It may be due to Application Link configuration.

    3. Atomic Batch Operations
      1. Standard: TBD

      2. key summary type created updated due assignee reporter priority status resolution

        Unable to locate Jira server for this macro. It may be due to Application Link configuration.

    4. Fixity
      1. Standard (partial, on ingest): http://tools.ietf.org/html/rfc3230#section-4.3.2

      2. key summary type created updated due assignee reporter priority status resolution

        Unable to locate Jira server for this macro. It may be due to Application Link configuration.

    5. Authorization
      1. Standard: WebAC

      2. type key summary assignee reporter priority status resolution created updated due

        Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  2. Formalize the core Fedora Service Provider Interfaces (SPIs)
    1. Messaging 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:
      1. number of resources
      2. number of bytes
      3. See: Performance and Scalability Test Plans

      4. type key summary assignee reporter priority status resolution created updated due

        Unable to locate Jira server for this macro. It may be due to Application Link configuration.

    2. Establish 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 an implementation".

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.