ACTION-452: Draft response to LC-2164
Draft response to LC-2164
- State:
- closed
- Person:
- Jaakko Kangasharju
- Due on:
- February 18, 2009
- Created on:
- December 17, 2008
- Associated Product:
- EXI Spec
- Related emails:
- Agenda for 07 Jan EXI Telecon (from tkamiya@us.fujitsu.com on 2009-01-06)
- ACTION-452: Reply text for LC-2164 (from jkangash@cc.hut.fi on 2008-12-22)
- Minutes of the EXI telecon of 17-Dec-2008 (from tkamiya@us.fujitsu.com on 2008-12-17)
Related notes:
EXI options schema uses a pragmatic approach based on frequency.
Implementation can provide an API that serves the suggested selection.
Original comment:
http://lists.w3.org/Archives/Public/public-exi-comments/2008Nov/0004.html
Drafted response:
http://lists.w3.org/Archives/Member/member-exi-wg/2008Dec/0033.html
Response from commenter:
http://lists.w3.org/Archives/Public/public-exi-comments/2009Jan/0014.html
Responded.
http://lists.w3.org/Archives/Public/public-exi-comments/2009Feb/0002.html
Response from commenter:
http://lists.w3.org/Archives/Public/public-exi-comments/2009Feb/0013.html
Discussed in 2009-03-18 telecon.
- The tweak required would cause only small amount of code in the order of bytes, not kilo-bytes.
- More broadly, EXI is prudent about the code size as well. EXI could have designed header in special mechanism, but it is using schema binding to enable code-sharing.
Responded.
http://lists.w3.org/Archives/Public/public-exi-comments/2009May/0002.html
Response from commenter:
http://lists.w3.org/Archives/Public/public-exi-comments/2009May/0009.html
Display change log.