diff --git a/hapi-dev/HAPI-data-access-spec-dev.md b/hapi-dev/HAPI-data-access-spec-dev.md index 524fe0f..d298bef 100644 --- a/hapi-dev/HAPI-data-access-spec-dev.md +++ b/hapi-dev/HAPI-data-access-spec-dev.md @@ -378,7 +378,7 @@ http://server/hapi/catalog | Name | Description | |------------|-------------------------------------------------------------------| | `depth` | **Optional** Possible values are `dataset` (the default) and `all`. Servers may choose to implement the `all` option, which allows all of the metadata from a server to be obtained in a single request. If this request parameter is supported, the `/capabilites` end point must return `catalogDepthOptions=["dataset", "all"]`. | - +| `resolve_references` | **Optional** If `false`, allow the server to send responses with references which need resolution by the client. Default is `true`. See [3.6.13 JSON References](#3613-json-references).| **Response** The response is in JSON format [[3](#6-references)] as defined by RFC-7159 and has a MIME type of `application/json`. The catalog @@ -514,6 +514,7 @@ Items with a * superscript in the following table have been modified from versio |------------|-------------------------------------------------------------------| | `dataset`[ * ](#1-significant-changes-to-specification) | **Required** The identifier for the dataset ([allowed characters](#82-allowed-characters-in-id-dataset-and-parameter)) | | `parameters` | **Optional** A comma-separated list of parameters to include in the response ([allowed characters](#82-allowed-characters-in-id-dataset-and-parameter)). Default is all; `...¶meters=&...` in URL should be interpreted as meaning all parameters. | +| `resolve_references` | **Optional** If `false`, allow the server to send responses with references which need resolution by the client. Default is `true`. See [3.6.13 JSON References](#3613-json-references).| **Response**