This HTML5 document contains 35 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Subject Item

n13:this

foaf:made

n2:ODSSemanticPingback

Subject Item

n7:item

n6:services_of

n2:ODSSemanticPingback

Subject Item

n21:this

sioc:creator_of

n2:ODSSemanticPingback

Subject Item

n2:ODSSemanticPingback

rdf:type

atom:Entry sioct:Comment

dcterms:created

2017-06-13T06:09:41.008078

dcterms:modified

2017-06-29T07:30:15.095769

rdfs:label

ODSSemanticPingback

foaf:maker

n13:this n17:this

dc:title

ODSSemanticPingback

opl:isDescribedUsing

n9:rdf

sioc:has_creator

n11:this n21:this

sioc:attachment

n14:png n16:png n18:png n20:png

sioc: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://&lt;cname&gt;[:&lt;port&gt;]/semping</nowiki></code> | parameters '<code>source</code>' and '<code>target</code>' (strings) as explained in the specification | | *REST* | <code><nowiki>http://&lt;cname&gt;[:&lt;port&gt;]/semping/rest?source=&lt;source uri&gt;&target=&lt;target uri&gt; </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]]

sioc:id

28ed7783d752dd484fcfc77adcdcc3e8

sioc:link

n2:ODSSemanticPingback

sioc:has_container

n4:ODS

n6:has_services

n7:item

atom:title

ODSSemanticPingback

sioc:links_to

n22:SemanticPingBack n23:Pingback

atom:source

n4:ODS

atom:author

n13:this

atom:published

2017-06-13T06:09:41Z

atom:updated

2017-06-29T07:30:15Z

sioc:topic

n4:ODS

Subject Item

n4:ODS

sioc:container_of

n2:ODSSemanticPingback

atom:entry

n2:ODSSemanticPingback

atom:contains

n2:ODSSemanticPingback

Subject Item

n11:this

sioc:creator_of

n2:ODSSemanticPingback