-
Notifications
You must be signed in to change notification settings - Fork 35
UTF-8 is not supported? #26
Comments
Hi @migalkin, no, it means that the dataset was wrongly encoded. Note that
is an invalid URI in Turtle syntax; it should be
My guess is that on the server side, you have used an HDT file to serve LinkedMDB? And that this HDT file was generated with |
Thank you @RubenVerborgh |
Excellent 😄 |
=> Do double check whether all the triples you want are in there though (i.e., |
@RubenVerborgh actually you are right, the dump created with the broken NT parser created an HDT file with all the triples from the LinkedMDB dump, but So what I do:
Then running hdtInfo:
The original linkedmdb dump has:
The problem is that HDT parser doesn't produce any error and writes that the file has been created successfully. |
Yes, I just fixed that in rdfhdt/hdt-cpp@d3b02a9 The solution is to ensure that the input file is valid, by passing it through a tool such as SERD first. |
@RubenVerborgh I used those regexps we found before to clean the entire LinkedMDB and retain all the triples, so that SERD and HDT parser never throw an error, so the parsing went fine. |
Not a server issue, but possibly an outdated HDT-Node version. Can you post your HDT file somewhere so I can check? |
Never mind, I found a testcase myself. On it. |
@migalkin I found the bug and proposed a fix: rdfhdt/hdt-cpp#43 Summary: you built your HDT file using the latest |
@migalkin This bug is now fixed; the laster version of hdt-cpp now generates compatible HDT files again. |
@RubenVerborgh great, thanks for the update |
I have a Fedbench query CD4:
which has been rewritten to execute the following triple pattern against LinkedMDB endpoint in LDF server:
The Client throws the error:
Does it mean that LDF Client does not support UTF-8?
The text was updated successfully, but these errors were encountered: