Hi. Arno Töll <a...@debian.org> writes:
> The RDF pages for a package in the BTS contains lots of You mean PTS, right ? > machine-readable information about the package. However, it misses the > information from the versions column (i.e. the current version of a > package told apart per suite). It would be super handy to have that > information encoded in XML as well. What kind of use case do you have ? I have thought about adding these kind of meta-data, but haven't yet tackled the problem. Do you know an existing ontology that could be used to link this version information to the existing RDF content ? I'd suggest a Turtle example (see http://www-public.telecom-sudparis.eu/~berger_o/weblog/2012/08/29/debian-package-tracking-system-now-produces-rdf-description-of-source-packages/ for details on how to generate one using rapper) for the sake of readability. > > This should be a fairly simple patch for those of whom the PTS code is not a > complete mystery (like it is for me). Essentially this would mean, that we'd > have > a (somewhat) easy readable method to retrieve the most current version of a > package in our suites. Depending on the use case, you may be interested in the SOAP interface of the PTS also : see http://packages.qa.debian.org/common/index.html for pointers. Best regards, -- Olivier BERGER http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87obiok01x....@inf-8657.int-evry.fr
