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-2110 Next: LC-2108
In the same spirit, it may be good to tighten the wording concerning the typing of global attributes. Currently, section 8.5.4.4.1 (strict = false section) states that: "when using schemas [...] If a global attribute definition exists for qname, represent the value of the attribute according to its datatype" First, it seems that only section 8.5.4.4.1 is dealing with this, while this seems quite applicable to strict mode in the case of attribute wildcards. Second, the "when using schemas" wording seems vague to me, at least for that particular sentence. A quick reading made me thought that this meant "when some schema information is available to the EXI processor", but I think it is actually meaning "when using a schema-informed grammar". The last interpretation would also lead to the fact that a schema containing only global attribute definitions would be useless for typing attribute values.