Audience:

• Application/framework developers?

• Managers/stakeholders?

• Fedora committers?

• ?

Purpose:

• Allow the community to make decisions about aspects of fedora’s current API that are outside of any specification?

• Breaking changes due to alignment with the specification (e.g. drop support for “snapshot” versioning, move to memento-based versioning in spec)

• Deprecating features completely

• Keeping features that are outside any specification, but allowable

• Allow the development of timelines for implementing specific breaking changes in the current Fedora impl?

• Aid in communicating “what’s changing” to the community?

• Aid in evaluating the proposed Fedora specification?  

• Allow application developers to identify what they need to do (if anything) to update their applications so that they work with Fedora instances that follow the new specification?

• Allow application developers to identify which not-specified-but-allowable behaviors unique to the the current Fedora implementation their application relies on?

• .. and either move away from them, or acknowledge and affirm them?

Outcomes:

• High-level overview document?

• Detailed/comprehensive section-by-section comparison with specs?