Hi David, and thanks. The code is already up there in the tarball, but I'll get the repo posted ASAP. I noticed pretty much everyone that visits the Google Code site goes straight to Browse Source (duh! of course :) and sees nothing, since the repo isn't there...
As for the libraries, yes and no. Yes I didn't want to use existing libs, because the existing libraries that I knew of wouldn't let me pretend that regular, pre-existing Django models are actually a triple store. That's the trick I wanted to pull off, because I want to be able to expose Django projects I've done for clients, as RDF data sources, without changing the project code in any other way. None of those guys would let me replace their databases with some triple store. (Not that I would seriously suggest it... "hey, guys, why don't we drop the Oracle stuff and use this cool open source thingy instead? No, it doesn't do transactions... No, also doesn't do X, Y, or Z... What do you mean, go home?" :) Put it another way, none of those libraries are very good at doing what Django does best - fielding great database-driven web sites, really fast. So I guess I was thinking, hey, I want to have my cake and eat it too - I want to keep using the Django ORM, it works for me, but I also want to process SPARQL and generate RDF/XML. Hence, the triple store is implemented with Django models, syncvb churns out RDF/ OWL ontology fragments from regular Django models, the SPARQL engine returns query sets (but not yet models, that's a little hard to do - I think the models have to be dynamic for that to work) and so forth. Arguing whether any of this is useful is a different matter, but it was at the very least a fun exercise! (Of course it's useful!... ;) But, no, there is no good reason not to reuse parts of libraries that are distributed with a suitable license. My SPARQL compiler comes nowhere close to what those other projects have, it might be nice to drop in some more stable code. There are plenty of RDF/XML and N3 serializers, etc. So - RDFLib, I think I had that one mixed up with LibRDF. I need to take another look. The parser and serializer collection is promising - I'm not at all happy with my serialization stuff, I banged it together without much of a thought. I think the only good thing to say about my serialization stuff is that there is not a lot of it. Redland (LibRDF) - I put in place the same kind of namespace[name] API Redland has, that's rather neat. Raptor and Rasqal are promising in the same way RDFLib is. But, Redland is pretty far removed from Django. I didn't want to start doing things in a certain way because that fit better with Redland. It's going to be useful to revisit Redland later. I think RDFAlchemy replaces the SQL database with a triple store, which is exactly what I wanted not to do. Correct me if I got it wrong. Cheers, Stefan On May 11, 11:19 am, David Larlet <[EMAIL PROTECTED]> wrote: > Stefan, > > It looks really promising but it's really hard to evaluate it without > any code (or detailled examples). I can't wait for the ready-for- > release time :) > Is there any reason that you don't use any existing lib (rdflib, > librdf, rdfalchemy, etc)? > Anyway, let me know if I can help, I'd just subscribed to the google > group. > > Cheers, > David > > Le 10 mai 08 à 13:19, stefan a écrit : > > > > > Hi there fellow Django enthusiasts, > > > My name is Stefan, I'm a tech type like probably all of you, and I'm > > based in Iceland for the time being. This is my first post here, > > although, I've been lurking on django-devel for awhile. I started > > working with Django in fall 2006 and I've been playing with Python and > > RDF on and off since ca. 2003. > > > I wanted to share a little project I've working on with you guys, in > > the hope that perhaps a couple of other folks might be interested in > > joining me? > > > The project is a reusable app called Django-RDF, and it's aimed at > > providing unintrusive RDF support for Django. > > > By unintrusive I mean, the Django-RDF app should work seamlessly with > > any existing Django projects without requiring changes to existing > > models, database setup, etc. Just, drop it into place. > > > And, RDF support means two things first - having the ability to query > > models using SPARQL, and return data using RDF/XML (and later N3 > > etc.). > > > Then, third (and not quite as important to me as having seamless > > support for existing models) - also having the ability to store data > > in a triple store in case one might like a user-extensible data model, > > etc. Fun stuff, but regular models have better performance. > > > I've got many of the basic pieces working, including a compiler that > > turns not-quite-SPARQL into SQL, models for storing ontology elements > > and implementing the triple store, and some view support that turns > > out RDF/XML - I think everything necessary for getting started, but > > not really anything more. > > > Of course, all this stuff is brand new and hasn't been used in a > > production environment yet, so please be prepared for speedbumps if > > you decide to give it a try :) > > > There is a couple of tarballs athttp://code.google.com/p/django-rdf, > > one with the code and another with a set of RDF ontology files that > > were collected from various places and are used during initial setup. > > The Google Code page also has a bit more text describing the project. > > I'll be importing the SVN repo shortly, the code was wrapped up inside > > another project, needed to be cut out, and I still need to do a bit of > > trimming. And, I know I need to write instructions, etc. etc. All in > > good time. I'll try to respond fast as I can to your emails with > > questions, pointing at all the stuff that's not right yet, etc. > > > I hope this will strike a chord with some of you guys - that would be > > highly motivating for me. Cheers, > > Stefan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
