[doi-discuss] DOI consistency
Nicolas Williams
Nicolas.Williams at sun.com
Thu Oct 23 12:30:57 PDT 2008
On Tue, Oct 21, 2008 at 11:17:38AM -0400, David P. Quigley wrote:
> In another email I clarified what I meant by negotiation and the system
> I described is closer to your first example. By negotiation I meant both
> sides say these are the DOIs I understand and based on that and other
> policy information they can determine the best one to speak in. I didn't
> mean to imply that they can magically establish mappings which would
> leak more information than necessary.
Although that wouldn't necessarily be out of the question either.
I can see several kinds of mappings:
- Mappings between different-but-semantically-similar DOIs
- such as mappings between deprecated and replacement DOIs
- or mappings between DTE DOIs historically constructed separately
but for the same apps and same roles
This warrants negotiation only if it is the client that must do the
mapping.
I think it will be easier to deploy server-does-mapping. But I'm not
sufficiently sure. To avoid having to add DOI negotiation later, but
also to avoid having it be a requirement, let's just make DOI
negotiation an option.
- Mappings between on-the-wire and server-internal DOIs.
This is an internal detail warranting no negotiation, of course.
Nico
--
More information about the doi-discuss
mailing list