Notation 3 support

[Gregory Williams]

On Jul 2, 2010, at 6:34 PM, Toby Inkster wrote:

> Property paths are definitely needed for this. N3 property paths are
> not the same as in SPARQL - they're a simpler thing that only need to
> be dealt with in the parser; not the model.

Ah, yes. Sorry, wasn't thinking when I wrote that.

> By the way, the Notation 3 parser is a subclass of the Turtle parser.
> It overrides tonnes of its parent class' private methods. How safe is
> this? Are the internals of the Turtle parser likely to change much?

Very unsafe, and very likely to change :) If you've ever tried to use the turtle parser, you might have noticed it's abysmally slow. I've been meaning to rewrite the whole thing which will absolutely break the N3 parser whenever I get around to it. But when that happens, we can work to either merge the old Turtle parser code with the N3 parser or convert it to rely on the new Turtle code.

.greg