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:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  January 2011

CODE4LIB January 2011

Subject:

Re: best persistent url system

From:

Kyle Banerjee <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Fri, 14 Jan 2011 12:29:20 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (66 lines)

>
> This attitude makes sense only if you are used to very bad “persistent
>
>> URL” systems. A URI is an identifier. Making it persistent is our job.
> Using a different identifier scheme won’t make our job easier.
>
I totally agree with all these statements as well as with the sentiment that
the approach I advocate is far from optimal.

>
My basic philosophy is that: 1) the greatest weakness in any system can be
found in the carbon-based liveware it depends on (i.e. people act like
people) ; 2) you can totally count on the second law of thermodynamics (the
entropy of a closed system always increases); and 3) there is too much work
to go around.

>
Translated for the case at hand, this means: 1) people will inevitably not
have enough time to do it right; 2) Data get more complicated and less
consistent; 3) The problems aren't going to be fixed. As a result,
methods/systems need to be engineered accordingly. This makes our job hard,
but that's employment security for us as that's where we contribute value to
the equation.


> can you give a practical example? I can see embedding an id somewhere in a
> digital file, and then creating a link to it as part of the indexing
> process, but what about external content that we have no control over... yet
> are expected to reference in a consistent way?
>


> As you observe, reality is messy. With regards to externally referenced
content, the options are limited. Ideally, the provider embeds their own
identifier either because they just do it, or they were convinced of the
value of doing so.

>
The reason I favor not being too prescriptive of syntax is that identifiers
are insanely useful and if you ask people to do anything they don't
understand or want to mess with, you'll inevitably find they ignore you
because they have too many other things to worry about. For maximum
compliance, barriers need to be low as possible.

>
But to get back to the example, let's suppose they don't provide any kind of
identifier no matter how much you bug them. Guess what the resolution
service provider's chances are of being informed if they move all the
content or even worse, change the system that serves the content?

>
Has anyone thought through, or put into practice, using Apache mod_rewrite
> tables for this simple "redirect one URL to another" use case?
>

Unless the URLs being directed to can be predicted from the source URLs (an
assumption that is only safe in certain types of closed systems), this is
just a different type of resolution service that suffers from all the same
issues as purls and handles.

To summarize this long email into a single sentence, you'll notice the ideas
that work the best and prove the most adaptable in the long run are simple
and compelling.

>
kyle

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 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
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