On Sep 14, 2014 1:11 PM, "Jean-Marc Vanel" <[email protected]> wrote:
>
> How to reproduce :
>
> wget --header='Accept: text/turtle' http://dbpedia.org/resource/Buddy_Guy
>
> /opt/eye/bin/eye.sh Buddy_Guy
> Id: euler.yap 7330 2014-07-07 22:35:19Z josd
> SWI-Prolog 6.6.6 (amd64): May 28 2014, 12:10:55
> starting 40 [msec cputime] 38 [msec walltime]
> ** ERROR ** file:///home/jmv/src/eulergui-code/eulergui/Buddy_Guy **
illegal_token(char_code(«,171),line(50))
>
> That was with Euler, a well maintained RDF tool [
http://eulersharp.sourceforge.net/ ] .
>
> Apache Jena says the same thing :
>
> java -cp $JENA_JAR riotcmd.riot http://dbpedia.org/resource/Buddy_Guy
> ERROR [line: 50, col: 13] Unknown char: «(171;0x00AB)
>
> What we have at line 50 is :
>
> ns23:Джордж_«Бадди»_Гай owl:sameAs dbpedia:Buddy_Guy .
Ough. It's the old incompatibility between XML names and IRIs. I didn't
know the problem also occurs in Turtle, thought it was just RDF/XML...
The character is legal in IRIs, but not in Turtle prefixed names, because
the latter are a superset of XML QNames:
http://www.w3.org/TR/turtle/#sec-iri
Euler and Jena are right, Virtuoso is wrong.
I can think of two solutions: Virtuoso could use the full IRI
<http://..._«Бадди»_Гай>
instead of the prefixed name. Or it could choose a prefix that includes the
character, e.g. with prefix n24=<http://..._«Бадди»_>, the subject becomes
ns24:Гай .
Regards,
JC
>
>
>
> --
> Jean-Marc Vanel
> Déductions SARL - Consulting, services, training,
> Rule-based programming, Semantic Web
> http://deductions-software.com/
> +33 (0)6 89 16 29 52
> Twitter: @jmvanel , @jmvanel_fr ; chat: irc://irc.freenode.net#eulergui
>
>
------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
>
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Dbpedia-discussion mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
>
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Dbpedia-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
