Comments on: Your Book as a Database: A Primer

By: Best of Digital Publishing 2010 | Publishing Perspectives

Best of Digital Publishing 2010 | Publishing Perspectives — Thu, 30 Dec 2010 08:01:32 +0000

[...] Book As a Database Part 1 Part 2 Part [...]

By: Dew Droplets | Cloverdew Creative

Dew Droplets | Cloverdew Creative — Mon, 20 Dec 2010 12:38:02 +0000

[...] margins? Technical manuals that self-update? All of these things may be possible with the use of relational databases and e-Books, says Chris Kubica on Publishing Perspectives. If you had no limits, what kind of book would YOU [...]

By: Richard Nash Q&A: Sneak Peak at Redlemonade, Discusses Reading Habits

Richard Nash Q&A: Sneak Peak at Redlemonade, Discusses Reading Habits — Mon, 08 Nov 2010 16:51:43 +0000

[...] series of articles for Publishing Perspectives “Your Book As a Database: A Primer” here, here and here. GD Star Ratingloading… Read more articles like this [...]

By: Book as Database | So Many Books

Book as Database | So Many Books — Tue, 29 Jun 2010 23:29:56 +0000

[...] Posted on June 29, 2010 by Stefanie Now, here is an interesting way to think about books: Book as a Database. Don’t go technophobic on me now, the author of the three-part article, Chris Kubica, [...]

By: Sunday Salon: 20 Examples That Feed My Fascinations | Semicolon

Sunday Salon: 20 Examples That Feed My Fascinations | Semicolon — Sun, 27 Jun 2010 04:27:31 +0000

[...] Your Book as a Database by Chris Kubica. I’m not sure I understand completely, but it’s definitely [...]

By: Thirty Three Things (v. 3) » First Thoughts | A First Things Blog

Thirty Three Things (v. 3) » First Thoughts | A First Things Blog — Sat, 26 Jun 2010 05:02:27 +0000

[...] The Book as a Database Imagine the future of books not as physical objects, but as relational [...]

By: Dew Droplets « Clover Dew Creative

Dew Droplets « Clover Dew Creative — Fri, 18 Jun 2010 17:33:53 +0000

By: Chris Kubica

Chris Kubica — Mon, 14 Jun 2010 18:45:31 +0000

Donald: a book could be finite. Like if I upload Moby Dick as a neverend book, the text of Moby Dick would not change. The data, notes, comments, highlights, etc of readers is what could e infinite.

On the other hand, a book about how to build computers, say, would constantly be updated as the tech itself is always changing. In that case, the book itself AND the reader metadata could be in a neverending state of flux.

By: Chris Kubica

Chris Kubica — Mon, 14 Jun 2010 18:43:33 +0000

Matt: a neverend version of the auto manual would have the readers/users being able to scream the errors and poor quality to the author which would hopefully prompt fast corrections/updates.

By: Your Book as a Database (Part 3)

Your Book as a Database (Part 3) — Mon, 14 Jun 2010 06:06:33 +0000

[...] in Your Book as a Database: A Primer, we laid the foundation for thinking of books as relational databases. Yesterday in Part 2 I [...]