ISSUE-98: Describe how EXI Options and schema options are communicated
Describe how EXI Options and schema options are communicated
- State:
- CLOSED
- Product:
- Canonical EXI
- Raised by:
- Takuki Kamiya
- Opened on:
- 2013-10-23
- Description:
- The spec needs to be updated along the line of what's discussed in:
http://lists.w3.org/Archives/Public/public-exi/2013Oct/0004.html - Related Actions Items:
- No related actions
- Related emails:
- ISSUE-98: Describe how EXI Options and schema options are communicated [Canonical EXI] (from sysbot+tracker@w3.org on 2013-10-23)
Related notes:
The WG is considering to adopt a proposal from JS.
https://lists.w3.org/Archives/Public/public-exi/2016May/0013.html
Regarding EXI Options, see ISSUE-114.
Takuki Kamiya, 1 Jun 2016, 21:49:27For schemaId, DP suggests to mandate the presence of schemaId element for schema-less and empty-schema schema-informed cases.
https://lists.w3.org/Archives/Public/public-exi/2016May/0017.html
JS disputed that schema-less and empty-schema schema-informed cases should also be treated in the same manner as the rest of the cases (i.e. schema-informed cases in general).
https://lists.w3.org/Archives/Public/public-exi/2016Jun/0001.html
JS pointed out providing a second way to express the every set of options will add implementation complexity without providing additional capability, suggesting to drop it from the spec (section E.2 Exchange Canonical EXI Options (Best Practices).
https://lists.w3.org/Archives/Public/public-exi/2016Jul/0001.html
The WG agreed to have a single way to represent every set of Canonical EXI options.
https://lists.w3.org/Archives/Public/public-exi/2016Aug/0000.html
JS was satisfied with the resoultion.
https://lists.w3.org/Archives/Public/public-exi/2016Aug/0005.html
Display change log
