Iwan Aucamp

This should be solved before further re-org: https://github.com/RDFLib/rdflib/issues/1839

> > Subsequently, we should also remove its use in the codebase where it occurs. Though, best to first mark it as deprecated. > > Bit of a chicken and...

> Can we already make a finite list of issues that would lead to W3C spec compliance for Dataset? This is harder than it would seem. We run the W3C...

@tobiasschweizer I would test the file with Jena's riot, and if Jena parses it without objections, it likely is a problem with RDFLib.

We could deprecate CG fairly easily now, it would require some odd things, like only raising a deprecation warning based on type of self, but it won't be too challenging....

This seems like a bit of an oversight, I think `bind_namespaces` should ideally be available on each subclass of `Graph`. One possible workaround is to assign a namespace manager to...

I'm uncertain if this is a bug or just suboptimal behaviour right now, but PRs to get us closer to the standard behaviour will be welcomed.

@JervenBolleman I made a PR against your branch with some changes: https://github.com/JervenBolleman/rdflib/pull/5 One problem with taking translators as an argument to `SPARQLProcessor.__init__` is that it is a bit awkward to...

I will have to double-check how exactly this will be called then by passing it to the store, using just graph with the default store, however, the current approach requires...

> To not have to pass the processor as a positional arg on every query,: > > ```python > result = rdfs_graph.query(requested_query, processor) > ``` > > (If it isn't...