Skip to content

Commit

Permalink
Update optimade.rst
Browse files Browse the repository at this point in the history
Co-authored-by: Rickard Armiento <gitcommits@armiento.net>
  • Loading branch information
merkys and rartino authored Jan 18, 2024
1 parent de64f0a commit b826b3d
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion optimade.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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 <https://spdx.org/licenses/>`__ 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.)
Expand Down

0 comments on commit b826b3d

Please sign in to comment.