{"id":516,"date":"2008-03-23T08:35:29","date_gmt":"2008-03-23T16:35:29","guid":{"rendered":"http:\/\/wapreview.com\/?p=516"},"modified":"2008-03-30T09:29:24","modified_gmt":"2008-03-30T17:29:24","slug":"how-web-to-mobile-transcoding-should-work","status":"publish","type":"post","link":"https:\/\/wapreview.com\/516\/","title":{"rendered":"How Web to Mobile Transcoding Should Work"},"content":{"rendered":"
Luca Passani, the co-creator and maintainer of the WURFL<\/a> mobile device characteristics database, with input from other mobile developers has published what he calls a “Manifesto for Ethical Reformatting<\/a>“. The manifesto outlines some simple rules for how transcoding can work to make non-mobile websites usable on any phone, without breaking the mobile web.<\/strong> This manifesto is a reation to the current transcoding implementations from Vodafone in the UK<\/a>, Spain, and Portugal with Novarra, and Vodafone Ireland with Bytemobile and Sprint USA using Openwave<\/a> – all of which are hurting usability by reformatting mobile sites that don’t need it and by removing and changing html headers with negative consequences for content delivery services.<\/p>\n The rules are:<\/p>\n These seem like reasonable guidelines that both transcoding proxy vendors and mobile developers can live with. I hope that Novarra, Openwave (which has been reaching out to the development community and promises significant improvements in the next release) and Bytemobile will adopt thes guidelines. It’s in everyone’s best interest; web developers, vendors of content reformatting transcoders and users. For developers of mobile content and users it insures that the mobile web and mobile content services work as designed and for transcoder vendors it lets them concentrate on the worthwhile goal of mobilizing the full-web without the negative publicity that breaking mobile services creates.<\/p>\n","protected":false},"excerpt":{"rendered":" Luca Passani, the co-creator and maintainer of the WURFL mobile device characteristics database, with input from other mobile developers has published what he calls a “Manifesto for Ethical Reformatting“. The manifesto outlines some simple rules for how transcoding can work to make non-mobile websites usable on any phone, without breaking the mobile web. This manifesto is a reation to the current transcoding implementations from Vodafone in the UK, Spain, and Portugal with Novarra, and Vodafone Ireland with Bytemobile and Sprint … Continue reading \n
x-*<\/code> headers is admissible.<\/li>\n
\napplication\/xhtml+xml,
\ntext\/vnd.wap.wml
\napplication\/vnd.wap.xhtml+xml<\/code>
\nand documents served with the XHTML-Basic 1.0 or XHTML-MP 1.1 DTD:
\n<!DOCTYPE html PUBLIC \"-\/\/OMA\/\/DTD XHTML Mobile 1.2\/\/EN\" \"http:\/\/www.openmobilealliance.org\/tech\/DTD\/xhtml-mobile12.dtd\">
\n<!DOCTYPE html PUBLIC \"-\/\/WAPFORUM\/\/DTD XHTML Mobile 1.1\/\/EN\" \"http:\/\/www.wapforum.org\/DTD\/xhtml-mobile11.dtd\">
\n<!DOCTYPE html PUBLIC \"-\/\/WAPFORUM\/\/DTD XHTML Mobile 1.0\/\/EN\" \"http:\/\/www.wapforum.org\/DTD\/xhtml-mobile10.dtd\">
\n<!DOCTYPE html PUBLIC \"-\/\/W3C\/\/DTD XHTML Basic 1.1\/\/EN\" \"http:\/\/www.w3.org\/TR\/xhtml-basic\/xhtml-basic11.dtd\">
\n<!DOCTYPE html PUBLIC \"-\/\/W3C\/\/DTD XHTML Basic 1.0\/\/EN\" \"http:\/\/www.w3.org\/TR\/xhtml-basic\/xhtml-basic10.dtd\"><\/code>
\nMUST be considered mobile-optimized and no transcoding should be applied<\/li>\n
\nCache-Control: no-transform<\/code> This also applies to the case when the header is specified through the <meta> HTTP-Equiv tag<\/li>\n
\n<link rel=\"alternate\" type=\"text\/html\" media=\"handheld\" href=\"[url]\" title=\"[title]\" \/> <\/code>The proxy should redirect the user to the [url] contained in the
href<\/code> attribute.<\/li>\n
\nm.*<\/code>
\nmobile.*<\/code>
\nwap.*<\/code>
\n*.mobi<\/code>
\npda.*<\/code>
\navantgo.*<\/code>
\niphone.*<\/code>
\nwml.*<\/code>
\nxhtml.*<\/code>
\n*\/mobile\/<\/code>
\n*\/iphone\/<\/code><\/li>\n