On Thu, Jul 19, 2007 at 06:46:20PM +0100, Graham Triggs wrote: > Possibilities that should be supportable: > * reassigning the existing id (handle) to a new file
This is, in my humble opinion, pure evil. How can you consider something to be an *identifier* if you can't actually guarantee that it identifies something? What if an object is replicated between repositories and the file is only replaced in one? The user would be seeing two objects that claim to be the same thing (given that they have the same identifier) but would actually be confronted with different content! We can't ever dilute the notion of what it means to be an identifier just to make our lives easier or to reduce the "cost" of assigning new identifiers or managing relationships between them. > * provide a fallback mapping - for example, to the item > * reporting that the id is invalid These are more reasonable, but see my previous email on the subject. cheers, Jim -- James Rutherford | Hewlett-Packard Limited registered Office: Research Engineer | Cain Road, HP Labs | Bracknell, Bristol, UK | Berks +44 117 312 7066 | RG12 1HN. [EMAIL PROTECTED] | Registered No: 690597 England The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error, you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated you should consider this message and attachments as "HP CONFIDENTIAL". ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
