LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  November 2009

CODE4LIB November 2009

Subject:

Re: Assigning DOI for local content

From:

Jonathan Rochkind <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Mon, 23 Nov 2009 14:52:43 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (72 lines)

Ross Singer wrote:
>
> Also, with your use cases, would these services be impossible if the
> only binding was HTTP?
Well, here's the trick about handles, as I understand it. A handle, for
instance, a DOI, is "10.1074/jbc.M004545200".

While, for DOI handles, normally we resolve that using dx.doi.org, at
http://dx.doi.org/10.1074/jbc.M004545200, that is not actually a
requirement of the handle system. You can resolve it through any handle
server, over HTTP or otherwise. Even if it's still over HTTP, it doesn't
have to be at dx.doi.org, it can be via any handle resolver.

For instance, check this out, it works:

http://hdl.handle.net/10.1074/jbc.M004545200

Cause the DOI is really just a subset of Handles, any resolver
participating in the handle network can resolve em. In Eric's
hypothetical use case, that could be a local enterprise handle resolver
of some kind. (Although I'm not totally sure that would keep your usage
data private; the documentation I've seen compares the handle network to
DNS, it's a distributed system, I'm not sure in what cases handle
resolution requests are sent 'upstream' by the handle resolver, and if
actual individual lookups are revealed by that or not. But in any case,
when Ross suggests -- "Presumably dx.hellman.net would need to harvest
its metadata from somewhere, which seems like it would leave a
footprint. It also needs some mechanism to stay in sync with the master
index." -- my reading this suggests this is _built into_ the handle
protocol, it's part of handle from the very start (again, the DNS
analogy, with the emphasis on the distributed resolution aspect), you
don't need to invent it yourself. The details of exactly how it works, I
don't know enough to say. )

Now, I'm somewhat new to this stuff too, I don't completely understand
how it works. Apparently hdl.handle.net can <strike>handle</strike>
deal with any handle globally, while presumably dx.doi.org can only deal
with the subset of handles that are also DOIs. And apparently you can
have a handle resolver that works over something other than HTTP too.
(Although Ross argues, why would you want to? And I'm inclined to agree).

But appears that the handle system is quite a bit more fleshed out than
a simple purl server, it's a distributed protocol-independent network.
The protocol-independent part may or may not be useful, but it certainly
seems like it could be, it doens't hurt to provide for it in advance.
The distributed part seems pretty cool to me.

So if it's no harder to set up, maintain, and use a handle server than a
Purl server (this is a big 'if', I'm not sure if that's the case), and
handle can do everything purl can do and quite a bit more (I'm pretty
sure that is the case)... why NOT use handle instead of purl? It seems
like handle is a more fleshed out, robust, full-featured thing than purl.

Jonathan




> Presumably dx.hellman.net would need to
> harvest its metadata from somewhere, which seems like it would leave a
> footprint. It also needs some mechanism to stay in sync with the
> master index. Your non-resolution service also seems to be looking
> these things up in realtime. Would a RESTful or SOAP API (*shudder*)
> not accomplish the same goal?
>
> Really, though, the binding argument here is less the issue here than
> if you believe http URIs are valid identifiers or not since there's no
> reason a URI couldn't be dereferenced via other bindings, either.
>
> -Ross.
>
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager