So, with regards to things SemanticWeb, I think I'm about to eat dogfood in considering a BlueSky project at work. We've been tossing around ideas for a kind of uber-space or organization-wide brain in which to gather all kinds of details about clients, projects, project details and components, lifecycle, etc.

We want this thing to be as flexible as possible, without filling up a wall with printouts of database tables and relations - in fact, we want the thing to provide ad-hoc relations we hadn't thought of at first. We want people (ie. project managers, sales) and robots (ie. metrics engine) to contribute data, and then people (ie. sales and clients) and robots (ie. automated project build) to be able to query and use this data. We want roles and access control. We want scalable centralization of data items. (ie. Why should the start date of a project be maintained in 12 different places?)

I'm certainly not naive or ignorant enough to think that this is virgin territory. There are entire industries devoted to these issues of business data integration - but here, budgets are very slim yet we love to play with new tech. It continues to astound, but with a little ingenuity (okay - a lot of ingenuity - we have smart people working here), this has led us time and time again to a combination of Open Source software and homegrown code that treats us better than any outside vendor solution. So, I'm hoping to pull another hat trick here and have some fun expanding my brane at the same time.

One of the first notions was to ease more information into our LDAP servers, since it has a very nice hierarchical layout and can accept arbitrary name-value attributes for items. But then the topic of RDF came up, and the discussion really caught on fire as everyone came to understand what RDF is - at least insofar as I understand it, since I seem to have become the local domain expert.

So, first thing is: I hope I really do grok this stuff, at least at a gut mojo level. No one's called me clueless about it yet. But the second thing is: Any practical tool suggestions, case studies, prior art, etc that I should be looking at? I've started with a Google search for RDF and I've been wandering W3C documents - but I need a Busy Developer's Guide. My ultimate hope through all of this, is that even if things are still baking, that there's enough out there with which to make something practical.

The goals are gigantic, but my intuition is that using SemanticWeb tech will let us start out small and simple and then add vocabularies and items as needed without massive tool rebuilding. This is the key thing - the ability to do some initial, fairly easy things that show early results without a heavy, multi-month process to get the thing providing value. My gut tells me it's possible. Am I mad?


Archived Comments

  • I haven't seen anything to dissuade me that this stuff isn't ready for use, even by (non-RDF-focused) developers. I could be wrong. That could also change quickly if OSAF/Chandler sticks with RDF. Could you give an example of a benefit such a system would provide beyond what you might accomplish through a combo similar to this very site using blog, wiki, and a file server (for excel files, etc., no text allowed there)? Still, if you want to go with RDF, I'd be inclined to use 4suite, which supports some "real" backends. You might also want to chat with AaronSwartz, with a focus on what's practical *now*...