AKSW - Projects/SemanticPingBack

2010-04-20 22:05:06

Comparison for /Projects / Semantic Ping Back of 2010-04-20 22:05:06 and 2010-04-24 17:24:39

Additions:

To distinguish these two request methods, the pingback vocabulary defines two different object properties: pingback:service (XML/RPC) and pingback:to (Simplified Post Request). Both properties can be used to link a pingback target resource with its pingback server.

Deletions:

2010-03-09 12:42:21

Comparison for /Projects / Semantic Ping Back of 2010-03-09 12:42:21 and 2010-04-20 22:05:06

Additions:

XML/RPC vs. Simplified Post Request

While the Pingback 1.0 specification defines a XML/RPC call for request a pingback on a Pingback Server, we discussed a simplified request representation using only HTTP-post attributes.
The simplified pingback post request has two obligatory and one optional post parameter:

source is the source resource URI (obligatory)
target is the target resource URI (obligatory)
comment is an optional comment for the pingback request given by the source owner or the source owners application.

2010-03-09 11:54:56

Comparison for /Projects / Semantic Ping Back of 2010-03-09 11:54:56 and 2010-03-09 12:42:21

Additions:

A prototype of a standalone Semantic Pingback server is available for download here.

Deletions:

A prototype of a standalone Semantic Pingback server is available for download here.

2010-03-05 14:03:08

Comparison for /Projects / Semantic Ping Back of 2010-03-05 14:03:08 and 2010-03-09 11:54:56

Additions:

Embed a http://purl.org/net/pingback/service statement into your FOAF profile, that links your Web ID 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.

Deletions:

Embed a http://purl.net/pingback/service statement into your FOAF profile, that links your Web ID 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.

2010-03-04 10:46:18

Comparison for /Projects / Semantic Ping Back of 2010-03-04 10:46:18 and 2010-03-05 14:03:08

Additions:

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/".

Deletions:

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.

2010-03-01 16:00:00

Comparison for /Projects / Semantic Ping Back of 2010-03-01 16:00:00 and 2010-03-04 10:46:18

Additions:

Semantic Pingback tackles the quality, timeliness and coherence as well as direct end user benefits of the emerging Linked Data Web. Semantic Pingback extends the well-known Pingback method, which is technological cornerstone of the blogosphere. It is based on the advertising of an RPC service for propagating typed RDF links between Data Web resources. It is downwards compatible with conventional Pingback implementations, thus allowing to connect and interlink resources on the Social Web with resources on the Data Web.

Deletions:

Semantic Pingback tackles the quality, timeliness and coherence as well as direct end user benefits of the emerging Linked Data Web. Semantic Pingback extends the well-known Pingback method, which is technological cornerstone of the blogosphere. It is based on the advertising of an RPC service for propagating typed RDF links between Data Web resources. It is is downwards compatible with conventional Pingback implementations, thus allowing to connect and interlink resources on the Social Web with resources on the Data Web.

2010-02-25 09:19:49

Comparison for /Projects / Semantic Ping Back of 2010-02-25 09:19:49 and 2010-03-01 16:00:00

Additions:

Semantic Pingback tackles the quality, timeliness and coherence as well as direct end user benefits of the emerging Linked Data Web. Semantic Pingback extends the well-known Pingback method, which is technological cornerstone of the blogosphere. It is based on the advertising of an RPC service for propagating typed RDF links between Data Web resources. It is is downwards compatible with conventional Pingback implementations, thus allowing to connect and interlink resources on the Social Web with resources on the Data Web.

Deletions:

Semantic Pingback tackles the quality, timeliness ans coherence as well as direct end user benefits of the emerging Linked Data Web. Semantic Pingback extends the well-known Pingback method, which is technological cornerstone of the blogosphere. It is based on the advertising of an RPC service for propagating typed RDF links between Data Web resources. It is is downwards compatible with conventional Pingback implementations, thus allowing to connect and interlink resources on the Social Web with resources on the Data Web.

2010-02-25 09:14:43

Comparison for /Projects / Semantic Ping Back of 2010-02-25 09:14:43 and 2010-02-25 09:19:49

Additions:

A linking resource (depicted in the upper left) links to another (Data) Web resource, here called linked resource. The linking resource can be either an conventional Web resource (e.g. wiki page, blog post) or a Linked Data resource. Links originating from Linked Data resources are always typed (based on the used property), links from conventional Web resources can be either untyped (i.e. plain HTML links) or typed (e.g. by means of RDFa annotations).
The Pingback client (lower left) is either integrated into the data/content management system or realized as a separate service, which observes changes of the Web resource.
Once the establishing of a link was noted, the Pingback client tries to autodiscover a Pingback server from the linked resource.
If the autodiscovery was successful, the respective Pingback RPC server is called, with the parameters linking resource (i.e. source) and linked resource (i.e. target).
In order to verify the retrieved request (and to obtain information about the type of the link in the semantic case), the Pingback server fetches (or dereferences) the linking resource.
Subsequently, the Pingback server can perform a number of actions, such as updating the linked resource (e.g. adding inverse links) or notifying the publisher of the linked resource (e.g. via email).

2010-02-24 23:34:35

Comparison for /Projects / Semantic Ping Back of 2010-02-24 23:34:35 and 2010-02-25 09:14:43

Additions:

If you do not want to provide a Pingback service on your own, you can use the AKSW Semantic Pingback Service. If a pingback-enabled client then detects the usage of your pingback-enabled resource, our service notifies you via email.

Deletions:

You can use the AKSW Semantic Pingback Service if, for example, you are not able to provide a Pingback service on your own. If a pingback-enabled client then detects the usage of your pingback-enabled resource, our service notifies you via email.