Hi Paul, Is it possible to add the /id/NNNNNN URI to the document that is returned for those URIs, as the links to related items all go to /id/NNNNN but the resolved RDF documents do not contain that URI.
For example, <http://linkeddata.few.vu.nl/slideshare/mhelmke/presentation-zen> contains information about (should map the resolution URI to this URI in RDF) <http://www.slideshare.net/mhelmke/presentation-zen> which contains a link to <http://linkeddata.few.vu.nl/slideshare/id/1478896> , which should be linked to (need this statement in RDF) <http://www.slideshare.net/guestc555bbe/business-presentation-wireless-powerpoint-2003-version> Cheers, Peter On 8 June 2010 04:18, Paul Groth <pgr...@gmail.com> wrote: > Hi All, > > I've wrapped the Slideshare.net API to expose it as RDF. You can find a blog > post about the service at [1] and the service itself at [2]. An interesting > bit is how we deal with Slideshare's API limits by letting you use your own > API key. > > It's still needs to be properly linked (i.e. point to other resources on the > WoD) but we're working on it. > > [1] http://thinklinks.wordpress.com/2010/06/07/linking-slideshare-data/ > [2] http://linkeddata.few.vu.nl/slideshare/ > > > Let me know what you think, > > Thanks, > Paul > > > > > -- > Dr. Paul Groth (pgr...@few.vu.nl) > http://www.few.vu.nl/~pgroth/ > Postdoc > Knowledge Representation & Reasoning Group > Artificial Intelligence Section > Department of Computer Science > VU University Amsterdam > >
