The contribution manual, located at https://bit.ly/contribution_manual is being updated, including more explicitly the need for a complete contribution. See pages 3 and 4.
No comments
Author: maestro
Smart Health domain
A new domain is available. Smart Health were subjects related to Smart health is going to be compiled.
Currently it is open with a incipient subject about #COVID19 and a VaccinationCertificate.
It is being assessed if OHDSI can be mapped into smart data models. For such purpose there is a directory in the pending repository.
VaccinationCertificate for COVID (or other) in the subject COVID19
In the new subject dataModel.COVID19 there is a new data model, VaccinationCertificate capable of storing a vaccination certificate and signing it with a DLT resource.
VaccinationCertificate. Description of a COVID-19 Vaccination Certificate.
Thanks to the contributors.
New Subject dataModel.RiskManagement
A new subject has been created in the CrossSector domain.
dataModel.RiskManagement compiles data models for generic risk management.
Candidate data models are being developed in the incubated repository .Â
Soon it will be populated with these data models: Asset, CyberAnalysis, Exposure, GISData, Hazard, Measure, Mitigation, NetworkServiceAlert, Risk, Vulnerability.
Summary of open session 2012-05-24
Find here the presentation of the open session
20210517-OPEN-SESSION-SMART-DATA-MODELS
To join these sessions connect to https://bit.ly/smartdatamodels (direct link to the online session)
To include your topic as a slot in the session, edit these slides https://bit.ly/open_session
2021-05-24 Topics:
- New and updated data models
- New regulations to be adopted
- Risk management data models
- Validation of examples
Data model README improvement
The README.md of every data model provides the links to the different translations of the specification. These sentences are now in their original languages.
Additionally, these links now take to the specification in GitHub and stop prompting to be downloaded.
Other information available in the README include:
- Links to the automatic creation of examples in NGSI-LD format
- Links to the actual examples of the use of this data model in 4 differnt formats
This format update will be completed today for all data models.
If you can think of other improvements please let us know.
Extended the device model
A new property dateObserved has been added to the device data model allowing the use of a customized data attached to any observation of the device payload. Also included the property mcc (mobile country code).
Device Subject comprises these data models:
- Device. An apparatus (hardware + software + firmware) intended to accomplish a particular task (sensing the environment, actuating, etc.).
- DeviceModel. This entity captures the static properties of a Device.
- PrivacyObject. Information about privacy for an IoT device
- SmartMeteringObservation. This entity contains a harmonised description of a Smart Meter Observation, generally applicable for Smart Homes, Industry, Cities and Agriculture. It is based mostly in the GSMA entity definition but it is extended
DTLtxReceipt data model for registering a transaction in a DLT resource
DTLtxReceipt is the first data model of the subject Distributed Ledger technologies for
DLTtxReceipt. Description of a DLT receipt storing some of the attributes (keys) of a transaction.
Coming from the EU project Cattle chain.
New subject RoboticIndustrialActivities an new data models Piece, Pallet, RoboticArm, RoboticCell and VacuumPump
There is a new subject, dataModel.RoboticIndustrialActivities, in the Smart Robotics domain for compiling data models related to industrial activities with robots. it currently compiles these data models.
- Pallet. A pallet containing pieces for manufacturing.
- Piece. A Piece to be manufactured.
- RobotArm. A robotic arm for moving pieces.
- RoboticCell. A Robotic cell.
- VacuumPump. A vacuum pump.
Thanks to the contributors of the DIH2 project.
Update the specs
Many of the contributors of the data models are providing changes into the spec.md and its translations.
Fortunately, this is not necessary. You just need to provide the changes in the descriptions included in the schema.json file of each data model.
Now in order to save time for the contributors, a warning message has been included in the specs.
The link takes you to the contribution manual section where the specification is described.
