Hi guys, I'm working on a N3 file to represent some edges of a graph:
This file doesn't validates because of the "%28" symbol. I tried to replace it with "Bench_(furniture)" and it doesn't work either.
Besides, when I parse it with JENA, the symbol "=" is not valid, although is valid in N3.
Any idea? Mulone
asked 28 Mar '11, 12:37
Section 6.4 of RDF concepts strongly discourages the use of percent-encoding in RDF URI references:
You might also be interested in this very long thread on URI equivalence.
Obviously, this doesn't help you when someone else has already created them. As far as I can tell, the non-percent-encoded versions are the canonical ones in use by DBpedia.
The Turtle spec (more on why-turtle-and-not-N3 soon) doesn't allow parentheses in the local part of a qname, so you're going to have to use use the whole URI between angle brackets.
The '=' won't work as Jena's Notation3 is actually just a Turtle parser that claims to handle Notation3 as a convenience. I've previously run into a similar issue with triple-quoted strings (which are also valid N3 but not Turtle). You can get round it by simply replacing '=' with the more verbose owl:sameAs. This issue in their SourceForge issue tracker gives a bit more context.
answered 28 Mar '11, 14:21
See the response by @Alexander. I tried double checking your N3 with a validator. The validator at rdfabout.com seems to agree with Jena, it gives:
And if you use unencoded parantheses you get:
And if you remove the parantheses all together it validates fine.
answered 28 Mar '11, 14:30