On 27/09/11 21:38, Stephen Allen wrote:
As a side note, my plan is to create a GraphDataBag that implements the
Graph interface, but stores the triples internally in a
DistinctDataBag<Triple>. This would then be used instead of an in-memory
Graph when we know we don't need to add triples after the query is finished
and don't need indexes (Fuseki for example).
-Stephen
Excellent idea - I like the idea of having sub-modules that have clearly
defined responsibilities, then combine (later) into useful features.
Often I start out putting something together that worsk, then fine the
components, then refactor.
In some ways, the whole of ARQ is like that. The first RDQL query
engine was one class, and mainly one method to do what is now BGPs.
Andy
