ok, this is rather trivial but good as a reminder for myself. Having the list of XMPP Publish-Subscribe Nodes noted down as in my scratch file figuring out what nodes I use is pretty easy with SPARQL:
just do a

SELECT ?nodeFROM <http://b4mad.net/R…

since all wordpress blogs have same or similar nomenclature/structure of pages, meaning divs and class names for entries, posts, comments, etc., isn’t it possible to extract necessary information from that data?

i doubt that many people will install this plugin any time soon, so if i want to make an application that searches and indexes rdf data from blogs, will I be able to do that without them having SIOC installed?

Bin gespannt, ob irgendeine Reaktion kommt.

Schöne Adventszeit noch

Hartmut

I didn’t include comments in the picture (which is already a bit overloaded), but indeed there are two types – the ones by you and others on content you create (so you can visualise a thread extending out from those post items in the picture) and others that are sitting on other people’s spaces (so there are lots of these personal spheres connected in that way). The picture shows the containers or channels that I “control” or own… I think a bigger picture could show the comments.

But indeed the big picture is that you can express commented-upon Web 2.0 content using the SIOC reply structure – I didn’t repeat it in my blog but mentioned it on the list:

I’m just kicking off a discussion to try and finalise some additions we are trying to make to SIOC to allow it to cover many other “Web 2.0″ community sites where content is posted in a forum or container area of a site and then may also be commented on (like in a discussion thread).

Der Podcast Award 2007 in den Kategorien private Podcasts, kommerzielle Podcasts und Jugend-Podcasts sowie der Publikums Preis wurden am 26.01.2007 im Rahmen des Podcast Kongresses in Köln verliehen. Die Gewinner sind:
Kultur

Kultur:aktion
Off…

https://www.redhat.com/docs/manuals/RHNetwork/release-notes/4.1.0/sat-release-notes-en.html

but, hey, mugshot is all opensource, so you can contribute :)

As far as I oversee this project, they are also providing a webservice http://developer.mugshot.org/wiki/API and a crossplatform client to integrate into your desktop.

And they are working on OpenID integration.

Blogs are likewise interesting only because they are RSS feeds so you should put RSS feeds (which are also available automatically from mediawiki to track page-”related changes” or overall “recent changes”, or even particular user contributions to a given wiki) at the centre, not the “weblog” as such. A “trackback” is just an unfortunate term for a stable URI such as major public wikis (like WIkipedia) already enforce, so I suggest you generalize this notion as well into something that fits the terms a serious study would recognize. For instance a stable URI is meritous in many other applications than blogs, and seems to have been the key to Wikipedia’s success. There were always better wikis for any given subject, but it was Wikipedia’s simple standard URI “en.wikipedia.org/wiki/…NAME…” that put it at the core of people’s reference habits.

Mail is also increasingly integrated with other web-based services (witness gmail, yahoogroups) so you may have to draw some explicit line between private, shared, and public discourse. Newsgroups are usually wholly public, mail usually assumed private, but there are exceptions, so deal with this dimension somehow in a way that isn’t tied to the media itself. I think you need also to distinguish between forwarding, “quoting” or otherwise just reposting something, vs. “citing” it as a credible “source” (as one might do for a newspaper article or firsthand report). You might want to look at the issue/position/argument form, which is easy to find references on.

Finally you don’t deal with chat (IRC, “IM”, jabber, etc.) at all nor the concept of logs for teleconferences or other phone logs. I think this is a mistake as these media are getting important. In the long run they will often be attached to specific (internal or external) wiki articles, being debates about them, so I suggest you deal with them as a subclass of conversations about pages if you want to remain content-focused in your ontology.

Compliments for taking it on. It’s a good start, good enough to criticize. but I wouldn’t be writing any software based on it just yet.

Could you provide the libraries you used. It seems that the libraries have change some bit since may.
It made some problems importing org.ontoware.rdf2go.Model for example.

Thanks in advance

I’m not sure I completely agree with the structure. It’s cool to see SKOS used though. There is a meta category which are Post, in this category there are sub-categories entries (ones made by the weblog authors), comments (made by the authors or readers), trackbacks (made by readers). These are three type of posts on a weblog but a comment is not a subcategory of an entry IMHO.

The latest bits and pieces people have been saying and doing related to SIOC:

Enabling SIOC for AI3 – Adaptive Information – Mike Bergman installs the SIOC WordPress exporter and describes his experiences
SIOC and AtomOWL: a new way to describe conten…

This is a good idea. Now the main question is technical – how to link from sioc:Post to AtomOWL:Content.

Yeah, this is cheap, but the problem is to generate that file, from a database, in real time, many times per 10 or 15 minutes (in a World where the pinging system interact with many crawlers/sfotware agents). Now the problem is not the bandwidth, but the buttleneck become the requests to the database (input/output) and the CPU (for the CPU we should check with some tests).

Right now I could do that without any problem, but in the long run, I don’t think that the system would be scalable for the budget I have. (this is the problem :) )

Thanks!

Take care,

Fred

Great suggestion thanks! However we have to discuss about it.

This is great, but I wonder if it worth it to add such an overhead of characters (per ping) for the export list. If it suitable to use a ScutterVocab instead that the XML I am proposing to export 10 000, 100 000 or even 1 000 000 entries? (considering that we have approximately 3, 4 or 5 times more characters for a single entry)?

My question is: what is the gain we have by using such a vocabulary when the only goal (at least I think) is to export a list of recently updated semantic web documents?

I am open to change the export format, but I wonder if it is the good way to do things.

We will talk more about it tomorrow.

Take care,

Salutations,

Fred

I have a first update to FOAF-EXT which is based on a comment by Richard Cyganiak, he suggested a more general way to indicate that something is my preferred way of contact/communication, a foafx:preferredMeansOfContact. So I have updated the FOAF EXTe…

Dies tritt auf wenn bei der debconf Konfiguration von openafs-client der FQDN verwendet wurde, `hostname` jedoch nicht den FQDN ausgibt.

Durch explizites setzen des Hostnames auf den FQDN hostname host.domain.tld und erneutes Aufrufen von afs-newcell wird der Fehler umgangen.

Based on Leigh Dodds idea about FOAF Bulletin Board RDF Export, I wrote some scripts that transform SIOC Wiki pages into RDF description…

Basically I don’t understand why people would use their RSS readers to be notified of incoming emails (isn’t the purpose of a mail client? I think so….).

It’s probably one of the reason why I took that example: at least I would like to be able to answer that email from my web feed reader ;)

–

“most of the time data ist older than 30min if it appears in the RSS Aggregator.”

I agree and it is why it would be nice to be able to “query” the feed server: “I would like to have archived content for the month of May”.

–

“But wait… what is good about the idea of representing mail meta data a RDF/XML (or n3 or…) and aggregate them? It is possible to store them in a database for later use, maybe for a context sensitive search or regrouping.
To have them available for mixing and integration with other data provided by other sources.
To form a homogenous view of the communication a user had in the past, regardless of the media/channel/application he used.”

As I said in a mail I sent on the SIOC mailing list:

“Would be cool, really. But what would be really cool is that all these softwares (email clients, web feed readers, browsers, etc) could communicate with a sort
of “Piggy Bank” (the SIMILE project of the MIT) with a simple and intuitive user
interface (something that my mom could use) to browse the relations between
aggregated RDF content. That would be cool but in the mean time, a link to the
SIOC browser could do the job :)”

–

By the way, thanks for this blog post, it’s always nice to see that some people care about what you write (good or bad)

Take care,

Salutations,

Fred

There’s been quite a few happenings in the “siocosphere” during the past month:

Christoph Goern posted some details about how to enable SIOC output for a community site such as a planet aggregator; I hope to work on this myself WRT P…

There’s been quite a few happenings in the “siocosphere” during the past month:

Christoph Goern posted some details about how to enable SIOC output for a community site such as a planet aggregator; I hope to work on this myself WRT P…

Super Update! Danke Ubuntu!!

Yet, the problem by translating RSS to SIOC is that you can’t make differences between original posts and replies, which is an interesting feature of SIOC.
But at the moment I can’t see how we can get this easilly without any access to ML datasources.

SIOC provides "an ontology for describing discussion forums and posts on topic threads in online community sites" and so called exporters for WordPress or Drupal blogging/cms software. Using that one is perfectly suited to provide informatio…

[GNU] writes in “SIOC enabling a community site”:
After installing the SIOC WordPress plugin this site is enabled to provide SIOC data for the site itself, users and all articles on B:\datenbrei. Many site on the internet don’t provide SIOC data,…

In my mind, a Community is a set of Sites.
If you merge sioc:Site and sioc:Community, it means that a Site will be a group of Sites, but this is already a group of Forums (w/ host_of), and it can be a bit confusing.

But indeed, we might need a Community class, mainly for agregators, which will sioc:gather /includes some Sites.
(In that case, planetRDF will be a Community, each site a sioc:Site, that got one or more sioc:Forum)

John has built quite a lot of features in planet.journals.ie based on that.

A funny thing – this feed is created by an iCal -> RDF script.
If someone converted it now to iCal that’d be a full circle. :)

I did not think of RSS to iCal at that moment, but having this RSS feed of events aggregated in the web aggregator was a very good reminder.

Note: while the feed may have events quite a lot in the future the aggregator (Planet PHP) was configured to show events that are up to a week (or 2) in the future.