- From: Luca Passani <passani@eunet.no>
- Date: Tue, 10 Mar 2009 21:25:45 +0100
- To: MWI BPWG Public <public-bpwg@w3.org>
I don't disagree. The problem is that this is a consequence of how transcoders work. They are intrinsically a hack. The group has been desperately trying to present transcoders as some kind of standard, but this is like putting lipstick on a pig. A hack they were and a hack they remain. The only solution (apart from banning transcoders altogether, which would be the best) is to have transcoders stay out of the way of whatever content *might* already be suitable for mobile devices, starting with avoiding spoofing the UA in the first place. In this context, any trace of "mobility" (including viewport and mobileOptimized meta tags which the grops just ruled out and including the XHTML MIME type) should be a good enough reason for transcoders to refrain from transcoding. Luca Jo Rabin wrote: > Something has trouled me for a while about the notion of a mandatory heuristic. > > If it's mandatory, it's not a heuristic, surely? > > Also, i'm sorry not to have been on the call, but are we really sure we want to mandate this? I fear that this locks the mobile web into specific doctypes that will become increasingly irrelevant. > > Fwiw, i think that mandatory heuristics are a bad idea and basically regressive in effect. > > Jo > > --- original message --- > From: "Dominique Hazael-Massieux" <dom@w3.org> > Subject: Re: ISSUE-288 (includeNonMandatedHeuristics): Should the Content Transformation Guidelines include a non normative list of mobile heuristics? [Guidelines for Web Content Transformation Proxies] > Date: 10th March 2009 > Time: 3:06:58 pm > > Le mardi 10 mars 2009 à 14:44 +0000, Mobile Web Best Practices Working > Group Issue Tracker a écrit : > >> ISSUE-288 (includeNonMandatedHeuristics): Should the Content Transformation Guidelines include a non normative list of mobile heuristics? [Guidelines for Web Content Transformation Proxies] >> > > I should clarify: non-normative and non-mandated heuristics: i.e. > heuristics that CT proxies may or may not take into account to determine > whether they'll transform or not - in opposition to the mandated > heuristics that have been determined as per ISSUE-286 in the call today > (minutes upcoming). > > Dom > > >> http://www.w3.org/2005/MWI/BPWG/Group/track/issues/288 >> >> Raised by: Dominique Hazaël-Massieux >> On product: Guidelines for Web Content Transformation Proxies >> >> Cons: create confusion on non-mandated vs mandated, can be an endless list, would go outdated quickly >> >> Pros: give some hints to content providers on things ct proxies are likely to consider >> > > > > > >
Received on Tuesday, 10 March 2009 20:26:23 UTC