Schema Configuration

Search…
Schema
All registries have attributes pertaining to the entity or the fact in question either person or things. Schema defines the structure and constraints of the entity, open saber rc uses standard JSON-LD based schema.
In the example given below Place is Concept that registry is storing supporting name, city, addressRegion (state) and country.
Example:
1
{
2
 "$schema": "http://json-schema.org/draft-07/schema",
3
 "type": "object",
4
 "properties": {
5
   "Place": {
6
     "$ref": "#/definitions/Place"
7
   }
8
 },
9
 "required": [
10
   "Place"
11
 ],
12
 "title": "Place",
13
 "definitions": {
14
   "Place": {
15
     "$id": "#/properties/Place",
16
     "type": "object",
17
     "title": "The Place Schema",
18
     "required": [
19
       "name",
20
       "city",
21
       "addressRegion",
22
       "country"
23
     ],
24
     "properties": {
25
       "name": {
26
         "type": "string"
27
       },
28
       "city": {
29
         "type": "string"
30
       },
31
       "addressLocality": {
32
         "type": "string"
33
       },
34
       "addressRegion": {
35
         "type": "string"
36
       },
37
       "country": {
38
         "type": "string"
39
       },
40
       "postalCode": {
41
         "type": "string"
42
       },
43
       "contact": {
44
         "type": "string"
45
       }
46
     }
47
   }
48
 }}
Copied!
Configuration
In addition to JSON LD specific data types OpenSaberRC supports various extension configurations under “_osConfig”. Access, indexing, primary key etc are configurable using schema configuration.
Entity and Properties
Property data types and restrictions
Supported types:
String - Unicode text, additional regular expressions restrictions can be applied.
Enum - restricted list of values
Number - numeric data
List of attributes
Collection of data values are also supported as multiple data value might represent the entity property for example subjects taught : [“english”,”science”, “mathematics”]
Visibility scope:
3 types of visibility on attributes.
1.
Public 
2.
Private (privateFields)
3.
Internal
Public data attributes are available in discovery by default any sort of permission / authorization is not needed by default.
Private attributes can be accessed by the owner by default, with consent 3rd party can access the data field.
Internal fields are system fields that only serve internal functionalities, these can never be accessed by any actors in the system.
Primary Keys for Entities
Primary keys from domain space will help enforce uniqueness of information and make it easily accessible. “uniqueIndexFields” can be used to configure the same.
Example:
"uniqueIndexFields": [
"identityValue"
]
Index field set
Indexes can help in faster access to information, based on usage context index fields can be configured. Example:
"indexFields": ["phoneNumber"],
Validation Extensions
JSON LD schema allows defining basic type constraints like numeric type, text or list of items etc. Also it allows a list of possible values for given attributes (enum) and regular expressions based constraints for the value.
USE - Previous
Technical Requirements
Next - USE
Setup the Backend
Last modified 1mo ago
Copy link
Contents
Validation Extensions