Adds error recovery to the Turtle/TriG parser

[Tpt]

The Turtle/TriG parser should be able to continue parsing the next triples after raising an error.

[YruamaLairba]

i think it's also good idea to get content of a faulty triples when it's possible, this allow to guess what was the intention. As, concrete example, i encountered some ttl file using some undeclared prefix. Due to a specific context of use and very common usage in this context, those prefix could easily be guessed.

[andrefs]

The Turtle/TriG parser should be able to continue parsing the next triples after raising an error.

@Tpt Is this happening in the near future, or not something being tackled right now?

[Tpt]

@Tpt Is this happening in the near future, or not something being tackled right now?

I am currently rewriting the Turtle parser to fix that, improve performances and make it compatible with async so it should be done in a few months (it's a "background" project with a fairly low priority)

[andrefs]

Ah ok, I will look forward to that, thanks!