RE: Linking to alternate resources

We're aware of the possible use of POWDER but made the decision that using it would be a later phase of work, given that it can't be used today.

The question about "does the link point to the Web page itself" is I think fraught with difficulties. If I multiserve from example.com then both my handheld and my desktop links both point to the same place. And also if I have redirection then is it the location: header that counts or is it the originally requested URI. And if I have an arrangement that has example.com?experience=handheld and example.com?experience=desktop are obviously different but can this be generalised into a rule about syntactic equivalence and whether or not URI queries and fragments count in such a determination? 

I don't disagree that this can be a useful heuristic, I just don't really know how one can write it down in a way that makes the written text informative, useful and not just plain wrong in a lot of cases. (Other than to say if it's a .mobi domain then it's required to be useful for mobile, of course)

Jo



> -----Original Message-----
> From: JOSE MANUEL CANTERA FONSECA [mailto:jmcf@tid.es]
> Sent: 06 May 2008 18:58
> To: Jo Rabin; Francois Daoust; public-bpwg-ct
> Subject: RE: Linking to alternate resources
> 
> I agree with you that <link rel="alternate" media="handheld"> in theory
> should be used by a desktop page to say "hey, there is a mobile optimized
> version of me", however now it is also used to say "hey myself it is a
> mobile web page!" (if the href atribute points to the page itself).
> 
> AFAIK Opera Mini uses other mechanism which is the detection of a <link
> rel="stylesheet" type="text/css" media="handheld">. If they see that they
> won't touch your page. That's because in MyMobileWeb we send a fake CSS to
> flag Opera Mini our pages :)
> 
> I agree that something standard is needed, to say that a page is a mobile
> optimized page, but also to say, for which DCs a page provide the best
> user experience.
> 
> I wonder if POWDER has something to do with this and can provide another
> solution ...
> 
> Best Regards
> ________________________________________
> De: public-bpwg-ct-request@w3.org [public-bpwg-ct-request@w3.org] En
> nombre de Jo Rabin [jrabin@mtld.mobi]
> Enviado el: martes, 06 de mayo de 2008 18:06
> Para: Francois Daoust; public-bpwg-ct
> Asunto: RE: Linking to alternate resources
> 
> > (and CSS media queries is a
> > Candidate Rec, not a Rec)
> 
> And implementations not exactly thick on the ground.
> 
> I'm not sure how this helps? I am looking for a way for a content provider
> to say "This representation is intended for mobile". Media queries doesn't
> do that, does it. Some think like:
> 
> <meta name="media" content="handheld" />
> 
> would fit the bill.
> 
> Jo
> 
> > -----Original Message-----
> > From: Francois Daoust [mailto:fd@w3.org]
> > Sent: 06 May 2008 16:54
> > To: Jo Rabin; public-bpwg-ct
> > Subject: Linking to alternate resources
> >
> > Not directly connected to the "confusing" part of the linking mechanism,
> > but re-reading today's minutes:
> >
> > > Link element in HTML requests
> > >[...]
> > >    jo: exactly, it's a useful mechanism to link to more appropriate
> > >    versions but how can you identify what user-agents THIS version is
> > >    suitable for?
> >
> > The mechanism being exactly the same as the one used to link to a CSS
> > style sheet, user-agent cannot be used for linking to alternate
> > representations, but CSS media queries should still be part of the
> > equation with the possibility to define something like:
> >       media="handheld and (max-device-width: 200px)"
> >
> > I don't think anyone uses links to alternate representations with that
> > level of details for the time being though (and CSS media queries is a
> > Candidate Rec, not a Rec)
> >
> > François.
>

Received on Tuesday, 6 May 2008 21:56:30 UTC