View Single Post
Old 03-27-2009, 02:07 PM   #25
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,410
Karma: 27757236
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
Quote:
Originally Posted by Hadrien View Post
The main identifier should be unique since it can be used internally by a reading system to identify books, or for things such as annotations/bookmarks to globally identify books.
The problem with electronic documents is that they are infintely copyable. Any reading ssytem that labors under the delusion that every file it ever encounters will have a unique id is not going to get very far. For example a user may change the file name of an epub file and copy two copies onto his reader. The whole idea of unique ids is aholdover from print publishing that needs to go away. A unique id belongs to a *book* not to a file.


Quote:
Of course multiple identifiers are fine, but:
1. You don't always have an ISBN
If the user specifies an ISBN calibre will always produce it. Or are you suggesting calibre manufacture random ISBNs?

Quote:
2. You're using the calibre id as the package identifier
[/quote]
Again, so what?
kovidgoyal is offline   Reply With Quote