Open patzomir opened 7 years ago
In the file "xsparql.xquery" commenting lines 196 and 197 fixes this issue. xs:anyURI should already cover all valid URIs .
(: else if (fn:starts-with(xs:string($Node), "https://") or fn:starts-with(xs:string($Node), "http://") or fn:starts-with(xs:string($Node), "mailto:") or fn:starts-with(xs:string($Node), "file:")) :) (: then _xsparql:_binding("_sparql_result:uri", $label, "", "") :)
The commented out lines are in _xsparql:_binding_term
here:
(: else if (fn:starts-with(xs:string($Node), "https://") or fn:starts-with(xs:string($Node), "http://") or fn:starts-with(xs:string($Node), "mailto:") or fn:starts-with(xs:string($Node), "file:")) :)
(: then _xsparql:_binding("_sparql_result:uri", $label, "", "") :)
@zacharywhitley Close this issue: it was fixed around Jan 2017. It was not picked up in the Feb 2019 release 1.1 but will be if you do #46.
The program guesses wrong whether an object is to be inserted as URI. Example: "http:\my.com Link to my site" will be converted to <http:\my.com Link to my site>, thus making the output turtle file incorrect.