add BibSonomy to the linked open data cloud (was/motivation: implement a pingback service for URLs/publications posted to BibSonomy)

[Robert Jäschke]

See here http://www.bibsonomy.org/bibtex/20e32b9750ee77fcdf2162f70aaee5622/jaeschke and here http://aksw.org/Projects/SemanticPingBack for details.

The idea is that everytime a URL/publication is posted to BibSonomy, the source (in case of URLs the originating server) gets a "ping" that the resource has been posted to BibSonomy. This is often done in blogs, where then a comment is added that the blog entry has been mentioned elsewhere (in that case in BibSonomy).

The paper describes a new (semantic) mechanism to do this - we should check, what the currently most supported mechanisms are.

[Robert Jäschke]

Hi all,

in the last weeks, we have analyzed which data sources in the new version of the LOD cloud comply to various best practices that are recommended by W3C or have emerged within the LOD community.

We have checked the implementation of the following nine best practices:

1. Provide dereferencable URIs 2. Set RDF links pointing at other data sources 3. Use terms from widely deployed vocabularies 4. Make proprietary vocabulary terms dereferencable 5. Map proprietary vocabulary terms to other vocabularies 6. Provide provenance metadata 7. Provide licensing metadata 8. Provide data-set-level metadata 9. Refer to additional access methods

The compliance with the best practices was either checked manually or by using scripts that downloaded and analyzed some data from the data sources. We have added the results of the evaluation in the form of tags to the LOD data set catalog on CKAN [1].

We are now happy to release the first statistics about the structure of the LOD could as well as the compliance of the datasets with the best practices. The statistics can be found here:

http://www4.wiwiss.fu-berlin.de/lodcloud/state/

The document contains an initial, preliminary release of the statistics. If you spot any errors in the data describing the LOD data sets on CKAN, it would be great if you would correct them directly on CKAN.

For information on how to describe datasets on CKAN please refer to the Guidelines for Collecting Metadata on Linked Datasets in CKAN [2].

After your feedback and corrections, we will then move the corrected version of the statistics to http://www.lod-cloud.net/ (around October 24th).

Have fun with the statistics and the encouraging as well as disappointing insights that they provide.

Cheers,

Chris Bizer, Anja Jentzsch and Richard Cyganiak

[1] http://www.ckan.net/group/lodcloud [2] http://esw.w3.org/TaskForces/CommunityProjects/LinkingOpenData/DataSets/CKANmetainformation

[Robert Jäschke]

OK,

We must think about how we can redirect requests to /user also to /foaf/user ... typically, we will return /pubrss/ or so ... it's really tricky. :-(

[Robert Jäschke]

The really tricky thing is, that in principle, we have three pages we could return on a "acceept: RDF" request to /user/USER:

1) /burst/user/USER 2) /foaf/user/USER 3) /rss/user/USER

Thus, one goal must be to unify this. I can imagine the following solution:

1) include links to the users posts in /foaf/user/USER 2) return a redirect to /foaf/user/USER on requesting RDF on /user/USER 3) semantic pingback always returns links to the resource, i.e., /bibtex/HASH/USER or /url/HASH/USER

4) /burst and /rss contain links to /user/USER ... such that we can get something to know about the user.