ISSUE-36: What to do with the appendix section "Content Coding"
Content Coding
What to do with the appendix section "Content Coding"
- State:
- CLOSED
- Product:
- EXI Spec
- Raised by:
- Takuki Kamiya
- Opened on:
- 2009-04-28
- Description:
- We encountered a mixed reaction from http-bis authorities
upon our request for content-coding tag "exi". The request
even spurred a discussion among http-bis comminuty that indicates
that they are inclined to explicitly abrogate not-byte-preserving
usage in the future because EXI WG is allegedly trying to use a
loophole.
- Related Actions Items:
ACTION-493 on John Schneider to Discuss with http-bis regarding content-encoding issue - due 2009-04-08, closedACTION-543 on Takuki Kamiya to Inform TAG of the registration of "exi" as a content-coding tag - due 2009-09-30, closed- Related emails:
- Agenda for 29 Apr EXI Telecon (from tkamiya@us.fujitsu.com on 2009-04-28)
- ISSUE-36 (Content Coding): What to do with the appendix section 'Content Coding' [EXI Spec] (from sysbot+tracker@w3.org on 2009-04-28)
Related notes:
Discussed during 2009-07-08 telecon. Carine and John agreed that this is not ultimately a blocking issue for declaring CR. JS to continue pursuing what we desire to have independent of CR schedule, though still with hope to see it resolved before CR.
Takuki Kamiya, 8 Jul 2009, 19:02:41Section "F Content Coding and Internet Media Type" has been
changed to be largely agnostic of the interpretation HTTP 1.1 spec.
Display change log
