<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ticket search results</title><link>https://forge-allura.apache.org/p/allura/tickets/</link><description>You searched for labels:"doap"</description><language>en</language><lastBuildDate>Thu, 20 Aug 2015 22:07:00 -0000</lastBuildDate><item><title>DOAP API for projects</title><link>https://forge-allura.apache.org/p/allura/tickets/7208/</link><description>Create a [DOAP](https://github.com/edumbill/doap/wiki) API endpoint for allura projects.  I think the URL should be /rest/p/projectname?doap (open to better suggestions).  It should be XML that is similar in format to SourceForge (classic) DOAP files like https://sourceforge.net/api/project/name/vivo/doap as much as possible.  A number of fields in that are not applicable to Allura, so just don't include them.  It is okay for Allura DOAP to continue to use some of the "sf" namespace elements like environment, database, etc (those are all the trove types of a project), as well as sf:awarded (for awards, use the current Allura award system available via neighborhood admin pages).  `&lt;maintainer&gt;` is for each project Admin and `&lt;developer&gt;` is for each Developer on the project.

In addition to the basics, each tool should be able provide its own XML/RDF data to include.  For example, SourceForge's internal mailman tool could provide `&lt;mailing-list&gt;` entries and Files tool could provide a `&lt;download-page&gt;` entry.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:00 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7208/</guid></item></channel></rss>