On Tue, May 29, 2007 at 11:12:13AM +0100, Graham Triggs wrote: > On Tue, 2007-05-29 at 10:44 +0100, James Rutherford wrote: > > > 3) Including special characters in the URL string doesn't seem like a > > > good idea. While they are valid characters, it does take extra > > > processing to encode/decode them from layer to layer. > > > > As I mention on the wiki, my current idea is to have URLs of the form: > > > > http://dspace.me.ac.uk/uri/hdl:1234/56 > > > > which will resolve to the object with Handle 1234/56, etc. If the > > object also has a DOI with value 7890/12 then the following URL would > > point to the object as well: > > > > http://dspace.me.ac.uk/uri/doi:7890/12 > > > > It is necessary to include the "hdl:" and "doi:" parts so we can > > distinguish between different persistent identifier mechanisms. The > > values allowed for the persistent identifier are dependent on the > > mechanism we are dealing with, and as far as possible this will be kept > > simple. > > Whilst it is necessary to identify the persistent id scheme, that > doesn't mean that using a colon as part of the identifier is necessary > or desirable. Colons - or other 'unusual' characters - will end up > causing problems.
I don't see what's so unusual or undesirable about colons. The reasoning behind doing it this way was so that the value after "/uri/" is the canonical form of the identifier. > In fact, I don't even see that there is a reason to include 'uri' in the > url. Why not just support the existing: > > http://dspace.me.ac.uk/handle/1234/56 > > for handles, and: > > http://dspace.me.ac.uk/doi/7890/12 > > for DOIs, etc.? This is certainly an option. 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 DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
