W3C home > Mailing lists > Public > www-svg@w3.org > November 2003

Re: [SVG 1.2] Other notes.

From: Robin Berjon <robin.berjon@expway.fr>
Date: Sun, 30 Nov 2003 18:03:21 +0200
Message-ID: <3FCA14C9.3040705@expway.fr>
To: Jim Ley <jim@jibbering.com>
Cc: www-svg@w3.org

Jim Ley wrote:
> "Robin Berjon" <robin.berjon@expway.fr> wrote in message
>>What part of pasting some RDF in there represents too much effort? The
>>UA needs do not nothing about it, the author can just grab it off
>>Creative Commons and copy it into her document.
> 
> Well there's a few problems, one is that creative commons is AIUI  generally
> only applicaple to US law, and is currently being translated into the
> copyright ideas of other countries, so there are problems with CC itself,
> but the problem is that the spec suggests that a UA could include the
> information before view-source, users will expect this, just like we've had
> to deal with lots of people wondering about why they don't get a tooltip
> from title after the previous specs suggested it.    I don't want the spec
> suggesting something that has significant implementation cost for no-ones
> benefit!

Your idea is that people expected to have tooltips because they read the 
MAY in "the user-agent MAY display tooltips" as a MUST, and ergo that 
the same thing will happen to the copyright thing. I think that people 
expected tooltips because they're used to having tooltips in their web 
browser. So I don't think that the current text will create false 
expectations.

Implementators that want people to put SVG content on the Web at large 
(and who here doesn't) are encouraged to display the copyright or at 
least a warning that the file may be copyrighted when the user views the 
source because we've had feedback from graphic artists that while 
they've grown used to publishing low quality rasters on the Web they're 
concerned that with the high quality provided by SVG people might steal 
their work. Displaying something, even if just a generic warning when 
some CC data is detected, is likely to assuage such concerns.

And yes there are still issues with CC, but I think you'll agree that 
it's better to point to them and to expect them to fix those issues than 
to ask the SVG WG to come up with a workable copyrighting system :)

-- 
Robin Berjon
Received on Sunday, 30 November 2003 11:04:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 5 November 2012 23:52:55 GMT