> The more 'interesting' aspect is that there is
> no standard for
> constructing these IDs and certainly no registry of them, so a client
> wishing to send a multi-database-search to two MSEs would have to
> re-formulate the database IDs for each of them. This issue is
> likely to be
> discussed at the forthcoming NISO IDs workshop.
I don't see this as a big issue - agreed a multi MSE client (is that an
MSE-MSE) would have to have an internal mapping document of equivalent
IDs but this isn't a major technical obstacle.
Whilst I agree, and agreed ID format and registry would be nice, past
experience with other global ID proposals make me suspect that it wo'n't
happen over night, and we can get some reasonably fuctional MSE's in the