ISSUE-46: The smart integer encoding rule is supposed to apply to datatypes other than xsd:integer when datatype representation map is used
The smart integer encoding rule is supposed to apply to datatypes other than xsd:integer when datatype representation map is used
- State:
- CLOSED
- Product:
- EXI Spec
- Raised by:
- Takuki Kamiya
- Opened on:
- 2009-10-14
- Description:
- The rule dispatching xsd:integer to one of the three actual encodings
should apply to other datatypes when datatype representation maps are
in use in such a way that xsd:decimal is mapped to exi:integer.
Currently, this rule only applies to xsd:integer.
- Related Actions Items:
- No related actions
- Related emails:
- ISSUE-46: The smart integer encoding rule was supposed to apply to datatypes other than xsd:integer when datatype representation map is used [EXI Spec] (from sysbot+tracker@w3.org on 2009-10-14)
Related notes:
It was pointed out some ramification that stems from the rule being applied to xsd:float or xsd:double due to the potential rounding issue that may sometimes make it diffucult to accurately determine whether the value range contains only 4096 integers or less. Note that XSD processors usually only gives you min/max values defined for xsd:float as native language typed value. Also, xsd:decimal and its derived datatypes would have to retain min/max values just in case datatype representation map are ever used. There issues should be considered and balanced with the benefit.
Takuki Kamiya, 14 Oct 2009, 15:44:10JS and TK discussed during lunch break at TPAC. The "exi:integer" will be assigned to Integer encoding, and "exi:nbitUnsignedInteger" (or whatever the name is) will be assigned to n-bit Unsigned Integer. The semantics is associated with exi:integer. JS to made modification accordingly.
Takuki Kamiya, 3 Nov 2009, 16:57:44JS addressed this issue in the spec.
Takuki Kamiya, 3 Nov 2009, 23:28:20Display change log
