OPTIMADE
OPTIMADE copied to clipboard
Materials-Consortia
Specification of a common REST API for access to materials databases
The COD implementation currently does not handle endpoint URLs with trailing slashes. While this issue is relatively easy to fix on the COD side, I am interested in OPTIMADE's stance...
On the OPTIMADE call came up the idea of a `_cif_` prefix (which was previously suggested and at the time rejected in #143). The idea is that any identifier `_x`...
During the OPTIMADE call came up the question that we already have two types of prefixes in https://providers.optimade.org/providers.json Those that are specifically tied to databases, and those that are more...
From a call discussion: We have a number of properties where the query support is marked as MUST, whereas support for the property itself is marked as SHOULD. The consensus...
Create and post here suggestions what could be used for testing OPTIMADE and what could be showcased in the paper.
As of v1.0.0, "5.3.1. Entry Listing URL Query Parameters" says: > The client MAY provide a set of URL query parameters in order to alter the response and provide usage...
We need to standardize mandatory and optional the fields in the calculation entry type.
Currently, some features of the OPTiMaDe specification are mandatory, and some are optional. For N optional features that databases choose to implement or not implement, we have 2^N combinations of...
To be able to dynamically and effectively handle (especially) provider-specific resource properties, e.g., `_exmpl_some_energy`, it would be useful to know the value type expected. It would make most sense to...
Metadata
Owner
Metadata
Specification of a common REST API for access to materials databases