I'm terribly sorry, this mail was miscategorized in my overcrowed
mailbox (too many mailing-lists ;] ), so I only just now read it. Is
this still relevant for you?
It sounds like your callback returns a str, it must be an URIRef
instance. This is something I hope will be fixed in RDFLib: there
should be type assertions in the core of it since issues like this
comes up a lot (because all parts of a triple must be of type
Identifier (the base class of Literal, URIRef and BNode), but rdflib
graphs accept "raw" values as input).
(Without a callback, graph.absolutize(filepath) is used.)
.. In regard to your suggestion to give the graphs.py to rdflib -
you're probably right, it's general enough to fit there (after some
cleanup perhaps). I haven't had time to spend on either oort nor
rdflib the last couple of months I'm afraid, but I hope to do so - and
then contribute more to RDFLib 3.0 which I've spoken some to Daniel
about.
Best regards - and again apologies for the long overdue reply,
Niklas