ACTION-416: Check how much lexical ordering would hurt compactness with compression on

Check how much lexical ordering would hurt compactness with compression on

State:
closed
Person:
Daniel Peintner
Due on:
October 27, 2008
Created on:
October 21, 2008
Related emails:
  1. RE: ACTION-416 Lexical order for element event-codes (from john.schneider@agiledelta.com on 2008-11-06)
  2. RE: ACTION-416 Lexical order for element event-codes (from john.schneider@agiledelta.com on 2008-11-06)
  3. RE: ACTION-416 Lexical order for element event-codes (from tkamiya@us.fujitsu.com on 2008-11-06)
  4. RE: ACTION-416 Lexical order for element event-codes (from tkamiya@us.fujitsu.com on 2008-11-06)
  5. Re: ACTION-416 Lexical order for element event-codes (from daniel.peintner@gmail.com on 2008-11-06)
  6. Re: ACTION-416 Lexical order for element event-codes (from jkangash@cc.hut.fi on 2008-11-06)
  7. Re: ACTION-416 Lexical order for element event-codes (from daniel.peintner@gmail.com on 2008-11-06)
  8. Re: ACTION-416 Lexical order for element event-codes (from jkangash@cc.hut.fi on 2008-11-06)
  9. ACTION-416 Lexical order for element event-codes (from daniel.peintner@gmail.com on 2008-11-04)
  10. Minutes of the EXI F2F meeting (from tkamiya@us.fujitsu.com on 2008-10-27)

Related notes:

No additional notes.

Display change log.


Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 416.html,v 1.1 2018/11/23 13:50:57 carine Exp $