Re: rdflib v5.0

[Gunnar Aastrand Grimnes]

Hi Nicholas,

(I've CC'd the rdflib-dev mailing list as well - so that everyone is on board!)

I've had a chat with Jörn, and come up with the following road-map:

RDFLib Roadmap
------------------------

I believe lots of people are already using master in “production”, so
I would like to get a 5.0-beta release ASAP.

We’ve already made some big changes since 4.2.2, in particular:
* We’ve removed 2.6 support
* We’ve changed to have one code-base for py2 and py3

In addition I would like to merge these:

* Remove SPARQLWrapper dep: https://github.com/RDFLib/rdflib/pull/744
* Remove RDFa/Microdata from core RDFLib
https://github.com/RDFLib/rdflib/pull/828
* Namespace inherting from unicode: https://github.com/RDFLib/rdflib/pull/597
* Improve compute_qname: https://github.com/RDFLib/rdflib/pull/649

Further down the line :

* Store context graph vs. uri fix: https://github.com/RDFLib/rdflib/pull/409
* Streaming APIs: https://github.com/RDFLib/rdflib/pull/411
* split up of core vs. extra functionlity - discussion in
https://github.com/RDFLib/rdflib/issues/391

Me and Jörn will try to sit together the weekend of 27th of October,
pull the trigger on a bunch of these PRs and get out a 5.0.0.

Then we can try to get 5.0.1 out a bit more quickly after that :D

And we don't have to be shy about going to 6.X quite soon as well - if
we chose to split up into more sub-modules for instance.

How does that sound?

Cheers,
- Gunnar
On Mon, 1 Oct 2018 at 09:51, Car, Nicholas (L&W, Dutton Park)
<Nichol...@csiro.au> wrote:
>
> Hi Gunnar,
>
>
>
> I’m keen to commit some of my time and some of my team’s to sorting open rdflib issues and actioning open PRs for a minor rdflib release perhaps by the end of the year to assist with the code bing up-to-date. Perhaps then we can think about what would be needed for a 5.0 release – something I think you and other lead devs have already got plans for – perhaps by July next year?
>
>
>
> If we do that, perhaps we could also ask around the community for help on this which, if we can suggest a timeline, might get interest.
>
>
>
> For a v5.0, I’m particularly keen on assessing all the various rdflib repositories and seeing if we have, within the project, really thought about covering all the things people might want to do with RDF in Python. We now have a SPARQL validator tool of course, the core rdflib toolkit itself, a couple of reasoners (mostly out of date though), ORM wrappers etc. but are there perhaps glaring holes in Python RDF support comparted to, say, Java that we could potentially think about repos for?
>
>
>
> Cheers,
>
>
>
> Nick
>
>
>
>
>
> Nicholas Car
>
> Senior Experimental Scientist
>
> CSIRO Land & Water
> 41 Boggo Road, Dutton Park, QLD 4102, Australia
>
> E nichol...@csiro.au M 0477 560 177 P 07 3833 5632
>
>
>
>
>
>
>
>



--
http://gromgull.net

[Car, Nicholas (L&W, Dutton Park)]

Hi Gunnar and all,

This is really encouraging - you're steaming ahead which is great! Happy to then think about that strategic review for a v 6.0 in time for perhaps June next year.

We are now updating further things in OWL-RL and pySHACL and there are a couple of bugs that prevent pyHACL from passing all SHACL tests:

https://github.com/RDFLib/rdflib/issues/847
https://github.com/RDFLib/rdflib/issues/848

Ashley, who raised those, has also suggested a simple patch for one of them (847).

So we would like to drop those (easy to fix) issues into the mix for a 5.0 release so that we can say rdflib is dealing with SHACL completely.

We're standing by to assist if requested.

Cheers,

Nick

[scossu]

That's exciting! Thanks all for your contributions to the project. Looking forward to this major release.

s

[Sergio Fernández]

Sounds like a good plan :-)

--
http://github.com/RDFLib
---
You received this message because you are subscribed to the Google Groups "rdflib-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rdflib-dev+...@googlegroups.com.
To post to this group, send email to rdfli...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rdflib-dev/CAGm1ODkDV_ntuZYqZb2YG412pBviLghGG7_nfqVrwGVDJnapsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Kristina]

Hello Gunnar,

it's great, that you are going to work on the rdflib v5.0!
How is it going? When it should be released?
Is there anything to test already available?

Best regards,
Kristina

[Nicholas Car]

Yes, we (Australian RDF people) are also interested in this.

Nick

--
http://github.com/RDFLib
---
You received this message because you are subscribed to the Google Groups "rdflib-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rdflib-dev+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/rdflib-dev/4c1575da-1c96-47e4-a948-eca01a055d85%40googlegroups.com.

[Nicholas Car]

Hi core devs,

Issue flagging with things like the 5.0.0 Milestone (https://github.com/RDFLib/rdflib/milestone/2) seems to have dropped off since last year and I guess this is because the momentum for 5.0.0 release has dropped off. There's also a pretty decent Issues list now!

Would it be possible to have core devs do an issue triage so non-core devs like me might be able to pitch in for issues grouped in related areas and assigned priority? I could perhaps work on something narrow like turtle handling, if core devs could first group issues so we're confined. That help people less familiar with the toolkit.

Thanks,

Nick