...
Expand |
---|
March 5, 2018 (Mon) Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2681 |
---|
| - Jared Whiklo Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2690 |
---|
| - Danny BernsteinMarch 6, 2018 (Tues) Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2694 |
---|
| - Jared Whiklo Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2675 |
---|
| - Longshou Situ Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2669 |
---|
| - Jared WhikloMarch 7th, 2018 (Wed) Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2696 |
---|
| - Longshou Situ Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2661 |
---|
| - Joe Harrington Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2686 |
---|
| - Longshou Situ Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2678 |
---|
| - Longshou Situ Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2677 |
---|
| - Yinlin ChenMarch 8th, 2018 (Thurs) |
Ticket to Specification Tracking
The table below is derived from the following document
Fedora API Spec and Delta Document Verification
...
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)
...
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2679 |
---|
| - Longshou Situ Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2617 |
---|
| - Ben Pennell Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2699 |
---|
| - |
...
Randall Floyd Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
|
...
...
- Danny Bernstein March 9th, 2018 (Fri) |
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2713 |
---|
| - |
...
Danny Bernstein March 12th, 2018 (Mon |
...
) Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
|
...
...
- Randall Floyd Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
|
...
...
- Though the message coming back in the case of an attempt to move from RDFSource to NonRDFSource says "Resource Already Exists" instead of returning a constrained by header
- Same message is returned trying to move from ldp:Container to an ldp:DirectContainer or ldp:BasicContainer or ldp:Container
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
Using PATCH it is currently possible to add an rdf:type of ldp:NonRDFSource to an existing ldp:RDFSource. This should fail with a 409.
...
- Longshou Situ March 13th, 2018 (Tues)none March 14th, 2018 (Wed) Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92 |
---|
|
|
...
-fd23-34c2-8fe3-956808caf8c5 | key | FCREPO-2706 |
---|
| - Ben Pennell Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2591 |
---|
| - Longshou Situ Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2594 |
---|
|
|
...
- Longshou Situ Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2701 |
---|
| - Randall Floyd |
...
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
|
...
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
If no LDPRm is appropriate to the Accept-Datetime
value, an implementation should return a 406 (Unacceptable).
...
- Randall Floyd Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2703 |
---|
| - Randall Floyd Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
|
...
The response to a GET
request on an LDPRv must include the following headers
- A
<http://mementoweb.org/ns#TimeGate>; rel="type"
link in the Link
header - A
<http://mementoweb.org/ns#OriginalResource>; rel="type"
link in the Link
header
- Ben Pennell Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2618 |
---|
| - Longshou Situ |
...
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO |
---|
|
|
...
- Joe HarringtonMarch 15th, 2018 (Thurs) Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
|
...
...
LDPm GET
- An implementation must support
GET
, as is the case for any LDPR. - The headers for
GET
requests and responses on this resource must conform to [RFC7089] section 2.1. Particularly it should be noted that the relevant TimeGate for an LDPRm is the original versioned LDPRv. - In addition, any response to a
GET
request must include a <http://mementoweb.org/ns#Memento>; rel="type"
link in the Link
header.
...
- Joe Harrington Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2722 |
---|
| - Yinlin Chen Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2615 |
---|
| - Longshou Situ |
...
LPPm OPTIONS
- An implementation must support
OPTIONS
. - A response to an
OPTIONS
request must include Allow: GET, HEAD, OPTIONS
as per [LDP]. - An implementation may include
Allow: DELETE
if clients can remove a version from the version history, as noted in 3.8 HTTP DELETE.
...
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2721 |
---|
| - |
...
Randall Floyd March 16th, 2018 (Fri) Jira |
---|
server | DuraSpace JIRA |
---|
serverId |
---|
|
|
c815ca92-fd23-34c2-8fe3-956808caf8c5 | key | FCREPO- |
---|
|
|
...
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
|
...
LDPm: DELETE
The server is responsible for all behaviors implied by the LDP-containment of the LDPRm.
...
- Longshou Situ Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2723 |
---|
| - Joe Harrington |
Ticket to Specification Tracking
The table below is derived from the following document
Fedora API Spec and Delta Document Verification
2620This is a MAY: Are we planning to implement? | LDPCv : An implementation must support GET
, as is the case for any LDPR. Any response to a GET
request must include a <http://mementoweb.org/ns#TimeMap>; rel="type"
link in the Link
header. Currently the <http://fedora.info/definitions/v4/repository#TimeMap> is being used.
4.3.2 | 1 | 2 | 2 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2643 |
---|
|
(may be closed - depending on approach to fcrepo-2617)Issue Description | Spec Reference | Priority | Difficulty | Story Points | Related JIRAs | Can be worked now | Sprint | Depends on | Notes |
---|
Duplicate headers when GETting binaries |
| 1 | 1 | 1 |
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
|
2681LDPCv: Disallow PUT and PATCH | 4.3.2 | 1 | 1 | 1 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
|
2686x | LDPCv: POST - A
POST that does not contain a Memento-Datetime header should be understood to create a new LDPRm contained by the LDPCv, reflecting the state of the LDPRv at the time of the POST . Any request body must be ignored. A Memento-Datetime header should be understood to create a new LDPRm contained by the LDPCv, with the state given in the request body and the datetime given in the Memento-Datetime request header.
| Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2696 |
---|
|
| x |
|
|
|
HTTP Head does not return the same headers as if the request were a GET | 3.3 | 3 | 1 | 1 |
4.3.3 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
|
2617 Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
|
2618LDPCv: DELETE: Delete of an LDPCv must remove the LDPCv and removing the versioning interaction model from the original LDPRv.
| 4.3 | 1 | 2 | | x |
|
|
|
POSTing a LDP-NR does not return correct constrainedBy Link header | 3.5 | 2 | 1 | 1 |
2 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
|
2684Vary : When an LDPCv supports POST , and allows clients to specify a datetime for created URI-Ms, Vary-Post/Vary-Put: Memento-Datetime. | 4.4 | 1 | 1 | 1 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | LDPm GET | Are we planning to support DELETE? | x |
|
|
|
MUST return 409 if request's type Link is not resource's current type or subtype thereof, or not in LDP namespace- Though the message coming back in the case of an attempt to move from RDFSource to NonRDFSource says "Resource Already Exists" instead of returning a constrained by header
- Same message is returned trying to move from ldp:Container to an ldp:DirectContainer or ldp:BasicContainer or ldp:Container
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 Using PATCH it is currently possible to add an rdf:type of ldp:NonRDFSource to an existing ldp:RDFSource. This should fail with a 409. | 3.6, 3.7.1 | 1 | 3 | 3 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId |
---|
|
|
c815ca92-fd23-34c2-8fe3-956808caf8c5 | key | FCREPO- |
---|
|
|
2685xLDPc POST | 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 URL
parameter in a Content-Type: message/external-body
header. For example, given an LDPRm with URL http://example.org/some/memento
, the full header would be
Content-Type: message/external-body; access-type=URL; expiration=1;
URL="http://example.org/some/memento"
4.5.3 | 5 | 3 | 2 | server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2594 |
---|
|
| x |
|
| Behavior or Direct and Indirect containers must be verified once these two tickets have been resolved. |
Replace current Link rel="type" Header with memento specified link (i.e. http://mementoweb.org/ns#OriginalResource) | 4.1 | 1 | 1 | 1 |
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
|
2682Default acls must be defined in accordance with the SOLID WEBAC spec. | 5.0 | 2 | 2 | 2 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2683 |
---|
|
| x | Non-normative note: Implementations may set default access controls for all resources by including an ACL for the root container with an authorization that applies to access by any agent (acl:agentClass foaf:Agent ), applies to any resource (acl:accessToClass ldp:Resource ), and is defined to be inherited (acl:default ). The example below grants read access (acl:mode acl:Read ) but any combination of modes may be specified. | 5.2 | 1 | 2 | | x |
|
|
|
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 If no LDPRm is appropriate to the Accept-Datetime value, an implementation should return a 406 (Unacceptable). | 4.1.1 | 1 | 2 | 2 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2613 |
---|
|
| x |
| LDPm GET |
|
The response to a GET request on an LDPRv must include the following headers
| 4.1.1 | 1 | 1 | 1 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2678 |
---|
|
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2679 |
---|
|
| x |
|
|
|
LDPm GET - An implementation must support
GET , as is the case for any LDPR. - The headers for
GET requests and responses on this resource must conform to [RFC7089] section 2.1. Particularly it should be noted that the relevant TimeGate for an LDPRm is the original versioned LDPRv. - In addition, any response to a
GET request must include a <http://mementoweb.org/ns#Memento>; rel="type" link in the Link header.
| 4.2.1 | 1 | 3 | 3 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2614 |
---|
|
| x |
| LDPCv: POST | This may be complete with the resolution to fcrepo-2617. Needs to be verified. |
LPPm OPTIONS - An implementation must support
OPTIONS . - A response to an
OPTIONS request must include Allow: GET, HEAD, OPTIONS as per [LDP]. - An implementation may include
Allow: DELETE if clients can remove a version from the version history, as noted in 3.8 HTTP DELETE.
| 4.2.2 | 1 | 1 | 1 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2615 |
---|
|
| x |
| LDPm GET |
|
LDPm: PUT, POST, and PATCH must return 405 method not allowed | 4.2.3-5 | 1 | 1 | 1 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2616 |
---|
|
| x |
| LDPm GET |
|
LDPm: DELETE The server is responsible for all behaviors implied by the LDP-containment of the LDPRm. | 4.2.6 |
|
|
| Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2620 |
---|
|
| x |
|
| This is a MAY: Are we planning to implement? |
LDPCv : An implementation must support GET , as is the case for any LDPR. Any response to a GET request must include a <http://mementoweb.org/ns#TimeMap>; rel="type" link in the Link header. Currently the <http://fedora.info/definitions/v4/repository#TimeMap> is being used.
| 4.3.2 | 1 | 2 | 2 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2643 |
---|
| (may be closed - depending on approach to fcrepo-2617) Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2681 |
---|
|
|
|
|
|
|
LDPCv: Disallow PUT and PATCH | 4.3.2 | 1 | 1 | 1 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2686 |
---|
|
| x |
|
|
|
LDPCv: POST - A
POST that does not contain a Memento-Datetime header should be understood to create a new LDPRm contained by the LDPCv, reflecting the state of the LDPRv at the time of the POST . Any request body must be ignored. A Memento-Datetime header should be understood to create a new LDPRm contained by the LDPCv, with the state given in the request body and the datetime given in the Memento-Datetime request header.
| 4.3.3 |
|
|
| Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2617 |
---|
|
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2618 |
---|
|
| x (2618) |
|
|
|
LDPCv: DELETE: Delete of an LDPCv must remove the LDPCv and removing the versioning interaction model from the original LDPRv.
| 4.3 | 1 | 2 | 2 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2684 |
---|
|
| x |
| LDPm GET | Are we planning to support DELETE? |
Vary : When an LDPCv supports POST , and allows clients to specify a datetime for created URI-Ms, Vary-Post/Vary-Put: Memento-Datetime. | 4.4 | 1 | 1 | 1 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2685 |
---|
|
| x |
| LDPc POST |
|
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 URL parameter in a Content-Type: message/external-body header. For example, given an LDPRm with URL http://example.org/some/memento , the full header would be
Content-Type: message/external-body; access-type=URL; expiration=1; URL="http://example.org/some/memento" | 4.5.3 | 5 | 3 | 2 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2682 |
---|
|
|
|
|
|
|
Create container mementos from body |
|
|
|
| Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2706 |
---|
|
|
|
|
|
|
Provide separate timemap for binary and description |
|
|
|
| Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2707 |
---|
|
|
|
|
|
|
Create historical binary mementos |
|
|
|
| Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2708 |
---|
|
|
|
|
|
|
Create binary description mementos |
|
|
|
|
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2709 |
---|
|
|
|
|
|
|
Ignore referential integrity of memento properties |
|
|
|
|
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2710 |
---|
|
|
|
|
|
|
Default acls must be defined in accordance with the SOLID WEBAC spec. | 5.0 | 2 | 2 | 2 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2683 |
---|
|
| x |
|
|
|
Non-normative note: Implementations may set default access controls for all resources by including an ACL for the root container with an authorization that applies to access by any agent (acl:agentClass foaf:Agent ), applies to any resource (acl:accessToClass ldp:Resource ), and is defined to be inherited (acl:default ). The example below grants read access (acl:mode acl:Read ) but any combination of modes may be specified. | 5.2 | 1 | 2 | 3 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2632 |
---|
|
| x |
|
|
|
The interaction pattern for ACL discovery is described in [SOLIDWEBAC] ACL Resource Location Discovery. A conforming server must advertise the individual resource ACL for every controlled resource in HTTP responses with a rel="acl" link in the Link header, whether or not the ACL exists. The ACL resource should be located in the same server as the controlled resource. | 5.3 | 1 | 2 | 2 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2704 |
---|
|
| x |
| depends on fcrepo-2688 |
|
The server must reject the request and respond with a 4xx or 5xx range status code, such as 409 (Conflict) if it isn't able to create the LDPR with the specifiedLDP-RS as the ACL. In that response, the restrictions causing the request to fail must be described in a resource indicated by a rel="http://www.w3.org/ns/ldp#constrainedBy" link in the Link response header, following the pattern of [LDP] 4.2.1.6. | 5.4 | 1 | 1 | 1 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2705 |
---|
|
| x |
| depends on fcrepo-2688 |
|
Restrict Cross Domain ACLs | 5.5 | 2 | 2 | 2 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2687 |
---|
|
| x |
|
|
|
Implement ACL linking on resource creation | 5.4 | 2 | 2 | 2 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2688 |
---|
|
| x |
|
|
|
| 5.7.1 | 1 | 1 | 1 |
3 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
|
2632Restrict Cross Domain ACLs | 5.5 | 2 | 2 |
|
|
|
| 5.7.1 | 1 | 1 | 1 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2716 |
---|
|
|
| depends on fcrepo-2716 |
|
|
| 5.7.1,2 | 1 | 1 | 1 |
2 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
|
2687x | |
| depends on fcrepo-2717 |
|
|
| 5.7.3 | 1 | 1 | 1 |
Implement ACL linking on resource creation | 5.4 | 2 | 2 | 2 | Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
|
2688x | ACL Append mode: jiras need to be created. | 5.7 | JIRAs needed! |
|
|
When an ACL includes an acl:accessToClass statement, it gives access to all resources with the specified type, whether that type is client-managed or server-managed.
| 5.8 |
|
|
| Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2689 |
---|
|
| x |
|
|
|
Verify ACL inheritance | 5.9 |
|
|
| JIRAs needed! |
|
|
|
|
Critical Non-Alignment Issues to be included in the 5.0.0 release
Jira | Priority | Depends On | Story Points |
---|
|
|
|
|
|
|
|
|
|
|
|
|