This document:Public document·View comments·Disposition of Comments·
Nearby:Efficient Extensible Interchange Working Group Other specs in this tool
Quick access to LC-2103 LC-2104 LC-2105 LC-2106 LC-2107 LC-2108 LC-2109 LC-2110 LC-2130 LC-2132 LC-2133 LC-2164 LC-2165 LC-2166 LC-2167 LC-2168 LC-2169 LC-2170 LC-2171 LC-2172 LC-2173 LC-2174 LC-2175 LC-2176 LC-2177 LC-2178 LC-2179 LC-2180 LC-2181 LC-2182 LC-2183 LC-2184 LC-2185 LC-2186 LC-2187 LC-2188 LC-2189 LC-2190 LC-2191 LC-2192 LC-2193 LC-2194 LC-2196 LC-2197 LC-2198 LC-2227 LC-2248
Previous: LC-2133 Next: LC-2187
4) Typed encoding in schema-less mode EXI enables limited typed encoding support in schema-less encoding. Since only predefined types are supported, xsi:type seems mainly useful to encode base64 chunks with the binary encoding. Even in that case, the usability is not so good : in some cases, elements whose content is base64 have also attributes. For instance ds:SignatureValue has an optional ID attribute. Of course, one could still use xsi:type=base64Binary in deviation mode but interoperability may be pretty bad and putting a wrong xsi:type for the purpose of compression seems broken. Also to be noted that: - Attribute values cannot be typed encoded with schema-less grammars. - Other useful types like "list of float","list of integers" cannot be used without external schema knowledge. Improved out-of-the-box support of this use case would be very helpful.