Thomas F. O'Connell
Thomas F. O'Connell
Per some internal discussion after a conformance-related call with ADL, it seems the spec might benefit from some additional material related to `PUT`. `PUT` is intended to be allowed for...
Currently, the second item under "[Procedure for the Exchange of Attachments](https://github.com/adlnet/xAPI-Spec/blob/master/xAPI-Communication.md#procedure-for-the-exchange-of-attachments)" says this: > The Statement is sent using a Content-Type of multipart/mixed. Any Attachments are placed at the end...
Upon review, it appears that all previous instances of "a system reading a Statement" got converted to "Learning Record Consumer". We missed [one](https://github.com/adlnet/xAPI-Spec/blob/master/xAPI-Data.md#verb-id-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)...