From b826b3dcdf26b187f5e0d2a1da6230ccb49bcce3 Mon Sep 17 00:00:00 2001 From: Andrius Merkys Date: Thu, 18 Jan 2024 16:41:01 +0200 Subject: [PATCH] Update optimade.rst Co-authored-by: Rickard Armiento --- optimade.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/optimade.rst b/optimade.rst index 61d8ae7de..735bad46c 100644 --- a/optimade.rst +++ b/optimade.rst @@ -1259,7 +1259,7 @@ The single resource object's response dictionary MUST include the following fiel If this member is *not* provided, the client MUST assume this is **not** an index meta-database base URL (i.e., the default is for :field:`is_index` to be :field-val:`false`). - **available\_licenses**: List of `SPDX license identifiers `__ specifying a set of alternative licenses under which the client is granted access to all the individual entries, all metadata, and the content and structure of the database itself. - If the database is available under multiple alternative licenses, identifiers of these multiple licenses SHOULD be provided to let clients know under which conditions they can be used. + If more than one license is available to the client, the identifier of each one SHOULD be included in the list. Inclusion of a license identifier in the list is a commitment of the database that the rights are in place to grant clients access to all the individual entries, all metadata, and the content and structure of the database itself according to the terms of any of these licenses (at the choice of the client). If the licensing information provided via the field :field:`license` omits licensing options specified in :field:`available_licenses`, or if it otherwise contradicts them, a client MUST still be allowed to interpret the inclusion of a license in :field:`available_licenses` as a full commitment from the database without exceptions, under the respective licenses. If the database cannot make that commitment, e.g., if only part of the database is available under a license, the corresponding license identifier MUST NOT appear in :field:`available_licenses` (but, rather, the field :field:`license` is to be used to clarify the licensing situation.)