AKSW Semantic Pingback Service

Adding a social dimension to the Linked Data Web.

The Semantic Pingback mechanism is an extension of the well-known Pingback method, a technological cornerstone of the blogosphere, thus supporting the interlinking within the Data Web.

This Standalone Semantic Pingback Service can be used to pingback-enable Semantic Web (and other) resources.

How to test Semantic Pingback / send a pingback?

You can ping this service by adding a HTML link to this service to one of your resources and start the pingback manually by using this web-pingback client.

In addition to this, you can type the source and target resource URLs directly into these input fields:

(source resource, e.g. your WebID)
(target resource, e.g. your new friends WebID)
(optional comment)

Note: This standalone pingback server does not modify any resource. Instead of this, it tries to identify a mail address which is associated to the target resource and sends an email to this address, informing the owner about the pingback request.

Currently, the following properties are used for this:

Here is a list of the last 10 Pingbacks to http://pingback.aksw.org/. links_to predicates typically indicate a HTML-link while every other predicate is from an RDF resource or RDFa encoded in a webpage.

How to use it with your resources / receive a pingback?

In order to use this service for one of your resources (e.g. your WebID) you can propagate the use of the AKSW Semantic Pingback service in two ways:

  • Return a X-Pingback: http://pingback.aksw.org/ HTTP header field, when your resource is requested. This solution is downward compatible with the conventional Pingback mechanism, since this method is part of the autodiscovery process. On a apache webserver, you could create a .htaccess file with the following code: Header set X-Pingback "http://pingback.aksw.org/".
  • Embed a pingback:service or pingback:to statement into your FOAF profile, that links your WebID with the URL of the service (see example below). This solution only works with Semantic Pingback clients, since this autodiscovery mechanism is not included in the original Pingback specification. pingback:service links to a traditional Pingback 1.0 Server, while pingback:to links to a server which accepts a simplified pingback request (this Pingback server can accept both).