Competing ontologies

• EvoOnt developed at the University of Zürich, in Switzerland, contains a very complete description of relations for what baetle is trying to do. This ontology is now on baetle server, available to be edited and improoved, with the approval of the University of Zurich, who have joined the mailing list, as owners of course.

Listed here are some ontologies that we should look at and work with

• FOAF: The Friend of a Friend Ontology is very important to identify people and relations between them
• DOAP: To describe bugs the Description of a Project ontology is clearly very handy. Local UML diagram at: DoapOntology
• SKOS: there are many ways of organising projects and classifying bugs. The SKOS ontology gives a very lightweigh way of creating metadata for wiki powered ontologies that are project specific, without requiring a full blown ontology such as this one to be designed.
• WorkFlowOntology: Tim Berners Lee wrote out a WorkFlowOntology. Bugs affect workflows. They are in certain states and can have state transitions.
• SIOC Semantically Interlinked Online Communities. We have a bug tracking community to interlink here. Things get Posted to Issues too.
• dcterms: Dublin Core Terms. Very basic but useful vocabulary. Namespace: http://purl.org/dc/terms/

Suggested one we can work with or should be compatible with

• Project Vocabulary Danny Ayers started a Project Vocabulary. Software projects are projects, so this looks useful.
• AtomOwl When looking at bug reports such as Netbeans bug id 21365 the bug looks very much like a feed, with the comments looking very much like entries. It also seems obvious that one could use the Atom Publication Protocol to publish replies to a bug or to create new issues.
• Tag Ontology every bug system allows one to assign keywords to bugs. Keywords are similar to tags which are similar to Atom Categories as argued in Folksonomies, Ontologies and Atom
• MetaLink has an xml format for helping mirroring of downloads and helping clients selecting the best mirror. twanj is working on an Ontology for it.
• Web Archictecture very helpful vocabulary. It would be nice to have it backed by a standards body.
• Test Metadata a w3c approved rdf vocabulary for describing tests
• EARL Evaluation and Report Language, a w3c approved ontology to test resources (could tie test classes to source code?)
• Plans Ontology (the rdf/xml is broken) How does this relate to the WorkFlowOntology?