{"id":756,"date":"2006-11-28T15:04:36","date_gmt":"2006-11-28T19:04:36","guid":{"rendered":""},"modified":"2006-11-28T15:04:36","modified_gmt":"2006-11-28T19:04:36","slug":"ping_the_semantic_web_a_new_pings_export","status":"publish","type":"post","link":"https:\/\/fgiasson.com\/blog\/index.php\/2006\/11\/28\/ping_the_semantic_web_a_new_pings_export\/","title":{"rendered":"Ping the Semantic Web: a new pings exportation feature"},"content":{"rendered":"

 <\/p>\n\n\n
\n \"\"<\/a>   \n <\/td>\n\nThe “pings exportation” feature<\/a> of Ping the Semantic Web<\/a> 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).<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

 <\/p>\n

The new way to request pings<\/strong><\/p>\n

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.<\/p>\n

There are 7 different constraints you can apply:<\/p>\n

    \n
  1. Constraint pings for a specific type of RDF document: SIOC, FOAF, DOAP, RDFS or OWL<\/li>\n
  2. Constraint pings for a specific serialization language: XML or N3<\/li>\n
  3. Constraint pings for a time frame: last hour, yesterday or any time<\/li>\n
  4. Constraint pings with a number of results: 0 to x<\/li>\n
  5. Constraint pings for a specific domain name, example: getting all the pings from www.talkdigger.com<\/li>\n
  6. Constraint pings for a specific namespace, example: getting all the pings where the namespace “http:\/\/purl.org\/dc\/elements\/1.1\/<\/li>\n<\/ol>\n

    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.<\/p>\n

     <\/p>\n

    The new way to handle namespaces<\/strong><\/p>\n

    Reworking this feature leaded me to rework the way Ping the Semantic Web was handling namespaces.<\/p>\n

    Now all the namespaces of the RDF documents aggregated by the service are aggregated by the service as well.<\/p>\n

    This means two things:<\/p>\n

      \n
    1. You can get RDF documents defining a specialized namespace<\/li>\n
    2. You can take a look at the list of namespaces know by Ping the Semantic Web<\/a><\/li>\n<\/ol>\n

      For the moment the service know about 400 namespaces, but it is discovering them at a rapid pace.<\/p>\n

       <\/p>\n

      Conclusion<\/strong><\/p>\n

      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.<\/p>\n

      Technorati: Pingthesemanticweb<\/a> | ping<\/a> | semantic<\/a> | web<\/a> | rdf<\/a> | export<\/a> | service<\/a> | web3.0<\/a> | <\/font><\/p>\n","protected":false},"excerpt":{"rendered":"

            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 […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[69,84,64],"tags":[],"class_list":["post-756","post","type-post","status-publish","format-standard","hentry","category-pingthesemanticweb","category-semantic-web","category-web"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/fgiasson.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/756","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fgiasson.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fgiasson.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fgiasson.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/fgiasson.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=756"}],"version-history":[{"count":0,"href":"https:\/\/fgiasson.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/756\/revisions"}],"wp:attachment":[{"href":"https:\/\/fgiasson.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=756"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fgiasson.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=756"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fgiasson.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=756"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}