Re: [rdf4j-dev] what major/breaking changes do we want? and when do we w

[Håvard Ottestad <hmottestad@xxxxxxxxx>]

Hi Jeen,

Thanks for taking initiative. 

Could we do a 2.5 release from develop and then designate develop to 3.0 release?

I would like to release the SHACL engine. It’s been out in beta for well over 3 months now and as far as I can tell we haven’t had any feedback other than feature requests. 

The main thing about the RDF4J SHACL engine is that it is incremental. It scales as well as the underlying store, so if you have 100 triples or 500 million triples in your native store; validation still takes the same amount of time. There are no other validation engines for RDF that work this way. 

The SHACL engine currently supports the following restrictions 

- min count

- Max count 

- datatype

- logical or (on the above restrictions)

These restrictions can apply to

 - all use of a predicate

 - use of a predicate on subjects of a specific type

Validation is true/false, with some logging to give you a hint for what might be wrong. 

I would love to have more features and functionality before we release it from beta. But I’m currently working on it evenings and weekends, so it’s very slow going. 

Documentation is the number one thing holding it back from a release. 

Håvard

On 17 Dec 2018, at 04:58, Jeen Broekstra <jeen.broekstra@xxxxxxxxx> wrote:

Folks,

The milestone for the next major release, 3.0, is undated, and has no real focus at the moment. As you can see here:

 https://github.com/eclipse/rdf4j/milestone/17

There isn't a lot of exciting new stuff planned for RDF4J 3.0 - it's mostly just about removing deprecated stuff and doing some cleanup.

So the question is: can we think of any major things that we'd like to include in RDF4J in the near future, stuff that we should

start thinking about and putting tickets into the 3.0 milestone for? 

And when do we want to start thinking about doing a major release? Is first thing after minor release 2.5 a good idea? Or should we wait until we actually have something major and urgent ready to put in there? 

Note: I'm perfectly fine with doing a major release even if most of what we do is non-exciting cleanup stuff. But it'd be a shame if we do a major release, and then two weeks after we figure out we want to do this other non-backward-compatible thing.

Cheers,

Jeen  

_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/rdf4j-dev