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. Finalize the Fedora Application Programming Interface (API)

    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. Align the community Fedora implementation with the API Specification
    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 (on 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. Fixity
      1. Standard: http://tools.ietf.org/html/rfc3230#section-4.3.1 (Want-Digest) & http://tools.ietf.org/html/rfc3230#section-4.3.2 (Digest)
      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. 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.

    5. Notifications
      1. Standard: Activity Streams 2.0
      2. Defining the interface that a Fedora repository implementation should implement to publish repository events
  3. Develop a Compliance Test Suite for each service defined in the Fedora API Specification.

  • No labels