BasicInfoType

The BasicInfoType is used to represent any datatype that is some form of a fundamental type, namely strings, numbers, booleans. When restrictions are properly filled, a validation schema can be generated for each BasicInfoType.

Schema

• All fields from the General Schema are included
• MeasuredUnits
  • Units that are measured using this type.
  • Type: array
  • path: #/properties/MeasuredUnits
    • Items
    • path: #/properties/MeasuredUnits/items

• Taxonomies

  • Taxonomy nodes that this type should be assigned to.
  • Type: array
  • path: #/properties/Taxonomies
    • Items
    • path: #/properties/Taxonomies/items

• Schema

  • Select the fundamental datatype this type should represent. "Number" can be further differentiated into integer and float.
  • Type: object
  • path: #/properties/Schema
  • Properties
  • The properties of the schema branch here into different directions based on the desired fundamental datatype. For each fundamental type, different restrictions are valid and internal validation is conducted accordingly. We now list the possibilities for each datatype.
    • Type required
      • For type "Number", further differentiate between integer and float.
      • Type: string
      • path: #/properties/Test/properties/Type
      • The value is restricted to the following:
        1. "String"
        2. "Integer"
        3. "Number"
        4. "Boolean"
        5. "Enum"
        6. "None"
    • PropRelations
      • Properties are chained by boolean operators. By default, through the AND operator all properties must apply. OR or XOR operators for properties are also possible.
      • Type: string
      • path: #/properties/Test/properties/PropRelations
      • The value is restricted to the following:
        1. "AND"
        2. "OR"
        3. "XOR"
    • Properties
      • Type: array/string
      • path: #/properties/Test/properties/Properties
      • The allowed values in the properties field depend on the desired fundamental type. Strings, Integers and Numbers have an array like described in the items field below. Note that when using field names described by the json-schema definition (i.e. minLength, maxLength...) the values are validated internally to avoid issues on the schema creation.
        • Items
        • Type: object
        • path: #/properties/Test/properties/Properties/items
        • Properties
          • Property
            • Type: string
            • path: #/properties/Property
        • Value - Type: string - path: #/properties/Value
      • If the selected Type is boolean, the Properties field is only one optional string, which may take one of the following two values.

      • Type: string

        1. "Always True"

        2. "Always False"

        3. Type: string

        4. path: #/properties/Property
        5. The value is restricted to the following:
           1. "Integer Enum" - Value
        6. Type: array
        7. path: #/properties/Value
           • Items

           • Enum Element

           • Type: integer
           • path: #/properties/Value/items