RDF in other open source CMS's
Today I talked with Thomas Hochhaltinger from ebSemantics, a project of "Smart Information Systems", an Austrian company that developed MyOntology.org a collaborative ontology designing platform with ontologies for consumer electronics goods.
Read moreGRDDL, Drupal, & Microformats
Hey all,
How many of you know about GRDDL ('griddle')?
If you've seen the acronym around but haven't read the spec, then you are missing out.
In short, it's a W3C recommended way to post links to XSL stylesheets in HTML and XML documents.
Those stylesheets are specifically designed to produce RDF/XML from a target document.
So what, you might say.
Well: these GRDDL transformations can be done for an individual document; or an entire xml namespace / xmdp (microformat) profile.
Read moreSemantic Drupal FP7: Code sprint series
Last week at Drupalcon in Boston I realised that it's just not possible to apply for a development FP7 (the 7th Framework Program of the European Union) for Drupal. Things are going so fast that any plan would be obsolete before the project could get granted. That's why I think it would be the most interesting to do a proposal for a series of expert meetings throughout Europe that brings together people to discuss their implementation of the semantic web in Drupal, every time followed by a code sprint.
Read moreDrupal 7 and Semantic Web Core
In regards to the Semantic Web developments announced recently about Drupal 7, I have posted a blog entry at SitePoint and also posted to the Linking Open Data mail list.
Read moreDrupal RDF Schema proposal
I'd like to share some quick thoughts on how Drupal Data could be described in RDF. The attached schema represents the mappings between the current Drupal data structure and the proposed RDF Schema, reusing existing ontologies such as Dublin Core, FOAF, SIOC and SKOS.
The green circles represent the Drupal objects (node, revision, user, role, term), with their equivalent RDF class. The rectangles are the values used in Drupal. It's important to differentiate a class from its actual instances (resources) which are each defined by a unique URI, see the examples below. This schema is meant to be simple, incomplete, and to show the main core features.
Comment and Node are 2 different elements in Drupal, they can be combined in the same Class with the recursive property sioc:has_reply
(Comment as Node). Node and Revision objects are separate here as they are in the Drupal Data structure, but they could fundamentally be merged as well.
I presented SIOC at DrupalCon Barcelona, and showed how it can be used to describe online communities. The SIOC sioc:Item
class which I used here as equivalent of a Node is a broad Class with many sub-types: AddressBook, AnnotationSet, AudioChannel, BookmarkFolder, MailingList, MessageBoard, BlogPost, BoardPost, WikiArticle... See the SIOC Types Module for more details.
OpenCalais
Reuters has opened up a web application to streamline the process of generating metadata around content. From their web site at http://opencalais.mashery.com/Overview
<
blockquote>
The Calais Web Service
EU Objective ICT-2007.4.2 (ICT-2007.4.4): Intelligent Content and Semantics
The ICT - INFORMATION AND COMMUNICATION TECHNOLOGIES workprogramme from the European commission has calls for applications that could fit a Drupal project. Especially Objective ICT-2007.4.2 (ICT-2007.4.4): Intelligent Content and Semantics is very interesting, anybody interested in collaborating on a grant proposal for this?
Target outcome
Medium term:
a) Advanced authoring environments for the creation of novel forms of interactive and
expressive content enabling multimodal experimentation and non-linear story-telling.
Dublin Core integration for CCK module
Relationships-categorization system wanted features
"Relationship" I understood as relationships between fields (nodes are many relationships, which are subject of more advanced process).
Wanted features:
- Powerful and without limitation thanks to the most abstract (see: "everything is a field", compare this to: Global CCK fields, A controversial(?) point: store translations as nodes).
- Build-in categorization features.
- Build-in views features (listing fields, not necessary nodes).
- Build-in menu features.
- Support for Semantic Web/Microformats/similar.
Observations about current situation:
Read more