[Debwebid-discuss] rdf coordination

[Iain R. Learmonth]

Hi,

On Wed, Aug 12, 2015 at 11:13:15PM +0200, chrysn wrote:
> One aspect would be how we can offer the data we're accumulating. Iain
> has mentioned issues with the dataset growing out of hand, so how can we
> serve it? Should we at all collect it in a single place, or have (in the
> spirit of the diverse services that are not UDD) the information spread
> breadcrumb style over the services? Can we, then, still offer it as a
> dump download and/or a SPARQL endpoint?

For some services it may be possible to provide a SPARQL endpoint. It got
out of hand extremely quickly when I added triples to represent package
inter-dependencies (over 40GB of rdflib graph followed by a crash). There is
no reason to avoid placing this data into UDD, and the aim should be to
place them into UDD.

> Once we collect the information, what can we offer (at least in the
> style of a demo) where the linked data nature of it can be leveraged?
> (Everything that only queries Debian internal data can be queried from
> UDD as well, and SPARQL might or might not be a more accessible approach
> than SQL on UDD). Which systems can we mash it up with? PyPI?

rdf.debian.net links to CPAN and PyPI currently. See:

  http://rdf.debian.net/project/librdf-linkeddata-perl.html

Another thing I've been considering is XMPP pubsub with RDF as me and pocock
have been talking about an XMPP service for Debian Developers, but I haven't
got much futher than that so far.

Thanks,
Iain.

-- 
e: irl at fsfe.org            w: iain.learmonth.me
x: irl at jabber.fsfe.org     t: EPVPN 2105
c: 2M0STB                  g: IO87we
p: 1F72 607C 5FF2 CCD5 3F01 600D 56FF 9EA4 E984 6C49
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/debwebid-discuss/attachments/20150812/ebb81745/attachment.sig>