Category: Smart Water Domain

Local context service

  By , , , , , , , , , , ,

If you want to use data models coming from several subjects you will have to merge (somehow) their @contexts.

In this first step, we offer you a service that allows you to choose what subjects you need to merge and to generate the @context.

See the instructions on the page. Now in Main menu -> @context -> Generate a local context

It also provides you with the conflicts in the attributes’ names, in order to let you solve them manually.

In the next step, possibly next week, you will have another service that will allow you to choose what reference ontologies and vocabularies you want to use and replace the Smart data models IRIs with those coming from these external sources.

Survey. What ontologies are you using, if any?

  By , , , , , , , , , , , ,

    Smart Data Models Program is willing to ease the use of existing and adopted ontologies.

    Q1: Do you use semantic ontologies for your data

    If you do not know it is quite likely that the answer would be no

    Q2: Do you use them with NGSI-LD?

    Q3: What ontologies are you using (or planning to use)?

    Q4: Are you a member of the Smart Data Models organizations ?

    Member of FIWARE FoundationMember of TMForumMember of IUDXMember of OASCNo membership

    Local @context improved

      By , , , , , , , , , , ,

    The local @context, used by NGSI-LD users of the platform has now taken into account those generic terms which are in the commons-schema.json at the root.

    In fact, there is a @context based on these terms named common-context.jsonld.

    So, the common terms have an IRI with this pattern https://smartdatamodels.org/term that in most cases is taking you to an actual page with some information about the term.

     

    5 New data models for Smart Water domain. OpenChannelManagement Subject

      By

    In the subject OpenChannelManagement of the Smart Water domain, there are 3 new data models available.

    [[File:Semi-circular artificial water channel.png|Semi-circular_artificial_water_channel]] It is located at dataModel.OpenChannelManagement subject.

    • OpenChannelCurve. This entity contains a harmonized description of a generic curve made for Raw-Water (Open Channels) System Management domain.
    • OpenChannelJunction. This entity contains a harmonized description of a generic Junction made for Raw-Water (Open Channels) System Management domain. A Junction defines a location where the characteristics of the channel change, two or more channels come together or split apart, amounts of water are abstracted or inserted into the system etc.
    • OpenChannelSystem. This entity contains a harmonized description of a generic system made for Raw-Water (Open Channels) System Management domain. This entity represents either a system composed of different components (e.g., channels, junctions, cross-sections etc.) or just a component (e.g., a SluiceGate).
    • RegulationStructure. This entity contains a harmonized description of a generic Regulation Structure made for Raw-Water (Open Channels) System Management domain. Regulation structure represents a junction-type object, controlling the water flow in the raw-water system.
    • RegulationStructureSimulation. This entity contains a harmonized description of a data model for regulation structure simulation, for Raw-Water (Open Channels) System Management domain.
    • SluiceGate. This entity contains a harmonized description of a generic Sluice Gate made for Raw-Water (Open Channels) System Management domain.

    Local context available in all subjects

      By , , , , , , , , , , ,

    We the middle of a reorganization of the @context resources.

    Our first priority is to not touch the @context that is currently available. We grant you we keep it.

    Why is this new option being created?, because otherwise is not possible to solve the conflicts in the IRI when we have attributes with the same ‘name’ but with different meanings. Consequently, their long IRIs (for use in NGSI-LD) need to be different.

    WHAT IS AVAILABLE TODAY

    The first step is the creation of a local context.jsonld in the root of every subject. It has been made available today.

    You can see an example of this local @context for the subject weather.

    The long IRI has the format  (predictable):

    “https://smartdatamodels.org/” +  subject name + “/” + attribute name

    Ej. “precipitation”: “https://smartdatamodels.org/dataModel.Weather/precipitation”,

    Soon there will be pages on that IRI (they are in fact URL) with some info about the attribute you could use for any purpose.

    WHAT WILL BE AVAILABLE

    1) In the coming future, you will be able to use the local IRI from the Smart Data Models program or commonly used ontologies and vocabularies.

    2) A core of attributes will be kept common for many data models e.g. name, description, alternateName, location, address, etc. They will have IRI in the format

    “https://smartdatamodels.org/” + attribute name

    currently we already have these IRI but there will be also a translator for the properties in the format

    “https://smartdatamodels.org/dataModel.Weather/category”: “https://smartdatamodels.org/category”,

    3) Additionally,  the Smart Data Models to remain interoperable with external ontologies and vocabularies. so there will be also the option to create a @context with external references in the format

    “https://smartdatamodels.org/name”: “schema:name”

    Your comments are welcomed

    New data models of the Smart Water domain, Spillway, OpenChannelFlowRegulation and RegulationStructureSimulation

      By

    In the subject OpenChannelManagement of the Smart Water domain there are 3 new data models available.

    [[File:Semi-circular artificial water channel.png|Semi-circular_artificial_water_channel]] It is located at dataModel.OpenChannelManagement subject.

    • OpenChannelFlowRegulation. This entity contains a harmonized description of a generic simulation of a series of independent regulation structures to establish specific flow conditions in the conveyance system. It is made for Raw-Water (Open Channels) System Management domain.
    • RegulationStructureSimulation. This entity contains a harmonized description of a data model for regulation structure simulation, for Raw-Water (Open Channels) System Management domain.
    • Spillway. This entity contains a harmonized description for a generic Spillway made for Raw-Water (Open Channels) System Management domain. Spillway represents a junction-type object, controlling the release of water from a dam or regulation structure downstream.

    Register to the open session all Mondays. Calendar shortcut. #support

      By , , , , , , , , , , ,

    Open sessions are 30 minutes of live support for users and contributors of the Smart Data Models held every Monday at 14:00 CET. You can also comment on your ideas about new required data models.
    Now you can see in the announcement banner in the upper part of the page this icon

    It allows you to add to your google calendar the open sessions all Mondays.

    Updated the resources for generating automatic examples

      By , , , , , , , , , , ,

    Once you have the json schema of a smart Data model there are two services that allow you to generate random payloads compliant with the JSON schema in NGSI-LD.
    both services are for generating

    these services have been updated and some errors were fixed.

    Soon these services will be also available for NGSI v2 platform.