Only allow Title headers when posting to Media Collections.
There is no need to set the Title header when posting to an Entry Collection since all Entry Resources should have a title already. Posting Entry Resources with two (possibly different) titles only introduces confusion without providing any obvious benefits.
Replace Section 8.1.2 of Draft -07 with the following:
8.1.2 Title Header A POST to a Media Collection creating a resource SHOULD contain a Title header that indicates the client's suggested title for the Media Resource. The server MAY ignore the content of the Title header or modify the suggested title. Title = "Title" ":" [text] The syntax of this header MUST conform to the augmented BNF grammar in section 2.1 of the HTTP/1.1 specification [RFC2616].
The original text had "MAY contain a Title header" rather than "SHOULD contain a Title header", but then went on to say that the practice was RECOMMENDED for Media Collections. Since this proposal is recommending the Title header for Media Collections only it would seem more accurate for that verb to change to SHOULD.
Also removed all colons from the word Title in the description as that is not part of the header.