headers
Jordan Hatcher's lists | 1 Feb 17:47

CC-Zero dissected

Rufus pointed out to me the other day that I should post some OKF  
related goings on to the list. This is about the new CCZero licence.  
The new CCZero licence is out, and you can read my thoughts here:

<http://www.opencontentlawyer.com/2008/01/16/dissecting-cczero/>

The major points (also posted to cc-licenses):

-- (Just a note/comment) this is based on US law and isn't an  
'unported' version. Is the unported template for internationalization  
the Science Commons protocol?
-- Waiver of moral rights and the conversation we've been having  
about CC v3.01
-- There is no sign up process like the current public domain  
dedication -- Why not? I'd think that a 'signed writing' would be  
needed or at least desired. Does this process fit that requirement?  
If not, do you think some email process should be there?
-- Are patents and trademarks included in the waiver? If not,  
shouldn't they be specifically excluded as the text of the waiver is  
fairly broad? If they are, why? It isn't required as part of the  
protocol.
-- Is there really a need to waive claims of unfair competition and  
privacy when you are explicitly giving commercial enterprises and  
others the right to use your work?
-- Does the legal code intend to cover database rights?  If so, I  
suggest wording that tracks the directive closely.
-- The human readable summary of the waiver doesn't include moral  
rights or database rights. This should probably be adjusted to match  
both the sign up process and the legal code.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Rufus Pollock | 4 Feb 12:14
Gravatar

Re: HI!

Dear Nicolas,

First, great to hear from you about your plan to create a student 
organization based focused on Open Knowledge. For clarification on what 
'Open Knowledge' means you might want to take a look at:

   http://www.okfn.org/three_meanings_of_open/
   http://www.opendefinition.org/

There is also links to further introductory material on this wiki page:

   http://okfn.org/wiki/Research

Finally, in response to your query I've just started an 'Open Knowledge 
Group Guide' here:

   http://okfn.org/wiki/GroupGuide/

I hope the current content is useful -- do feel free to edit it to add 
any feedback or ideas of your own.

Regards,

Rufus Pollock

Nicolas Valerkos wrote:
> Hi!,
> My name is Nikos Valerkou, I want to create a student organization
> based on Open Knowledge concept. Please, if you could guide me into
> the concept that will enable the group to be under that concept will
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jonathan Gray | 5 Feb 12:52

Re: CC-Zero dissected

Many thanks for this Jordan!

J.

Jordan Hatcher's lists wrote:
> Rufus pointed out to me the other day that I should post some OKF  
> related goings on to the list. This is about the new CCZero licence.  
> The new CCZero licence is out, and you can read my thoughts here:
> 
> <http://www.opencontentlawyer.com/2008/01/16/dissecting-cczero/>
> 
> The major points (also posted to cc-licenses):
> 
> -- (Just a note/comment) this is based on US law and isn't an  
> 'unported' version. Is the unported template for internationalization  
> the Science Commons protocol?
> -- Waiver of moral rights and the conversation we've been having  
> about CC v3.01
> -- There is no sign up process like the current public domain  
> dedication -- Why not? I'd think that a 'signed writing' would be  
> needed or at least desired. Does this process fit that requirement?  
> If not, do you think some email process should be there?
> -- Are patents and trademarks included in the waiver? If not,  
> shouldn't they be specifically excluded as the text of the waiver is  
> fairly broad? If they are, why? It isn't required as part of the  
> protocol.
> -- Is there really a need to waive claims of unfair competition and  
> privacy when you are explicitly giving commercial enterprises and  
> others the right to use your work?
> -- Does the legal code intend to cover database rights?  If so, I
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jonathan Gray | 5 Feb 14:13

[Fwd: COMMUNIA workshop: your article]

Hi all,

Just to let you know that I've been asked to submit an article for the 
proceedings for the first COMMUNIA workshop [1]. I've attached the 
guidelines and the original email from the publications co-ordinator 
below. It looks like it should either be 4-6 pages (short) or 8-12 pages 
(long), with abstract, authors, keywords, and so on.

I'll pop something up on the wiki in the next few days, but in the 
meantime it would be good to hear if there's anything that anyone would 
particularly like to see included, so that I can take this into account 
when I write the first draft.

Regards,

Jonathan

[1] see 
http://blog.okfn.org/2008/01/25/first-communia-workshop-technology-and-the-public-domain/

-------- Original Message --------
Dear authors,

Please find enclosed the guidelines to prepare your article to be 
published on Communia website at http://www.communia-project.eu/ and 
later in written proceedings.

Articles should be sent as an .rtf attachment 
to publications@... 
<mailto:publications@...>, copying your
(Continue reading)

Permalink | Reply | 0 comments |
headers
Philippe Aigrain | 5 Feb 15:46
Favicon
Gravatar

co-ment text annotation and commenting system

About a year ago, there were a few posts on this list on text annotation 
systems. We have developed an entirely new system whose client commenting 
interface is inspired from the STET system used for the GPLv3 revision, but 
with a much extended overall functionality :
- the system provides a full symetrical service : anyone can upload or create  
texts and manage rights of access and commenting,
- Comments can be tagged and there are a number of basic workflows for 
processing them,
- text versioning is included,
- exports are in process.

The code base is licensed under the Affero GPLv3, with a trademark restriction 
clause (co-ment is a registered trademark that can not be used without 
authorization). Technology : AJAX + Django + PostgreSQL.

We operate the service at :
http://www.co-ment.net

The code is at :
http://www.sopinspace.com/products/co-ment/en?set_language=en&cl=en

Usage and feeback most welcome.
--

-- 
Philippe Aigrain
Sopinspace, Society for Public Information Spaces
Permalink | Reply | 5 comments |
headers
Jonathan Gray | 5 Feb 17:08

Re: co-ment text annotation and commenting system

Dear Phillipe,

Many thanks for following this up! It was good to briefly meet you and 
sorry I've not been in touch since COMMUNIA!

The Co-ment system looks very interesting, and I've added a link to the 
'annotation' section of our Software Tools wiki page:

   http://www.okfn.org/wiki/SoftwareTools

Some details about the system we use for Open Shakespeare are here:

   http://www.openshakespeare.org/2007/04/10/annotation-is-working/

I'm sure others on the list who were involved in implementing this will 
be able to give more detail!

Regards,

Jonathan

Philippe Aigrain wrote:
> About a year ago, there were a few posts on this list on text annotation 
> systems. We have developed an entirely new system whose client commenting 
> interface is inspired from the STET system used for the GPLv3 revision, but 
> with a much extended overall functionality :
> - the system provides a full symetrical service : anyone can upload or create  
> texts and manage rights of access and commenting,
> - Comments can be tagged and there are a number of basic workflows for 
> processing them,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Rufus Pollock | 5 Feb 18:17
Gravatar

Re: co-ment text annotation and commenting system

Philippe Aigrain wrote:
> About a year ago, there were a few posts on this list on text annotation 
> systems. We have developed an entirely new system whose client commenting 
> interface is inspired from the STET system used for the GPLv3 revision, but 
> with a much extended overall functionality :
> - the system provides a full symetrical service : anyone can upload or create  
> texts and manage rights of access and commenting,
> - Comments can be tagged and there are a number of basic workflows for 
> processing them,
> - text versioning is included,
> - exports are in process.
> 
> The code base is licensed under the Affero GPLv3, with a trademark restriction 
> clause (co-ment is a registered trademark that can not be used without 
> authorization). Technology : AJAX + Django + PostgreSQL.

Wow, Phillipe this is amazing -- I'm particularly happy that the code is 
in python.

I'll definitely be checking this out. We developed our original code [1] 
for use on http://demo.openshakespeare.net but have been hampered by the 
performance issues of using js to parse through large texts (e.g. a 
shakespeare play). One way to deal with this (that the author of 
marginalia has explored) is to use xpath locations but that apparently 
does not work on IE. How have you dealt with the performance issues and 
does co-ment work in both IE and Firefox?

[1]: http://knowledgeforge.net/shakespeare/svn/annotater/trunk

> We operate the service at :
(Continue reading)

Permalink | Reply | 1 comment |
headers
Philippe Aigrain | 5 Feb 19:11
Favicon
Gravatar

Re: co-ment text annotation and commenting system

 I am forwarding in a separate mail your technical questions to the developers 
(Raphaël Badin and Renaud Bernard) but here are some immediate answers :

- yes, co-ment works with both Firefox and IE (though it was the usual 
nightmare to solve some issues in IE).

- we have limits on size of text uploads that are due to the OpenOffice 
converter that we are using, but a Shakespeare play is definitely OK. In 
practice cutting and pasting gives most of the time better results than 
uploading from a word processor. I have just uploaded "As you like it" by cut 
and paste and turned to public viewing and commenting to public. You can test 
it at :
http://www.co-ment.net/text/104/

Philippe
Le Tuesday 05 February 2008 18:17:57 Rufus Pollock, vous avez écrit :
> Philippe Aigrain wrote:
[...]
> Wow, Phillipe this is amazing -- I'm particularly happy that the code is
> in python.
>
> I'll definitely be checking this out. We developed our original code [1]
> for use on http://demo.openshakespeare.net but have been hampered by the
> performance issues of using js to parse through large texts (e.g. a
> shakespeare play). One way to deal with this (that the author of
> marginalia has explored) is to use xpath locations but that apparently
> does not work on IE. How have you dealt with the performance issues and
> does co-ment work in both IE and Firefox?
>
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Philippe Aigrain | 6 Feb 10:48
Favicon
Gravatar

Copyright status of the Open Shakespeare texts ?

I did a further test on co-ment by creating a text with both parts of Henry 
the Fourth, and it is still works OK (just takes a while to open the text).

However, while doing so, I actually checked the Project Gutenberg source, and 
it looks like the copyright status is uncertain : is it because of the 
translation to modern English in As you like it and Part I of Henry IV ?
Thanks for letting me know if I can keep such texts public on co-ment, or 
pointing me to Shakespeare texts that are actually in teh public domain.

Best,
--

-- 
Philippe Aigrain
Permalink | Reply | 4 comments |
headers
Rufus Pollock | 6 Feb 11:45
Gravatar

Re: Copyright status of the Open Shakespeare texts ?

Philippe Aigrain wrote:
> I did a further test on co-ment by creating a text with both parts of Henry 
> the Fourth, and it is still works OK (just takes a while to open the text).
> 
> However, while doing so, I actually checked the Project Gutenberg source, and 
> it looks like the copyright status is uncertain : is it because of the 
> translation to modern English in As you like it and Part I of Henry IV ?
> Thanks for letting me know if I can keep such texts public on co-ment, or 
> pointing me to Shakespeare texts that are actually in teh public domain.

You've just stumbled across one of the major (initial) reasons for doing 
Open Shakespeare -- that even though the texts are really old a lot of 
the versions found on the Internet display copyright notices (including 
some of those on PG). Some of these notices may be valid some of them 
may not be but who wants to spend the time to find out?

Open Shakespeare has done the work for you and all the texts we took 
from PG we believe to be in the public domain (when I last looked PG has 
roughly 4 version of each Shakespeare text PG and 2 of these have 
copyright notices). Thus you can definitely keep the texts you've used 
on co-ment.

~rufus
Permalink | Reply | 3 comments |

Gmane