- From: Hugh Glaser <hugh@glasers.org>
- Date: Fri, 25 Jul 2014 20:02:20 +0100
- To: Linked Data community <public-lod@w3.org>
So sameAs.org never appears in any of this stuff. That’s deliberate. The whole idea of it is that it doesn’t add to the plethora of URIs by generating new ones. But it seems that people do find it useful - I get emails from people about it, especially when it does strange things :-) sameAs.org is a service that consumes LD URIs from other PLDs and delivers the answer as LD. So it is, in fact, a proper Linked Data site. So you can do the stuff you expect with a URI like http://www.sameas.org/?uri=http%3A%2F%2Fdbpedia.org%2Fresource%2FEdinburgh As you can see, this is not a Cool URI (I think), and as I said, I really don’t want people to think of this as the ID for a sameAs bundle, although in fact it is! So what should I do? Keep sameAs.org living outside the BTC and LOD Cloud world? Or change things so that it becomes a more normal part of the LOD world? In addition, I have quite a lot of other services that work over LD URIs to produce LD about the URI, but as with sameAs.org are also LD URIs because the service interface itself supports the LD model. Should these brought into the PR fold, and if so how? It would be very painful to allow these to be spidered, because they are heavy computations, and running the service over all the URIs that could be run would be many years of computation for my server. I suspect that others have similar services, so a policy might be useful. In fact, as LD becomes more mature (!), I think we are finding that it is more a communication mechanism between cooperating service than simply delivering RDF in response to an identifying URI - how do we capture this massive LD resource? I hope that makes some sort of sense. Best Hugh -- Hugh Glaser 20 Portchester Rise Eastleigh SO50 4QS Mobile: +44 75 9533 4155, Home: +44 23 8061 5652
Received on Friday, 25 July 2014 19:03:44 UTC