Skip to content
Snippets Groups Projects
Commit 40504945 authored by Yongjing Zhang's avatar Yongjing Zhang
Browse files

adding a change-log section in the README

parent cc7bcc24
No related branches found
No related tags found
1 merge request!5Mas 2018 0081 sdt4 change log
...@@ -8,9 +8,21 @@ Note that this project runs under the 3-Clause BSD License. Read the [LICENSE](L ...@@ -8,9 +8,21 @@ Note that this project runs under the 3-Clause BSD License. Read the [LICENSE](L
Any contributions made to this project must comply with the aforementioned license. Any contributions made to this project must comply with the aforementioned license.
This version contains the following changes comparing to Version 3.0:
1. Rename 'Device' to 'DeviceClass'
2. Remove 'Module' to simplify the SDT model
3. Introduced 'Product' for concrete model definition of real products.
4. Support JSON serialization
5. Support inheritance of 'DeviceClass'
6. Enum type ...
7. Data Type Facets ...
8. ...
*Editor's note: the current change log is just an examplary list (a projection), which lists some initial thoughts that the group is working on based on previous discussion. It needs to be revisited according to all implemented features before SDT4.0 publication.*
## Quick Introduction ## Quick Introduction
The Smart Device Template (SDT) is a template which is used to model the capabilities, actions and events of connected devices. The intent of the SDT is to be able to model any type of connected device using a well accepted and standardised format. The main application of SDT is to enable a uniformly structured Application Programmers Interface (API) to applications that need to interact with connected devices. Usually, these applications would communicate to devices using an Abstraction Layer as an intermediary logic. The Abstraction Layer hides the technology-specific, native language format of devices of different technology type from the applications. The Smart Device Template (SDT) is a template which is used to model the capabilities, actions and events of connected devices. The intent of the SDT is to be able to model any type of connected device using a well accepted and standardised format. The main application of SDT is to enable a uniformly structured Application Programmer's Interface (API) to applications that need to interact with connected devices. Usually, these applications would communicate to devices using an Abstraction Layer as an intermediary logic. The Abstraction Layer "hides" the technology-specific, native language format of devices of different technology type from the applications.
[Read the full Introduction.](SDT/schema4.0/docs/Introduction.md) [Read the full Introduction.](SDT/schema4.0/docs/Introduction.md)
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment