The table below is derived from the following document
Fedora API Spec and Delta Document Verification
Issue Description | Spec Reference | Priority | Difficulty | Related JIRAs | Depends on | Notes |
---|---|---|---|---|---|---|
Change the PreferInboundReferences URI in Prefer header from http://fedora.info/definitions/v4/repository#InboundReferences to the one defined in the spec (ie http://fedora.info/definitions/fcrepo#PreferInboundReferences) | 3.2.1 | 1 | 1 | |||
HTTP Head does not return the same headers as if the request were a GET | 3.3 | |||||
POSTing a LDP-NR does not return correct constrainedBy Link header | 3.5 | |||||
MUST return 409 if request's type Link is not resource's current type or subtype thereof, or not in LDP namespace
MUST change resource's type if request's type Link is a subtype of resource's current type MUST change resource's interaction model if request's type Link has an LDP interaction model | 3.6 | |||||
Using PATCH it is currently possible to add an rdf:type of ldp:NonRDFSource to an existing ldp:RDFSource. This should not | 3.7.1 | |||||
Replace current Link rel="type" Header with memento specified link (i.e. http://mementoweb.org/ns#OriginalResource) | 4.1 | |||||
The Accept-Datetime header is used to request a past state, exactly as per [RFC7089] section 2.1.1. A successful response must be a 302 (Found) redirect to the appropriate LDPRm | 4.1.1 | |||||
If no LDPRm is appropriate to the Accept-Datetime value, an implementation should return a 406 (Unacceptable). | 4.1.1 | |||||
The response to a
| 4.1.1 | |||||
LDPm GET
| 4.2.1 | find existing | ||||
LPPm OPTIONS
| 4.2.2 | |||||
LDPm: PUT, POST, and PATCH must return 405 method not allowed | 4.2.3-5 | |||||
LDPm: DELETE The server is responsible for all behaviors implied by the LDP-containment of the LDPRm. | 4.2.6 | This is a MAY: Are we planning to implement? | ||||
LDPCv : An implementation must support | 4.3.2 | |||||
LDPCv: Disallow PUT and PATCH | 4.3.2 | |||||