Isn't there always a single point of failure if you are expecting to be
able to resolve an http URI via the HTTP protocol?
Whether it's purl.org or not, there's always a single point of failure
on a given http URI that you expect to resolve via HTTP, the entity
operating the web server at the
At Thu, 2 Apr 2009 11:34:12 -0400,
Jonathan Rochkind wrote:
[…]
I think too much of this conversation is about people's ideal vision of
how things _could_ work, rather than trying to make things work as best
as we can in the _actual world we live in_, _as well as_ planning for
the future
I keep telling myself I'm going to stop posting on this thread, but ...
Erik Hetzner writes:
Could somebody explain to me the way in which this identifier:
http://suphoa5d.org/phae4ohg
does not work *as an identifier*, absent any way of getting
information about the referent, in a
Erik Hetzner writes:
Could somebody explain to me the way in which this identifier:
http://suphoa5d.org/phae4ohg
does not work *as an identifier*, absent any way of getting
information about the referent, in a way that:
info:doi/10.10.1126/science.298.5598.1569
does work?
A quick
On Fri, Apr 3, 2009 at 10:44, Mike Taylor m...@indexdata.com wrote:
Going back to someone's point about living in the real
world (sorry, I forget who), the Inconvenient Truth is that 90% of
programs and 99% of users, on seeing an http: URL, will try to treat
it as a link. They don't know any
Mike Taylor wrote:
Going back to someone's point about living in the real
world (sorry, I forget who), the Inconvenient Truth is that 90% of
programs and 99% of users, on seeing an http: URL, will try to treat
it as a link. They don't know any better.
And they can't know any better because
