On 4/26/06, Mark Nottingham <[EMAIL PROTECTED]> wrote: > I'm interested; not very high-bandwidth right now, but definitely > interested. > > I think the question on the table is how best to integrate the APIs. > > I'll subscribe. > > Cheers,
I have some ideas on this. I think, the nice thing about Sparta currently is that it sits directly on top of the Graph API, and I think it would make sense for it to remain that way. Using the integration of sparql-q as a guide, if it were added as a top-level module (rdflib.Sparta) it could be ported as is with the recent changes to the Graph API being the only real thing to contend with (though I don't think they impact Sparta as it is currently constituted). Generally, it suggests 3 levels of abstraction for rdflib APIs: 1) Querying / Data Binding (sparql-p / Sparta) 2) 'Core' / Programming (Graph) 3) Persistence (Store) Chimezie _______________________________________________ Dev mailing list [email protected] http://rdflib.net/mailman/listinfo/dev
