We’ve been working on modeling bug reports properties for quite a long time, but never managed to stabilize an ontology specification. Better late than never, here’s our first proposed draft and our request for comments :
More details in the helios project’s blog :
To summarize some ideas and try and promote the work we’ve done in the frame of Helios, we’ve submitted a short paper (PDF) to the triplification challenge.
Alas, others had better projects, and we didn’t win, apparently. Still, we’ll continue to work beyond these initial demonstrators, in order to try and push for a standard of interchange of “facts” / meta-data about bugs, for instance as RDF using the EvoOnt BOM ontology plus our extensions.
The paper describes the 2 first demonstrators that we’ve setup (and for which I previously blogged) : one for the triplification of bugzilla, and one for the triplification about Debian bugs, using UDD to do so.
Abstract: To interconnect bugtrackers, and especially the one used to manage free
software projects, one need tools to convert their custom format to a common interop-
erable form. We, in the context of the Helios project, are working on refining existing
ontologies to describe bugs from the most used bugtrackers in open source software. We
propose two prototypes for review, based on triplify and EvoOnt BOM, which export
bugs from bugzilla installations and Debian’s UDD in the form of RDF triples.
Read the rest in “Bugtrackers triplification” (PDF)