Replace most instances of HDF Kita with HDF REST API

Remove unnecessary doc files that don't relate to REST API itself

Author: jhendersonHDF

AdminTools.rst

@@ -4,7 +4,7 @@ Authorization and Authentication
 
 Request Authentication
 -----------------------
-HDF Kita supports HTTP Basic authentication to authenticate users by comparing an encrypted 
+The HDF REST API supports HTTP Basic authentication to authenticate users by comparing an encrypted 
 username and password against a value stored within a password file.
 
 If neither the requested object (Group, Dataset, or Committed Datatype) nor the object's root group
@@ -36,11 +36,4 @@ If the authorization string is validated, the server will verify the request is
 per the object's ACL list.  If not authorized a http status 403 - Forbidden will be returned.
 
 
-User IDs and passwords
-----------------------
-
-User IDs and passwords are maintained in a plaintext file: 
-``admin/config/passwd.txt``.
-
-
 

Authorization.rst

@@ -2,10 +2,10 @@
 Common Error Responses
 ***************************
 
-For each request, HDF Kita returns a standard HTTP status code as described below.
+For each request, the HDF REST API returns a standard HTTP status code as described below.
 In general 2xx codes indicate success, 3xx codes are returned for some form of redirection,
 4xx codes are returned for a client error, and 5xx codes are returned for server errors. 
-In addition to the numeric code, HDF Kita will return an informational message as part of
+In addition to the numeric code, the HDF REST API shall return an informational message as part of
 the response providing further information on the nature of the error.
 
  * ``200 OK`` - The request was completed successfully
@@ -17,6 +17,5 @@ the response providing further information on the nature of the error.
  * ``405 Method Not Allowed`` - The HTTP request type was not valid for the given resource (e.g. ``PUT /datasets/<id>/type``)
  * ``409 Conflict`` - This error is used with PUT requests where the resources cannot be created because there is an existing resource with the same name (e.g. PUT / where the requested domain is already present).
  * ``410 Gone`` - The resource requested has been recently deleted.
- * ``413 Selection Too Large`` - This error is used when the selection within a dataset encompasses too large of an area of data for the server to accept/return.
  * ``500 Internal Error`` - An unexpected error that indicates some problem occurred on the server.
  * ``501 Not Implemented`` - The request depends on a feature that is not yet implemented.

COPYING

@@ -2,7 +2,7 @@
 Common Request Headers
 ***********************
 
-The following describe common HTTP request headers as used in HDF Kita:
+The following describe common HTTP request headers as used in the HDF REST API:
 
  * Request line: The first line of the request, the format is of the form HTTP verb (GET, PUT, DELETE, or POST) followed by the path to the resource (e.g. /group/<uuid>.  Some operations take one or more query parameters (see relevant documentation)
  * Accept: Specifies the media type that is acceptable for the response.  Valid values are "application/json", and "*/*.  In addition, GET/PUT/POST Value (see :doc:`DatasetOps/GET_Value`, :doc:`DatasetOps/PUT_Value`, :doc:`DatasetOps/POST_Value`) support the value "application/octet-stream"

CommonErrorResponses.rst

@@ -2,7 +2,7 @@
 Common Response Headers
 ***************************
 
-The following describes some of the common response lines returned by HDF Kita.
+The following describes some of the common response lines returned by the HDF REST API.
 
  * Status Line: the first line of the response will always be: "``HTTP/1.1``" followed by 
     a status code (e.g. 200) followed by a reason message (e.g. "``OK``").  For errors, 

CommonRequestHeaders.rst

@@ -2,12 +2,13 @@
 Domains
 #######################
 
-In HDF Kita, domains are containers for a related collection of resources, similar to a
-file in the traditional HDF5 library.  In the HDF Kita implementation of the HDF5 REST API,
+In the HDF REST API, domains are containers for a related collection of resources, similar to a
+file in the traditional HDF5 library.  In the HDF Kita implementation of the HDF REST API,
 domains *are* files, but in general the HDF REST API supports alternative implementations 
 (e.g. data that is stored in a database).
 Most operations of the service act on a domain resource that is provided in 
 the *Host* http header or (alternatively) the Host query parameter.
+TODO: X-Hdf-domain header, domain/host query parameter
 
 Mapping of file paths to domain names
 -------------------------------------

CommonResponseHeaders.rst

@@ -2,7 +2,7 @@
 Hypermedia
 *************************
 
-HDF Kita supports the REST convention of **HATEOAS** or *Hypermedia as the Engine of 
+The HDF REST API supports the REST convention of **HATEOAS** or *Hypermedia as the Engine of 
 Application State*.  The idea (see http://en.wikipedia.org/wiki/HATEOS for a full 
 explanation) is that each response includes links to resources related to 
 the requested resource.
@@ -35,7 +35,7 @@ a JSON array.  Each array element has a key: ``href`` - the related resource, an
     
 This enables clients to "explore" the API without detailed knowledge of it.
 
-This is the list of relations used in HDF Kita:
+This is the list of relations used in the HDF REST API:
 
  * attributes - the attributes of the resource 
  * data - the resource's data (used for datasets)