ISSUE-44: Implication of EXI strict mode and lexical value preservation

Implication of EXI strict mode and lexical value preservation

State:

CLOSED

Product:

EXI Spec

Raised by:

Daniel Peintner

Opened on:

2009-09-23

Description:

We may need to add a note to section "8.5.4.4.2 Adding Productions when Strict is True" that the combination of Strict and preserve.LexicalValues set to TRUE may not suceed to encode a schema-valid document in all cases. This is due to the fact that the right path in the automaton may not be taken.

See http://lists.w3.org/Archives/Member/member-exi-wg/2009Sep/0031.html

Related Actions Items:

No related actions

Related emails:

1. Tomorrow's Agenda (from msc@mitre.org on 2009-10-13)
2. RE: EXI : xsi:type and xsi:nil when lexicalValues is true (from tkamiya@us.fujitsu.com on 2009-10-12)
3. RE: EXI : xsi:type and xsi:nil when lexicalValues is true (from john.schneider@agiledelta.com on 2009-10-08)
4. RE: EXI : xsi:type and xsi:nil when lexicalValues is true (from tkamiya@us.fujitsu.com on 2009-10-07)
5. Agenda for this week's telecon (from msc@mitre.org on 2009-10-06)
6. Agenda for 30 September Telecon (from tkamiya@us.fujitsu.com on 2009-09-29)
7. ISSUE-44: Implication of EXI strict mode and lexical value preservation [EXI Spec] (from sysbot+tracker@w3.org on 2009-09-23)
8. Agenda for 23 September Telecon (from tkamiya@us.fujitsu.com on 2009-09-22)

Related notes:

Display change log