From: swedebugia@riseup.net
To: Roel Janssen <roel@gnu.org>
Cc: guile-user <guile-user-bounces+swedebugia=riseup.net@gnu.org>,
guile-user@gnu.org
Subject: Re: New library: guile-wikidata
Date: Thu, 13 Dec 2018 07:01:27 -0800 [thread overview]
Message-ID: <413312f3b999443b86b604ea9beff618@riseup.net> (raw)
In-Reply-To: <33b7a105-8529-1043-c5bd-5b7fccefc042@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]
On 2018-12-11 11:29, Roel Janssen wrote:
> On 11-12-18 01:32, swedebugia@riseup.net wrote:
snip
>> I now implemented sparql queries as well. See
>> https://gitlab.com/swedebugia/guile-wikidata
>>
>
> "guile-wikidata" looks cool! And I'm glad to see you've added SPARQL
> support as well. It would be great to integrate it with
> "guile-sparql" if you find the time for it. The "guile-sparql" code
> is quite short, and hopefully readable enough.. :)
Do you mean integrate only the SPARQL-part or the whole? I agree to the
first statement :) but the other wikidata specifics are perhaps better
kept on its own.
Actually the endpoint is a Blazegraph-server and my get-query code does
not seem to work right (see the bug mentioned in the latest commit).
Does guile-sparql work with Blazegraph? If yes we don't need the (buggy)
sparql-get-query-code I wrote.
I could not get it to work and rolled my own as a teach-yourself-scheme
learning-by-doing pet project :)
I tried with the file attached but got this because the driver does not
support URIs but only host, port, type, token:
...
In web/client.scm:
461:0 2 (http-post "http://http://query.wikidata.org/sparql:80…" …)
181:7 1 (open-socket-for-uri _)
In unknown file:
0 (getaddrinfo "http" "http" 0 #<undefined> #<undefined> #)
ERROR: In procedure getaddrinfo:
In procedure getaddrinfo: Name or service not known
>
> I've been working on a web interface to work with RDF/SPARQL (written
> mostly in Guile Scheme, which uses "guile-sparql" as well). You might
> find it interesting:
> https://github.com/UMCUGenetics/sparqling-genomics
>
> The Guile Scheme parts are in the "web" subfolder.
Thanks for the tip :)
Additionally I have a suggestion for guile-sparql. Could you generate a
pdf from the texi-manuel and include in the repo?
--
Cheers
Swedebugia
[-- Attachment #2: sdb-test.scm --]
[-- Type: text/plain, Size: 230 bytes --]
(use-modules (sparql driver)
(sparql lang))
(sparql-query
"SELECT ?item
WHERE
{
?item wdt:P31 wd:Q146.
}
LIMIT 10
"
#:host "http://query.wikidata.org/sparql"
;; #:port 80
#:type "text/xml"
;; #:token "..."
)
next prev parent reply other threads:[~2018-12-13 15:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5ffe968620f1d2d940b7db2b1900dc43@riseup.net>
2018-12-09 9:11 ` New library: guile-wikidata swedebugia
2018-12-09 11:08 ` tomas
2018-12-09 21:26 ` Arne Babenhauserheide
2018-12-11 0:32 ` swedebugia
2018-12-11 10:29 ` Roel Janssen
2018-12-13 15:01 ` swedebugia [this message]
2018-12-13 16:06 ` Trouble parsing a response (Was: Re: New library: guile-wikidata) swedebugia
2018-12-13 22:03 ` Roel Janssen
2018-12-13 22:29 ` Trouble parsing a response swedebugia
2018-12-14 15:59 ` Roel Janssen
2018-12-26 19:49 ` Trouble parsing a response (Was: Re: New library: guile-wikidata) swedebugia
2019-01-03 12:25 ` swedebugia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=413312f3b999443b86b604ea9beff618@riseup.net \
--to=swedebugia@riseup.net \
--cc=guile-user-bounces+swedebugia=riseup.net@gnu.org \
--cc=guile-user@gnu.org \
--cc=roel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).