Re: CR089 (was: Status: Editorial action items)

DONE.

Jonathan Marsh wrote:
> Re CR087, if no content encoding is specified, or if an empty value is
> specified, a Content-Encoding header with an empty value is inserted.  Is
> this what we want or can empty Content-Encoding headers be omitted?  My
> reading of http://www.ietf.org/rfc/rfc2616.txt is that an empty value isn't
> permitted.  A fairly intrusive rewording of 6.4.2 would be necessary to
> reflect this.
>
>   6.4.2 HTTP Content Coding Selection
>
>   When formulating the HTTP message to be transmitted, content encoding for 
>   a given Binding Message Reference component is determined as follows:
>
>   - If the {http content coding} property has a non-empty value, a 
>     Content-Encoding header-field MUST be inserted with the value of 
>     this property.
>
>   - Otherwise, if the value of the parent Binding Operation component's 
>     {http content coding default} property has a non-empty value, a 
>     Content-Encoding header-field MUST be inserted with the value of this 
>     property.
>
>   - Otherwise, if the value of the grandparent Binding component's {http
>     content coding default} property has a non-empty value, a 
>     Content-Encoding header-field MUST be inserted with the value of 
>     this property.
>
>
>   When formulating the HTTP fault message to be transmitted, content 
>   Encoding for a given Binding Fault component is determined as
>   follows:
>
>   - If the {http content coding} property has a non-empty value, then a
>     Content-Encoding header-field MUST be inserted with the value of this
>     property.
>
>   - Otherwise, if the parent Binding component's {http content coding
>     default} has a non-empty value, then a Content-Encoding header-field 
>     MUST be inserted with the value of this property.
>
>   The body of the response message is encoded using the specified content 
>   encoding.