All models¶

A string specifying a versioned base URL that MUST adhere to the rules in section Base URL

A string containing the full version number of the API served at that versioned base URL. The version number string MUST NOT be prefixed by, e.g., 'v'. Examples: 1.0.0, 1.0.0-rc.2.

Presently used full version of the OPTIMADE API. The version number string MUST NOT be prefixed by, e.g., "v". Examples: 1.0.0, 1.0.0-rc.2.

A list of dictionaries of available API versions at other base URLs

List of available endpoints (i.e., the string to be appended to the versioned base URL).

Available entry endpoints as a function of output formats.

List of available output formats.

If true, this is an index meta-database base URL (see section Index Meta-Database). 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 is_index to be false).

A human-readable description of the entry property

Defines whether the entry property can be used for sorting with the "sort" parameter. If the entry listing endpoint supports sorting, this key MUST be present for sortable properties with value true.

The type of the property's value. This MUST be any of the types defined in the Data types section. For the purpose of compatibility with future versions of this specification, a client MUST accept values that are not string values specifying any of the OPTIMADE Data types, but MUST then also disregard the type field. Note, if the value is a nested type, only the outermost type should be reported. E.g., for the entry resource structures, the species property is defined as a list of dictionaries, hence its type value would be list.

The physical unit of the entry property. This MUST be a valid representation of units according to version 2.1 of The Unified Code for Units of Measure. It is RECOMMENDED that non-standard (non-SI) units are described in the description for the property.

Description of the entry.

List of output formats available for this type of entry.

Dictionary of available output fields for this entry type, where the keys are the values of the formats list and the values are the keys of the properties dictionary.

A dictionary describing queryable properties for this entry type, where each key is a property name.

Object containing links to relationships with entries of the references type.

Object containing links to relationships with entries of the structures type.

The entry's immutable ID (e.g., an UUID). This is important for databases having preferred IDs that point to "the latest version" of a record, but still offer access to older variants. This ID maps to the version-specific record, in case it changes in the future.

• Type: string.

• Requirements/Conventions:

  • Support: OPTIONAL support in implementations, i.e., MAY be null.
  • Query: MUST be a queryable property with support for all mandatory filter features.

• Examples:

  • "8bd3e750-b477-41a0-9b11-3a799f21b44f"
  • "fjeiwoj,54;@=%<>#32" (Strings that are not URL-safe are allowed.)

Date and time representing when the entry was last modified.

• Type: timestamp.

• Requirements/Conventions:

  • Support: SHOULD be supported by all implementations, i.e., SHOULD NOT be null.
  • Query: MUST be a queryable property with support for all mandatory filter features.
  • Response: REQUIRED in the response unless the query parameter response_fields is present and does not include this property.

• Example:

  • As part of JSON response format: "2007-04-05T14:30:20Z" (i.e., encoded as an RFC 3339 Internet Date/Time Format string.)

JSON API resource linkage. It MUST be either null or contain a single Links identifier object with the fields id and type

Resource ID

Resource type

an application-specific error code, expressed as a string value.

A human-readable explanation specific to this occurrence of the problem.

A unique identifier for this particular occurrence of the problem.

A links object storing about

a meta object containing non-standard meta-information about the error.

An object containing references to the source of the error

the HTTP status code applicable to this problem, expressed as a string value.

A short, human-readable summary of the problem. It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization.

A link that leads to further details about this particular occurrence of the problem.

a string indicating which URI query parameter caused the error.

a JSON Pointer [RFC6901] to the associated entity in the request document [e.g. "/data" for a primary data object, or "/data/attributes/title" for a specific attribute].

Non-standard meta information

Version of the json API used

a string containing the link’s URL.

a meta object containing non-standard meta-information about the link.

Resource linkage

a links object containing at least one of the following: self, related

a meta object that contains non-standard meta-information about the relationship.

A related resource link.

A link for the relationship itself (a 'relationship link'). This link allows the client to directly manipulate the relationship. When fetched successfully, this link returns the linkage for the related resources as its primary data. (See Fetching Relationships.)

an attributes object representing some of the resource’s data.

a links object containing links related to the resource.

a meta object containing non-standard meta-information about a resource that can not be represented as an attribute or relationship.

Relationships object describing relationships between the resource and other JSON API resources.

A link that identifies the resource represented by the resource object.

Outputted Data

A list of unique errors

A list of unique included resources

Information about the JSON API used

Links associated with the primary data or errors

A meta object containing non-standard information related to the Success

The first page of data

The last page of data

The next page of data

The previous page of data

A related resource link

A link to itself

A string indicating whether a client that is following links to aggregate results from different OPTIMADE implementations should follow this link or not. This flag SHOULD NOT be indicated for links where link_type is not child.

If not specified, clients MAY assume that the value is ok. If specified, and the value is anything different than ok, the client MUST assume that the server is suggesting not to follow the link during aggregation by default (also if the value is not among the known ones, in case a future specification adds new accepted values).

Specific values indicate the reason why the server is providing the suggestion. A client MAY follow the link anyway if it has reason to do so (e.g., if the client is looking for all test databases, it MAY follow the links marked with aggregate=test).

If specified, it MUST be one of the values listed in section Link Aggregate Options.

JSON API links object, pointing to the base URL for this implementation

Human-readable description for the OPTIMADE API implementation, e.g., for use in clients to show a description to the end-user.

JSON API links object, pointing to a homepage URL for this implementation

The type of the linked relation. MUST be one of these values: 'child', 'root', 'external', 'providers'.

Human-readable name for the OPTIMADE API implementation, e.g., for use in clients to show the name to the end-user.

An OPTIONAL human-readable string indicating the reason for suggesting not to aggregate results following the link. It SHOULD NOT be present if aggregate=ok.

OPTIONAL human-readable description of the relationship

Relationship meta field. MUST contain 'description' if supplied.

A JSON API links object pointing to the homepage of the implementation.

A dictionary providing details about the maintainer of the implementation.

name of the implementation

A JSON API links object pointing to the implementation source, either downloadable archive or version control system.

version string of the current implementation

the maintainer's email address

a longer description of the database provider

a JSON API links object pointing to homepage of the database provider, either directly as a string, or as a link object.

a short name for the database provider

database-provider-specific prefix as found in section Database-Provider-Specific Namespace Prefixes.

Presently used full version of the OPTIMADE API. The version number string MUST NOT be prefixed by, e.g., "v". Examples: 1.0.0, 1.0.0-rc.2.

An integer containing the total number of data resource objects available in the database for the endpoint.

An integer containing the total number of data resource objects returned for the current filter query, independent of pagination.

a dictionary describing the server implementation

a string containing the last ID returned

false if the response contains all data for the request (e.g., a request issued to a single entry endpoint, or a filter query at the last page of a paginated response) and true if the response is incomplete in the sense that multiple objects match the request, and not all of them have been included in the response (e.g., a query with multiple pages that is not at the last page).

A JSON API links object that points to a schema for the response. If it is a string, or a dictionary containing no meta field, the provided URL MUST point at an OpenAPI schema. It is possible that future versions of this specification allows for alternative schema types. Hence, if the meta field of the JSON API links object is provided and contains a field schema_type that is not equal to the string OpenAPI the client MUST not handle failures to parse the schema or to validate the response against the schema as errors.

information on the database provider of the implementation.

Information on the Query that was requested

response string from the server

A timestamp containing the date and time at which the query was executed.

A list of warning resource objects representing non-critical errors or warnings. A warning resource object is defined similarly to a JSON API error object, but MUST also include the field type, which MUST have the value "warning". The field detail MUST be present and SHOULD contain a non-critical message, e.g., reporting unrecognized search attributes or deprecated features. The field status, representing a HTTP response status code, MUST NOT be present for a warning resource object. This is an exclusive field for error resource objects.

A string with the part of the URL following the versioned or unversioned base URL that serves the API. Query parameters that have not been used in processing the request MAY be omitted. In particular, if no query parameters have been involved in processing the request, the query part of the URL MAY be excluded. Example: /structures?filter=nelements=2

Warnings must be of type "warning"

First name of the person.

Last name of the person.

Full name of the person, REQUIRED.

Meaning of property matches the BiBTeX specification.

Meaning of property matches the BiBTeX specification.

List of person objects containing the authors of the reference.

Type of the reference, corresponding to the type property in the BiBTeX specification.

Meaning of property matches the BiBTeX specification.

Meaning of property matches the BiBTeX specification.

Meaning of property matches the BiBTeX specification.

The digital object identifier of the reference.

Meaning of property matches the BiBTeX specification.

List of person objects containing the editors of the reference.

Meaning of property matches the BiBTeX specification.

Meaning of property matches the BiBTeX specification.

Meaning of property matches the BiBTeX specification.

Meaning of property matches the BiBTeX specification.

Meaning of property matches the BiBTeX specification.

Meaning of property matches the BiBTeX specification.

Meaning of property matches the BiBTeX specification.

Meaning of property matches the BiBTeX specification.

Meaning of property matches the BiBTeX specification.

Meaning of property matches the BiBTeX specification.

Meaning of property matches the BiBTeX specification.

Meaning of property matches the BiBTeX specification.

Meaning of property matches the BiBTeX specification.

The URL of the reference.

Meaning of property matches the BiBTeX specification.

Meaning of property matches the BiBTeX specification.

Statistical probability of each group. It MUST have the same length as sites_in_groups. It SHOULD sum to one. See below for examples of how to specify the probability of the occurrence of a vacancy. The possible reasons for the values not to sum to one are the same as already specified above for the concentration of each species.

Index of the sites (0-based) that belong to each group for each assembly.

• Examples:
  • [[1], [2]]: two groups, one with the second site, one with the third.
  • [[1,2], [3]]: one group with the second and third site, one with the fourth.

If provided MUST be a list of length 1 or more of strings of chemical symbols for the elements attached to this site, or "X" for a non-chemical element.

MUST be a list of strings of all chemical elements composing this species. Each item of the list MUST be one of the following:

• a valid chemical-element name, or
• the special value "X" to represent a non-chemical element, or
• the special value "vacancy" to represent that this site has a non-zero probability of having a vacancy (the respective probability is indicated in the concentration list, see below).

If any one entry in the species list has a chemical_symbols list that is longer than 1 element, the correct flag MUST be set in the list structure_features.

MUST be a list of floats, with same length as chemical_symbols. The numbers represent the relative concentration of the corresponding chemical symbol in this species. The numbers SHOULD sum to one. Cases in which the numbers do not sum to one typically fall only in the following two categories:

• Numerical errors when representing float numbers in fixed precision, e.g. for two chemical symbols with concentrations 1/3 and 2/3, the concentration might look something like [0.33333333333, 0.66666666666]. If the client is aware that the sum is not one because of numerical precision, it can renormalize the values so that the sum is exactly one.
• Experimental errors in the data present in the database. In this case, it is the responsibility of the client to decide how to process the data.

Note that concentrations are uncorrelated between different site (even of the same species).

If present MUST be a list of floats expressed in a.m.u. Elements denoting vacancies MUST have masses equal to 0.

Gives the name of the species; the name value MUST be unique in the species list.

If provided MUST be a list of length 1 or more of integers indicating the number of attached atoms of the kind specified in the value of the :field:attached key.

Can be any valid Unicode string, and SHOULD contain (if specified) the name of the species that is used internally in the source database.

Note: With regards to "source database", we refer to the immediate source being queried via the OPTIMADE API implementation.

A description of groups of sites that are statistically correlated.

• Type: list of dictionary with keys:

  • sites_in_groups: list of list of integers (REQUIRED)
  • group_probabilities: list of floats (REQUIRED)

• Requirements/Conventions:

  • Support: OPTIONAL support in implementations, i.e., MAY be null.
  • Query: Support for queries on this property is OPTIONAL. If supported, filters MAY support only a subset of comparison operators.
  • The property SHOULD be null for entries that have no partial occupancies.
  • If present, the correct flag MUST be set in the list structure_features.
  • Client implementations MUST check its presence (as its presence changes the interpretation of the structure).

  • If present, it MUST be a list of dictionaries, each of which represents an assembly and MUST have the following two keys:

    • sites_in_groups: Index of the sites (0-based) that belong to each group for each assembly.

      Example: [[1], [2]]: two groups, one with the second site, one with the third. Example: [[1,2], [3]]: one group with the second and third site, one with the fourth.

    • group_probabilities: Statistical probability of each group. It MUST have the same length as sites_in_groups. It SHOULD sum to one. See below for examples of how to specify the probability of the occurrence of a vacancy. The possible reasons for the values not to sum to one are the same as already specified above for the concentration of each species.

  • If a site is not present in any group, it means that it is present with 100 % probability (as if no assembly was specified).

  • A site MUST NOT appear in more than one group.

• Examples (for each entry of the assemblies list):

  • {"sites_in_groups": [[0], [1]], "group_probabilities: [0.3, 0.7]}: the first site and the second site never occur at the same time in the unit cell. Statistically, 30 % of the times the first site is present, while 70 % of the times the second site is present.
  • {"sites_in_groups": [[1,2], [3]], "group_probabilities: [0.3, 0.7]}: the second and third site are either present together or not present; they form the first group of atoms for this assembly. The second group is formed by the fourth site. Sites of the first group (the second and the third) are never present at the same time as the fourth site. 30 % of times sites 1 and 2 are present (and site 3 is absent); 70 % of times site 3 is present (and sites 1 and 2 are absent).

• Notes:

  • Assemblies are essential to represent, for instance, the situation where an atom can statistically occupy two different positions (sites).

  • By defining groups, it is possible to represent, e.g., the case where a functional molecule (and not just one atom) is either present or absent (or the case where it it is present in two conformations)

  • Considerations on virtual alloys and on vacancies: In the special case of a virtual alloy, these specifications allow two different, equivalent ways of specifying them. For instance, for a site at the origin with 30 % probability of being occupied by Si, 50 % probability of being occupied by Ge, and 20 % of being a vacancy, the following two representations are possible:

    • Using a single species:

      {
        "cartesian_site_positions": [[0,0,0]],
        "species_at_sites": ["SiGe-vac"],
        "species": [
        {
          "name": "SiGe-vac",
          "chemical_symbols": ["Si", "Ge", "vacancy"],
          "concentration": [0.3, 0.5, 0.2]
        }
        ]
        // ...
      }
      

    • Using multiple species and the assemblies:

      {
        "cartesian_site_positions": [ [0,0,0], [0,0,0], [0,0,0] ],
        "species_at_sites": ["Si", "Ge", "vac"],
        "species": [
          { "name": "Si", "chemical_symbols": ["Si"], "concentration": [1.0] },
          { "name": "Ge", "chemical_symbols": ["Ge"], "concentration": [1.0] },
          { "name": "vac", "chemical_symbols": ["vacancy"], "concentration": [1.0] }
        },
        "assemblies": [
          {
        "sites_in_groups": [ [0], [1], [2] ],
        "group_probabilities": [0.3, 0.5, 0.2]
          }
        ]
        // ...
      }
      

  • It is up to the database provider to decide which representation to use, typically depending on the internal format in which the structure is stored. However, given a structure identified by a unique ID, the API implementation MUST always provide the same representation for it.

  • The probabilities of occurrence of different assemblies are uncorrelated. So, for instance in the following case with two assemblies:

    {
      "assemblies": [
        {
          "sites_in_groups": [ [0], [1] ],
          "group_probabilities": [0.2, 0.8],
        },
        {
          "sites_in_groups": [ [2], [3] ],
          "group_probabilities": [0.3, 0.7]
        }
      ]
    }
    

    Site 0 is present with a probability of 20 % and site 1 with a probability of 80 %. These two sites are correlated (either site 0 or 1 is present). Similarly, site 2 is present with a probability of 30 % and site 3 with a probability of 70 %. These two sites are correlated (either site 2 or 3 is present). However, the presence or absence of sites 0 and 1 is not correlated with the presence or absence of sites 2 and 3 (in the specific example, the pair of sites (0, 2) can occur with 0.20.3 = 6 % probability; the pair (0, 3) with 0.20.7 = 14 % probability; the pair (1, 2) with 0.80.3 = 24 % probability; and the pair (1, 3) with 0.80.7 = 56 % probability).

Cartesian positions of each site in the structure. A site is usually used to describe positions of atoms; what atoms can be encountered at a given site is conveyed by the species_at_sites property, and the species themselves are described in the species property.

• Type: list of list of floats

• Requirements/Conventions:

  • Support: SHOULD be supported by all implementations, i.e., SHOULD NOT be null.
  • Query: Support for queries on this property is OPTIONAL. If supported, filters MAY support only a subset of comparison operators.
  • It MUST be a list of length equal to the number of sites in the structure, where every element is a list of the three Cartesian coordinates of a site expressed as float values in the unit angstrom (Å).
  • An entry MAY have multiple sites at the same Cartesian position (for a relevant use of this, see e.g., the property assemblies).

• Examples:

  • [[0,0,0],[0,0,2]] indicates a structure with two sites, one sitting at the origin and one along the (positive) z-axis, 2 Å away from the origin.

The anonymous formula is the chemical_formula_reduced, but where the elements are instead first ordered by their chemical proportion number, and then, in order left to right, replaced by anonymous symbols A, B, C, ..., Z, Aa, Ba, ..., Za, Ab, Bb, ... and so on.

• Type: string

• Requirements/Conventions:

  • Support: SHOULD be supported by all implementations, i.e., SHOULD NOT be null.
  • Query: MUST be a queryable property. However, support for filters using partial string matching with this property is OPTIONAL (i.e., BEGINS WITH, ENDS WITH, and CONTAINS).

• Examples:

  • "A2B"
  • "A42B42C16D12E10F9G5"

• Querying:

  • A filter that matches an exactly given formula is chemical_formula_anonymous="A2B".

The chemical formula for a structure as a string in a form chosen by the API implementation.

• Type: string

• Requirements/Conventions:

  • Support: SHOULD be supported by all implementations, i.e., SHOULD NOT be null.
  • Query: MUST be a queryable property with support for all mandatory filter features.
  • The chemical formula is given as a string consisting of properly capitalized element symbols followed by integers or decimal numbers, balanced parentheses, square, and curly brackets (,), [,], {, }, commas, the +, -, : and = symbols. The parentheses are allowed to be followed by a number. Spaces are allowed anywhere except within chemical symbols. The order of elements and any groupings indicated by parentheses or brackets are chosen freely by the API implementation.
  • The string SHOULD be arithmetically consistent with the element ratios in the chemical_formula_reduced property.
  • It is RECOMMENDED, but not mandatory, that symbols, parentheses and brackets, if used, are used with the meanings prescribed by IUPAC's Nomenclature of Organic Chemistry.

• Examples:

  • "(H2O)2 Na"
  • "NaCl"
  • "CaCO3"
  • "CCaO3"
  • "(CH3)3N+ - [CH2]2-OH = Me3N+ - CH2 - CH2OH"

• Query examples:

  • Note: the free-form nature of this property is likely to make queries on it across different databases inconsistent.
  • A filter that matches an exactly given formula: chemical_formula_descriptive="(H2O)2 Na".
  • A filter that does a partial match: chemical_formula_descriptive CONTAINS "H2O".

The chemical formula for a structure in Hill form with element symbols followed by integer chemical proportion numbers. The proportion number MUST be omitted if it is 1.

• Type: string

• Requirements/Conventions:

  • Support: OPTIONAL support in implementations, i.e., MAY be null.
  • Query: Support for queries on this property is OPTIONAL. If supported, only a subset of the filter features MAY be supported.
  • The overall scale factor of the chemical proportions is chosen such that the resulting values are integers that indicate the most chemically relevant unit of which the system is composed. For example, if the structure is a repeating unit cell with four hydrogens and four oxygens that represents two hydroperoxide molecules, chemical_formula_hill is "H2O2" (i.e., not "HO", nor "H4O4").
  • If the chemical insight needed to ascribe a Hill formula to the system is not present, the property MUST be handled as unset.
  • Element names MUST have proper capitalization (e.g., "Si", not "SI" for "silicon").
  • Elements MUST be placed in Hill order, followed by their integer chemical proportion number. Hill order means: if carbon is present, it is placed first, and if also present, hydrogen is placed second. After that, all other elements are ordered alphabetically. If carbon is not present, all elements are ordered alphabetically.
  • If the system has sites with partial occupation and the total occupations of each element do not all sum up to integers, then the Hill formula SHOULD be handled as unset.
  • No spaces or separators are allowed.

• Examples:

  • "H2O2"

• Query examples:

  • A filter that matches an exactly given formula is chemical_formula_hill="H2O2".

The reduced chemical formula for a structure as a string with element symbols and integer chemical proportion numbers. The proportion number MUST be omitted if it is 1.

• Type: string

• Requirements/Conventions:

  • Support: SHOULD be supported by all implementations, i.e., SHOULD NOT be null.
  • Query: MUST be a queryable property. However, support for filters using partial string matching with this property is OPTIONAL (i.e., BEGINS WITH, ENDS WITH, and CONTAINS). Intricate queries on formula components are instead suggested to be formulated using set-type filter operators on the multi valued elements and elements_ratios properties.
  • Element names MUST have proper capitalization (e.g., "Si", not "SI" for "silicon").
  • Elements MUST be placed in alphabetical order, followed by their integer chemical proportion number.
  • For structures with no partial occupation, the chemical proportion numbers are the smallest integers for which the chemical proportion is exactly correct.
  • For structures with partial occupation, the chemical proportion numbers are integers that within reasonable approximation indicate the correct chemical proportions. The precise details of how to perform the rounding is chosen by the API implementation.
  • No spaces or separators are allowed.

• Examples:

  • "H2NaO"
  • "ClNa"
  • "CCaO3"

• Query examples:

  • A filter that matches an exactly given formula is chemical_formula_reduced="H2NaO".

List of three integers. For each of the three directions indicated by the three lattice vectors (see property lattice_vectors), this list indicates if the direction is periodic (value 1) or non-periodic (value 0). Note: the elements in this list each refer to the direction of the corresponding entry in lattice_vectors and not the Cartesian x, y, z directions.

• Type: list of integers.

• Requirements/Conventions:

  • Support: SHOULD be supported by all implementations, i.e., SHOULD NOT be null.
  • Query: Support for queries on this property is OPTIONAL.
  • MUST be a list of length 3.
  • Each integer element MUST assume only the value 0 or 1.

• Examples:

  • For a molecule: [0, 0, 0]
  • For a wire along the direction specified by the third lattice vector: [0, 0, 1]
  • For a 2D surface/slab, periodic on the plane defined by the first and third lattice vectors: [1, 0, 1]
  • For a bulk 3D system: [1, 1, 1]

Names of the different elements present in the structure.

• Type: list of strings.

• Requirements/Conventions:

  • Support: SHOULD be supported by all implementations, i.e., SHOULD NOT be null.
  • Query: MUST be a queryable property with support for all mandatory filter features.
  • The strings are the chemical symbols, i.e., either a single uppercase letter or an uppercase letter followed by a number of lowercase letters.
  • The order MUST be alphabetical.
  • Note: This property SHOULD NOT contain the string "X" to indicate non-chemical elements or "vacancy" to indicate vacancies (in contrast to the field chemical_symbols for the species property).

• Examples:

  • ["Si"]
  • ["Al","O","Si"]

• Query examples:

  • A filter that matches all records of structures that contain Si, Al and O, and possibly other elements: elements HAS ALL "Si", "Al", "O".
  • To match structures with exactly these three elements, use elements HAS ALL "Si", "Al", "O" AND elements LENGTH 3.

Relative proportions of different elements in the structure.

• Type: list of floats

• Requirements/Conventions:

  • Support: SHOULD be supported by all implementations, i.e., SHOULD NOT be null.
  • Query: MUST be a queryable property with support for all mandatory filter features.
  • Composed by the proportions of elements in the structure as a list of floating point numbers.
  • The sum of the numbers MUST be 1.0 (within floating point accuracy)

• Examples:

  • [1.0]
  • [0.3333333333333333, 0.2222222222222222, 0.4444444444444444]

• Query examples:

  • Note: Useful filters can be formulated using the set operator syntax for correlated values. However, since the values are floating point values, the use of equality comparisons is generally inadvisable.
  • OPTIONAL: a filter that matches structures where approximately 1/3 of the atoms in the structure are the element Al is: elements:elements_ratios HAS ALL "Al":>0.3333, "Al":<0.3334.

The three lattice vectors in Cartesian coordinates, in ångström (Å).

• Type: list of list of floats or unknown values.

• Requirements/Conventions:

  • Support: SHOULD be supported by all implementations, i.e., SHOULD NOT be null.
  • Query: Support for queries on this property is OPTIONAL. If supported, filters MAY support only a subset of comparison operators.
  • MUST be a list of three vectors a, b, and c, where each of the vectors MUST BE a list of the vector's coordinates along the x, y, and z Cartesian coordinates. (Therefore, the first index runs over the three lattice vectors and the second index runs over the x, y, z Cartesian coordinates).
  • For databases that do not define an absolute Cartesian system (e.g., only defining the length and angles between vectors), the first lattice vector SHOULD be set along x and the second on the xy-plane.
  • MUST always contain three vectors of three coordinates each, independently of the elements of property dimension_types. The vectors SHOULD by convention be chosen so the determinant of the lattice_vectors matrix is different from zero. The vectors in the non-periodic directions have no significance beyond fulfilling these requirements.
  • The coordinates of the lattice vectors of non-periodic dimensions (i.e., those dimensions for which dimension_types is 0) MAY be given as a list of all null values. If a lattice vector contains the value null, all coordinates of that lattice vector MUST be null.

• Examples:

  • [[4.0,0.0,0.0],[0.0,4.0,0.0],[0.0,1.0,4.0]] represents a cell, where the first vector is (4, 0, 0), i.e., a vector aligned along the x axis of length 4 Å; the second vector is (0, 4, 0); and the third vector is (0, 1, 4).

Number of different elements in the structure as an integer.

• Type: integer

• Requirements/Conventions:

  • Support: SHOULD be supported by all implementations, i.e., SHOULD NOT be null.
  • Query: MUST be a queryable property with support for all mandatory filter features.

• Examples:

  • 3

• Querying:

  • Note: queries on this property can equivalently be formulated using elements LENGTH.
  • A filter that matches structures that have exactly 4 elements: nelements=4.
  • A filter that matches structures that have between 2 and 7 elements: nelements>=2 AND nelements<=7.

An integer specifying the number of periodic dimensions in the structure, equivalent to the number of non-zero entries in dimension_types.

• Type: integer

• Requirements/Conventions:

  • Support: SHOULD be supported by all implementations, i.e., SHOULD NOT be null.
  • Query: MUST be a queryable property with support for all mandatory filter features.
  • The integer value MUST be between 0 and 3 inclusive and MUST be equal to the sum of the items in the dimension_types property.
  • This property only reflects the treatment of the lattice vectors provided for the structure, and not any physical interpretation of the dimensionality of its contents.

• Examples:

  • 2 should be indicated in cases where dimension_types is any of [1, 1, 0], [1, 0, 1], [0, 1, 1].

• Query examples:

  • Match only structures with exactly 3 periodic dimensions: nperiodic_dimensions=3
  • Match all structures with 2 or fewer periodic dimensions: nperiodic_dimensions<=2

An integer specifying the length of the cartesian_site_positions property.

• Type: integer

• Requirements/Conventions:

  • Support: SHOULD be supported by all implementations, i.e., SHOULD NOT be null.
  • Query: MUST be a queryable property with support for all mandatory filter features.

• Examples:

  • 42

• Query examples:

  • Match only structures with exactly 4 sites: nsites=4
  • Match structures that have between 2 and 7 sites: nsites>=2 AND nsites<=7

A list describing the species of the sites of this structure. Species can represent pure chemical elements, virtual-crystal atoms representing a statistical occupation of a given site by multiple chemical elements, and/or a location to which there are attached atoms, i.e., atoms whose precise location are unknown beyond that they are attached to that position (frequently used to indicate hydrogen atoms attached to another element, e.g., a carbon with three attached hydrogens might represent a methyl group, -CH3).

• Type: list of dictionary with keys:

  • name: string (REQUIRED)
  • chemical_symbols: list of strings (REQUIRED)
  • concentration: list of float (REQUIRED)
  • attached: list of strings (REQUIRED)
  • nattached: list of integers (OPTIONAL)
  • mass: list of floats (OPTIONAL)
  • original_name: string (OPTIONAL).

• Requirements/Conventions:

  • Support: SHOULD be supported by all implementations, i.e., SHOULD NOT be null.
  • Query: Support for queries on this property is OPTIONAL. If supported, filters MAY support only a subset of comparison operators.

  • Each list member MUST be a dictionary with the following keys:

    • name: REQUIRED; gives the name of the species; the name value MUST be unique in the species list;
    • chemical_symbols: REQUIRED; MUST be a list of strings of all chemical elements composing this species. Each item of the list MUST be one of the following:
      • a valid chemical-element name, or
      • the special value "X" to represent a non-chemical element, or
      • the special value "vacancy" to represent that this site has a non-zero probability of having a vacancy (the respective probability is indicated in the concentration list, see below).

    If any one entry in the species list has a chemical_symbols list that is longer than 1 element, the correct flag MUST be set in the list structure_features.

    • concentration: REQUIRED; MUST be a list of floats, with same length as chemical_symbols. The numbers represent the relative concentration of the corresponding chemical symbol in this species. The numbers SHOULD sum to one. Cases in which the numbers do not sum to one typically fall only in the following two categories:

      • Numerical errors when representing float numbers in fixed precision, e.g. for two chemical symbols with concentrations 1/3 and 2/3, the concentration might look something like [0.33333333333, 0.66666666666]. If the client is aware that the sum is not one because of numerical precision, it can renormalize the values so that the sum is exactly one.
      • Experimental errors in the data present in the database. In this case, it is the responsibility of the client to decide how to process the data.

      Note that concentrations are uncorrelated between different sites (even of the same species).

    • attached: OPTIONAL; if provided MUST be a list of length 1 or more of strings of chemical symbols for the elements attached to this site, or "X" for a non-chemical element.

    • nattached: OPTIONAL; if provided MUST be a list of length 1 or more of integers indicating the number of attached atoms of the kind specified in the value of the attached key.

    The implementation MUST include either both or none of the attached and nattached keys, and if they are provided, they MUST be of the same length. Furthermore, if they are provided, the structure_features property MUST include the string site_attachments.

    • mass: OPTIONAL. If present MUST be a list of floats, with the same length as chemical_symbols, providing element masses expressed in a.m.u. Elements denoting vacancies MUST have masses equal to 0.

    • original_name: OPTIONAL. Can be any valid Unicode string, and SHOULD contain (if specified) the name of the species that is used internally in the source database.

    Note: With regards to "source database", we refer to the immediate source being queried via the OPTIMADE API implementation.

    The main use of this field is for source databases that use species names, containing characters that are not allowed (see description of the list property species_at_sites).

  • For systems that have only species formed by a single chemical symbol, and that have at most one species per chemical symbol, SHOULD use the chemical symbol as species name (e.g., "Ti" for titanium, "O" for oxygen, etc.) However, note that this is OPTIONAL, and client implementations MUST NOT assume that the key corresponds to a chemical symbol, nor assume that if the species name is a valid chemical symbol, that it represents a species with that chemical symbol. This means that a species {"name": "C", "chemical_symbols": ["Ti"], "concentration": [1.0]} is valid and represents a titanium species (and not a carbon species).

  • It is NOT RECOMMENDED that a structure includes species that do not have at least one corresponding site.

• Examples:

  • [ {"name": "Ti", "chemical_symbols": ["Ti"], "concentration": [1.0]} ]: any site with this species is occupied by a Ti atom.
  • [ {"name": "Ti", "chemical_symbols": ["Ti", "vacancy"], "concentration": [0.9, 0.1]} ]: any site with this species is occupied by a Ti atom with 90 % probability, and has a vacancy with 10 % probability.
  • [ {"name": "BaCa", "chemical_symbols": ["vacancy", "Ba", "Ca"], "concentration": [0.05, 0.45, 0.5], "mass": [0.0, 137.327, 40.078]} ]: any site with this species is occupied by a Ba atom with 45 % probability, a Ca atom with 50 % probability, and by a vacancy with 5 % probability. The mass of this site is (on average) 88.5 a.m.u.
  • [ {"name": "C12", "chemical_symbols": ["C"], "concentration": [1.0], "mass": [12.0]} ]: any site with this species is occupied by a carbon isotope with mass 12.
  • [ {"name": "C13", "chemical_symbols": ["C"], "concentration": [1.0], "mass": [13.0]} ]: any site with this species is occupied by a carbon isotope with mass 13.
  • [ {"name": "CH3", "chemical_symbols": ["C"], "concentration": [1.0], "attached": ["H"], "nattached": [3]} ]: any site with this species is occupied by a methyl group, -CH3, which is represented without specifying precise positions of the hydrogen atoms.

Name of the species at each site (where values for sites are specified with the same order of the property cartesian_site_positions). The properties of the species are found in the property species.

• Type: list of strings.

• Requirements/Conventions:

  • Support: SHOULD be supported by all implementations, i.e., SHOULD NOT be null.
  • Query: Support for queries on this property is OPTIONAL. If supported, filters MAY support only a subset of comparison operators.
  • MUST have length equal to the number of sites in the structure (first dimension of the list property cartesian_site_positions).
  • Each species name mentioned in the species_at_sites list MUST be described in the list property species (i.e. for each value in the species_at_sites list there MUST exist exactly one dictionary in the species list with the name attribute equal to the corresponding species_at_sites value).
  • Each site MUST be associated only to a single species. Note: However, species can represent mixtures of atoms, and multiple species MAY be defined for the same chemical element. This latter case is useful when different atoms of the same type need to be grouped or distinguished, for instance in simulation codes to assign different initial spin states.

• Examples:

  • ["Ti","O2"] indicates that the first site is hosting a species labeled "Ti" and the second a species labeled "O2".
  • ["Ac", "Ac", "Ag", "Ir"] indicating the first two sites contains the "Ac" species, while the third and fourth sites contain the "Ag" and "Ir" species, respectively.

A list of strings that flag which special features are used by the structure.

• Type: list of strings

• Requirements/Conventions:

  • Support: MUST be supported by all implementations, MUST NOT be null.
  • Query: MUST be a queryable property. Filters on the list MUST support all mandatory HAS-type queries. Filter operators for comparisons on the string components MUST support equality, support for other comparison operators are OPTIONAL.
  • MUST be an empty list if no special features are used.
  • MUST be sorted alphabetically.
  • If a special feature listed below is used, the list MUST contain the corresponding string.
  • If a special feature listed below is not used, the list MUST NOT contain the corresponding string.
  • List of strings used to indicate special structure features:
    • disorder: this flag MUST be present if any one entry in the species list has a chemical_symbols list that is longer than 1 element.
    • implicit_atoms: this flag MUST be present if the structure contains atoms that are not assigned to sites via the property species_at_sites (e.g., because their positions are unknown). When this flag is present, the properties related to the chemical formula will likely not match the type and count of atoms represented by the species_at_sites, species and assemblies properties.
    • site_attachments: this flag MUST be present if any one entry in the species list includes attached and nattached.
    • assemblies: this flag MUST be present if the property assemblies is present.

• Examples: A structure having implicit atoms and using assemblies: ["assemblies", "implicit_atoms"]

The base version string without patch and metadata info.

The build metadata.

The major version number.

The minor version number.

The patch version number.

The pre-release tag.