On Wed, Apr 1, 2009 at 6:14 AM, Mike Taylor m...@indexdata.com wrote:
As usual, an ounce of example is worth a ton of exposition, so:
Suppose I always keep a PDF of my latest paper at
http://www.miketaylor.org.uk/latest.pdf
for the benefit of people who want to keep an eye on my
On Wed, Apr 1, 2009 at 8:37 AM, Mike Taylor m...@indexdata.com wrote:
Worse, consider how the actionable-identifier approach would translate
to other non-actionable identifiers like ISBNs. If I offer the
non-actionable identifier
info:isbn/025490
which identified Farlow and
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Mike Taylor
Sent: Wednesday, April 01, 2009 8:38 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] registering info: uris?
Ross Singer writes:
I suppose my point is, there's a valid case for identifiers like
On Wed, 2009-04-01 at 14:17 +0100, Mike Taylor wrote:
Ed Summers writes:
Assuming a world where you cannot de-reference this DOI what is it
good for?
It wouldn't be good for much if you couldn't dereference it at all.
The point is that (I argue) the identifier shouldn't tie itself to a
Houghton,Andrew writes:
The point is that (I argue) the identifier shouldn't tie itself
to a particular dereferencing mechanism (such as dx.doi.org, or
amazon.com) but should be dereferenced by software that knows
what's the most appropriate dereferencing mechanism _for you_ in
your
I'll bite.
There are actually a number of http URLs that work like
http://dx.doi.org/10./j.1475-4983.2007.00728.x
One of them is http://doi.wiley.com/10./j.1475-4983.2007.00728.x
Another is run by crossref; Some OpenURL ink servers also have doi
proxy capability.
So for code to
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Mike Taylor
Sent: Wednesday, April 01, 2009 9:35 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] registering info: uris?
Houghton,Andrew writes:
So creating an info URI for it is meaningless, it's just
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Eric Hellman
Sent: Wednesday, April 01, 2009 9:51 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] registering info: uris?
There are actually a number of http URLs that work like
Houghton,Andrew writes:
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Eric Hellman
Sent: Wednesday, April 01, 2009 9:51 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] registering info: uris?
There are actually a number of http URLs that work
Houghton,Andrew wrote:
Lets separate your argument into two pieces. Identification and
resolution. The DOI is the identifier and it inherently doesn't
tie itself to any resolution mechanism. So creating an info URI
for it is meaningless, it's just another alias for the DOI. I
can create an
+1
Jon Stroop
Metadata Analyst
C-17-D2 Firestone Library
Princeton University
Princeton, NJ 08544
Email: jstr...@princeton.edu
Phone: (609)258-0059
Fax: (609)258-0441
http://diglib.princeton.edu
http://diglib.princeton.edu/ead
Edward M. Corrado wrote:
I disagree. Keep this going. A delete
I admit that httprange-14 still confuses me. (I have no idea why it's
called httprange-14 for one thing).
But how do you identify the URI as being a Real World Object? I don't
understand what it entails.
And http://doi.org/*; describes it's own type only to software that
knows what a URI
On Wed, Apr 1, 2009 at 11:37 AM, Jonathan Rochkind rochk...@jhu.edu wrote:
I admit that httprange-14 still confuses me. (I have no idea why it's
called httprange-14 for one thing).
http://www.w3.org/2001/tag/group/track/issues/14
Some background:
From: Houghton,Andrew hough...@oclc.org
The point being that:
urn:doi:*
info:doi:*
provide no advantages over:
http://doi.org/*
I think they do.
I realize this is pretty much a dead-end debate as everyone has dug
themselves into a position and nobody is going to change their mind. It is
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Mike Taylor
Sent: Wednesday, April 01, 2009 10:17 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] registering info: uris?
Houghton,Andrew writes:
Again we have moved the discussion to a specific resolution
I completely disagree. There are all sorts of useful identifiers I use
in my work every day that can not be automatically dereferenced.
Jonathan
Ed Summers wrote:
On Wed, Apr 1, 2009 at 9:17 AM, Mike Taylor m...@indexdata.com wrote:
It wouldn't be good for much if you couldn't
On Wed, Apr 1, 2009 at 12:22 PM, Karen Coyle li...@kcoyle.net wrote:
But shouldn't we be able to know the difference between an identifier and a
locator? Isn't that the problem here? That you don't know which it is if it
starts with http://.
But you do if it starts with http://dx.doi.org
I
From: Jonathan Rochkind rochk...@jhu.edu
There are all sorts of useful identifiers I use in my work every day that
can not be automatically dereferenced.
Even more to the point: there is no sound definition of dereference. To
dereference a resource means to retrieve a representation of it.
A concrete example.
The MODS schema, version 3.3, has an info identifier, for SRU purposes:
info:srw/schema/1/mods-v3.3
So in an SRU request you can say
recordSchema=info:srw/schema/1/mods-v3.3
Meaning you want records returned in the mods version 3.3 schema. And
that's really the purpose
Ross Singer wrote:
On Wed, Apr 1, 2009 at 12:22 PM, Karen Coyle li...@kcoyle.net wrote:
But shouldn't we be able to know the difference between an identifier and a
locator? Isn't that the problem here? That you don't know which it is if it
starts with http://.
But you do if it starts
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Karen Coyle
Sent: Wednesday, April 01, 2009 1:06 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] resolution and identification (was Re:
[CODE4LIB] registering info: uris?)
The general convention is that
Houghton,Andrew wrote:
Organization need to have a clear understanding of what they are minting
URIs for.
Precisely. And in the real world... they don't always have that. Neither
the minters nor the users of URIs, especially the users of http URIs,
where you can find so many potential
On Wed, Apr 1, 2009 at 12:28 PM, Ray Denenberg, Library of Congress
r...@loc.gov wrote:
Even more to the point: there is no sound definition of dereference. To
dereference a resource means to retrieve a representation of it. There has
never been any agreement within the w3c of what constitutes
My point is that I don't see how they're different in practice.
And one of them actually allowed you to do something from your email client.
-Ross.
On Wed, Apr 1, 2009 at 1:20 PM, Karen Coyle li...@kcoyle.net wrote:
Ross, I don't get your point. My point was about the confusion between two
At Wed, 1 Apr 2009 14:34:45 +0100,
Mike Taylor wrote:
Not quite. Embedding a DOI in an info URI (or a URN) means that the
identifier describes its own type. If you just get the naked string
10./j.1475-4983.2007.00728.x
passed to you, say as an rft_id in an OpenURL, then you can't
I'm not neccesarily arguing anything. I think either way _could_ work,
or _could_ end up not working as well as the other one.
I think that it's harder for someone to mint an info uri without knowing
what they are doing. If a uri is in the info registry, you know someone
at least had to think
26 matches
Mail list logo
