Changes between Version 2 and Version 3 of HackageDB/2.0/URIs

Timestamp:

05/30/10 10:08:18 (3 years ago)

Author:

mgruen

Comment:

fix bad phrasing

HackageDB/2.0/URIs

@@ -76 +76 @@
 
 == Content types ==
-Except for the cabal and tarball files, all of the above URIs will either serve an HTML content-type, and POST requests will either be submitted as multipart/form-data or application/x-www-form-urlencoded. To use a different format, for example JSON, either send an Accept: application/json header, or indicate the format in the URL. This may be a simple ?format=json query, or a .json extension to any URL (see [http://code.reddit.com/wiki/API#FetchingInformation Reddit's API] for explanation).
+Except for the cabal and tarball files, all of the above URIs will serve an HTML content-type, and POST requests will be submitted either as multipart/form-data or application/x-www-form-urlencoded. To use a different format, for example JSON, either send an Accept: application/json header or indicate the format in the URL. This may be a simple ?format=json query, or a .json extension to any URL (see [http://code.reddit.com/wiki/API#FetchingInformation Reddit's API] for explanation).
 
 == User groups ==
-I'm leaning towards having a relatively decentralized set of user groups. So you can view a given user group for a given resource at <resource>/<groupname>, and PUT or DELETE at <resource>/<groupname>/<username> so long as the user exists and, for DELETE, is already in the group.
+I'm leaning towards having a relatively decentralized set of user groups. So you can view a given user group for a given resource at <resource>/<groupname>, and PUT or DELETE at <resource>/<groupname>/<username> so long as the user exists, deleting only if already in the group.
 
 == HTTP methods ==