[cc-community] cc-community Digest, Vol 47, Issue 22

Hannah hu at openbusiness.cc
Thu Apr 17 14:18:21 EDT 2008


unsubscribe me please


Hannah Upritchard	
hu at openbusiness.cc

OpenBusiness
www.openbusiness.cc
The Young Foundation
18 Victoria Park Square
Bethnal Green
London E2 9PF
United Kingdom


On 17 Apr 2008, at 18:20, cc-community-request at lists.ibiblio.org wrote:

> Send cc-community mailing list submissions to
> 	cc-community at lists.ibiblio.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.ibiblio.org/mailman/listinfo/cc-community
> or, via email, send a message with subject or body 'help' to
> 	cc-community-request at lists.ibiblio.org
>
> You can reach the person managing the list at
> 	cc-community-owner at lists.ibiblio.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of cc-community digest..."
>
>
> Today's Topics:
>
>    1. Re: another anecdote: color: #e2e2e2 (Lucas Gonze)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 17 Apr 2008 09:52:13 -0700
> From: "Lucas Gonze" <lucas.gonze at gmail.com>
> Subject: Re: [cc-community] another anecdote: color: #e2e2e2
> To: cc-community at lists.ibiblio.org
> Message-ID:
> 	<ab069aa00804170952r4564df86pb459fedc53be241c at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Alek, my understanding is that attribution is defined as being
> human-readable.  There is no difference between not having attribution
> and displaying but hiding the attribution, except to the extent that
> you are satisfied with machine data.
>
> Nothing protects this person from having you sue him except your
> agreement that he has lived up to the terms of the license, and once
> you sue him a wise lawyer would advise him to settle.
>
> But then again, I am a programmer, not a lawyer.
>
> On Thu, Apr 17, 2008 at 7:27 AM, Alek Tarkowski 
> <alek at creativecommons.pl> wrote:
>> Hi everyone,
>>
>>  I wish there was some common space to store these little examples -
>>  which seem to be slightly too small for this big list; and 
>> nevertheless
>>  interesting. I know there are works on a best practices repository -
>>  would it make sense to have a worst practices repository as well?
>>
>>  I co-write in Poland a blog under CC BY and one of our posts, 
>> written by
>>  my friend, got re-used at a different site. They included both the
>>  author's name, original title and source - but have written it with 
>> font
>>  color #e2e2e2, which equals very bleak, whitish grey.
>>
>>  Formally, they do attribute. And importantly, the attribution is
>>  machine-indexable, if I understand correctly. But to the human eye,
>>  there's almost no attribution - I've got a letter from a friend 
>> telling
>>  me about the case, but not mentioning the attribution, which he 
>> probably
>>  missed. See for yourself how difficult it is to spot.
>>
>>  So I'm wondering whether there is anything to worry about here, or 
>> not.
>>  And then what can we do - stipulate the allowable color range of
>>  attribution notices?
>>
>>  Cheers,
>>
>>  Alek
>>
>>  --
>>  koordynator / public lead
>>  Creative Commons Polska / Poland
>>  http://creativecommons.pl
>>  skype: alektarkowski
>>
>>  _______________________________________________
>>  cc-community mailing list
>>  cc-community at lists.ibiblio.org
>>  http://lists.ibiblio.org/mailman/listinfo/cc-community
>>
>
>
> ------------------------------
>
> _______________________________________________
> cc-community mailing list
> cc-community at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/cc-community
>
>
> End of cc-community Digest, Vol 47, Issue 22
> ********************************************
>
>



More information about the cc-community mailing list