Issues

Unclear what metadata property should represent in Status Document
swordapp/swordv3#36 · opened on Oct 13, 2025
Service document should support advertising min and max segment sizes
swordapp/swordv3#34 · opened on Apr 2, 2020
2
Consider adding a worked example of an object that sword works with
swordapp/swordv3#32 · opened on Mar 12, 2020
1
May wish to split SWORD Behaviours 2.6 into two entries
swordapp/swordv3#30 · opened on Feb 29, 2020
1
Be more clear with errors which protocol operations can raise them
swordapp/swordv3#27 · opened on Feb 29, 2020
1
AuthenticationFailed error response is inconsistent with HTTP spec
swordapp/swordv3#20 · opened on Jan 31, 2020
1
Consider whether Digest requirement is MUST, MAY, SHOULD or unnecessary
swordapp/swordv3#19 · opened on Jan 29, 2020
1
Consider using a /.well-known/ URI for service discovery
swordapp/swordv3#18 · opened on Jan 29, 2020
2
POST to Object-URL should return 201 in some circumstances
swordapp/swordv3#17 · opened on Jan 29, 2020
2
Move lastAction out of status doc
swordapp/swordv3#16 · opened on Jan 29, 2020
1
We ask for filename in the Content-Disposition but we don't do anything with it
swordapp/swordv3#13 · opened on Jan 10, 2020
2
BagIt Profile for SWORDBagIt
swordapp/swordv3#6 · opened on Jan 2, 2020
2
Clarify what happens when you POST to a Service-URL with an empty body
swordapp/swordv3#5 · opened on Dec 13, 2019
1
The tables of layered requirements are unusable
swordapp/swordv3#2 · opened on Dec 12, 2019
1
Guidance on multiple metadata documents in different formats
swordapp/swordv3#1 · opened on Dec 11, 2019
2