This document:Public document·View comments·Disposition of Comments·
Nearby:Mobile Web Best Practices Working Group Other specs in this tool Mobile Web Best Practices Working Group's Issue tracker
Quick access to LC-2267 LC-2268 LC-2269 LC-2270 LC-2289 LC-2316 LC-2317 LC-2318 LC-2319 LC-2320 LC-2321 LC-2322 LC-2323 LC-2324 LC-2327 LC-2328 LC-2329 LC-2358 LC-2359 LC-2360
Next: LC-2323
> "Is the current version of the document good enough to ship?" No, it is not. - it is not good enough for mobile developers who desperatly need a solid platform to build their apps (and not a spec that can be leveraged by someone somewhere to justify messing with HTTP in unforeseeable ways) - it is not good enough for content owners (who don't want to have their content messed with) - it is not good enough for telcos which want to deploy transcoders (there are no clear rules about what they should and should not do to avoid liability when they transcode other companies' content) The only people who CTG is good for at the moment are transcoder vendors, who can refer to a document which is ambiguous enough that they can read whatever they want into it and wrap their products into a shroud of W3C legitimacy. Luca