Semantic Web

Hi there,

I'd like to start a thread to discuss about available RDF APIs for PHP.

I took a look at Benjamin Nowack's ARC2 (http://arc.semsol.org). It looks sound and it's already used in several projects. It features several i/o parsers/serializers, an integrated RDF store, SPARQL query engine (didn't read anything about compliance with W3C DAWG test cases...), SPARQL endpoint, some simple inferencing and there are also some plugins I didn't look at for now.

Moved to official ideas list: http://drupal.org/node/237907

I want to propose a project for building a module that pulls news content from a global news service called Daylife (http://daylife.com)

Daylife is a global news aggregation service that offers an Open API platform called DayPI (http://developer.daylife.com) for any developer, blogger, news service to pull stories and photos about any topic in the world. The API returns data in XML, JSON and PHP serialized formats. You can read the Daylife About page at http://www.daylife.com/page/about to learn more about the company. All platform documentation is on http://developer.daylife.com/docs

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.

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.

KarenS has kicked off a discussion on CCK field structure for core in D7. It's also webchick's itch of the week.

David Strauss is already commenting, and has experience in RDF from the Internet Archive, but it would be good to have other experienced people giving this the once over. Since these fields are likely to be a major way that people "transparently" create subject/predicate/object relationships, we better get this right (and performant, working on shared hosts, etc. etc.).

This is the beginnings of a design specification proposal for an abstracted API for implementing web services within Drupal 7. This allows Drupal to act as both a server and client for web services in any protocol medium (XML-RPC, RDF, RSS, JSON, etc). It is the combined efforts from a number of people at Druplicon including Marc Ingram, Scott Nelson, Nedjo Rogers, Dmitri Gaskin, etc.

Services API

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.

Following up on my previous post introducing the in-progress RDF API for Drupal 6.x, I'm going to be, bit by bit, posting some of the materials that I've earlier put together internally for the project this is being developed for. Development of this project is supported through M.C. Dean and MakaluMedia on behalf of their clients.

I've been working on an RDF API for Drupal 6.x for a few months now, but have been reluctant to much discuss it publicly until such time that I had something that was viable and (dare I say it) usable. Given that I've been fortunate enough to recently find funding for part of this work, and that certain key people (thanks Boris and Ivan) have encouraged me to be less of an introvert, I will in the immediate future be doing a series of posts about the project.