It probably doesn't make a ton of sense to implement it now with UUIDs, only to change again to a mapped, museum-specific identifier for 0.5. I do agree that this makes sense for the next release. In short, having museum-specific IDs will allow us that permanent linkage with the upstream source of data, making it possible for us to do smart refreshing data imports and so on.
Colin On 2010-02-11, at 11:58 AM, Antranig Basman wrote: > That said, if we *do* go forwards, I think it would be important to use a > stable domain-specific key rather than the doc UUID. It would be impossible > to operate stable URLs for artefacts and other entities otherwise. Hugues has > told us how to derive these for McCord and it is an essential requirement of > any other integration that we could do this for another institution. So this > is certainly something we will do for 0.5 but the question is whether it > makes sense this week. --- Colin Clark Technical Lead, Fluid Project http://fluidproject.org _______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
