Nothing wrong with using the GUID there, I dont' think, but if you have
to change your URI's you've kind of already failed. If you don't think
you can keep that domain, it'd be better to spend time/energy setting up
another domain you have reasonable confidence can remain persistent,
rather than using GUID as a way to plan for a domain switch. If your
URI's change, that's bad.
But if you want to use a GUID as part your URI, I can't see anything
_wrong_ with that, it's not a problem, if it's convenient for you. But
it's probably not a good idea to use it to plan for a domain name
change, instead of planning to NOT have a domain name change, heh.
Jonathan
Dan Matei wrote:
> -----Original Message-----
> From: Jonathan Rochkind <rochkind_at_JHU.EDU>
> Date: Tue, 27 Oct 2009 12:24:06 -0400
>
>
>> [ There is potentially something wrong with having your URI begin
>> http://clasate.cimec.co/Detailu.asp though. Some day you might stop
>> using asp. You don't want all your URI's to be ruined when you do so.
>>
>
> Right, right ! But that's ancient ! It is c. 4 years old :-)
>
>
>> Much better to keep your URI's technology independent.
>> http://clasate.cimec.co/Detalu?id is much better. Although the REST
>> fanatics will tell you it should be http://clasate.cimec.co/Detailu/id
>>
>
> I completely agree. We will do that.
>
>
>> instead. (Depending on what 'detailu' means, I don't know). I think
>>
>
> detaliu (ro) = detail (en) :-)
>
>
>> But if I just have an OCLC number, say "23233455", it's very easy for me
>> to lose the context that that IS an OCLC number. I need to make sure
>> not to confuse it with the LCCN "23233455". If instead I'm using
>> "http://www.worldcat.org/23233455" as an identifier, the context comes
>> with it, it's not gonna get seperated, and it's not gonna collide with
>> "http://id.loc.gov/lccn/23233455". It's globally unique _without_
>> needing to use something cumbersome like a GUID.
>>
>
> True. But if the ugly GUID is used and I'm loosing my www.cimec.ro domain and I have to move my object, then
>
> http://www.cimec.ro/a1f81a4e-e298-4472-86e1-ad788331e260
>
> could morph to
>
> http://www.x.org/a1f81a4e-e298-4472-86e1-ad788331e260
>
> and I know that it points to the same object (maybe on a different disk, in a different country).
>
> Dan
>
>
Received on Tue Oct 27 2009 - 15:34:54 EDT