Formalize Finalize 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.

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. 
      

      Expand
      title tickets...
      Jira server DuraSpace JIRA jqlQuery filter=13402 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

      
      

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

   2. 
      

      Expand
      title tickets...
      Jira server DuraSpace JIRA jqlQuery filter=13403 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

      
      

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

   2. 
      

      Expand
      Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter= 13407 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

      
      

4. Authorization
   1. Standard: WebAC

   2. 
      

      Expand
      title tickets...
      Jira server DuraSpace JIRA jqlQuery filter=13404 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

1. 1. 
      

2. Notifications
   1. Standard: Activity Streams 2.0
3. Messaging SPI
   2. Defining the interface that a Fedora repository implementation should implement to publish repository events