Dear rdflib manitainers,
I am a user of rdflib. When I use rdflib.Graph to parse one .nt file, the terminal output is
rdflib.exceptions.ParserError: Invalid line: http://dbpedia.org/resource/2015_African_Rugby_Under-19_Cup_Division_"A" .
While I remove the double quotations of ”A", i.e., "A" -> A，the program is OK. I want to know if there are other ways to parsing the .nt file rather than remove the double quotations of ”A".
Thanks a lot.
Yours Sincerely.
Appendix
Data{ <a:> http://www.w3.org/2002/07/owl#sameAs http://dbpedia.org/resource/2015_African_Rugby_Under-19_Cup_Division_"A" .}
Code{
from rdflib import Graph
g = Graph()
g.parse("./data/example.nt")
print(f"Graph g has {len(g)} statements.")
print(g.serialize(format="turtle"))
}
Looks like a problematic URL for dbpedia. With, or without the double qutoes, that dbpedia URL returns a “301 See other” and the relocate is
https://dbpedia.org/resource/2015_African_Rugby_Under-19_Cup_Division_%22A%22- which itself fails to resolve. OTOH, wikipedia returns a corresponding redirect https://en.wikipedia.org/wiki/2015_African_Rugby_Under-19_Cup_Division_%22A%22 which is found. The dbpedia page is essentially blank, it has none of the info for that entry on wikipedia.
1 reply
@greattang123 https://gitlab.com/aucampia/incubator/-/blob/master/osdu-ld/tools.py/src/osdu/ld/util.py#L143 < nasty code, but that is one place where I used it
Hi! I would love to get feedback on: RDFLib/rdflib#1396
I am moving forward with my Oxigraph project (https://github.com/oxigraph/oxigraph) and I would love to be able to provide a fast rdflib store based on it.
I am moving forward with my Oxigraph project (https://github.com/oxigraph/oxigraph) and I would love to be able to provide a fast rdflib store based on it.
The task description a bit convoluted. I can work to make it clearer if needed
I'm working in that area atm, trying to progress the "identifier-as-context" issue that's been extant since 2010 or thereabouts and which has had a couple of implementations, the last one being oohlaf's PR of RDFLib/rdflib#958. It's looking reasonably good thus far but there's a coupla aspects I'm not sure about but may just be down to terminological inexactitude - f'rinstance https://github.com/RDFLib/rdflib/blob/9379a69d6ec6e18819aa0c5a0d54849e7abb8223/rdflib/graph.py#L1558 where
ConjunctiveGraph binds a Graph to the instance variable self.default_context.
should prbbably do it anyway
's not my primary dev env, I'm on Mint and Python 3.9. I have an up-date-ish Win10 VM but that's running Python 3.10, so for modularity, I've just reinstated an old Windows10 VM and installed 3.8 on it. I also have Big Sur on a VM so I can investigate any MacOS-specific issues.
If only they helped with brain farts :(
Will do, grateful for the offer. If that approach can be made to work, it'll relieve a particular pain point: ConjunctiveGraph.parse() creates a Graph to handle the parsing and has a profoundly-unwanted side-effect creates a BNode in the Store's contexts, which screws things up from the Dataset side.
is there a test to reproduce? Maybe I can write one
I pared it all down to just the rebased PR plus the changes from your commit and a file of tests which I took from my alternate thread of work - which preserves the original approach of using a Graph for parsing. https://github.com/DOACC/rdflib/tree/identifier-as-context
In another repos (https://github.com/gjhiggins/rdflib/tree/identifier-as-context), I have a way more extensive re-working (tbh, it's a something of an ad hoc mess, very much a cluttered workbench because of the extensive impact of the changes but the tests are keeping me fairly straight). There are a number of issues that are pertinent and serve to set the scope of the changes required to make the result coherent. The core dataset test file is
test_dataset_default.py, it exercises the three aspects of dataset functionality, direct manipulation with Python, indirect manipulation via RDF input and indirect manipulation via SPARQL update. (I've also had to keep the ConjunctiveGraph in lockstep because of Dataset's inheritance of that class). There are two main working outputs test_dataset_anomalies.py and test_dataset_anomalies_resolved.py, there's also test_dataset_anomalies_wip.py and test_dataset_graph_ops.py both for work-in-progress on different aspects of the subject. Apologies for the mess but I've completely failed to be able to reduce it to a logical sequence of changes.
sorry been a bit swamped @gjhiggins
Very nice, my inbox is full of messages from you. I hope someone will finf time to go through it.
but I can't recall it now
doing a review of this now: RDFLib/rdflib#1646
@aucampia Dunno if it's worth it really, all I intended to do oriignally was rebase oohlaf's rebase of gromgull's original PR. Problem is that it doesn't work, so I thrashed around for a while trying to find a means of getting it to work without a major rewrite, found soemthing that works but without the rewriting of the parsers, it's bound to be crude.
The only actual up side is the raft of extant issues that get resolved but some of them date back years, so the implication is that they're not exactly showstoppers/
@gjhiggins there are some minor changes intermixed with your PR that is very uncontroversial and safe, like
$ git diff origin/master -- rdflib/util.py
diff --git a/rdflib/util.py b/rdflib/util.py
index 7318dcc3..c98dfdac 100644
--- a/rdflib/util.py
+++ b/rdflib/util.py
@@ -364,6 +364,7 @@ SUFFIX_FORMAT_MAP = {
"html": "rdfa",
"svg": "rdfa",
"nq": "nquads",
+ "nquads": "nquads",
"trig": "trig",
"json": "json-ld",
"jsonld": "json-ld",
Would you mind if I slice these off and make seperate PRs, will keep your commits but basically just take slices of it, will make an example to show you.
No need for example