tag:blogger.com,1999:blog-19803222.post1848400013384286294..comments2024-03-18T01:45:45.724-06:00Comments on natural language processing blog: To err is human, but what about researchers?halhttp://www.blogger.com/profile/02162908373916390369noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-19803222.post-48902522483754810262009-05-12T10:56:00.000-06:002009-05-12T10:56:00.000-06:00酒店經紀PRETTY GIRL 台北酒店經紀人 ,禮服店 酒店兼差PRETTY GIRL酒店公關 酒...酒店經紀PRETTY GIRL <A HREF="http://www.taipeilady.com/" REL="nofollow" TITLE="台北酒店經紀人">台北酒店經紀人</A> ,<A HREF="http://tw.myblog.yahoo.com/jw!qZ9n..6QEhhc0LkItOBm/" REL="nofollow" TITLE="禮服店">禮服店</A> 酒店兼差PRETTY GIRL<A HREF="http://www.mashow.org/" REL="nofollow" TITLE="酒店公關">酒店公關</A> 酒店小姐 彩色爆米花<A HREF="http://blog.xuite.net/jkl338801/blog/" REL="nofollow" TITLE="酒店兼職">酒店兼職</A>,酒店工作 彩色爆米花<A HREF="http://tw.myblog.yahoo.com/jw!BIBoU5SeBRs21nb_ajFpncbTqXds" REL="nofollow" TITLE="酒店經紀">酒店經紀</A>, <A HREF="http://mypaper.pchome.com.tw/news/thomsan/3/1310065116/20080905040949/" REL="nofollow" TITLE="酒店上班">酒店上班</A>,酒店工作 PRETTY GIRL<A HREF="http://tw.myblog.yahoo.com/jw!rybqykeeER6TH3AKz1HQ5grm/" REL="nofollow" TITLE="酒店喝酒">酒店喝酒</A>酒店上班 彩色爆米花<A HREF="http://mypaper.pchome.com.tw/news/jkl338801/" REL="nofollow" TITLE="台北酒店">台北酒店</A>酒店小姐 PRETTY GIRL<A HREF="http://www.mashow.org/" REL="nofollow" TITLE="酒店上班">酒店上班</A>酒店打工PRETTY GIRL<A HREF="http://www.tpangel.com/" REL="nofollow" TITLE="酒店打工">酒店打工</A>酒店經紀 彩色爆米花Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-19803222.post-89416452156318431462007-03-26T18:47:00.000-06:002007-03-26T18:47:00.000-06:00There's a discussion about this issue on reddit to...There's a discussion about this issue on reddit today:<BR/><BR/>http://programming.reddit.com/info/1d1d1/commentsDavid Gelbarthttps://www.blogger.com/profile/09930813569213912228noreply@blogger.comtag:blogger.com,1999:blog-19803222.post-83012377806703444922007-02-21T15:38:00.000-07:002007-02-21T15:38:00.000-07:00I checked with the IEEE and it's against their pol...I checked with the IEEE and it's against their policy to replace the PDF. The policy is understandable. I hope at some point in the future the IEEE will start offering archiving of supplementary online material related to IEEE papers (such as source code or expanded tables of results), as Science and Nature do, and perhaps some kind of mechanism for noting corrections could be made part of that, but I don't expect that would apply<BR/>to older papers.<BR/><BR/>I published a later paper which cites my IEEE paper and mentions the corrections, but it is not an IEEE paper (it's published by ISCA) and doesn't show up in citation tracking. I have been volunteering with ISCA to help an effort to have ISCA archives indexed by Google Scholar. If that happens, anybody who finds IEEE paper through Google Scholar will be able to find the ISCA paper through the Google Scholar citation tracking, and that will put my mind greatly at ease.David Gelbarthttps://www.blogger.com/profile/09930813569213912228noreply@blogger.comtag:blogger.com,1999:blog-19803222.post-36937571848032391902007-02-03T23:06:00.000-07:002007-02-03T23:06:00.000-07:00I wonder if there is a way to have a paper annotat...I wonder if there is a way to have a paper annotated with a correction in the IEEE Xplore system? <br /><br />Several years ago, I published an incorrect IEEE workshop paper, and at that time I didn't follow my current practice of linking to a web page in each paper. So I put a new PDF copy of the paper on my group's web site with a footer added on the bottom of the first page containing a URL for the correction. (I think this was better than simply mentioning the correction on my home page, since search engines will sometimes bring people directly to the PDF.) Still, people are likely to find the IEEE Xplore PDF instead. Perhaps the IEEE would be willing to stick the new PDF into the Xplore database for me?David Gelbarthttps://www.blogger.com/profile/09930813569213912228noreply@blogger.comtag:blogger.com,1999:blog-19803222.post-10815678884873063922007-02-03T19:44:00.000-07:002007-02-03T19:44:00.000-07:00I am dealing with the same problem right now. the ...I am dealing with the same problem right now. the prescribed approach is:<br /><br />1. send a mail to the PC chair for the conference notifying them of the error, fixes if any, related docs, and the text of an erratum to be added to the next proceedings.<br /><br />2. do all the website stuff that David mentioned. <br /><br />3. If the paper was arXiv'd, then the comments on the updated version can incorporate this as wellSuresh Venkatasubramanianhttps://www.blogger.com/profile/15898357513326041822noreply@blogger.comtag:blogger.com,1999:blog-19803222.post-74053418334967648902007-02-03T18:49:00.000-07:002007-02-03T18:49:00.000-07:00When I write a conference paper, I create an assoc...When I write a conference paper, I create an associated web page, and I say in the paper that the reader can find additional information at that page, or that I may use that page in the future for updates. This way I can make a correction instantly if I need to. The web page is also handy as a place I can use after publication to release source code, give pointers to new related work, and so on. <br /><br />I put the web page in my research group's web space, rather than my personal web space, so it will still be available after I leave my group and my account is deleted.<br /><br />The expected lifespan of the web page would be even longer if I could use an institutional-level web space through a service like DSpace. (I'm not sure DSpace has the required capability for post-submission editing, but I think this capability is either available or under discussion in the DSpace community. However, I don't think my university provides a a DSpace service.)David Gelbarthttps://www.blogger.com/profile/09930813569213912228noreply@blogger.comtag:blogger.com,1999:blog-19803222.post-81763582206317525322007-02-03T18:43:00.000-07:002007-02-03T18:43:00.000-07:00This comment has been removed by the author.David Gelbarthttps://www.blogger.com/profile/09930813569213912228noreply@blogger.comtag:blogger.com,1999:blog-19803222.post-78521298752666809932007-02-03T18:40:00.000-07:002007-02-03T18:40:00.000-07:00This comment has been removed by the author.David Gelbarthttps://www.blogger.com/profile/09930813569213912228noreply@blogger.com