The “pings exportation” feature of Ping the Semantic Web was a little bit messy and I was really not satisfied with it. So I took the time to re-work it and I think I came up with something much better (probably something that people were expecting from the beginning).


The new way to request pings

The new way to request a list of pings from Ping the Semantic Web is quite simple. You have a set of pings (all pings received by the service so far) and you apply constraints on that set to get the subset of pings you really want for your application.

There are 7 different constraints you can apply:

  1. Constraint pings for a specific type of RDF document: SIOC, FOAF, DOAP, RDFS or OWL
  2. Constraint pings for a specific serialization language: XML or N3
  3. Constraint pings for a time frame: last hour, yesterday or any time
  4. Constraint pings with a number of results: 0 to x
  5. Constraint pings for a specific domain name, example: getting all the pings from
  6. Constraint pings for a specific namespace, example: getting all the pings where the namespace “

This new method is much more powerful. That way you can easily get a specific subset of pings for the specialized needs of your web services or software agent.


The new way to handle namespaces

Reworking this feature leaded me to rework the way Ping the Semantic Web was handling namespaces.

Now all the namespaces of the RDF documents aggregated by the service are aggregated by the service as well.

This means two things:

  1. You can get RDF documents defining a specialized namespace
  2. You can take a look at the list of namespaces know by Ping the Semantic Web

For the moment the service know about 400 namespaces, but it is discovering them at a rapid pace.



I am stabilizing the system right now and the redevelopment of this feature was resulting from that stabilization. All my updates are mostly finished and soon enough a first version of a SPARQL endpoint (and user interface) should be publicly available.

Technorati: | | | | | | | |

Leave a Reply

Your email address will not be published. Required fields are marked *