From bc89ad7a692a23dfe26879c20f5a321fcc81703b Mon Sep 17 00:00:00 2001 From: Rickard Armiento Date: Wed, 1 Mar 2023 16:29:17 +0100 Subject: [PATCH] Apply suggestions from review Co-authored-by: Matthew Evans <7916000+ml-evs@users.noreply.github.com> --- optimade.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/optimade.rst b/optimade.rst index f0bdc773b..772898fd2 100644 --- a/optimade.rst +++ b/optimade.rst @@ -1873,7 +1873,7 @@ A Property Definition MUST be composed according to the combination of the requi .. _definition of the x-optimade-type field: -- :field:`x-optimade-type`: String +- :field:`x-optimade-type`: String. Specifies the OPTIMADE data type for this level of the defined property. MUST be one of :val:`"string"`, :val:`"integer"`, :val:`"float"`, :val:`"boolean"`, :val:`"timestamp"`, :val:`"list"`, or :val:`"dictionary"`. @@ -1953,7 +1953,7 @@ A Property Definition MUST be composed according to the combination of the requi Note: the specification by this field of whether the defined property can be :val:`null` or not MUST match the value of the :field:`type` field. If :val:`null` values are allowed, that field must be a list where the string :val:`"null"` is the second element. - - :field:`response-default-level`: String + - :field:`response-default-level`: String. Expresses if an implementation of this property is required to include or exclude it in responses when not specifically requested. This field only has meaning for the defined property when appearing in the :field:`x-optimade-requirements` at the outermost level of the definition. Nevertheless, it MAY appear at other places, e.g., if a nested property definition has been inserted that references its own :field:`$id`.