Re: FRBR WEMI and identifiers

From: Alexander Johannesen <alexander.johannesen_at_nyob>
Date: Mon, 16 Nov 2009 15:11:21 +1100
To: NGC4LIB_at_LISTSERV.ND.EDU
On Mon, Nov 16, 2009 at 14:52, Ed Summers <ehs_at_pobox.com> wrote:
> Perhaps I wasn't very clear.

No, no, you were clear enough. I was just offering methods within the
HTTP headers which talks about origins of requests (I suppose the
proxy directives also might indirectly have some), but also pointing
out that anything in the HTTP header is easily spoofed if you're
looking for *reliable* data.

> People are speculating about id.loc.gov not being used very
> much, but really it's just some people on a discussion list talking
> about what they *think* is going on.

Sure. My own two Bob's worth is that it is too little to late, and
also that LCSH in all its glory itself is a complicated scheme that it
would take mostly librarians to love and use, and hence others out
there couldn't care too much about it. (You spoke of the NRK use case
of which I have insider information that suggests that LCSH isn't
suitable, mostly by virtue of being poorly and too slowly maintained
as a Norwegian subset).

In fact, let's venture out on a controversy limb; what good is LCSH
for, apart from being part of a huge body of mostly books? What can
modern systems gain from adopting LCSH in as their classification
platform?

>The Linked Data folks have their high level view of what they think is
> going on too [http://richard.cyganiak.de/2007/10/lod/] ...

Which is a manually maintained graph of major players only. :) No,
it's an actually rather interesting question you bring up; who is
going to use it, and could or should we try to figure out how? Does it
matter that there's a low number of players with high hit-rates as
opposed to many players with fewer hits each? Is there a difference
between them in turns of value?

> but ideally
> there would be a way for Linked Data publishers to look in their web
> server logs and gather some sort of idea of how their stuff is being
> referenced in other people's data.

We all do this, and we all know the dangers and pitfalls of thinking
we understand how to interpret server logs. It's an art wrapped in
mystery and smoke. :)


Regards,

Alex
-- 
 Project Wrangler, SOA, Information Alchemist, UX, RESTafarian, Topic Maps
--- http://shelter.nu/blog/ ----------------------------------------------
------------------ http://www.google.com/profiles/alexander.johannesen ---
Received on Sun Nov 15 2009 - 23:13:06 EST