Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guessing for URI #16

Open
patzomir opened this issue Jan 16, 2017 · 3 comments
Open

Guessing for URI #16

patzomir opened this issue Jan 16, 2017 · 3 comments
Labels

Comments

@patzomir
Copy link
Contributor

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.

@patzomir
Copy link
Contributor Author

patzomir commented Jan 17, 2017

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, "", "") :)

@VladimirAlexiev
Copy link
Contributor

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, "", "") :)

@VladimirAlexiev
Copy link
Contributor

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants