ISSUE-106: Schema(Id) and Canonical EXI consequences
Schema(Id) and Canonical EXI consequences
- State:
- CLOSED
- Product:
- Canonical EXI
- Raised by:
- Don Brutzman
- Opened on:
- 2015-04-29
- Description:
- Don raised the question: does the schemaId actually have to point to an
actual schema? since not, perhaps it should be listed under
limitations section.
This is significant when schema-based EXI compression is used.
Note: [DP] I think this is something that related to the EXI core spec as well. - Related Actions Items:
- No related actions
- Related emails:
- Re: ISSUE-106: Schema(Id) and Canonical EXI consequences [Canonical EXI] (from brutzman@nps.edu on 2015-05-05)
- AW: Canononical EXI - Last Call Publication (from daniel.peintner.ext@siemens.com on 2015-04-29)
- ISSUE-106: Schema(Id) and Canonical EXI consequences [Canonical EXI] (from sysbot+tracker@w3.org on 2015-04-29)
Related notes:
In section 3 (i.e. Canonical EXI Header), the following description was added as a note.
"Applications that use Canonical EXI need to ensure that the senders and the receivers of EXI documents are using the same schema information. This is regardless schemaId is included in the header options or not."
Display change log
