Fedora's alignment with each category of the Fedora API Specification needs to be verified for completeness and correctness. Below is a listing of the specification categories, the person/people taking the lead on ensuring alignment, and the current status of alignment.
- Untested |
3.1 General (Jared Whiklo)
3.1.1 LDP Containers
3.1.2 LDP-NR creation
3.1.3 Constraints Document
3.1.4 Data Model
3.2 HTTP GET3.2.1 Additional values for the Prefer header
3.2.2 LDP-RSs
3.2.3 LDP-NRs
3.3 HTTP HEAD
3.4 HTTP OPTIONS (Yinlin Chen)
3.5 HTTP POST
3.5.1 LDP-NRs
3.6 HTTP PUT
3.6.1 LDP-RSs
3.6.2 LDP-NRs (Danny Bernstein)
3.6.3 Creating resources with HTTP PUT
3.7 HTTP PATCH (Jared Whiklo)
3.7.1 Containment Triples
3.7.2 Interaction models
3.8 HTTP DELETE (Yinlin Chen)
3.8.1 Recursive Delete
3.9 External Binary Content (As of 4/21/18, this section is in the process of being implemented)
3.9.1 Referenced RDF content in mandataory LDP serializations
3.8.2 Proxied content vs. redirected content
|
4.1 Versioned Resources
4.1.1 HTTP GET (LDPRv)
4.1.2 HTTP PUT (Danny Bernstein)
4.2 Version Resources (LDPRm)
4.2.1 HTTP GET §
4.2.2 HTTP OPTIONS §
4.2.3 HTTP POST
4.2.4 HTTP PUT
4.2.5 HTTP PATCH
4.2.6 HTTP DELETE
4.3 Version Containers (LDPCv) (Jared Whiklo)
4.3.1 HTTP GET (Jared Whiklo)
4.3.2 HTTP OPTIONS (Jared Whiklo)
4.3.3 HTTP POST
4.3.4 HTTP DELETE
4.4 VaryNon-normative note: When a Verify whether this is done and if not create JIRA.e 4.5 Implementation PatternsNon-normative note: This section describes the way the normative specification might be applied to implement discoverable versioning patterns. If an implementation of an LDPCv does not support 4.5.1 Server-Managed Version Creation §Non-normative note: Upon 4.5.2 Client-Managed Version Creation §Non-normative note: An LDPRm for a particular LDPRv is created on 4.5.3 Replacing Contents from Mementos §Non-normative note: Using the ingest-by-reference mechanism, one can replace the contents of an LDPRvwith that of an LDPRm by providing it's URL as the |
5. Resource Authorization §
5.1 ACLs are LDP RDF Sources §5.2 ACL Representation and Interpretation § (Danny Bernstein)
5.3 ACLs are discoverable via Link Headers §
5.4 ACL linking on resource creation §
5.5 Cross-Domain ACLs §
5.6 Cross-Domain Group Listings §
5.7 Append Mode §
5.7.1 LDP-RS §
5.7.2 LDPC §
5.7.3 LDP-NR §
5.8 Access To Class §
5.9 Inheritance and Default ACLs §
|
6.2 Notification Events §
6.3 Notification Serialization §
Each event described by a notification must contain:
Each event described by a notification should contain:
|
7.1 What is fixity?Example proceedures that may be used to verify fixity:
7.2 Transmission Fixity
7.3 Persistance Fixity
|