• Domains

  • Governance

    The availability of widely adopted (de-facto standard) information models is key for creating a global digital single market of interoperable and replicable (portable) smart solutions in multiple domains (smart cities, smart agrifood, smart utilities, smart industry, …).

    More

    Such models provide an essential element in the common technical ground needed for standards-based open innovation and procurement. Data Models play a crucial role because they define the harmonised representation formats and semantics that will be used by applications both to consume and to publish data.

    The FIWARE Foundation, TM Forum, IUDX and other entities to join, are leading a joint collaboration program to support the adoption of a reference architecture and compatible common data models that underpin a digital market of interoperable and replicable smart solutions in multiple sectors, starting with smart cities. All data models are public and royalty-free nature of specifications. Data Model Licensing mode. Preferred Creative Commons by Attribution 4.0

    Organizations can evolve their current data sharing policies towards a vision which, shared with other organizations, brings support to a Data Economy.

    This GitHub organization structure contains JSON Schemas and documentation on Smart Data Models for different Smart Domains. For each Domain (industrial sector) there is a Repository containing as submodules the link to the Subjects containing all the Data Models related. And some other shared elements for all the domain. For each Vertical(Subject) there is a Repository containing the Data Models related to that vertical. These repositories do admit pull requests regardign data models.

    General Principles
    1. Driven-by-implementation approach: Specifications will be considered stable as soon as enough end user organizations (e.g., cities) have validated them in practice.
    2. Open-closed. Breaking changes to already approved specs are not allowed. Instead, new versions shall deprecate attributes, add new attributes, extend enumerations, etc.
    3. Open contribution. Contributions open to anybody (not only members), while final decision making corresponds to the administrators of the domains and Subjects. Management (currently TM Forum, FIWARE Foundation and IUDX) could opposed to some contributions if it does not meet coding guidelines.

Drafted Node data model

This data model, node, is not officially approved but is on the path for becoming a resource for simulation a node inside a digital twin model (See this video) receiving the measures from an array of sensors controlling different properties and to provide these data to several other nodes which can be connected to.

Remember that incubated repository is devoted to the design and test before submitting officially to the Smart Data Models initiative.

You can claim access to this repository in the issue form option access to the incubated repository.

 

Converted Global Data dictionary codes

What is Global Data Dictionary

The GS1 Global Data Dictionary (GDD) is a repository of the data elements defined across all GS1 Standards.

What is the scope of the Global Data Dictionary?

GS1 Business Message Standards (BMS) and their components with definitions for GDSN 3.1, 3.1.2 , 3.1.3 and 3.1.4, GS1 XML for EDI 3.0, 3.13.2 and 3.3, TSD and EPCIS 1.0.1. Higher versions will be added upon ratification.

  • Business Messages
  • Business Information Entities – message components and the relationship between them
  • Business Data Types
  • Code Lists used in Business Messages

The Business Messages are composed of Business Information Entities that comprise classes of information and their attributes. The attributes, in turn, have data types that may contain code list

The Full Set of GDSN & Shared Code Lists, and the Full Set of EDI, EPCIS, CPV & Shared Code Lists is now in a structured format in json much easier to integrate with NGSI platform.

Soon there will be part of them integrated into the smart data models.

Working with https and improvement in the issue form

1.- It is just a technical improvement but now you can access everything in this site with https://data-models.fiware.org.

2.- The issue form has also been improved with new options but simplified structure.

Check it out and please report any issue.

Best

Simplified the subscription page

The subscription page is being dramatically simplified keeping the same functionality.

Now instead of having different forms for the different mail lists nos it is just a checkbox fo the list you are willing to subscribe.

Remember just one mail once a week.

These are the weekly domains lists unless there is something relevant on any topic.
Subscribe to the newsletter you wish by clicking in the option.

New version of contributors file

Every subject had a file named CONTRIBUTORS.md which compiles all contributors to the different data models in this subject. However, from the point of view of the management, it was not a structured format. Due to this, it is going to be replaced with a new file named CONTRIBUTORS.yaml with the same info but structured so we could manage properly and answer questions like:

  • How many contributors collaborate in this subject?
  • How many subjects are being contributed by this person?
  • What organisations are contributing to the initiative?

Now there is also a field for allocating comments.

The format is friendly enough to be simply edited but at the same time, it can be automatically processed.

Next week CONTRIBUTORS.md will be removed from the different repos.

New commons section for data models

There is a new common section, named “DateTime-Commons“,  in the file common-schema.json (the one which is partially included into most of the data models) because it compiles some shared elements (like Location-Commons or GSMA-Commons).
This section includes the first element, which is the mapping into a property (type object) of the schema.org class OpeningHoursSpecification. (see below)

So whenever there is an opening hours specification this would be the chosen format. (It is true that there is a similar property named OpeningHours, also mapped in schema.org) that it is only a text (oriented to be printed more than queried).

It only affects the museum data model that it will be updated after gathering the feedback of the contributors.

The new section included.

“DateTime-Commons”: {
“type”: “object”,
“description” : “All date-time elements in data models unless explicitly stated are ISO 8601 compliant”,
“properties”: {
“openingHoursSpecification”: {
“type”: “array”,
“description”: “A structured value providing information about the opening hours of a place or a certain service inside a place.”,
“items”: {
“properties”: {
“opens”: {
“type”: “string”,
“format”: “date-time”
},
“closes”: {
“type”: “string”,
“format”: “date-time”
},
“dayOfWeek”: {
“type”: “string”,
“enum”: [
“Monday”,
“Tuesday”,
“Wednesday”,
“Thursday”,
“Friday”,
“Saturday”,
“Sunday”,
“PublicHolidays”
] },
“validFrom”: {
“type”: “string”,
“format”: “date-time”
},
“validThrough”: {
“type”: “string”,
“format”: “date-time”
}
}
},
“minItems”: 1
}
}

See it in the original file common-schema.json.