I still think we need SDB or an SDB like package. My reasoning is that there are a number of places (think cloud providers, think large corporations that have internal data centers) where you can get a standard DB with all the backup and restore capability built in. The ability to deploy on an existing well known infrastructure makes Jena an easier sell to management.
On Mon, Jan 26, 2015 at 9:56 PM, Stian Soiland-Reyes <st...@apache.org> wrote: > +1 for the plan. > > Some thoughts for "other changes" I have wanted to get my teeth into: > > a) remove legacy Model reader/writer API > b) move RIOT into jena-core (as was suggested), keep SPARQL in arq > b2) rename jena-arq to jena-query? > b3) rename jena-tdb to jena-triplestore ? > b4) retire jena-sdb? Some interest still.. > > c) cleanup of RDFDataMgr - do we need all those methods? > d) use java.nio.file.Path instead of java.util.File all over > e) get rid of any remaining Class.forName and add registries/ServiceLoader > patterns as needed > > e) and b) can be done already in 2.x. > > To do git merge across file renamed requires some hand holding, but seems > to work surprisingly well. New files on the branch will appear in the wrong > place, and any new import statements in existing files will be wrong on the > other branch. > > Beta or 3.0.0? Well, that depends on what goes into the other changes! ;-) > On 24 Jan 2015 18:34, "Andy Seaborne" <a...@apache.org> wrote: > > > Here is a suggestion for Jena3. > > > > After 2.12.2 or 2.12.3, > > > > 1/ A branch for Jena2 ; master is Jena3. > > 2/ Switch to RDF 1.1 setting for strings > > 3/ Rename com.hp.hpl.jena packages to org.apache.jena > > 4/ Other changes > > 5/ Let things settle down. > > 6/ Release (beta? just go for it as 3.0.0?) > > > > (3) is the disruptive step - I doubt git merge is going to be much help > > after that for managing changes related to com.hp.hpl.jena packages > > > > I wrote some migration notes for the RDF 1.1 isms and packages. > > > > http://jena.staging.apache.org/documentation/migrate_jena2_jena3.html > > > > There is a lot of things that could be done. I like us to avoid > > over-committing ourselves. The question I have is what is *necessary* to > > drive into jena 3.first. > > > > Andy > > > -- I like: Like Like - The likeliest place on the web <http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
