Re: [dotNetRDF-Develop] Advancing Fluent SPARQL

[Rob V. <rv...@do...>]

Yes if you want to extract things into other libraries then please go
ahead, if you need to make the current Query API mutable then please do
this as needed.

Longer term I want to have things be more modular anyway and a Fluent
Query API is an obvious candidate for a separate module.

In the 1.9 branch I have rewritten much of the Query API to address many
of the current limitations which includes making it a mutable interface
based API

Rob

On 06/01/2015 21:00, "tom...@gm..."
<tom...@gm...> wrote:

>Hi Rob
>
>I've been many times in need of unfinished features of the query builder
>API. Especially CONSTRUCT but SPARQL Update won't be hard to add either.
>I'd like to finish them finally but I was thinking whether it would be
>somehow possible to extract it from the core library so that it can be
>released independently. I'd like that because dotNetRDF releases quite
>infrequently. 
>
>The problem is that I use the query API of which all classes are
>internal. Do you see a good way around that?
>
>Thanks,
>Tom
>
>--------------------------------------------------------------------------
>----
>Dive into the World of Parallel Programming! The Go Parallel Website,
>sponsored by Intel and developed in partnership with Slashdot Media, is
>your
>hub for all things parallel software development, from weekly thought
>leadership blogs to news, videos, case studies, tutorials and more. Take a
>look and join the conversation now. http://goparallel.sourceforge.net
>_______________________________________________
>dotNetRDF-develop mailing list
>dot...@li...
>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop