Document PUT requirements eliminate natural idempotence of PUT

[bscSCORM]

Note that these requirements do not allow an exception for the same exact body being PUT multiple times:

If a PUT request is received without either header for a resource that already exists, the LRS:

• MUST return HTTP status 409 Conflict.
• MUST return a response explaining that the Learning Record Provider SHOULD
  • check the current state of the resource.
  • set the "If-Match" header with the current ETag to resolve the conflict.
• MUST NOT make a modification to the resource.

I suggest we change the language above to:

If a PUT request is received without either header for a resource that already exists *but is not identical to the body of the request*, the LRS:

(detailed requirements unchanged)

[garemoko]

+1, we can tweak the language whenever it's added.

Would you agree this is a minor change?

[bscSCORM]

Yes, minor not patch or major, it will require an LRS change but no clients should be relying on the old behavior.

[andyjohnson]

+1, this became too process oriented and less to the point. Agree this is minor.

[andyjohnson]

Per the 2/1/17 call, @bscSCORM 's revision is sound