From: swedebugia <swedebugia@riseup.net>
To: Guix-devel <guix-devel@gnu.org>
Subject: Guix Wikidata module - next steps
Date: Tue, 08 Jan 2019 12:29:09 +0100 [thread overview]
Message-ID: <0BD0CA1F-AF8F-4584-969E-5C9A2D78E768@pretty.Easy.privacy> (raw)
In-Reply-To:
[-- Attachment #1.1: Type: text/html, Size: 3427 bytes --]
[-- Attachment #1.2: Type: text/plain, Size: 2758 bytes --]
Hi
I started today writing a new module and would like to share my ideas with you.
Feel free to add your ideas too!
I imagine it as an utils collection for a wd importer (correlate the two) and a wd exporter that can push e.g. version updates, synopsis and descriptions and whole new entries to wd.
Steps:
First thing to add is the procedures from guile-wikidata that enables us to get a label for a given Qid and the output of queries like the one below.
The second thing to add is fold procedures to guess the right qid according to the upstream names of guix packages.
The third thing to add is an importer that helps us add qid to our packages.
Here we have a decision to make. Should we add them as properties or extend our record with a field?
I.e.
...
(properties
`((wikidata . "qid"))
Or
...
(wikidata "qid")
I prefer the latter because I find it more easily handled.
Upstreaming and FSD:
Personally I would like to see new properties on wd making it possible for them to hold all our synopses and descriptions.
Guix is quickly growing towards becoming the largest general repository of free software with these details.
Writing this I have not forgotten the FSD, but it is in my view not a good approach to the "problem" of providing and curating a free software only repository. For one thing it seems to lack proper APIs. Also it does not have the traction, manpower and programming features of wd or guix. It is obsolete.
I beleive we could generate a much better read-only FSD rather easily with guile from guix and wd and tell users some place to report errors and contribute corrections (preferably directly on wd).
This said, One thing we currently miss that FSD recently got is an importer based on the Mozilla API to import add-ons.
I believe we will soon have 1000+ npm packages imported as well. I did a little comparison of FSD vs WD earlier and the result was that only a few of the most prominent npm packages are in either of the databases.
--------
Here comes a little statistics about wd:
The query below lists all software on wikidata.
Of the millions of software out there WD currently have only 14686 entries.
Of these not all are correctly tagged correctly e.g. free software tagged instance of "software".
https://query.wikidata.org/#SELECT%20%3Fsoftware%20%3FsoftwareLabel%20WHERE%20%7B%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%20%20VALUES%20%28%3Fv%29%20%7B%0A%20%20%20%20%28wd%3AQ506883%29%0A%20%20%20%20%28wd%3AQ341%29%0A%20%20%20%20%28wd%3AQ7397%29%0A%20%20%7D%0A%20%20%3Fsoftware%20wdt%3AP31%20%3Fv.%0A%7D%0ALIMIT%2050000
--
Sent from my p≡p for Android.
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 3825 bytes --]
next reply other threads:[~2019-01-08 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 11:29 swedebugia [this message]
2019-01-08 17:25 ` Guix Wikidata module - next steps Ludovic Courtès
2019-01-09 6:15 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0BD0CA1F-AF8F-4584-969E-5C9A2D78E768@pretty.Easy.privacy \
--to=swedebugia@riseup.net \
--cc=guix-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.