-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ignoring unknown fields in QALD #69
Conversation
ignores unknown fields while reading the QALD json
Huh, can you show me the json line where it happens? I wasn't aware of a new field (/CC @xixi019 ) |
I do not know if this is it but these, Xi, should also be removed from https://raw.githubusercontent.com/KGQA/QALD_10/main/data/qald_10/qald_10.json
|
For example (do not mind the wrongly predicted sparql ;) ):
|
Ah, that happens in the training file (/CC @Perevalov )I would say, we can safely ignore it. Aleksandr, what do you think? |
From the example by @nikit91, I understood that the: "distinct": false,
"ordered": true, and "datatype": "http://www.w3.org/2001/XMLSchema#integer", is something that should be ignored? If yes, then I agree. It does not affect anything. |
Perfect, so let's go ahead here and resolve the QALD-10 test issue (empty answers in the repo). |
It would be nice to have this fix for GERBIL QA. 😉 |
Erm...no, I am not foreseeing working on this repo anytime soon actually. But as far as I know, you could also mvn deploy it to archiva (honestly, I do not even have the keys anymore due to laptop changes) |
Hi @RicardoUsbeck,
Is it fine if we just ignore the unknown fields in the QALD format?
I recently faced a problem where the query results from the dbpedia endpoint introduced new fields which were not part of the
QALD format previously. However, these newly introduce fields do not affect the existing expected functionality and can be ignored. Below is the stacktrace for the problem:
What is your opinion of this?