Quote:
Originally Posted by Hadrien
You're mixing things up: first of all, unique identifiers are not something from the "print world", we use URI every day to identify resources.
|
Uniquely and permanently? For content that isn't actually on a website? I don't think so. And UUIDs are not unique, they just have a low probability of collision. The whole concept of assigning permanently unique numbers to content that can be infinitely duplicated and modified is deeply flawed.
Quote:
|
Basically from what I can guess, with Calibre you're using an identifier that you increment every time that a file is generated (1, 2, 3 etc.). Instead you could generate a UUID, which would still work internally with the way you handle books but wouldn't be as likely to confuse a reading system.
|
Actually, calibre does generate a UUID if you convert from the command line, which is what any large scale conversion service would do anyway.
And my point was that a reading system that relies on every file that it comes across having a unique id is going to look rather silly.