Author: maestro

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.

    GBFS standard mapped

      By

    The standard GBFS for real-time mobility in bike has been completely mapped (version 2.2) in the subject dataModel.GBFS of the Smart Data Models program.

    the standard is maintained by North American Bikeshare and Scootshare association

    It is located at dataModel.GBFS subject.

    • free_bike_status. Describes the vehicles that are available for rent (as of v2.1-RC2). According to the Standard GBFS 2.2
    • gbfs. Auto-discovery file that links to all of the other files published by the system. According to the Standard GBFS 2.2
    • gbfs_versions. Lists all feed endpoints published according to version sof the GBFS documentation. (added in v1.1) According to the Standard GBFS 2.2
    • geofencing_zones. Describes geofencing zones and their associated rules and attributes (added in v2.1-RC). According to the Standard GBFS 2.2
    • station_information. Details including system operator, system location, year implemented, URL, contact info, time zone. According to the Standard GBFS 2.2
    • station_status. Describes the capacity and rental availability of the station According to the Standard GBFS 2.2
    • system_alerts. Describes ad-hoc changes to the system. According to the Standard GBFS 2.2
    • system_calendar. Describes the operating calendar for a system. According to the Standard GBFS 2.2
    • system_hours. Describes the system hours of operation. According to the Standard GBFS 2.2
    • system_information. Details including system operator, system location, year implemented, URL, contact info, time zone. According to the Standard GBFS 2.2
    • system_pricing_plans. Describes the pricing schemes of the system. According to the Standard GBFS 2.2
    • system_regions. Describes regions for a system that is broken up by geographic or political region. According to the Standard GBFS 2.2
    • vehicle_types. Describes the types of vehicles that System operator has available for rent (added in v2.1-RC). According to the Standard GBFS 2.2