Author: maestro

On the front page under the Community menu, there are two new entries
– Adopters: Lists the use cases documented in the different data models. It includes searchable facilities. It contains these fields:  adopter, description, mail, organization, project, comments, start date, subject and data model.

If you want to be listed, just make a PR on the file ADOPTERS.yaml of the data model folder. (The PR has to include an example ‘payload’ on how you use it)

– Contributors: Lists the people. It contains these fields:  name, surname, mail, organization, project, comments, year, and subject.

If you want to be listed you have to have contributed to any of the data models of the subject and then make a PR on the CONTRIBUTORS.yaml at the root of the subject.

In both cases the attributes are not mandatory so they can be empty.

In the documentation menu (Home -> documentation -> Basic info for:), there are now 4 new options to provide you with the basic information depending on your profile

• User. For those visitors with limited knowledge about what are the Smart Data Models
• Contributor. For those visitors willing to extend or to contribute with new data models
• Developer. For those visitors willing to integrate the data models with other tools or initiatives
• Researcher. For those visitors whose aim is to understand what is agile standardization and how it is implemented at the Smart Data Models Program

If you have some of these profiles and you miss some information please let us know

Initially, you will see few changes in the specifications of all data models,(it is in progress because it will last around 2 days to get it completed)

– The inclusion of the model for those attributes having it.

– Including the data type (when there is only one) for the attributes. ”

• address[object]: The mailing address. Model: https://schema.org/address“

– A footer with some useful links, etc

Smart Data Models +++ Contribution Manual +++ About

but there is another hidden relevant change. The specifications are now divided into sections by these tags:

<!– section name –>

<!– /section name –>

It makes easier to update part of the specification without disrupting the rest of the content, and in most markdown viewers it is unnoticed. Besides this, it also allows the extension of the specification (if needed in a coming future) with new sections.

And, of course, everything can be done automatically. Thus we can keep being agile according to our principles.

Therefore, if you see that the specifications are presenting an update don’t worry, Initially, it is just the format and this new trick.

And welcome to the Chinese translation which is using this new format already.

Now the list of specifications has a new language, Chinese. they are called spec_ZH.md
See the example with the WaterConsumption data model.