- Created by Chris Beer, last modified by David Wilcox on Jul 27, 2016
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 76 Next »
2016-2017 Technical Roadmap
Formalize the core Fedora services Application Programming Interface (API)
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Note: Items 1 and 2 define priorities related to "Fedora as a specification", whereas Items 3 and 4 relate to "Fedora as an implementation".
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
The Fedora services are:
type
key
summary
assignee
reporter
priority
status
resolution
created
updated
due
type
key
summary
assignee
reporter
priority
status
resolution
created
updated
due
key
summary
type
created
updated
due
assignee
reporter
priority
status
resolution
key
summary
type
created
updated
due
assignee
reporter
priority
status
resolution
type
key
summary
assignee
reporter
priority
status
resolution
created
updated
due
type
key
summary
assignee
reporter
priority
status
resolution
created
updated
due
2015-2016 Technical Roadmap
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:- Create/Read/Update/Delete on repository resources
- Standard: Linked Data Platform
- Include Import and Export of RDF, and option for RDF serialization to disk
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
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.
- Transactions
- Standard: TBD
- Fixity
- Standard (partial, on ingest): http://tools.ietf.org/html/rfc3230#section-4.3.2
- Authorization
- Standard: WebAC
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.
- Create/Read/Update/Delete on repository resources
- Formalize the core Fedora Service Provider Interfaces (SPIs)
- Eventing SPI
- Defining the interface that a Fedora repository implementation should implement to publish repository events
- Eventing SPI
- Runtime configurability
- Enable the update of configuration settings at runtime, e.g. changing hostname published in repository events
- Enable pluggability of extension modules, e.g. adding an OAI-PMH module at runtime
- Performance and Scale
- Establish metrics for repository limits, including:
- number of resources
- number of bytes
- See: Performance and Scalability Test Plans
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.
- Establish guidelines for storage options based on usage patterns
- Establish metrics for repository limits, including:
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".
Previous Technical Roadmap Items
Currently Supported Features | Design | Core | Non-core | 4.0 | Use Cases |
---|---|---|---|---|---|
AuthN/Z | design | x | |||
Backup | design | x | |||
Clustering | x |
| |||
Content Modeling - Structural | x |
Content by label
There is no content with the specified labels | |||
Managed External Datastreams | x | ||||
Store/Deliver Large Files | design | x | |||
design | x | ||||
Transactions | x | ||||
Triplestore | design | x | |||
Versioning | x | ||||
Non-Functional: Easy Deployment | |||||
Non-Functional: Performance - Single-node | |||||
Post-4.0 Priority 1 Features | Design | Core | Non-core | 4.0 | Use Cases |
3 to 4 Upgrade | design | x |
Content by label
There is no content with the specified labels | ||
Audit Service | design | x | |||
Managed External Datastreams - Indexing | x | ||||
Asynchronous storage API | design | x | |||
Asynchronous storage Implementation | x | ||||
LDP-Paging | x | ||||
Web Access Control | x | ||||
API Partitioning | x | ||||
Post-4.0 Priority 2 Features | Design | Core | Non-core | 4.0 | |
Batch Operations | x |
| |||
CMIS | x | ||||
Content Modeling - Services and Validation | |||||
Disseminator-like Functionality | x | ||||
Human-readable Filesystem Storage | x | ||||
Metrics | x | ||||
Multi-tenancy | x | ||||
OAI-PMH | design | x | |||
ORCID Support | x | ||||
Policy-driven Storage | design | x |
| ||
Relationships API | x | ||||
Self-healing Storage | x | ||||
WebDAV | x | ||||
Non-Functional: Performance - Clustered | |||||
Previously Un-prioritized Features | Design | Core | Non-core | 4.0 | Use Cases |
Admin UI | x | ||||
Content API | x | ||||
Identifiers | x | ||||
Large-Scale Content | x |
- No labels