adlnet
Statement Batches: LRS Requirements Should Be as Strict as Request Requirements
Right now, "Requirements for Attachment Statement Batches" requires this of requests:
MUST include a Content-Transfer-Encoding parameter with a value of "binary" in each part's header after the first (statements) part.
But the LRS requirements include this:
When receiving a PUT or POST with a document type of "multipart/mixed”, an LRS SHOULD assume a Content-Transfer-Encoding of binary for attachment parts.
Allowing an LRS to be less strict than the issuer of the request would seem to set a bad precedent for strictness.
This will probably have to wait for 2.0, but I wanted to go ahead and open the issue, as it recently raised an implementation question.
Looks like those were added together intentionally in https://github.com/adlnet/xAPI-Spec/commit/0c861ecbb8259ff2cccd30d2281ce4547ab665b2
Definitely an area we could touch up in a future version.
