finally a bnode with a uri

Posts tagged with: rdfer

Got some SemWeb DOAP 'n' FOAF?

Starting to collect RDF descriptions of SemWeb projects at rdfer.com
All baby steps, but I've activated a DOAP editor, an RDF/XML loader, and a basic browser store dump at RDFer.com. Would be great to get some DOAP files describing SemWeb projects in there, and maybe some FOAF files as well. That'd make coding the browsers more fun and a bit more real-world-ish.
Thanks for your help!

Term Shopping for Trackbacks and Projects

Describing trackbacks, and projects with basic vocabularies.
I already mentioned the nice HTTP vocab I'm using to describe page views in RDF. I had to add some custom properties to cover things like visits and access hosts, but the main part of the statistics module is built on top of the W3C vocab. The more I work with RDF, the less I feel comfortable with homegrown terms (although they can be handy for prototyping) and thus spend quite some time on the vocabulary market. Here are two other use cases I was gladly able to model with existing vocabs.

Trackbacks

I wanted to add support for incoming trackbacks to SemSol's blog module. Trackbacks consist of 4 parameters:
  • title (title of the remote post)
  • excerpt (excerpt of the remote post)
  • url (permalink of the remote post)
  • blog_name (name of the remote blog)
Additional local information:
  • date/time of the trackback (i.e. now)
  • permalink of the local post (derived from the trackback URL)
After a fruitful IRC chat with John "SIOC" Breslin, I'm now using (something similar to) the following code:
<$url> a rss:item ;
       an:annotates <$permalink> ;
       dc:title "$title" ;
       dc:description "$excerpt" ;
       dc:date "$now" ;
       dc:source [ dc:title "$blog_name"] .
I could have used rss:description instead of Dublin Core's but thought the structure could more easily be extended to local comments this way. Anyway, as you can see, trackbacks can nicely be described with DC, Annotea, and RSS 1.0.

Projects, Tools, Applications

The second use case comes from RDFer.com where I'd like to make some of the project and tools data collected during 2005 available. Additionally, I want to provide easy editing forms to let members describe and annotate RDF software. For SemanticWeb.org, we invented an swo:Application class to separate (developer) tools from (end-user) apps. But while analyzing the dataset, I saw that there are additional resource types which fit under the generic "project" concept, e.g. lists or data dumps. I was already in the middle of making up a whole bunch of classes when I remembered an earlier DCMI discussion about the negligible difference between dc:type and rdf:type which referred to DCMI Type definitions. Long story short, DC Types (dctype) combined with FOAF (foaf), DOAP (doap), and the DAML Tool vocab (tool) can be used to describe a whole range of resources:
  • general projects (foaf:Project)
  • software projects (doap:Project, which covers non-OS software as well)
  • resource collections (dctype:Collection, dctype:Dataset)
  • software products (dctype:Software or dctype:InteractiveResource, these could be used to e.g. attach tool:price properties which would perhaps look a bit odd on projects)
  • tools (tool:Tool)
  • online services (dctype:Service)
Something like dct:isPartOf could perhaps even be used to model sub-projects, but I'm not 100% sure.

Bottom line, again: no need for new terms, it's (often) all there already.

Official Start of the RDFer.com Project

RDFer.com announcement.
The community project idea I mentioned last week has a name: RDFer.com. The site is already public, content and features will be added step by step now. If there is anything you'd like to see at the RDFer site, I'd be happy about feature requests via comments in the announcement post over there.
RDFer.com

SemSol Site launched

Basic description and some screenshots.
I've put up a little preview site for the SemSol framework today. Not much yet, just a basic description and some screenshots. A first public release is planned for Q1/2007, I'd like to test it with some other projects first.

Speaking of projects: you may have noticed that my 10/2006 re-re-launch version of the SemanticWeb.org site has been removed (if you noticed the relaunch at all), DERI is going to put more internal resources on the portal from now on. Although it would have been a great stress-test project, I have to admit that using already mature tools like Wordpress, Mediawiki, and Drupal reduces risks on their side and also frees a lot of resources here. The new site is going to get a conceptual change, but I'll try to make the already aggregated and manually created data available via some other community project. The new site I plan to test SemSol with is going to be a Semantic Social Networking Service which will also provide some editorial content (my personal little non-W3C SWEO initiative). The SNS will of course be RDF-based, so there is still a back-integration option for semanticweb.org, should it get a SPARQL upgrade at some later stage.

Archives/Search

YYYY or YYYY/MM
No Posts found

Feeds