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.

 

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.

Updated the attributes search data base

In order to create a new data model is always interesting what others have done in order copy and to maintain interoperability.

That’s why we have available a database with all attributes and enumerations across all data models.

Now it’s updated daily and the number of occurrences is also available.

What’s is your opinion of the new specification model?

We are testing a potential new format for the specification that

1) makes easier for people to read the specification

2) provides additional utility to be connected with other platforms making NGSI more compatible

Could you check these two new specifications Building, BuildingOperation compared with the old two Building, BuildingOperation and gives us your opinion?

(once in, click on the name of the object for deploying all the content)

[cf7form cf7key=”new-specification-format”]

The actual new specs are here without viewer (building, building operation) what you see above is generated automatically from the yaml specs.

What’s the idea behind adopting yaml specifications? To allow multiple evolutions (automatic multilanguage spec, integration with other platforms, etc)

Documentation status for all data models

Every day will be checked the documentation available for each data model and the result is dumped in the file documentationStatus.json

It would help a user to identify all the documentation, examples, schemas and specification available and it allows an automated use for any other purpose.

Check it out.

 

Open issues for all data models

There is a new widget on the front page titled “Open PR and issues” there you can browse all the Pull requests contributed by the community and the open issues across all the data models.

Updated every 5 minutes

This way you can be informed about evolution going on and to make sure that all contributions are considered.