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
Finalize the Fedora Application Programming Interface (API)
tickets...
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.
Align the community Fedora implementation with the API Specification Create/Read/Update/Delete on repository resources Standard: Linked Data Platform Include Import and Export of RDF, and option for RDF serialization to disk tickets...
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.
Versioning Standard (partial, only retrieval): Memento tickets...
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.
Fixity Standard (partial, on ingest): http://tools.ietf.org/html/rfc3230#section-4.3.2 Click here to expand...
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.
Authorization Standard: WebAC tickets...
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.
Notifications Standard: Activity Streams 2.0 Defining the interface that a Fedora repository implementation should implement to publish repository events Develop a Compliance Test Suite for each service defined in the Fedora API Specification .