Every Debian source package, which used to have an HTML page like
http://packages.qa.debian.org/packagename now has a corresponding RDF/XML document available provided that the
application/rdf+xml content-type is required (the HTTP client being redirected to the proper HTML or RDF document).
The main objective is to try and produce (closest as possible from the source, at debian.org) an authoritative description of Debian’s packages in an interoperable format (RDF using the ADMS.SW 1.0 ontology).
Thus, each package in Debian can be identified on the Semantic Web with a unique URI like
http://packages.qa.debian.org/apache2, which is dereferenceable as RDF.
You can see an example of such an RDF representation for the
apache2 source package in trying (with the ‘raptor2-utils’ package installed):
$ rapper -o turtle http://packages.qa.debian.org/apache2
For more details about the underlying format see a raw RDF/XML dump :
$ curl -L -v -H 'Accept: application/rdf+xml' http://packages.qa.debian.org/apache2
Any Semantic Web application can then reference that resource, which becomes part of the Linked Open Data cloud.
There are probably lots of uses that could emerge from this, but the immediate I can think of is the matching of Debian packages with other packages/projects (upstream, downstream, other dists) in an interoperable way (see other projects like distromatch, etc.). At the moment, the
doap:homepage of the upstream
SoftwareProject resources generated by the PTS can be such a simple matching key (it’s actually much more complex than that, but will be the topic of further efforts).
AFAICT, this is the first large deployment of an ADMS.SW 1.0 implementation. On my machine, I’ve counted almost 1.5 million triples generated.
Stay tuned for more installments on similar topics.