409 Conflict under 7.1 Error Codes specifically calls out PUT for statements but not POST

[bscSCORM]

POST of statements should also be mentioned here (when posting a batch of statements there can still be a conflict, in which case 409 should still be used)

[andyjohnson]

Fine with this change in patch as sections below clearly reference POST using error code 409.

[garemoko]

Do we also need to look at section 6.3 Concurrency? This currently refers only to PUT (and GET) but not POST.

[andyjohnson]

I'd think we'd only need POST in the context of if it had a GET in it, but I think we don't need to spell that out here. That's my 2 cents but it is definitely worth discussing!

[fugu13]

I'm not sure I follow your comment, @andyjohnson ; 409 conflict occurs when something is being updated, so this is for true POSTs that update state & profile.

I'm fine with this, except the correct response is 412 (per the RFC), not 409, which was an error in the spec. See #356

[fugu13]

Or rather, both, since it looks like the 409/412 stuff is sorted (and both are potentially appropriate and only fully called out for PUT).

[andyjohnson]

So as a part of 1.0.3, lets rework section 6.3 to take into account these considerations as @garemoko said, sorry for the confusing comment earlier.

[garemoko]

This has since been resolved by #520 and #564

I believe this issue can be closed.