In the process of converting repositories to the new format, the repo dataModel.Parking is being converted.
It means:
- json schema has already documented every property
- The new specs in EN-US, FR and ES are available
In the process of converting repositories to the new format, the repo dataModel.Parking is being converted.
It means:
In the process of converting repositories to the new format, the repo dataModel.Streetlighting is being converted.
It means:
There is a working group about risk assessment. They are starting to work in the incubated repository in a Risk assessment repository. Some results are expected in the coming 4 weeks.
The initial evaluation of risks will be focused on the water networks’ risks, but generaliation is expected.
Thanks to the contributors of Store data model inside the point of interest repository it has been detected an error in the shared element which maps schema.org concept of opening hours specification which was located at commons in the root of data models repository.
The manual for a simple contribution of a data model has been updated. See it in this link.
This is the first survey to the USERS of the Smart Data Models. We want to know what is more important to you and try to prioritize our efforts. This is an agile initiative, therefore we will take into very consideration your comments. Your survey is anonymous although if you wish you can include your email in comments and we will contact you regarding your comments.
You can answer it here.
Soon there will be another survey for the CONTRIBUTORS.
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.
Published the contribution manual for the repository.
If you are not a developer (But if you are you can also use it) we have created a page for being updated about the last news of your domain of interest
Check the 10 mail lists available, one per domain. Click in the image to access it.
It is also available in the main menu in the option Subscribe
Most of the data models come from different groups of people interested in the creation of standards in an agile way.
Here you can access a cheat sheet (Let’s call it methodology) on how to tackle these tasks.
summarized these are the steps. It takes for granted that the group is already available.
Step 0. Gather documentation
Step 1. Compile elements.
Step 2. Meet to reach a Generalization proposal
Step 3. Internal validation
Step 4. Create the technical documentation of a data model
Step 5. Submit your data model
Step 6. Review
Step 7. Disseminate