Can't do anything about the lines until 8 hrs from now. Will do later.

Date: Wed, 27 Mar 2013 14:03:05 -0700
From: notifications@github.com
To: xAPI-Spec@noreply.github.com
CC: paul.esch@outlook.com
Subject: Re: [xAPI-Spec] Rewrite of 4.1.11 Attachments (#99)

In xAPI.md:
>  
> -In order to allow systems receiving statements with attachments to examine the rest of the statement,
> -and possibly decide to reject it, before receiving attachments, statements with attachments will be
> -transmitted using a content-Type of multipart/mixed rather than in-lining the attachments. Attachments 
> -will be placed at the end of such transmissions, though they are still logically part of the statements.
> -This capability will be available when issuing PUT or POST against the statement resource.
> +###Rationale: 
> +In some cases an attachment may logically be an important part of a learning record. Think of a simulated communication with ATC, an essay, a video,  etc. Another common example of such an attachment is (the image of) a certificate that was granted as a result of an experience. It is useful to have a way to store these attachments in and retrieve them from an LRS. 

Hi Paul,

Thanks again for your continued work. 

Please can I ask that you put things across multiple lines so it's easier to review and comment on?

I'd avoid the word common on this line as we don't yet know what's common. 

I'll try and have a look at the rest tomorrow. 

Andrew

—
Reply to this email directly or view it on GitHub.