reunification

[Gunnar Aastrand Grimnes]

Hello all,

I've just merged the "reunification" branch

This includes the rdflib-sparql code back into rdflib, and also some
other bits and pieces that we feel are stable enough to be in
rdflib-core.

This means rdflib-sparql/rdfextras is no longer needed for sparql support.

I will soon release this as rdflib 4.0 - with RDFa/Microdata and
SPARQL 1. 1 support out of the box, it should be the best rdflib
release so far!

From my point of view, I'll fix these two, then release:

URI Validation
https://github.com/RDFLib/rdflib/issues/266

And SPARQL variable orderings:
https://github.com/RDFLib/rdflib-sparql/issues/9

Anything else that is very broken in master atm?

If anyone has any spare cycles, I would some extra eyes to make sure
the documentation is up to date, and that code examples are as simple
as possible!

Cheers,

- Gunnar

--
http://gromgull.net

[u...@andonyar.com]

Great news!

I would like you to take a look at this new issue too
before making a release:

Non-ascii characters in SPARQL query
https://github.com/RDFLib/rdflib/issues/270

Another thing:
Is it true that one now has to use processUpdate from
rdflib.plugins.sparql.processor in order to make SPARQL
updates or is there another way now?

Maybe I will take a look at the documentation later this week.

[Gunnar Aastrand Grimnes]

On 1 May 2013 18:27, <u...@andonyar.com> wrote:
>
> Is it true that one now has to use processUpdate from
> rdflib.plugins.sparql.processor in order to make SPARQL
> updates or is there another way now?

it's also imported into rdflib.plugins.sparql :

>>> from rdflib.plugins.sparql import processUpdate

We could always consider adding it to Graph somehow...

[u...@andonyar.com]

Am Mittwoch, 1. Mai 2013 19:47:36 UTC+2 schrieb Gunnar Aastrand Grimnes:
> it's also imported into rdflib.plugins.sparql :
>
> >>> from rdflib.plugins.sparql import processUpdate
>
> We could always consider adding it to Graph somehow...

Would make sense, because this could also be supported by the store directly, e.g. rdflib-sparqlstore.

[Gunnar Aastrand Grimnes]

On 1 May 2013 20:11, <u...@andonyar.com> wrote:
>> We could always consider adding it to Graph somehow...
>
> Would make sense, because this could also be supported by the store directly, e.g. rdflib-sparqlstore.

https://github.com/RDFLib/rdflib/commit/2165ed98c9927a565646c59376941f2624c976c3

graph.update is now there!

I have a slight feeling that the plugin infrastructure here is making
thing complicated for future flexibility that will never be used, but
it matches the .query method :)


--
http://gromgull.net

[u...@andonyar.com]

> graph.update is now there!

Hey thanks! Just considired to implement it myself when I saw that the code I wanted to write is already there in graph.py. You're doing excellent work!

[Gunnar Aastrand Grimnes]

So, from my point of view, all issues that were blocking a 4.0 release
are solved!

I would still like to brush up the docs a bit - I think rdflib is by
far the easiest way to work with RDF, but we do not always communicate
it very well, and there are lots of "hidden features". Also, I see a
lot of overly complicated/"old fashioned" rdflib questions on
stackoverflow etc.

If anyone has some spare cycles I would love another pair of eyes for
this! A fun task is for instance trying to write doc strings for any
non-trivial method :)

I have already tried to clean-up in the "wiki" part of the rdflib
github project - having duplicate information there and in docs/rtd is
just inviting one of them to become outdated.

Also, a good example speaks a thousand words - if you have anything to
contribute to the examples directory feel free!

Anything else we should change/fix just now? 4.0 already breaks
backwards compatability slightly - so if there is anything that always
bothered you, now is the time!

Cheers,
- Gunnar

--
http://gromgull.net

[u...@andonyar.com]

Am Freitag, 3. Mai 2013 21:13:03 UTC+2 schrieb Gunnar Aastrand Grimnes:
> I would still like to brush up the docs a bit

When do you want to finish the release? Maybe I can find some time to look at the documentation this week, but not for shure.

It would be great if as many people as possible could take a serious look at the documentation. The most basic things really must be described in a prominent place. Docstrings alone don't help much for a new user who doesn't even know which class she should be looking for. And this information should be correct, so we should double check it. Then also, someone should update the the architectural diagram in the documentation. It still shows things outside of core rdflib which are now inside, as far as I know.

[Gunnar Aastrand Grimnes]

I dont really have a plan for the release, this week or next are both ok.

I've updated the doc ticket with some thoughts on documentation:

https://github.com/RDFLib/rdflib/issues/265

I'm open for anything though :)

I've already made a start - but I've not been able to make read the
docs build the docs from master on github - Graham? (or just make me
an admin I can fiddle myself!)

[Graham Higgins]

On Mon, 2013-05-06 at 21:26 +0200, Gunnar Aastrand Grimnes wrote:

> I've not been able to make read the
> docs build the docs from master on github - Graham? (or just make me
> an admin I can fiddle myself!)

Docs rebuilt [1], gromgull is an admin.

[1] http://rdflib.readthedocs.org/en/latest/

Cheers,

--
Graham Higgins

http://bel-epa.com/gjh/

[Gunnar Aastrand Grimnes]

So, I've fixed "the last bug" and I've updated almost all the docs,
better doc-strings could be added to many methods, also more use of
http://sphinx-doc.org/domains.html?highlight=param#info-field-lists,
but you gotta release some time.

Have a last look over things, if I hear nothing RDFLib 4.0 goes out
tomorrow evening! I.e. in about 24 hours!

Cheers,

- Gunnar

--
http://gromgull.net