Author: maestro

No comments

Updated all the data models (11) in subject WaterDistributionManagement EPANET

  By

The data models of the subject WaterDistributionManagement EPANET have been updated with flow properties and other improvements. New properties are already available for search in the database.

Additionally, there is an alpha version of the German translation of the specification.

  • Curve. This entity contains a harmonized description of a generic curve made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • Junction. This entity contains a harmonized description of a generic junction made for the Water Network Management domain. This entity is primarily associated with the water network management vertical and related IoT applications.
  • WaterNetwork. This entity contains a harmonized description of a generic network made for the Water Network Management domain. This entity is primarily associated with the water network management vertical and related IoT applications.
  • Pattern. This entity contains a harmonized description of a generic pattern made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • Pipe. This entity contains a harmonized description of a generic pipe made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • Pump. This entity contains a harmonized description of a generic pump made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • Reservoir. This entity contains a harmonized description of a generic Reservoir made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • SimulationResult. This entity contains a harmonized description of a generic simulation result made for the Water Network Management domain. This entity is primarily associated with the water network management vertical and related IoT applications.
  • SimulationScenario. This entity contains a harmonized description of a generic simulation scenario made for the Water Network Management domain. This entity is primarily associated with the water network management vertical and related IoT applications.
  • Tank. This entity contains a harmonized description of a generic tank made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • Valve. This entity contains a harmonized description of a generic Valve made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.

You can answer our survey in order to know what more useful for you.

    Q1: What elements of a smart data model are useful for you?

    Examples of the options:
    1.-Json Schema
    2.-Examples
    3.-Specification
    Mark those relevant for you

    Optional. Other element useful. (Available or desired)

    Q2: What services do you use?

    1.- Search data models
    2.- Validation of payload
    3.-Validate schema before contribution
    4.-Generate a NGSI-LD payload out of a schema
    Search data modelsValidation of payloadValidate of json schema before contributionGenerate a NGSI-LD payload out of a schema
    Optional. Other services missing. (Available or desired)

    Membership

    Member of FIWARE FoundationMember of TMForumMember of IUDXNo membership

    No comments

    New data model StorageBatteryMeasurement in dataModel.Battery subject

      By ,

    1 new data model in the subject datamodel.Battery

    StorageBatteryMeasurement. Storage Battery Observed Data Model is intended to measure the remaining energy capacity in a battery, which can be redistributed in the form of electrical energy. These functions apply from a source that depends on the type of battery (a reference to the attribute ‘batteryType’ of the Data Model StorageBatteryDevice).

    Thanks to the contributors

    No comments

    Contribution checklist

      By , , , , , , , , , ,

    There is a new option in the main menu Data Models -> Contribution Checklist

    It is strongly recommended to pass every element before submitting your new data model.

    See below the checklist

      schema.json

      1.-
      2.-

      3.-

      4.-

      Examples

      5.-
      6.-

      Optional documents

      7.-
      8.-
      9.-
      10.-

      Contribution

      11.-

      Comments




      By using this form you agree with the storage and handling of your data by this website.

      No comments

      New data model in Energy subject InverterDevice

        By

      1 new data model is available in the subject dataModel.Energy.

      InverterDevice. The data model is intended to describe the mechanical, electrical characteristics of an Inverter according to DC – Direct Current Information supplied as input and AC – Alternating Current Information returned as output. Remark: This Data Model can be used directly as the main entity to describe the device [Inverter] or as a sub-entity of the Data Model {DEVICE] using a reference by the [refDevice] attribute.

      Thanks to the contributors of the subject.

      No comments

      New NGSI linked data generator for every data model

        By , , , , , , , , , ,

      Now the README file of every data model includes a link to the generator of NGSI-LD payloads compliant with the data model.

      As you can see in the image below there is a new section “Dynamic examples generation”

      There is the sentence “Link to the Generator of NGSI-LD payloads compliant with this data model. Refresh for new values”. By clicking the Generator link an example of payload appears on the web page. Refreshing (F5) generates new payloads.

       

      No comments

      Updated interactive specification

        By , , , , , , , , , ,

      Now all data models have an interactive specification. (As long as they have examples)
      This is the first step to deeper interactive services for every data model contributed.
      See the example for weatherForecast.

      No comments

      First Survey to users and contributors of Smart Data Models

        By , , , , , , , , , ,

        Q1: What elements of a smart data model are useful for you?

        Examples of the options:
        1.-Json Schema
        2.-Examples
        3.-Specification
        Mark those relevant for you

        Optional. Other element useful. (Available or desired)

        Q2: What services do you use?

        1.- Search data models
        2.- Validation of payload
        3.-Validate schema before contribution
        4.-Generate a NGSI-LD payload out of a schema
        Search data modelsValidation of payloadValidate of json schema before contributionGenerate a NGSI-LD payload out of a schema
        Optional. Other services missing. (Available or desired)

        Membership

        Member of FIWARE FoundationMember of TMForumMember of IUDXNo membership

        No comments

        Include userAlias in common-schema.json

          By , , , , , , , , , ,

        The file common-schema.json compiles those properties massively used across the different data models in the different domains.
        The property userAlias has been included to store those anonymous identifiers of a user that cannot be traced back to the user.
        It can be referenced in any data model just by including this code

        “userAlias”: {
        “$ref” : “https://smart-data-models.github.io/data-models/common-schema.json#/definitions/userAlias”
        }