282
Comment:
|
1469
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
See http://packages.qa.debian.org/common/RDF.html | See http://packages.qa.debian.org/common/RDF.html for the "RDF homepage" of the PTS. |
Line 5: | Line 5: |
''TBD'' | The PTS produces RDF descriptions (as RDF/XML) of Debian source packages (based on the same reference version as the PTS, i.e. usually the "latest" version in unstable). Every package has a "stable" reference RDF document available (through content-negociation) at the "same" place as the human-readable variant, at {{{http://packages.qa.debian.org/SRC_PACKAGE_NAME}}}. In practive, the HTML variant is generated (statically) by the PTS at {{{http://packages.qa.debian.org/PREFIX/SRC_PACKAGE_NAME.html}}} and the RDF variant at {{{http://packages.qa.debian.org/PREFIX/SRC_PACKAGE_NAME.rdf}}} (the {{{PREFIX}}} being computed depending on the source package name first letters. Content-negociation for RDF/XML is classically done with the {{{'application/rdf+xml'}}} content type requested (in the HTTP {{{'Accept'}}} header. To view the RDF/XML raw document, issue : {{{ $ curl -L -H 'Accept: application/rdf+xml' http://packages.qa.debian.org/SRC_PACKAGE_NAME}}} For other format, use rapper, for instance (from package 'raptor2-utils') : {{{ $ rapper -o turtle http://packages.qa.debian.org/SRC_PACKAGE_NAME}}} ''work in progress'' |
The PTS has a ?Linked Data / RDF interface.
See http://packages.qa.debian.org/common/RDF.html for the "RDF homepage" of the PTS.
The PTS produces RDF descriptions (as RDF/XML) of Debian source packages (based on the same reference version as the PTS, i.e. usually the "latest" version in unstable).
Every package has a "stable" reference RDF document available (through content-negociation) at the "same" place as the human-readable variant, at http://packages.qa.debian.org/SRC_PACKAGE_NAME.
In practive, the HTML variant is generated (statically) by the PTS at http://packages.qa.debian.org/PREFIX/SRC_PACKAGE_NAME.html and the RDF variant at http://packages.qa.debian.org/PREFIX/SRC_PACKAGE_NAME.rdf (the PREFIX being computed depending on the source package name first letters.
Content-negociation for RDF/XML is classically done with the 'application/rdf+xml' content type requested (in the HTTP 'Accept' header.
To view the RDF/XML raw document, issue : $ curl -L -H 'Accept: application/rdf+xml' http://packages.qa.debian.org/SRC_PACKAGE_NAME
For other format, use rapper, for instance (from package 'raptor2-utils') : $ rapper -o turtle http://packages.qa.debian.org/SRC_PACKAGE_NAME
work in progress
See http://www-public.it-sudparis.eu/~berger_o/weblog/2012/08/29/debian-package-tracking-system-now-produces-rdf-description-of-source-packages/ for more details.