W3C home > Mailing lists > Public > public-bpwg@w3.org > January 2009

Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting.

From: Luca Passani <passani@eunet.no>
Date: Sun, 18 Jan 2009 13:22:27 +0100
Message-ID: <49731F03.7040706@eunet.no>
To: Mobile Web Best Practices Working Group WG <public-bpwg@w3.org>

Tom Hume wrote:
> Which legal advice are you referring to here Luca? If it's the one 
> that Jo originally posted, and that you and I debated on wapreview.com 
> then, then this advice wasn't sought in connection with HTTPS but with 
> transformation in general. You may choose to infer a link between the 
> two, but we should probably leave such inferences for someone legally 
> qualified.
true. I am inferring. Rigo thinks that no-transform and robots.txt are 
an effective ways to protect different aspects of one's content. In 
W3C's view, those who don't respect those mechanisms are infringing on 
the rights of the content owner.  How can breaking HTTPS be permissible 
without content owner consent in W3C's view?
> However, if there's concern re a legal issue here (and the manual 
> whitelisting of banking sites by some operators to prevent transcoding 
> would seem to indicate that there are concerns), then could I suggest 
> we do get a legal opinion on it?
good idea.

Received on Sunday, 18 January 2009 12:23:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:08:58 UTC