|
3359 | 3359 | "type": "number" |
3360 | 3360 | }, |
3361 | 3361 | "description": "If present MUST be a list of floats expressed in a.m.u.\nElements denoting vacancies MUST have masses equal to 0.", |
| 3362 | + "x-optimade-unit": "a.m.u.", |
3362 | 3363 | "x-optimade-queryable": "optional", |
3363 | | - "x-optimade-support": "optional", |
3364 | | - "x-optimade-unit": "a.m.u." |
| 3364 | + "x-optimade-support": "optional" |
3365 | 3365 | }, |
3366 | 3366 | "original_name": { |
3367 | 3367 | "title": "Original Name", |
|
3639 | 3639 | }, |
3640 | 3640 | "description": "The three lattice vectors in Cartesian coordinates, in \u00e5ngstr\u00f6m (\u00c5).\n\n- **Type**: list of list of floats or unknown values.\n\n- **Requirements/Conventions**:\n - **Support**: SHOULD be supported by all implementations, i.e., SHOULD NOT be `null`.\n - **Query**: Support for queries on this property is OPTIONAL.\n If supported, filters MAY support only a subset of comparison operators.\n - 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.\n (Therefore, the first index runs over the three lattice vectors and the second index runs over the x, y, z Cartesian coordinates).\n - 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.\n - MUST always contain three vectors of three coordinates each, independently of the elements of property `dimension_types`.\n The vectors SHOULD by convention be chosen so the determinant of the `lattice_vectors` matrix is different from zero.\n The vectors in the non-periodic directions have no significance beyond fulfilling these requirements.\n - 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.\n If a lattice vector contains the value `null`, all coordinates of that lattice vector MUST be `null`.\n\n- **Examples**:\n - `[[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 \u00c5; the second vector is `(0, 4, 0)`; and the third vector is `(0, 1, 4)`.", |
3641 | 3641 | "nullable": true, |
| 3642 | + "x-optimade-unit": "\u00c5", |
| 3643 | + "x-optimade-queryable": "optional", |
| 3644 | + "x-optimade-support": "should" |
| 3645 | + }, |
| 3646 | + "space_group_hall": { |
| 3647 | + "title": "Space Group Hall", |
| 3648 | + "type": "string", |
| 3649 | + "description": "A Hall space group symbol representing the symmetry of the structure as defined in Hall, S. R. (1981), Acta Cryst. A37, 517-525 and erratum (1981), A37, 921.\n\n- **Type**: string\n\n- **Requirements/Conventions**:\n - **Support**: OPTIONAL support in implementations, i.e., MAY be `null`.\n - **Query**: Support for queries on this property is OPTIONAL.\n - Each component of the Hall symbol MUST be separated by a single space symbol.\n - If there exists a standard Hall symbol which represents the symmetry it SHOULD be used.\n - MUST be null if `nperiodic_dimensions` is not equal to 3.", |
3642 | 3650 | "x-optimade-queryable": "optional", |
3643 | | - "x-optimade-support": "should", |
3644 | | - "x-optimade-unit": "\u00c5" |
| 3651 | + "x-optimade-support": "optional" |
| 3652 | + }, |
| 3653 | + "space_group_it_number": { |
| 3654 | + "title": "Space Group It Number", |
| 3655 | + "maximum": 230.0, |
| 3656 | + "minimum": 1.0, |
| 3657 | + "type": "integer", |
| 3658 | + "description": "Space group number for the structure assigned by the International Tables for Crystallography Vol. A.\n- **Type**: integer\n\n- **Requirements/Conventions**:\n - **Support**: OPTIONAL support in implementations, i.e., MAY be `null`.\n - **Query**: Support for queries on this property is OPTIONAL.\n - The integer value MUST be between 1 and 230.\n - MUST be null if `nperiodic_dimensions` is not equal to 3.", |
| 3659 | + "x-optimade-queryable": "optional", |
| 3660 | + "x-optimade-support": "optional" |
3645 | 3661 | }, |
3646 | 3662 | "cartesian_site_positions": { |
3647 | 3663 | "title": "Cartesian Site Positions", |
|
3656 | 3672 | }, |
3657 | 3673 | "description": "Cartesian positions of each site in the structure.\nA 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.\n\n- **Type**: list of list of floats\n\n- **Requirements/Conventions**:\n - **Support**: SHOULD be supported by all implementations, i.e., SHOULD NOT be `null`.\n - **Query**: Support for queries on this property is OPTIONAL.\n If supported, filters MAY support only a subset of comparison operators.\n - 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 (\u00c5).\n - An entry MAY have multiple sites at the same Cartesian position (for a relevant use of this, see e.g., the property `assemblies`).\n\n- **Examples**:\n - `[[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 \u00c5 away from the origin.", |
3658 | 3674 | "nullable": true, |
| 3675 | + "x-optimade-unit": "\u00c5", |
3659 | 3676 | "x-optimade-queryable": "optional", |
3660 | | - "x-optimade-support": "should", |
3661 | | - "x-optimade-unit": "\u00c5" |
| 3677 | + "x-optimade-support": "should" |
3662 | 3678 | }, |
3663 | 3679 | "nsites": { |
3664 | 3680 | "title": "Nsites", |
|
0 commit comments