My vote is not binding, but I'd be +1 for that. I'm using
ParameterizedSparqlString from ARQ to create simple INSERT's that will go to a
Fuseki SPARQL endpoint, but my guess is that QueryBuilder would ease the other
users to understand how the query was being built (pun intended :)
So you'll probably already have 1 user to annoy you with bug and feature
requests in the future.
CheersBruno
From: Claude Warren <[email protected]>
To: [email protected]
Sent: Tuesday, October 7, 2014 1:15 PM
Subject: Query Builder
Does anyone have an objection to adding the query builder code to the jena
project?
Does anyone have a suggestion for where to put it?
I assume we don't want it in ARQ (though the code is currently ARQ package
based).
It seems to me that it is a nice to have utility and should be packaged
with other nice to have utilities or perhaps on it's own.
Do we need to have a discussion and come to consensus about how to package
other similar packages?
Claude
--
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren
