Recently Ross wrote an excellent document on DOAP and it got me thinking about what other kinds of things people are likely to be doing with DOAP and what best-practises there were out there that we could copy.

DOAP (Description Of A Project) is a vocabulary for describing projects (particularly open source projects) using RDF (Resource Description Framework) Essentially it is a set of objects to be used in RDF logical triples, allowing websites, mailing lists, bug tracking databases and similar to be specified. DOAP can be freely mixed with other vocabularies, such as FOAF (Friend Of A Friend) is a set of objects and verbs to describe people and their connections.

There are a couple of interesting DOAP files with novel features (or novel to me, anyway). Common characteristics of these files are that they're generated by RDF aware people (first language speakers of RDF/DOAP if you like) and that they're hand crafted by members of the project (who're in a position to know a maximal amount about the project).

One problem with having a single DOAP file for an open source project, is that it assumes that a single entity (i.e. the entity that generated the DOAP file) knows everything that is useful to know about the project. One way of overcoming this problem is by linking to a surrogate elsewhere that other entities can add information too. A candidate for this is an RDF-aware wiki such as

SIOC (Semantically-Interlinked Online Communities) seems like an obvious place to start looking at describing a community in RDF it focuses on describing blogs, wikis, mailing lists and forums. DOAP specifies tags such as <Repository>, <mailing-list>, <wiki>, <bug-database> and <screenshots> which point to content structured in ways could be described using <sioc:Post>s.

OSSWatchWiki: DOAPThoughts (last edited 2013-04-15 13:56:23 by localhost)

Creative Commons License
The content of this wiki is licensed under the Creative Commons Attribution-ShareAlike 2.0 England & Wales Licence.

OSS Watch is funded by the Joint Information Systems Committee (JISC) and is situated within the Research Technologies Service (RTS) of the University of Oxford.