incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cory Johns" <>
Subject [allura:tickets] Re: #7208 DOAP API for projects
Date Wed, 05 Mar 2014 21:00:44 GMT
I was suggesting allowing `Accept:` in addition to specifying the format in the URI, but I
doubt it's worth bothering with.

Regarding `.doap` vs `?doap` (or `?format=doap`), I read an argument that `.doap` is significantly
"worse" because the URI no longer identifies a resource, but a format / encoding of a resource.
 But we do have precedent for it, as I noted.

I'm not really keen on modifying the `NeighborhoodRestController._lookup` (which is where
I think it would need to go to work) with code specific to the format of a single view, even
if the code itself is relatively simple.  It also raises the question of what happens when
someone requests (which, again, indicates that the
URI should identify the resource, irrespective of format).


** [tickets:#7208] DOAP API for projects**

**Status:** in-progress
**Milestone:** forge-backlog
**Labels:** allura-api 42cc doap 
**Created:** Fri Feb 21, 2014 10:04 PM UTC by Dave Brondsema
**Last Updated:** Mon Mar 03, 2014 08:45 PM UTC
**Owner:** nobody

Create a [DOAP]( 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
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 because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message