- gutvol-d - lists.pglaf.org

changing email addresses
by Norm Wolcott 24 May '06

24 May '06

Can whoever reads this please aarrange or tell me how to get reconnected with gutvol-d Thanks nwolcott2(a)post.harvard.edu

3 2

re: [gutvol-d] Kevin Kelly in NYT on future of digital libraries
by Bowerbird＠aol.com 24 May '06

24 May '06

michael said: > Obviously the press coverage about "Google library scanning" > has done more "as the main impetus for resurg[ent] interest > in a cyberlibrary" than the actualy scanning itself. well, d'uh, of course. that's how it always is. > And the latest estimated I have received show that Google's > total number of books has just recently passed 50,000 i do believe you misread that. 50,000 public-domain titles, with another 42,000 under copyright, for a total of 92,000. but even if it is just 50,000 total, they're still on my schedule: i predicted 10,000 after one year, 100,000 after two years, 1 million after three years, and 10 million after four years... > similar reports say that 88% are neither downloadable > nor proofread to any particular level of accuracy. except it's not google's job to make them downloadable, not in convenient form, nor to proofread the digitized text. it is _our_ job to grab the scans (as nicely and neatly as possible, courteous and respectful of the cost they entailed by scanning), and to make them available in a convenient format for reading, as well as to formulate automatic procedures to digitize the text and take it to a very high degree of accuracy. even if google did do these jobs for us, i would still replicate it, because i don't want to have to be dependent on google forever. > Somehow I don't think this was accidental. . . . the point is, if your books were _already_ "reading each other", people would have been talking about it long before this article. -bowerbird p.s. i see you're one of those old-fashioned people who refuse to recognize "resurging" as an adjective. it's ok. hopefully, if i keep using it that way, i'll win. (i'm trying to change the usage of "hopefully" with the same strategy.) :+)

6 6

re: [gutvol-d] re: Kevin Kelly in NYT on future of digital libraries]
by Bowerbird＠aol.com 23 May '06

23 May '06

i said: > > it is relatively easy for a programmer to "embed" > > shared annotations into an e-book marcello said: > > How would you know? um, because i've built a number of prototypes that do it. of course. before i make bold assertions, i've done years of research... didn't i post a message saying i could do a demo-app for david, to show how simple it is?, and didn't david say, "ok, go ahead", and didn't i say "ok, i will, you can expect it by thursday, i'd say?" just a minute, let me check... ok, the first two messages did indeed post ("i can do it", "ok, do it"), but i never got around to sending the third one this morning, sorry... i'll send it first thing tomorrow, since i think we've had enough for today... still, this is fairly easy to program. here's the code that sends out a note: > dim abcd as dictionary > dim socket1 as new httpsocket > dim lec as integer > abcd=new dictionary > abcd.value("myname")=editfield1.text > abcd.value("myemail")=editfield2.text > abcd.value("mycomment")=editfield3.text > socket1.setformdata abcd > socket1.post "http://users.aol.com/cgi-bin/guestbook/bowerbird/bbb.html" that's it. all the code you need. that's a real-live form, on the web right now, found at: > http://users.aol.com/bowerbird/bbb.html you can post from the page itself, filling out the form right there, using any web-browser on any internet-connected machine... or you can compose your comment on your own machine, and, using the program that contains the code listed above, post that comment to the website. (the downstream app is interacting with the code that runs the guestbook script on the .html page, so you will find the same variable names as above if you look at the code that creates the .html form on that page. fairly easy to figure out.) *** and here's the code that fetches the text of the webpage and puts it in an editfield. this is realbasic source-code, by the way. > dim http as new httpsocket > readit.text=http.get("users.aol.com/bowerbird/bbb.html",30) open another window in the app on your machine, and the two-line function above loads and displays the comments from the webpage. well, _that_ was certainly simple, wasn't it? and those are our two functions, one to post, the other to read. *** ok, wrap a g.u.i. around it, and you've got the demo app, pronto. with what?, a dozen lines of code?, all copied from the manual? like i said, pretty elementary. realbasic does all the heavy lifting. your mileage, using your language and your compiler, may vary. so, from my vantage-point, yes, this is dirt-simple. do you have any questions? -bowerbird p.s. marcello, thanks for creating my shrine. i can point to it in the future as holding a good number of my prognostications, not to mention my phat and sassy attitude, donchajustadoreit? thank goodness for the internet archive, right? brewster rocks!

1 0

re: [gutvol-d] re: Kevin Kelly in NYT on future of digital libraries]
by Bowerbird＠aol.com 23 May '06

23 May '06

michael said: > It is quite obvious that many people view > both Bowerbird's and Mr. Rothman's comments as attacks, > even Bowerbird and Mr. Rothman, though rarely would the > mention include self-reflection on this matter. for the record, i do not feel i have made _any_ "attacks". and i firmly believe if you look at what i have actually said -- as opposed to how david has _characterized_ what i've said -- you will see that that is so. indeed, if you find otherwise, i'd be happy for you to draw attention to it, so i can explain. i have said _unflattering_ things. but with good evidence. i _never_ resort to spin-doctoring, such as his name-calling. he flames me, and then tries to blame it on me by calling me "a troll". don't tell me you can't see through that transparency. and really, take a look at the latest thread. i made a simple point -- which is that it is relatively easy for a programmer to "embed" shared annotations into an e-book -- and he eventually ended up dragging in a _myriad_ of unrelated charges, some of them _silly_. meanwhile, it still remains easy to embed annotations in an e-book. contrary to what a naive observer might be led to believe by teleblog -- or even his recent posts here -- openreader is _not_ the only way to provide "interactivity" to electronic-books. not even close. all these other issues that he is throwing up are a _smokescreen_ intended to divert your attention from that very simple fact, and if anyone reading these posts doesn't realize that, then i _fear_ for their reading comprehension. of course, david doesn't _want_ people to read these posts, that's why he's throwing up a barrage, hoping that lurkers will just view the subject-headers (where he promulgates his smear job by prominently using the "troll" word). is what i'm saying here unflattering? you betcha. is it true? you betcha. but i don't do "attacks". i do hard-headed analysis with a focus on fact. and i don't get emotionally involved -- it interferes badly with the logic. it's a lot smarter to stay on-point. i do a lot of self-reflection. i can look at myself in a mirror just fine... -bowerbird

3 2

Bowerbird's development schedule and the $200K he's demanding [Re: [gutvol-d] re: blogs in e-books]
by David H. Rothman 23 May '06

23 May '06

As for your doing a demo, hey, be my guest. OSoft and others have long since carried out the basic concept of shared annotation, and the SA-capable dotReader is on the way from OSoft. Of course I'm actually concerned that your demo would hurt the cause of shared annotations by showing it off less than optimally, whether it was brower- or reader-based or both. And you're not going to have the related standards infrastructure that dotReader will. Who knows, you might even want to give us, er, "lock-in." Now, back to some grubby details from the ZML world, such as the rival reader app that you've spent so many hours trolling for--against OpenReader. What's your development schedule for your reader, so we can guard against "hype" and "vaporware"? Isn't true you've taken forever to get your reader out? And beyond people not paying you $200K or whatever, how come you won't share the source code for your rival reader? Are you ashamed of it? I still don't have a satisfactory answer. Code can be dear to one's heart, but still is a long way from poetic musings. Why must you keep your brillance to yourself? Don't you believe in open source? Answer those questions, and then I suggest that we wind down this thread in the interest of bandwidth and time--both mine and others'. PG people are very welcome to write me privately or phone me--especially Greg, if he's really serious about the comments he made to U.S. Today extolling interactivity. Here's PG's chance to adopt a powerful format (OpenReader) and enjoy readers worthy of it (dotReader and in the future FBReader). I'm all ears as far as suggestions from Greg or anyone else, and I know others will be as well. David Rothman | davidrothman(a)openreader.org | 703-370-6540 OpenReader: http://www.openreader.org OR's first implementer: http://www.dotreader.org TeleBlog: http://www.teleread.org/blog

2 3

re: Kevin Kelly in NYT on future of digital libraries]
by Bowerbird＠aol.com 23 May '06

23 May '06

david said: > You gratuitously attacked OpenReader out of the blue. no, i didn't. but i'm sure you'd like to spin it that way. what i said was that you were making a big deal about "putting a blog inside an e-book", when that is actually a somewhat trivial thing to do. look, i've inserted a blog inside of this e-mail: > http://www.buzzmachine.com/index.php/2006/05/19/the-book-is-dead-long-live-… -bowerbird

2 1

re: [gutvol-d] Kevin Kelly in NYT on future of digital libraries
by Bowerbird＠aol.com 23 May '06

23 May '06

michael said: > I seem to recall an earlier report from someone > who did lots of searches for Google books and > determined that 88% of them were published after 1922. i've posted this before, taken from lorcan dempsey's weblog, summarizing an article in d-lib. i always find it again easily by searching his site for "anatomy". > http://orweblog.oclc.org/archives/000800.html > The anatomy of an aggregate collection > September 17, 2005 > Approximately half of the print books > in the combined Google 5 collection > were published after 1974. > Almost three-quarters were published > after the Second World War. > Using the year 1923 as a rough break-off > point between materials that are > out of copyright and materials that are > in copyright [16], more than 80 percent > of the materials in the Google 5 collections are > still in copyright (this is of course an upper bound). if google has scanned roughly 100,000 pre-1923 items, and they were taking books off the shelves randomly, then we could assume they scanned 400,000 post-1923. but if we assume they were doing the pre-1923 items first, 100,000 pre-1923 scanned means 100,000 total scanned. seems to me assuming things does us absolutely no good. but google is _going_ to scan 10+ million books, eventually, so i'm not sure what difference it makes _how_many_ they've done "so far". are we really questioning their _resolve_ here? seems to me that they've proven they are dedicated to this... so attempts to figure out "how many books so far?" are silly. especially since we know that many of the post-1923 items did not have their copyrights renewed -- except that we do _not_ know what percentage, and thus cannot even _assume_ the answer to that important question, not with any certainty. if we say that half of the post-1923 books were not renewed, then that means that 60% (20% and 40%) are not in copyright. if we say that 1/3 of the post-1923 books were not renewed, then that means that 53% (20% and 33%) are not in copyright. if we say that 2/3 of the post-1923 books were not renewed, then that means that 86% (20% and 66%) are not in copyright. not that the answer would matter any, because due to the litigious arena into which we have allowed the project to be thrown, there's probably no way google would be likely to take the risk of showing _any_ of the orphaned material. so we're back to the original 20% that is pre-1923 and clear. of course, the answer to this is to give google an immunity, to let them serve as the "test-bed" that will act to bring out any claims of copyrighted material that might be lurking... in other words, let google show each book, in full, _until_ some _proof_ of copyright is rendered by another party. (and i do mean proof, and not just some bullshit claim...) -bowerbird

1 0

DotReader.com adr. [Re: OpenReader vs. the troll in the basement [re: [gutvol-d] Kevin Kelly in NYT on future of digital libraries]]
by David H. Rothman 23 May '06

23 May '06

Actually that's http://www.dotreader.com , not .org --mea culpa--and if PG really cares about open source, then it should encourage strong open source efforts of the OSoft variety rather than just wait until they catch on. Here's a little two-man software house in Tacoma, Washington, gambling hundreds of thousands of dollars on an open-source reader that can do far more than Plucker, allowing blogs and forums to be embedded inside books. Plucker has many appreciative users, but dotReader/OpenReader will be of far greater importance to commercial publishers, who are already starting to show interest. In turn, that'll be wonderful for PG works and other public domain books. dotReader reader can work with many kinds of books while improving the user experience. dotReader uses a turbocharged version of existing e-book standards that techies and publishers have thrashed aroundfor years. It's the best of all worlds: open source for programmers and a powerful free reader for users--and e-book standards similar to existing ones for publishers. Plus, dotReader can handle other XML/CSS-related formats as well. > We serverd 89504 plucker books in May 2006. I think you'll do much better with OpenReader available as well. OSoft's e-reader for the format is a thing of beauty, and, as noted, it'll be free to download. Plus, another awesome implementation is planned via the FBReader, which, according to the Wikipedia, is catching on among Nokia 770 users. See http://only.mawhrin.net/fbreader/plans.html and http://en.wikipedia.org/wiki/Plucker. Thanks, David David Rothman | davidrothman(a)openreader.org | 703-370-6540 TeleRead: http://www.teleread.org/blog On 5/22/06, Marcello Perathoner <marcello(a)perathoner.de> wrote: > > David H. Rothman wrote: > > > > See the true details for yourself at http://www.dotreader.org. > > It says: > > www.dotreader.org > > This page is parked free, courtesy of GoDaddy.com > > Did the .reader bubble already burst? > > > > I'd love for Gutenberg itself to offer OpenReader format > > We already offer most books in plucker. That's because they are open > format, widely deployed and offer an open toolchain. > > We serverd 89504 plucker books in May 2006. > > We'll see about OpenReader once you'll have widely deployed your .reader > and made available an open toolchain. > > > -- > Marcello Perathoner > webmaster(a)gutenberg.org > > _______________________________________________ > gutvol-d mailing list > gutvol-d(a)lists.pglaf.org > http://lists.pglaf.org/listinfo.cgi/gutvol-d >

4 3

re: [gutvol-d] Kevin Kelly in NYT on future of digital libraries
by Bowerbird＠aol.com 23 May '06

23 May '06

bruce said: > I have no idea how many books Google scanned > published after 1922 which are probably PD > because the copyright was apparently not renewed it would be foolish for google to take the risk of showing books published after 1922. if even one had been renewed, it would become ammunition for the other side. > nor the number of books scanned even though > the book is still under copyright. we could extrapolate from the ratio of public-domain to copyrighted titles in the libraries, but that would assume that they aren't taking that into consideration, and they might well be. i believe they had said that they would concentrate on public-domain titles first. (or maybe that's just what michael _said_ they said.) at any rate, i'm happy to sit back and wait while they continue to do more scanning... -bowerbird

2 2

re: [gutvol-d] re: blogs in e-books
by Bowerbird＠aol.com 23 May '06

23 May '06

david said: > You're extrapolating from a specific setup > at a specific company--one that will change in time. i have nothing else to go on. and i have no indication of the way -- if any -- that it "will change in time"... nothing technical has been written up. unlike many open-source programs, this one would appear to be being developed in secret. nothing technical about the app is written up... and while i'm quite happy to wait until the capability actually appears in an app that runs on my machine, so i can see what it does and exactly how it does it, you meanwhile are busy spewing glowing p.r.-speak. which, when you "answer" a hard question, turns to mush. if you can put a link in an e-mail here that takes a user to a comment that has been made in an osoft e-book -- let's say the one that i made in the "my antonia" demo -- then do it. otherwise, admit that -- at this point in time, with that e-book, anyway -- that capability is not present. or not. the answer here is of little or no consequence, because whether the annotations are viewable with an ordinary web-browser or not, the capability to code it (either way) is rather elementary to implement, which is the point that i made at the outset. if you'd like to see a demo program demonstrating the ease with which this can be done, i would be willing to code one up for you... but you don't really want me to steal dotreader thunder, do you? why not let mark carey roll out his version first? -bowerbird

1 0