---
** [tickets:#7208] DOAP API for projects**
**Status:** open
**Labels:** doap allura-api
**Created:** Fri Feb 21, 2014 10:04 PM UTC by Dave Brondsema
**Last Updated:** Fri Feb 21, 2014 10:04 PM UTC
**Owner:** nobody
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). `<maintainer>` is
for each project Admin and `<developer>` 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 `<mailing-list>` entries and Files tool could provide a
`<download-page>` entry.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed
to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.