Hi Andy
I am currently putting together a longer term roadmap for the dotNetRDF project partly because I want to have a clearer plan of where it is going and partly because I'm planning on applying to be a mentoring organisation for Google Summer of Code (GSoc) this year. One of the possible projects I'm interested in is doing a native .Net port of TDB. I am aware that TDB can be run on .Net using the Jena.Net distribution created by Mark Seaden but I'm not interested in that for various reasons. I'd like to have a native port since then the .Net client code can be written to use .Net paradigms - Properties, LINQ to Objects etc. - and also plugged in directly to my Leviathan SPARQL engine rather than having to have ARQ IKVM'd as well. Having read through all the details of TDB on the wiki I can't see any obvious technical barries to doing this. Additionally provided that the implementation generates the persistent data files in exactly the same format and encoding as the Java implementation then the two implementations will potentially be fully interoperable What do you think about this? I have no timeframe for when and if this will get done at the moment as I have other priorities higher up the list but I would be interested in your opinions on this? Best Regards, Rob Vesse -- PhD Student IAM Group Bay 20, Room 4027, Building 32 Electronics & Computer Science University of Southampton
