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@openreader.org | 703-370-6540 OpenReader: http://www.openreader.org OR's first implementer: http://www.dotreader.org TeleBlog: http://www.teleread.org/blog