SegFault on TTL that has PREFIX lines mixed into "data" lines

[markwilkinson]

Hi Gregg

I believe this is an rdf-raptor problem, but I can't quite track it down precisely.

I have Turtle being sent to me by an LDP server. It has a few lines of @Prefix, then a few lines of data, then a few more lines of @Prefix and so on. No line of data uses a prefix before it is defined, so the TTL appears to be valid; however, when I parse it using the raptor library, I get a segfault. If I reorder the lines to push the prefixes to the top, the segfault goes away.

My "patch" to get around the problem is not a good idea, since Turtle allows PREFIXes to be redefined at any point in the document, so by pushing them to the top, I am potentially breaking the data.

Suggestions? Am I sending this bug report to the right place?

Cheers!

[TallTed]

This link to the initial discussion of this issue may be helpful to @gkellogg et al.

That said, as I read things, this issue probably lies in the raptor library from @dajobe on which rdf-raptor depends, but I'm not quickly finding how/where to log an issue on raptor itself (possibly here?).