ISSUE-100: Invalid typed attributes/elements in strict mode - wildcard available
Invalid typed attributes/elements in strict mode - wildcard available
- State:
- CLOSED
- Product:
- Canonical EXI
- Raised by:
- Daniel Peintner
- Opened on:
- 2014-01-13
- Description:
- >> Youenns email.. see last par of #1
1. Typed event selection in section 2.2
The section could be clarified a bit for productions that have a type associated to represent an event value.
It may be better to state from the start that any production that has a type that cannot represent the event value is removed from the production selection choice. Is it the meaning behind "After excluding productions that are not usable according to the convention in use"?
Related to that, it is not totally clear what would happen for an invalid typed attribute in strict mode.
If it can be represented as a wildcard, EXI canonicalization should probably be ok with that.
https://lists.w3.org/Archives/Member/member-exi-wg/2013Dec/0005.html - Related Actions Items:
- No related actions
- Related emails:
- RE: ACTION-736: Check issue 100 to see canonical exi section 4.2.2 properly handles it (from tkamiya@us.fujitsu.com on 2016-03-28)
- AW: ACTION-736: Check issue 100 to see canonical exi section 4.2.2 properly handles it (from daniel.peintner.ext@siemens.com on 2016-03-16)
- AW: EXI canonicalization questions (from daniel.peintner.ext@siemens.com on 2014-05-06)
- RE: EXI canonicalization questions (from tkamiya@us.fujitsu.com on 2014-04-29)
- RE: EXI canonicalization questions (from tkamiya@us.fujitsu.com on 2014-04-28)
- AW: EXI canonicalization questions (from daniel.peintner.ext@siemens.com on 2014-04-23)
- RE: EXI canonicalization questions (from Youenn.Fablet@crf.canon.fr on 2014-04-07)
- RE: ISSUE-100: Invalid typed attribute in strict mode - wildcard available [Canonical EXI] (from tkamiya@us.fujitsu.com on 2014-01-14)
- AW: EXI canonicalization questions (from daniel.peintner.ext@siemens.com on 2014-01-13)
- ISSUE-100: Invalid typed attribute in strict mode - wildcard available [Canonical EXI] (from sysbot+tracker@w3.org on 2014-01-13)
Related notes:
The same issue applies to elements.
https://lists.w3.org/Archives/Member/member-exi-wg/2014Jan/0011.html
DP found the latest Canonical EXI draft already covers that point.
https://lists.w3.org/Archives/Public/public-exi/2016Mar/0011.html
Display change log