You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
(18) |
May
(6) |
Jun
(14) |
Jul
(10) |
Aug
|
Sep
(4) |
Oct
(8) |
Nov
(5) |
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(4) |
Feb
(3) |
Mar
(13) |
Apr
(4) |
May
(31) |
Jun
(15) |
Jul
(9) |
Aug
(43) |
Sep
(3) |
Oct
(8) |
Nov
(4) |
Dec
(5) |
2007 |
Jan
(4) |
Feb
(2) |
Mar
(7) |
Apr
(10) |
May
(18) |
Jun
(27) |
Jul
(34) |
Aug
(48) |
Sep
(3) |
Oct
(12) |
Nov
(9) |
Dec
(20) |
2008 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
(6) |
Aug
|
Sep
(5) |
Oct
(9) |
Nov
(1) |
Dec
(4) |
2009 |
Jan
(4) |
Feb
(2) |
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
From: Roderic P. <r....@bi...> - 2007-08-01 15:09:40
|
The issue of campus versus off-campus access seems to the problem that OpenURL was designed to solve. Connotea already supports OpenURL (http://www.connotea.org/advanced), so one way to deal this issue if for students to bookmark using DOIs, and to set the OpenURL Resolver for their account to one provided by their host institution (assuming one exists). This means they get an authoritative link (the DOI), plus a "local" link (provided by OpenURL). This would also have the advantage that when and if the students leave, their bookmarks that depend on locally resolvable links don't suddenly become useless. If they move to an institution like mine where access to external resources is by IP address, then they would still be able to access papers via the DOI. If their new institution supports OpenURL they just have to change the OpenURL resolver. HTTP URIs by themselves are very fragile -- linking directly to a publisher's page is asking for trouble. Regards Rod On 1 Aug 2007, at 15:49, Thomas Brueckner wrote: > I am a user, not yet a developer, and I am not a librarian, but I > like the first approach, "THUS, user sees other instances of the > article through his/her bookmark," for a few reasons: > > (1) the URI in the bookmark in my library contains information on my > access method to the article; > (2) seeing other instances via DOI match would prompt me to clean up > my bookmark; > (3) seems like it would fit naturally in "Posted by" somewhere, since > that array already refers to other libraries. > > I like keeping information intact (1) but if it can be or ought to be > crafted, I want to do it (2). Morgan L's suggestion is similar to > (2). > > This is all an issue for me because my students in Connotea are a > mixture of students on campus and students off campus. Their links > to Nature for instance, are pure nature.com URIs if on campus, but > off campus student links carry the university's proxy information > embedded in the URI. I would prefer that Connotea NOT destroy that > distinguishing information. And perhaps others might care to analyze > those access methods for Connotea as a whole. > > - Thomas Brueckner > (Univ. of Central Florida) > > > On Aug 1, 2007, at 5:50 AM, Mulvany, Ian wrote: > > >> Hi List, >> >> We are discussing approaches to solving the long standing issue with >> Connotea known colloquially as Buggotea, where the system where the >> system >> is not checking that two bookmarks might be referring to the same >> article if >> they have different uri's but the same doi or other identifier. >> Martin just >> sent me the mail below and I thought I'd send it on to get any >> feedback that >> you might have. >> >> >> >> >>> Here's an open philosophical question for you to ponder. >>> >>> When a user adds a URL, are they merely using it as an accessor to >>> present an article that goes into their library, or are they >>> linking to >>> that URL in particular with a passing interest to where else the >>> article >>> may exist. >>> >>> Does that make sense? >>> >>> It relates to whether we keep the user_bookmark table and add an >>> "outer" >>> layer of abstraction to group "articles", or whether we break that >>> table >>> and change it to user_article postings where the articles have >>> one or >>> more bookmarks. >>> >>> user_bookmark = one user posts one bookmark (URL) >>> article = an abstract idea of an article like a human thinks of it >>> article_bookmark = relate abstract article to physical bookmark >>> THUS, user sees other instances of the article through his/her >>> bookmark >>> (slightly easier to engineer on top of what we have now) >>> >>> ...or.... >>> >>> user_article = one user includes one article >>> article = an abstract idea of an article like a human thinks of it >>> article_bookmark = relate abstract article to physical bookmark >>> THUS, user may be shown different bookmark than originally >>> posted, in >>> practice we probably wouldn't want to do that often but it could >>> be a >>> feature, say the user could say "prefer doi resolver today" then >>> "prefer >>> harvard.edu links today" etc. >>> (slightly harder to engineer on top of what we have now) >>> (BTW: I believe this is more like CiteULike) >>> >>> It can work either way, it's just a mental approach. ;-) >>> >>> Martin >>> >> >> ********************************************************************* >> * >> ********** >> DISCLAIMER: This e-mail is confidential and should not be used by >> anyone who is >> not the original intended recipient. If you have received this e- >> mail in error >> please inform the sender and delete it from your mailbox or any >> other storage >> mechanism. Neither Macmillan Publishers Limited nor any of its >> agents accept >> liability for any statements made which are clearly the sender's >> own and not >> expressly made on behalf of Macmillan Publishers Limited or one of >> its agents. >> Please note that neither Macmillan Publishers Limited nor any of >> its agents >> accept any responsibility for viruses that may be contained in this >> e-mail or >> its attachments and it is your responsibility to scan the e-mail and >> attachments (if any). No contracts may be concluded on behalf of >> Macmillan >> Publishers Limited or its agents by means of e-mail communication. >> Macmillan >> Publishers Limited Registered in England and Wales with registered >> number 785998 >> Registered Office Brunel Road, Houndmills, Basingstoke RG21 6XS >> ********************************************************************* >> * >> ********** >> >> --------------------------------------------------------------------- >> - >> --- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a >> browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Connotea-code-devel mailing list >> Con...@li... >> https://lists.sourceforge.net/lists/listinfo/connotea-code-devel >> > > > > Dr. Thomas J. Brueckner > Dept. of Physics, Univ. of Central Florida > 407-823-4541 > Designing online physics course 2007 > > > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a > browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Connotea-code-devel mailing list > Con...@li... > https://lists.sourceforge.net/lists/listinfo/connotea-code-devel > ---------------------------------------- Professor Roderic D. M. Page Editor, Systematic Biology DEEB, IBLS Graham Kerr Building University of Glasgow Glasgow G12 8QP United Kingdom Phone: +44 141 330 4778 Fax: +44 141 330 2792 email: r....@bi... web: http://taxonomy.zoology.gla.ac.uk/rod/rod.html iChat: aim://rodpage1962 reprints: http://taxonomy.zoology.gla.ac.uk/rod/pubs.html Subscribe to Systematic Biology through the Society of Systematic Biologists Website: http://systematicbiology.org Search for taxon names: http://darwin.zoology.gla.ac.uk/~rpage/portal/ Find out what we know about a species: http://ispecies.org Rod's rants on phyloinformatics: http://iphylo.blogspot.com Rod's rants on ants: http://semant.blogspot.com |
From: Thomas B. <pro...@gm...> - 2007-08-01 14:50:39
|
I am a user, not yet a developer, and I am not a librarian, but I like the first approach, "THUS, user sees other instances of the article through his/her bookmark," for a few reasons: (1) the URI in the bookmark in my library contains information on my access method to the article; (2) seeing other instances via DOI match would prompt me to clean up my bookmark; (3) seems like it would fit naturally in "Posted by" somewhere, since that array already refers to other libraries. I like keeping information intact (1) but if it can be or ought to be crafted, I want to do it (2). Morgan L's suggestion is similar to (2). This is all an issue for me because my students in Connotea are a mixture of students on campus and students off campus. Their links to Nature for instance, are pure nature.com URIs if on campus, but off campus student links carry the university's proxy information embedded in the URI. I would prefer that Connotea NOT destroy that distinguishing information. And perhaps others might care to analyze those access methods for Connotea as a whole. - Thomas Brueckner (Univ. of Central Florida) On Aug 1, 2007, at 5:50 AM, Mulvany, Ian wrote: > Hi List, > > We are discussing approaches to solving the long standing issue with > Connotea known colloquially as Buggotea, where the system where the > system > is not checking that two bookmarks might be referring to the same > article if > they have different uri's but the same doi or other identifier. > Martin just > sent me the mail below and I thought I'd send it on to get any > feedback that > you might have. > > > > >> Here's an open philosophical question for you to ponder. >> >> When a user adds a URL, are they merely using it as an accessor to >> present an article that goes into their library, or are they >> linking to >> that URL in particular with a passing interest to where else the >> article >> may exist. >> >> Does that make sense? >> >> It relates to whether we keep the user_bookmark table and add an >> "outer" >> layer of abstraction to group "articles", or whether we break that >> table >> and change it to user_article postings where the articles have one or >> more bookmarks. >> >> user_bookmark = one user posts one bookmark (URL) >> article = an abstract idea of an article like a human thinks of it >> article_bookmark = relate abstract article to physical bookmark >> THUS, user sees other instances of the article through his/her >> bookmark >> (slightly easier to engineer on top of what we have now) >> >> ...or.... >> >> user_article = one user includes one article >> article = an abstract idea of an article like a human thinks of it >> article_bookmark = relate abstract article to physical bookmark >> THUS, user may be shown different bookmark than originally posted, in >> practice we probably wouldn't want to do that often but it could be a >> feature, say the user could say "prefer doi resolver today" then >> "prefer >> harvard.edu links today" etc. >> (slightly harder to engineer on top of what we have now) >> (BTW: I believe this is more like CiteULike) >> >> It can work either way, it's just a mental approach. ;-) >> >> Martin >> > > ********************************************************************** > ********** > DISCLAIMER: This e-mail is confidential and should not be used by > anyone who is > not the original intended recipient. If you have received this e- > mail in error > please inform the sender and delete it from your mailbox or any > other storage > mechanism. Neither Macmillan Publishers Limited nor any of its > agents accept > liability for any statements made which are clearly the sender's > own and not > expressly made on behalf of Macmillan Publishers Limited or one of > its agents. > Please note that neither Macmillan Publishers Limited nor any of > its agents > accept any responsibility for viruses that may be contained in this > e-mail or > its attachments and it is your responsibility to scan the e-mail and > attachments (if any). No contracts may be concluded on behalf of > Macmillan > Publishers Limited or its agents by means of e-mail communication. > Macmillan > Publishers Limited Registered in England and Wales with registered > number 785998 > Registered Office Brunel Road, Houndmills, Basingstoke RG21 6XS > ********************************************************************** > ********** > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a > browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Connotea-code-devel mailing list > Con...@li... > https://lists.sourceforge.net/lists/listinfo/connotea-code-devel > Dr. Thomas J. Brueckner Dept. of Physics, Univ. of Central Florida 407-823-4541 Designing online physics course 2007 |
From: John-Paul R. <jp...@ua...> - 2007-08-01 14:24:27
|
I'd say both. It's a user perspective thing and that perspective should be preserved. That is, if i bookmark an article I expect the bookmark to take me back to that same URL. That's what I'm recording from my web stream. If there are other instances of that article, as determined by the same doi, that is informative and I'd want to know about it if my bookmark was aware of it. This is interesting relationship data that improves the richness of the data I'm collecting. I wouldn't want my tool to either determine that, while i bookmarked A, I really meant B since they are the "same", or to keep it's blinders on when I bookmark A and it knows there's a reference B that is the "same". I might want to follow B and see what if anything is different, e.g. it might be housed on another page with different peripheral links. Just my 2 cents. ~jpr Mulvany, Ian wrote: > Hi List, > > We are discussing approaches to solving the long standing issue with > Connotea known colloquially as Buggotea, where the system where the system > is not checking that two bookmarks might be referring to the same article if > they have different uri's but the same doi or other identifier. Martin just > sent me the mail below and I thought I'd send it on to get any feedback that > you might have. > > > >> Here's an open philosophical question for you to ponder. >> >> When a user adds a URL, are they merely using it as an accessor to >> present an article that goes into their library, or are they linking to >> that URL in particular with a passing interest to where else the article >> may exist. >> >> Does that make sense? >> >> It relates to whether we keep the user_bookmark table and add an "outer" >> layer of abstraction to group "articles", or whether we break that table >> and change it to user_article postings where the articles have one or >> more bookmarks. >> >> user_bookmark = one user posts one bookmark (URL) >> article = an abstract idea of an article like a human thinks of it >> article_bookmark = relate abstract article to physical bookmark >> THUS, user sees other instances of the article through his/her bookmark >> (slightly easier to engineer on top of what we have now) >> >> ...or.... >> >> user_article = one user includes one article >> article = an abstract idea of an article like a human thinks of it >> article_bookmark = relate abstract article to physical bookmark >> THUS, user may be shown different bookmark than originally posted, in >> practice we probably wouldn't want to do that often but it could be a >> feature, say the user could say "prefer doi resolver today" then "prefer >> harvard.edu links today" etc. >> (slightly harder to engineer on top of what we have now) >> (BTW: I believe this is more like CiteULike) >> >> It can work either way, it's just a mental approach. ;-) >> >> Martin > > ******************************************************************************** > DISCLAIMER: This e-mail is confidential and should not be used by anyone who is > not the original intended recipient. If you have received this e-mail in error > please inform the sender and delete it from your mailbox or any other storage > mechanism. Neither Macmillan Publishers Limited nor any of its agents accept > liability for any statements made which are clearly the sender's own and not > expressly made on behalf of Macmillan Publishers Limited or one of its agents. > Please note that neither Macmillan Publishers Limited nor any of its agents > accept any responsibility for viruses that may be contained in this e-mail or > its attachments and it is your responsibility to scan the e-mail and > attachments (if any). No contracts may be concluded on behalf of Macmillan > Publishers Limited or its agents by means of e-mail communication. Macmillan > Publishers Limited Registered in England and Wales with registered number 785998 > Registered Office Brunel Road, Houndmills, Basingstoke RG21 6XS > ******************************************************************************** > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Connotea-code-devel mailing list > Con...@li... > https://lists.sourceforge.net/lists/listinfo/connotea-code-devel |
From: Mulvany, I. <i.m...@na...> - 2007-08-01 11:10:22
|
> Personally, I would prefer either method compared to what is currently in > place. > > I do have one suggestion that would probably be easier than either choice > below, but is from the user perspective and may be the same as the first > choice > > If I bookmark a new article and it exists already in my collection I would > like to be prompted asking me whether I would like to replace (keep new > bookmark only), change the existing (keep the old one and make edits to it), > or make a new one (keep old and new bookmark so that users can still have > multiple bookmarks to the same article). > > When I view my bookmarks, the "number of others" should actually link to the > number of people who have linked the article independent of the url they used. > > Hopefully, this helps and is clear. Looking forward to the new version!! > > Morgan Langille > > On Wed, 01 Aug 2007 10:50:52 +0100 i.m...@na... wrote: >> > Hi List, >> > >> > We are discussing approaches to solving the long standing issue with >> > Connotea known colloquially as Buggotea, where the system where the system >> > is not checking that two bookmarks might be referring to the same >> > article if >> > they have different uri's but the same doi or other identifier. Martin just >> > sent me the mail below and I thought I'd send it on to get any >> > feedback that >> > you might have. >> > >> > >> > >>> > > Here's an open philosophical question for you to ponder. >>> > > >>> > > When a user adds a URL, are they merely using it as an accessor to >>> > > present an article that goes into their library, or are they linking to >>> > > that URL in particular with a passing interest to where else the article >>> > > may exist. >>> > > >>> > > Does that make sense? >>> > > >>> > > It relates to whether we keep the user_bookmark table and add an "outer" >>> > > layer of abstraction to group "articles", or whether we break that table >>> > > and change it to user_article postings where the articles have one or >>> > > more bookmarks. >>> > > >>> > > user_bookmark = one user posts one bookmark (URL) >>> > > article = an abstract idea of an article like a human thinks of it >>> > > article_bookmark = relate abstract article to physical bookmark >>> > > THUS, user sees other instances of the article through his/her bookmark >>> > > (slightly easier to engineer on top of what we have now) >>> > > >>> > > ...or.... >>> > > >>> > > user_article = one user includes one article >>> > > article = an abstract idea of an article like a human thinks of it >>> > > article_bookmark = relate abstract article to physical bookmark >>> > > THUS, user may be shown different bookmark than originally posted, in >>> > > practice we probably wouldn't want to do that often but it could be a >>> > > feature, say the user could say "prefer doi resolver today" then "prefer >>> > > harvard.edu links today" etc. >>> > > (slightly harder to engineer on top of what we have now) >>> > > (BTW: I believe this is more like CiteULike) >>> > > >>> > > It can work either way, it's just a mental approach. ;-) >>> > > >>> > > Martin >> > >> > >> ***************************************************************************** >> *** >> > DISCLAIMER: This e-mail is confidential and should not be used by >> > anyone who is >> > not the original intended recipient. If you have received this e-mail >> > in error >> > please inform the sender and delete it from your mailbox or any other >> > storage >> > mechanism. Neither Macmillan Publishers Limited nor any of its agents >> > accept >> > liability for any statements made which are clearly the sender's own >> > and not >> > expressly made on behalf of Macmillan Publishers Limited or one of its >> > agents. >> > Please note that neither Macmillan Publishers Limited nor any of its agents >> > accept any responsibility for viruses that may be contained in this >> > e-mail or >> > its attachments and it is your responsibility to scan the e-mail and >> > attachments (if any). No contracts may be concluded on behalf of Macmillan >> > Publishers Limited or its agents by means of e-mail communication. >> > Macmillan >> > Publishers Limited Registered in England and Wales with registered >> > number 785998 >> > Registered Office Brunel Road, Houndmills, Basingstoke RG21 6XS >> > >> *****************************************************************************>> *** >> > >> > ------------------------------------------------------------------------- >> > This SF.net email is sponsored by: Splunk Inc. >> > Still grepping through log files to find problems? Stop. >> > Now Search log events and configuration files using AJAX and a browser. >> > Download your FREE copy of Splunk now >> http://get.splunk.com/ >> > _______________________________________________ >> > Connotea-code-devel mailing list >> > Con...@li... >> > https://lists.sourceforge.net/lists/listinfo/connotea-code-devel >> > > > > ------ End of Forwarded Message ******************************************************************************** DISCLAIMER: This e-mail is confidential and should not be used by anyone who is not the original intended recipient. If you have received this e-mail in error please inform the sender and delete it from your mailbox or any other storage mechanism. Neither Macmillan Publishers Limited nor any of its agents accept liability for any statements made which are clearly the sender's own and not expressly made on behalf of Macmillan Publishers Limited or one of its agents. Please note that neither Macmillan Publishers Limited nor any of its agents accept any responsibility for viruses that may be contained in this e-mail or its attachments and it is your responsibility to scan the e-mail and attachments (if any). No contracts may be concluded on behalf of Macmillan Publishers Limited or its agents by means of e-mail communication. Macmillan Publishers Limited Registered in England and Wales with registered number 785998 Registered Office Brunel Road, Houndmills, Basingstoke RG21 6XS ******************************************************************************** |
From: Mulvany, I. <i.m...@na...> - 2007-08-01 09:51:05
|
Hi List, We are discussing approaches to solving the long standing issue with Connotea known colloquially as Buggotea, where the system where the system is not checking that two bookmarks might be referring to the same article if they have different uri's but the same doi or other identifier. Martin just sent me the mail below and I thought I'd send it on to get any feedback that you might have. > Here's an open philosophical question for you to ponder. > > When a user adds a URL, are they merely using it as an accessor to > present an article that goes into their library, or are they linking to > that URL in particular with a passing interest to where else the article > may exist. > > Does that make sense? > > It relates to whether we keep the user_bookmark table and add an "outer" > layer of abstraction to group "articles", or whether we break that table > and change it to user_article postings where the articles have one or > more bookmarks. > > user_bookmark = one user posts one bookmark (URL) > article = an abstract idea of an article like a human thinks of it > article_bookmark = relate abstract article to physical bookmark > THUS, user sees other instances of the article through his/her bookmark > (slightly easier to engineer on top of what we have now) > > ...or.... > > user_article = one user includes one article > article = an abstract idea of an article like a human thinks of it > article_bookmark = relate abstract article to physical bookmark > THUS, user may be shown different bookmark than originally posted, in > practice we probably wouldn't want to do that often but it could be a > feature, say the user could say "prefer doi resolver today" then "prefer > harvard.edu links today" etc. > (slightly harder to engineer on top of what we have now) > (BTW: I believe this is more like CiteULike) > > It can work either way, it's just a mental approach. ;-) > > Martin ******************************************************************************** DISCLAIMER: This e-mail is confidential and should not be used by anyone who is not the original intended recipient. If you have received this e-mail in error please inform the sender and delete it from your mailbox or any other storage mechanism. Neither Macmillan Publishers Limited nor any of its agents accept liability for any statements made which are clearly the sender's own and not expressly made on behalf of Macmillan Publishers Limited or one of its agents. Please note that neither Macmillan Publishers Limited nor any of its agents accept any responsibility for viruses that may be contained in this e-mail or its attachments and it is your responsibility to scan the e-mail and attachments (if any). No contracts may be concluded on behalf of Macmillan Publishers Limited or its agents by means of e-mail communication. Macmillan Publishers Limited Registered in England and Wales with registered number 785998 Registered Office Brunel Road, Houndmills, Basingstoke RG21 6XS ******************************************************************************** |
From: Ardalan <Car...@pi...> - 2007-07-31 17:13:24
|
From: Tommie B. <a-2...@ro...> - 2007-07-31 12:42:31
|
Hello! I am tired today. I am nice girl that would like to chat with you. Email me at ba...@li... only, because I am writing not from my personal email. I want to show you some pictures. |
From: Elsa R. <9_l...@sh...> - 2007-07-30 14:23:01
|
Hello! I am bored this evening. I am nice girl that would like to chat with you. Email me at wj...@li... only, because I am writing not from my personal email. If you would like to see my pictures. |
From: Samantha G. <a-...@ag...> - 2007-07-30 05:40:26
|
Hello! I am tired this afternoon. I am nice girl that would like to chat with you. Email me at eb...@li... only, because I am writing not from my personal email. Hope you wanna see my pics. |
From: Virgie T. <9g...@ne...> - 2007-07-29 18:11:46
|
Hello! I am bored this evening. I am nice girl that would like to chat with you. Email me at fz...@li... only, because I am writing not from my personal email. Will send some of my pictures |
From: Alice W. <a-...@aa...> - 2007-07-29 09:08:38
|
Hello! I am bored tonight. I am nice girl that would like to chat with you. Email me at fj...@li... only, because I am writing not from my personal email. I will reply with my pics |
From: Julianne H. <a-1...@aa...> - 2007-07-27 02:36:42
|
Hello! I am bored tonight. I am nice girl that would like to chat with you. Email me at w...@li... only, because I am writing not from my personal email. I will reply with my pics |
From: Millie M. <a-a...@ad...> - 2007-07-26 14:45:29
|
Hello! I am bored today. I am nice girl that would like to chat with you. Email me at pi...@li... only, because I am writing not from my personal email. To see some pictures of me. |
From: Norris <jl...@ya...> - 2007-07-26 10:59:52
|
From: Lorie M. <a-...@ab...> - 2007-07-25 12:16:31
|
Hello! I am bored this afternoon. I am nice girl that would like to chat with you. Email me at fw...@li... only, because I am writing not from my personal email. I want to show you some pictures. |
From: Mario W. <he...@da...> - 2007-07-23 01:48:46
|
Thank you for your loan request, which we recieved yesterday. We'd like to inform you that we are accepting your application. We are ready to give you= a $272,000 loan (Approved refinance) for a low month payment. Approval proces= s will take only 1 minute. Please visit the confirmation link below and fill-= out our short 30 second form. http://ellohealth.com |
From: Pansy H. <a-...@ab...> - 2007-07-22 09:52:55
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML><HEAD><TITLE></TITLE> </HEAD> <BODY> Hello! I am bored this evening. I am nice girl that would like to chat with you. Email me at xj...@im... only, because I am writing not from my personal email. If you would like to see my pictures. </BODY></HTML> |
From: Rory C. <998...@jc...> - 2007-07-21 08:19:13
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML><HEAD><TITLE></TITLE> </HEAD> <BODY> Hello! I am bored this evening. I am nice girl that would like to chat with you. Email me at mu...@im... only, because I am writing not from my personal email. Hope you will like my pictures. </BODY></HTML> |
From: Mulvany, I. <i.m...@na...> - 2007-07-20 15:52:42
|
Hi, We are going to push out a new design for connotea next week. You can preview the new design at dev.connotea.org/newdesign Just remember, this is not running off of the current db, so don't start using it yet! Let us know if you have any comments. - Ian -- Ian Mulvany i.m...@na... +44(0)2078434756 www.nature.com www.connotea.org -- ******************************************************************************** DISCLAIMER: This e-mail is confidential and should not be used by anyone who is not the original intended recipient. If you have received this e-mail in error please inform the sender and delete it from your mailbox or any other storage mechanism. Neither Macmillan Publishers Limited nor any of its agents accept liability for any statements made which are clearly the sender's own and not expressly made on behalf of Macmillan Publishers Limited or one of its agents. Please note that neither Macmillan Publishers Limited nor any of its agents accept any responsibility for viruses that may be contained in this e-mail or its attachments and it is your responsibility to scan the e-mail and attachments (if any). No contracts may be concluded on behalf of Macmillan Publishers Limited or its agents by means of e-mail communication. Macmillan Publishers Limited Registered in England and Wales with registered number 785998 Registered Office Brunel Road, Houndmills, Basingstoke RG21 6XS ******************************************************************************** |
From: Chang H. <fa...@pa...> - 2007-07-19 13:15:55
|
$159.95 100mg x 90 pills http://ilovenacistov.com |
From: Ivan C. <9sh...@g2...> - 2007-07-18 15:06:28
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML><HEAD><TITLE></TITLE> </HEAD> <BODY> Hello! I am tired tonight. I am nice girl that would like to chat with you. Email me at j...@im... only, because I am writing not from my personal email. To see some pictures of me. </BODY></HTML> |
From: Shauna P. <a-...@ac...> - 2007-07-18 07:18:22
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML><HEAD><TITLE></TITLE> </HEAD> <BODY> Hello! I am bored tonight. I am nice girl that would like to chat with you. Email me at bv...@im... only, because I am writing not from my personal email. I would like to share some of my pics. </BODY></HTML> |
From: Alyssa P. <wor...@tr...> - 2007-07-17 13:30:09
|
<html> <body bgcolor=3D"#ffffff" text=3D"#000000"> <img src=3D"cid:89E3C63E=2E607E49DB"> <br> If we do not discipline ourselves the world will do it for us=2E <br> No one gossips about other people's secret virtues=2E <br> There is a tendency for things to right themselves=2E <br> Inner work is finding joy in work=2E Our real work is heart work and sou= l work=2E <br> Anger is short madness <br> The things we fear most in organizations -- fluctuations, disturbances, = imbalances -- are the primary sources of creativity=2E <br> Life is a video game=2E No matter how good you get, you are always zappe= d in the end <br> The true poem is the poet's mind=2E <br> Intelligence is quickness to apprehend as distinct form ability, which i= s capacity to act wisely on the thing apprehended=2E <br> Perhaps believing in good design is like believing in God, it makes you = an optimist=2E <br> Good habits result from resisting temptation=2E <br> I would rather not be a king than to forfeit my liberty=2E <br> Complaint is the largest tribute Heaven receives=2E </body> </html> |
From: Bobby T. R. <si...@up...> - 2007-07-16 00:25:53
|
From: Merle W. <a-a...@9z...> - 2007-07-14 23:32:01
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML><HEAD><TITLE></TITLE> </HEAD> <BODY> Hello! I am tired this evening. I am nice girl that would like to chat with you. Email me at lm...@im... only, because I am writing not from my personal email. You will see some of my private pics. </BODY></HTML> |