ISSUE-28: Where should the next event after a self-contained element start?
Where should the next event after a self-contained element start?
- State:
- CLOSED
- Product:
- EXI Spec
- Raised by:
- Daniel Peintner
- Opened on:
- 2009-03-31
- Description:
- There have been a discussion whether self-contained elements should
end at octet boundary, stating there are use cases that legitimize
such behaviour. On the other hand, a concern was expressed stating
that the cost incurred by such behaviour sometimes is not acceptable
for use cases that do not care about it.
Use cases, the issue and suggestion:
http://lists.w3.org/Archives/Member/member-exi-wg/2009Mar/0074.html (DP)
More use cases:
http://lists.w3.org/Archives/Member/member-exi-wg/2009Apr/0040.html (DP) - Related Actions Items:
- No related actions
- Related emails:
- Agenda for 29 Apr EXI Telecon (from tkamiya@us.fujitsu.com on 2009-04-28)
- Agenda for 22 Apr EXI Telecon (from tkamiya@us.fujitsu.com on 2009-04-21)
- ISSUE-28: Where should the next event after a self-contained element start? [EXI Spec] (from sysbot+tracker@w3.org on 2009-03-31)
Related notes:
A couple of initial responses as of 2009-03-31.
Suggesting prudent approach to this issue (JS)
http://lists.w3.org/Archives/Member/member-exi-wg/2009Mar/0081.html
Suggesting 3rd way to approach this issue (TK)
http://lists.w3.org/Archives/Member/member-exi-wg/2009Mar/0088.html
[caribou]: resolved-accepted
5 May 2009, 11:58:55RESOLUTION: event after a SelfContained Element should start at a byte boundary (WG F2F, may 5th 2009)
Carine Bournez, 5 May 2009, 12:00:31The spec has been changed to address this issue.
http://lists.w3.org/Archives/Member/member-exi-edits/2009May/0016.html
Display change log