The May/June issue of Computing in Science and Engineering http://computer.org/cise: is out and has a Python theme. Many folks we know and love from the community and mailing lists contribute to the issue. Read articles by Paul Dubois and Travis Oliphant for free online.
<plug>
Since authors are allowed by their publication policy to keep a
publicly available copy of their papers on their personal website,
here's the ipython one:
http://amath.colorado.edu/faculty/fperez/preprints/ipython-cise-final.pdf
</plug>
Cheers,
f
···
On 4/25/07, Andrew Straw <strawman@...106...> wrote:
The May/June issue of Computing in Science and Engineering
http://computer.org/cise: is out and has a Python theme. Many folks we
know and love from the community and mailing lists contribute to the
issue. Read articles by Paul Dubois and Travis Oliphant for free online.
Didn't know that... here's a link to my matplotlib article
http://nitace.bsd.uchicago.edu/misc/c3sci.pdf
It might be nice to create a scipy wiki page linking to these PDFs.
JDH
···
On 4/25/07, Fernando Perez <fperez.net@...287...> wrote:
Since authors are allowed by their publication policy to keep a
publicly available copy of their papers on their personal website,
here's the ipython one:
I'm going by the language here:
http://www.ieee.org/web/publications/rights/policies.html
Specifically:
When IEEE publishes the work, the author must replace the previous
electronic version of the accepted paper with either (1) the full
citation to the IEEE work or (2) the IEEE-published version, including
the IEEE copyright notice and full citation. Prior or revised versions
of the paper must not be represented as the published version.
This explicitly mentions author website redistribution, as long as
the official IEEE version is used.
Unless I'm misreading the above, I think it's OK for us to keep such
copies in our personal sites. We can link to them from the scipy
wiki, though I don't think it would be OK to /copy/ the PDFs to the
scipy wiki.
As always, IANAL and all that.
Cheers,
f
···
On 4/25/07, John Hunter <jdh2358@...287...> wrote:
On 4/25/07, Fernando Perez <fperez.net@...287...> wrote:
> Since authors are allowed by their publication policy to keep a
> publicly available copy of their papers on their personal website,
> here's the ipython one:Didn't know that... here's a link to my matplotlib article
(Off list...)
(Another g-mailer, huh? Soon they'll know everything about everyone...)
Thanks for that info re: online paper copies. I'm actually a week or two away from submitting a follow-up paper from my SciPy '06 talk to them... And submitting to a non-open-access journal was one issue. But this makes it... bearable.
Cannae make SciPy '07 
Will be at a insect/robot flight conference in the Italian-speaking part of Switzerland! 
-Andrew
Fernando Perez wrote:
···
On 4/25/07, John Hunter <jdh2358@...287...> wrote:
On 4/25/07, Fernando Perez <fperez.net@...287...> wrote:
> Since authors are allowed by their publication policy to keep a
> publicly available copy of their papers on their personal website,
> here's the ipython one:Didn't know that... here's a link to my matplotlib article
I'm going by the language here:
http://www.ieee.org/web/publications/rights/policies.html
Specifically:
When IEEE publishes the work, the author must replace the previous
electronic version of the accepted paper with either (1) the full
citation to the IEEE work or (2) the IEEE-published version, including
the IEEE copyright notice and full citation. Prior or revised versions
of the paper must not be represented as the published version.This explicitly mentions author website redistribution, as long as
the official IEEE version is used.Unless I'm misreading the above, I think it's OK for us to keep such
copies in our personal sites. We can link to them from the scipy
wiki, though I don't think it would be OK to /copy/ the PDFs to the
scipy wiki.As always, IANAL and all that.
Cheers,
f
Andrew Straw wrote:
(Off list...)
Eek, well, not off-list!
Fernando Perez wrote:
This explicitly mentions author website redistribution, as long as
the official IEEE version is used.Unless I'm misreading the above, I think it's OK for us to keep such
copies in our personal sites. We can link to them from the scipy
wiki, though I don't think it would be OK to /copy/ the PDFs to the
scipy wiki.
I assume you are referring to this:
""
D. Personal Servers. Authors and/or their companies shall have the right to post their IEEE-copyrighted material on their own servers without permission, provided that the server displays a prominent notice alerting readers to their obligations with respect to copyrighted material and that the posted work includes the IEEE copyright notice as shown in Section 8.1.9A above.
"""
IANAL either, but I'm not sure how they would define a "personal" server. Would a web page on a University server count, for instance? I"d think putting it on the Wiki would count. Key is that copyright is properly attributed.
I assume there is someone at IEEE that you could ask.
-Chris
···
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@...259...
Well, I simply interpreted 'personal' as "my personal page, on my
institution's servers", while I worry that physically uploading it to
scipy's servers, which are owned by an external entity (Enthought)
might land them in trouble. I may be overly cautious here, but I just
didn't want to take chances.
Cheers,
f
···
On 4/25/07, Christopher Barker <Chris.Barker@...259...> wrote:
Fernando Perez wrote:
> This explicitly mentions author website redistribution, as long as
> the official IEEE version is used.
>
> Unless I'm misreading the above, I think it's OK for us to keep such
> copies in our personal sites. We can link to them from the scipy
> wiki, though I don't think it would be OK to /copy/ the PDFs to the
> scipy wiki.I assume you are referring to this:
""
D. Personal Servers. Authors and/or their companies shall have the right
to post their IEEE-copyrighted material on their own servers without
permission, provided that the server displays a prominent notice
alerting readers to their obligations with respect to copyrighted
material and that the posted work includes the IEEE copyright notice as
shown in Section 8.1.9A above.
"""IANAL either, but I'm not sure how they would define a "personal"
server. Would a web page on a University server count, for instance? I"d
think putting it on the Wiki would count. Key is that copyright is
properly attributed.I assume there is someone at IEEE that you could ask.
This is correct, and is standard for almost all publications I know. You are allowed to publish the article on your own personal website (provided
you use the published version or explicitly list the copyrights), but nowhere else.
Cheers,
Suresh
···
On Wed, 25 Apr 2007, Fernando Perez wrote:
Well, I simply interpreted 'personal' as "my personal page, on my
institution's servers", while I worry that physically uploading it to
scipy's servers, which are owned by an external entity (Enthought)
might land them in trouble. I may be overly cautious here, but I just
didn't want to take chances.Cheers,
My CiSE article can be downloaded from here:
http://www.siue.edu/~rkrauss/python_stuff.html
Ryan
···
On 4/25/07, John Hunter <jdh2358@...287...> wrote:
On 4/25/07, Fernando Perez <fperez.net@...287...> wrote:
> Since authors are allowed by their publication policy to keep a
> publicly available copy of their papers on their personal website,
> here's the ipython one:Didn't know that... here's a link to my matplotlib article
http://nitace.bsd.uchicago.edu/misc/c3sci.pdf
It might be nice to create a scipy wiki page linking to these PDFs.
JDH
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
matplotlib-users List Signup and Options