Skip to content

# Exabyte Data Convention¶

Our approach towards storing and organizing structured data is based on the Exabyte Data Convention (EDC) explained in the present documentation. We use this convention to store and organize the information associated with the Entities present across our platform, and their corresponding Accounts and Permissions. The convention is designed with the aim of facilitating both the access and collaboration with regards to such entities. The fundamental practices are further elucidated in the sections below.

## JSON Representation¶

We make use of the JSON format 1 2 for storing structured data . This structured data might for example be relevant for storing information about the entities present in the account-owned collections, and for storing their respective properties.

### Example¶

Data included in the expandable section below shows an example JSON representation of a material sample of silicon and is presented to demonstrate the concept. The explanation of the keywords specific to Material entity can be found here.

JSON representation

  1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 { "exabyteId": "RKiswuxHKkF3uvLyA", "hash": "4ac3fa057e3530628eb1295c77110eaa", "name": "Silicon FCC", "creator": { "_id": "HtxACY2wX4b2hS8Rv", "slug": "exadmin", "cls": "User" }, "scaledHash": "5bd4eb168e3530628eb1295d88221cbb", "derivedProperties": [ { "units": "angstrom^3", "name": "volume", "value": 131.1 }, { "units": "g/cm^3", "name": "density", "value": 2.33 }, { "tolerance": { "units": "angstrom", "value": 0.3 }, "name": "symmetry", "spaceGroupSymbol": "Fd-3m" }, { "value": 0.71, "name": "p-norm", "degree": 10 }, { "name": "elemental_ratio", "value": 0.71, "element": "Si" } ], "basis": { "units": "crystal", "elements": [ { "id": 1, "value": "Si" }, { "id": 2, "value": "Si" } ], "name": "basis", "coordinates": [ { "id": 1, "value": [ 0.0, 0.0, 0.0 ] }, { "id": 2, "value": [ 0.25, 0.25, 0.25 ] } ] }, "lattice": { "a": 5.0, "c": 5.0, "b": 5.0, "name": "lattice", "beta": 90.0, "alpha": 90.0, "type": "CUB", "gamma": 90.0 }, "isDefault": false, "updatedAt": "2016-04-04T17:58:42.867Z", "unitCellFormula": "Si2", "owner": { "_id": "HtxACY2wX4b2hS8Rv", "slug": "exabyte", "cls": "Account" }, "formula": "Si", "schemaVersion": "0.2.0", "_id": "LCthJ6E2QabYCZqf3", "slug": "silicon-fcc", "createdAt": "2016-04-03T05:25:37.430Z" } 

## JSON Schemas¶

In computer science, a schema 3 is a general concept referring to how structured data can be stored and organized within a database. JSON schemas 4 5 in particular consist in a vocabulary that allows to validate JSON-based documents containing structured data, and to annotate them with descriptions.

## Examples¶

Multiple schemas are deployed on our platform in order to describe the data. The reader is referred to the specific pages associated with the different entities and their respective Properties.