a semi-legal question: linking to the BioC mailing list
1
0
Entering edit mode
@mai98ftustudservuni-leipzigde-338
Last seen 9.6 years ago
Ramon, > do I need to ask for explicit permission from every one on the linked > email? I'm not an expert on this but why would you? I mean, everyone could find those postings on her own anyway, right? So, I don't see a problem with linking to specific postings. Johannes P.S. Can you send me a link to your FAQ page? Quoting Ramon Diaz-Uriarte <rdiaz@cnio.es>: > Dear All, > > Is there a problem if, in a publicly viewable FAQ, I have links to > specific > postings on the BioC list? (Something like: "for some comments on > whatever, > see > href="https://www.stat.math.ethz.ch/pipermail/bioconductor/2003-Octo ber/ > this.whatever.html">") > > or do I need to ask for explicit permission from every one on the linked > > email? > > Thanks, > > R. > > -- > Ram?n D?az-Uriarte > Bioinformatics Unit > Centro Nacional de Investigaciones Oncol?gicas (CNIO) > (Spanish National Cancer Center) > Melchor Fern?ndez Almagro, 3 > 28029 Madrid (Spain) > Fax: +-34-91-224-6972 > Phone: +-34-91-224-6900 > > http://bioinfo.cnio.es/~rdiaz > PGP KeyID: 0xE89B3462 > (http://bioinfo.cnio.es/~rdiaz/0xE89B3462.asc) > > _______________________________________________ > Bioconductor mailing list > Bioconductor@stat.math.ethz.ch > https://www.stat.math.ethz.ch/mailman/listinfo/bioconductor >
0
Entering edit mode
Dear Johannes, Thanks for your answer. That is what I thought, but I never know with these things. A probably not-good analogy: anyone can find a crack to proprietary program xyz, but I guess there are limits to what one is supposed to be allowed to do with those programs and/or key generators. Since I link to the whole message, all information about author, etc, is included (i.e., there is no problem of quoting without attribution), but would someone be able to claim that they wrote the message for the BioC email list, not for it to be linked by me? Anyway, the link to the rudimentary FAQ (including the links to BioC) in: http://bioinfo.cnio.es/~rdiaz/StatsConsulting/CNIO-stats-FAQ.htm Best, R. On Tuesday 27 January 2004 10:13, Johannes Freudenberg wrote: > Ramon, > > > do I need to ask for explicit permission from every one on the linked > > email? > > I'm not an expert on this but why would you? I mean, everyone could find > those postings on her own anyway, right? So, I don't see a problem with > linking to specific postings. > > Johannes > > P.S. Can you send me a link to your FAQ page? > > Quoting Ramon Diaz-Uriarte <rdiaz@cnio.es>: > > Dear All, > > > > Is there a problem if, in a publicly viewable FAQ, I have links to > > specific > > postings on the BioC list? (Something like: "for some comments on > > whatever, > > see > > > href="https://www.stat.math.ethz.ch/pipermail/bioconductor/2003-Oc tober/ > > this.whatever.html">") > > > > or do I need to ask for explicit permission from every one on the linked > > > > email? > > > > Thanks, > > > > R. > > > > -- > > Ram?n D?az-Uriarte > > Bioinformatics Unit > > Centro Nacional de Investigaciones Oncol?gicas (CNIO) > > (Spanish National Cancer Center) > > Melchor Fern?ndez Almagro, 3 > > 28029 Madrid (Spain) > > Fax: +-34-91-224-6972 > > Phone: +-34-91-224-6900 > > > > http://bioinfo.cnio.es/~rdiaz > > PGP KeyID: 0xE89B3462 > > (http://bioinfo.cnio.es/~rdiaz/0xE89B3462.asc) > > > > _______________________________________________ > > Bioconductor mailing list > > Bioconductor@stat.math.ethz.ch > > https://www.stat.math.ethz.ch/mailman/listinfo/bioconductor -- Ram?n D?az-Uriarte Bioinformatics Unit Centro Nacional de Investigaciones Oncol?gicas (CNIO) (Spanish National Cancer Center) Melchor Fern?ndez Almagro, 3 28029 Madrid (Spain) Fax: +-34-91-224-6972 Phone: +-34-91-224-6900 http://bioinfo.cnio.es/~rdiaz PGP KeyID: 0xE89B3462 (http://bioinfo.cnio.es/~rdiaz/0xE89B3462.asc)
ADD REPLY

Login before adding your answer.

Traffic: 460 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6