W3C home > Mailing lists > Public > public-lod@w3.org > October 2010

Re: Concordance, Reconciliation, and shared identifiers

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Fri, 22 Oct 2010 16:01:04 -0400
Message-ID: <4CC1ED80.9020007@openlinksw.com>
To: Leigh Dodds <leigh.dodds@talis.com>
CC: Linking Open Data <public-lod@w3.org>
On 10/22/10 11:47 AM, Leigh Dodds wrote:
> Hi,
>
> The announcement of that the Guardian has begun cataloguing other
> identifiers (e.g. ISBN, Musicbrainz) within its API [1] is a nice
> illustration that the importance of cross-linking between datasets is
> starting to become more generally accepted. Setting aside the debate
> about what constitutes "linked data", I think its important that this
> community tracks these various initiatives to help explore the
> trade-offs between different approaches, as well as to build bridges
> with the wider developer community.
>
> A great project would be for someone to produce a Linked Data wrapper
> for the Guardian API, that allows linking *in* to their data, based on
> ISBNs and MusicBrainz ids. Its on my TODO list, but then so is a lot
> of other stuff ;)

We've had sponger meta cartridges [1] for the Guardian API since its 
early incarnations.

Anyone that uses URIBurner [2] ends up with a look-up pass through 
Guardians API (amongst a boat load of others) en route to the final 
URIBurner generated Linked Data graph. URIBurner then pings PTSW which 
ultimately leads to data in the LOD Cloud Cache we maintain.

Sindice also does URIBurner lookups, and URIBurner also looks up Sindice 
(sames.org  etc..) .

End result, dynamic Web of Linked Data. We stopped counting its size in 
2007 :-)

Of course, others too should make wrappers for these APIs so that their 
perspectives are expressed in the burgeoning Web of Linked Data etc..


> If we look back a few months we can see signs of the importance of
> cross-linking appearing in other projects. Google Refine (nee Freebase
> Gridworks) has the notion of a "reconcilication service" that is used
> to build and set links [2]. Yahoo meanwhile have their "concordance"
> service [3, 4] which is basically a sameAs.org service for building
> cross-links between geo data.
>
> Again, it would be interesting to build bridges between different
> communities by showing how one can achieve the same effects with
> Linked Data, as well as integrating Linked Data into those services by
> providing gateways services, e.g. implementing the same API but backed
> by RDF. This is what I did for the Gridworks, but the same could be
> extended to other services.

On our part, we've been doing so since Linked Data inception, and will 
continue to do so :-)

Links:

1. http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtSponger -- 
Sponger
2. http://uriburner.com -- Virtuoso Sponger Service .

> Cheers,
>
> L.
>
> [1]. http://www.guardian.co.uk/open-platform/blog/linked-data-open-platform
> [2]. http://www.ldodds.com/blog/2010/08/gridworks-reconciliation-api-implementation/
> [3]. http://blog.programmableweb.com/2010/04/05/yahoos-new-geo-concordance-a-geographic-rosetta-stone/
> [4]. http://developer.yahoo.com/geo/geoplanet/guide/api-reference.html#api-concordance
>


-- 

Regards,

Kingsley Idehen	
President&  CEO
OpenLink Software
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen
Received on Friday, 22 October 2010 20:01:32 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:29 UTC