| Attributes | Values |
|---|
| type
| |
| Date Created
| |
| Date Modified
| |
| label
| |
| seeAlso
| |
| maker
| |
| Title
| |
| isDescribedUsing
| |
| has creator
| |
| attachment
| |
| content
| - ---+ Usage Guide for Semantic Pingback in ODS
%TOC%
---++ What is Semantic Pingback?
[[http://aksw.org/Projects/SemanticPingBack][Semantic Pingback]] is a mechanism through which data space owners receive notification, in the form of triple statements, when external sources (typically other data spaces) make references to their data spaces. This mechanism is basically an adaptation of the blog [[http://dbpedia.org/page/Pingback][pingback]], with payloads now taking the form of RDF-based structured data resources.
For instance, the owner of <nop>DataSpaceA might assert that they know the owner of <nop>DataSpaceB via a local <code>foaf:knows</code> assertion --
<verbatim>
{ DataSpaceA:owner foaf:knows DataSpaceB:owner }
</verbatim>
Depending on data space settings, the owner of <nop>DataSpaceB might then receive an email notice of the <code>foaf:knows</code> assertion, or <nop>DataSpaceA might use the notification to automatically generate a local reciprocal assertion.
<verbatim>
{ DataSpaceB:owner foaf:knows DataSpaceA:owner }
</verbatim>
The Semantic Pingback functionality in ODS supports operation in both client and server modes.
---++ Semantic Pingback Endpoints in ODS
| *XML-RPC* | <code><nowiki>http://<cname>[:<port>]/semping</nowiki></code> | parameters '<code>source</code>' and '<code>target</code>' (strings) as explained in the specification |
| *REST* | <code><nowiki>http://<cname>[:<port>]/semping/rest?source=<source uri>&target=<target uri> </nowiki></code> | parameters are as with XML-RPC, but payloads are delivered using HTTP <code>POST</code> or <code>GET</code> operations. |
---++ Semantic Pingback Setup in ODS
This scenario assumes two ODS instances, where one is the <i>Ping Receiver</i> and the other is the <i>Ping Sender</i>.
---+++ Configuring the Ping Receiver
1 The ODS data space owner designates data space applications for which ping notification will be enabled through the *Application Settings* menu *Semantic Pingback Setup* option.
1 The data space owner must choose what will happen upon ping notification: email; automatic generation of reciprocal data (i.e., triple-based data generation); or both:
%BR%%BR%<img src="%ATTACHURLPATH%/step2.png" style="wikiautogen"/>%BR%%BR%
---+++ Actions to take on the Ping Sender
1 Go to a ping-enabled ODS data space application. For example, the *Profile Manager and Editor* includes an *Annotations* tab, which offers a UI for making arbitrary assertions about anything with triples-based statements.
1 Make a simple Annotation claiming to know the owner of the Ping Receiver instance configured above, with a <code>foaf:knows</code> relation targeting the <nop>WebID of the Ping Receiver instance owner.
1 Tick the *Issue Semantic Pingback* checkbox.
1 Click the *Add* button to complete the pingback enabled annotation.
%BR%%BR%<img src="%ATTACHURLPATH%/step3.png" style="wikiautogen"/>%BR%%BR%
---+++ Actions to take on the Ping Receiver
1 Go to your ODS Profile Page, or simply load your <nop>WebID into the Address Bar of any HTTP compliant browser.
1 Observe the addition of the new <code>foaf:knows</code> relation posted by the Ping Sender.
%BR%%BR%<img src="%ATTACHURLPATH%/step4.png" style="wikiautogen"/>%BR%%BR%
1 If the email option was enabled, you will also receive an email indicating that you are the "Object" of a <code>foaf:knows</code> relation asserted by the Ping Sender.
---++ Security of Ping Notifications
The access control feature of Virtuoso (your ODS host environment) may be used to add an ACL named '<nop>SemanticPingback' via the Conductor admin interface. A variety of controls may be set there, as depicted below:
%BR%%BR%<img src="%ATTACHURLPATH%/semping_acl.png" style="wikiautogen"/>%BR%%BR%
---++Related
* [[OdsConfig][Installing and Configuring ODS]]
|
| id
| - 28ed7783d752dd484fcfc77adcdcc3e8
|
| link
| |
| has container
| |
| http://rdfs.org/si...ices#has_services
| |
| atom:title
| |
| links to
| |
| atom:source
| |
| atom:author
| |
| atom:published
| |
| atom:updated
| |
| topic
| |
| is made
of | |
| is container of
of | |
| is link
of | |
| is http://rdfs.org/si...vices#services_of
of | |
| is creator of
of | |
| is atom:entry
of | |
| is atom:contains
of | |
![[RDF Data]](/fct/images/sw-rdf-blue.png)
![[cxml]](/fct/images/cxml_doc.png)
![[csv]](/fct/images/csv_doc.png)
![[text]](/fct/images/ntriples_doc.png)
![[turtle]](/fct/images/n3turtle_doc.png)
![[ld+json]](/fct/images/jsonld_doc.png)
![[rdf+json]](/fct/images/json_doc.png)
![[rdf+xml]](/fct/images/xml_doc.png)
![[atom+xml]](/fct/images/atom_doc.png)
![[html]](/fct/images/html_doc.png)