Hi,
Great to hear of your effort; I hope you have chosen to implement the NISO
1.0 standard.
I have no idea what the NISO standard is. The only standard followed is the
OpenURL (currently 0.1) standard.
But of course, this is an open source project, so I or anyone else can
implemented it if needed.
I would urge you to carefully consider your choice of license, however. As I
wrote last year when
the issue came up in Koha, using AGPL in stead of the less restrictive GPL
can have some unintended
consequences.
http://go-to-hellman.blogspot.com/2010/07/koha-community-considers-affero-license.html
Iteresting link :=) I focus mainly on code, and I am not that well-versed with
different versions of open source licenses.
I chose AGPL since it it seemed better adapted to server scripts.
What I would want is a license that keeps the software free, and that people
has to make improvements availible. Any suggestions?
Tony
-Ursprungligt meddelande-
Från: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] För Eric Hellman
Skickat: den 17 februari 2011 14:23
Till: CODE4LIB@LISTSERV.ND.EDU
Ämne: [CODE4LIB] AGPL for libraries (was: A to Z lists)
Hej Tony!
Great to hear of your effort; I hope you have chosen to implement the NISO 1.0
standard.
I would urge you to carefully consider your choice of license, however. As I
wrote last year when the issue came up in Koha, using AGPL in stead of the less
restrictive GPL can have some unintended consequences.
http://go-to-hellman.blogspot.com/2010/07/koha-community-considers-affero-license.html
It is still a reality today that many library resources release api's that are
provided only to customers and often come with interface licenses incompatible
with GPL. If you use AGPL, a library that modified the software to use it with
one of these resources would be in violation of your license, even if they did
not redistribute the software. If that's your intention, then fine, but please
make sure you understand the implications.
Also, please don't confuse AGPL, which is a restrictive license rooted in
copyright law, with public domain, which has no restrictions on use.
Eric
On Feb 17, 2011, at 4:34 AM, Tony Mattsson wrote:
Hi,
We are at the final stages of building an EBM system with AZ-list and OpenURL
resolver developed in LAMP (with Ajax) which we will release into the public
domain (AGPL). I'll put up a notice on this list when it's done, and you can
try it out to see if it measures up :=)
Tony Mattsson
IT-Librarian
Landstinget Dalarna Bibliotek och informationscentral
http://materio.fabicutv.com
-Ursprungligt meddelande-
Från: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] För Michele DeSilva
Skickat: den 16 februari 2011 22:18
Till: CODE4LIB@LISTSERV.ND.EDU
Ämne: [CODE4LIB] A to Z lists
Hi Code4Lib-ers,
I want to chime in and say that I, too, enjoyed the streaming archive from
the conference.
I also have a question: my library has a horribly antiquated A to Z list of
databases and online resources (it's based in Access). We'd like to do
something that looks more modern and is far more user friendly. I found a
great article in the Code4Lib journal (issue 12, by Danielle Rosenthal
Mario Bernado) about building a searchable A to Z list using Drupal. I'm also
wondering what other institutions have done as far as in-house solutions. I
know there're products we could buy, but, like everyone else, we don't have
much money at the moment.
Thanks for any info or advice!
Michele DeSilva
Central Oregon Community College Library
Emerging Technologies Librarian
541-383-7565
mdesi...@cocc.edu
Eric Hellman
President, Gluejar, Inc.
41 Watchung Plaza, #132
Montclair, NJ 07042
USA
e...@hellman.net
http://go-to-hellman.blogspot.com/
@gluejar
-Ursprungligt meddelande-
Från: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] För Eric Hellman
Skickat: den 17 februari 2011 14:23
Till: CODE4LIB@LISTSERV.ND.EDU
Ämne: [CODE4LIB] AGPL for libraries (was: A to Z lists)
Hej Tony!
Great to hear of your effort; I hope you have chosen to implement the NISO 1.0
standard.
I would urge you to carefully consider your choice of license, however. As I
wrote last year when the issue came up in Koha, using AGPL in stead of the less
restrictive GPL can have some unintended consequences.
http://go-to-hellman.blogspot.com/2010/07/koha-community-considers-affero-license.html
It is still a reality today that many library resources release api's that are
provided only to customers and often come with interface licenses incompatible
with GPL. If you use AGPL, a library that modified the software to use it with
one of these resources would be in violation of your license, even if they did
not redistribute the software. If that's your intention, then fine, but please
make sure you understand the implications.
Also, please don't confuse AGPL, which is a restrictive license rooted
