I've made https://issues.apache.org/jira/browse/JENA-1266 to remind ourselves about this.
--- A. Soroka The University of Virginia Library > On Dec 14, 2016, at 12:09 PM, Andy Seaborne <a...@apache.org> wrote: > > > > On 14/12/16 11:24, Martynas Jusevičius wrote: >> Shouldn't Dataset be in rdf.model together with Model, now that RDF >> 1.1 standardized named graphs? > > Yes, and the class packaging of other things. > > User code would have to change. > > Andy > >> >> On Wed, Dec 14, 2016 at 10:54 AM, Rob Vesse <rve...@dotnetrdf.org> wrote: >>> Yes pull requests on Git Hub are fine >>> >>> This will probably need to rely upon ARQ because that is where the Dataset >>> API lives. It might be useful initially to have it be a separate module >>> under jena-extensions >>> >>> Rob >>> >>> On 13/12/2016 16:48, "Martynas Jusevičius" <marty...@graphity.org> wrote: >>> >>> I will try some time during holidays. >>> >>> Will a PR on https://github.com/apache/jena/tree/master/jena-core work >>> for this? >>> >>> On Tue, Dec 13, 2016 at 10:48 AM, Rob Vesse <rve...@dotnetrdf.org> wrote: >>> > Well why don’t you put together and implementation and get it a try? >>> > >>> > Jena has always supported multiple APIs e.g. Model and Graph for >>> achieving the same goals. Contributions of alternative APIs would always be >>> welcome >>> > >>> > Rob >>> > >>> > On 12/12/2016 21:45, "Martynas Jusevičius" <marty...@graphity.org> >>> wrote: >>> > >>> > Well, this probably requires some generic method(s) in >>> Dataset/Model >>> > as well, something like: >>> > >>> > T apply(Function<Dataset, T> f); >>> > >>> > This would allow nice chaining of multiple queries, e.g DESCRIBE >>> and SELECT: >>> > >>> > ResultSet results = dataset.apply(describe).apply(select); >>> > >>> > Seems more elegant to me than all the QueryExecution boilerplate. >>> > >>> > On Mon, Dec 12, 2016 at 9:00 PM, A. Soroka <aj...@virginia.edu> >>> wrote: >>> > > What are the kinds of usages to which you are imagining these >>> kind of types being put? >>> > > >>> > > --- >>> > > A. Soroka >>> > > The University of Virginia Library >>> > > >>> > >> On Dec 12, 2016, at 2:03 PM, Martynas Jusevičius >>> <marty...@graphity.org> wrote: >>> > >> >>> > >> Hey, >>> > >> >>> > >> has Jena considered taking advantage of the functional features >>> in Java 8? >>> > >> >>> > >> What I have in mind is interfaces like: >>> > >> >>> > >> Construct extends Query implements Function<Dataset, Model> >>> > >> >>> > >> Describe extends Query implements Function<Dataset, Model> >>> > >> >>> > >> Select extends Query implements Function<Dataset, ResultSet> >>> > >> >>> > >> Ask extends Query implements Function<Dataset, ResultSet> >>> > >> >>> > >> >>> > >> Martynas >>> > >> atomgraph.com >>> > > >>> > >>> > >>> > >>> > >>> > >>> >>> >>> >>> >>>
