The revolution in data synchronization — the Open Integration Hub enables simple data synchronization between any software applications and thus accelerates digitalisation
Visit the official Open Integration Hub homepage
The Open Integration Hub enables data synchronization across a variety of applications. This requires unified data structures — the master data models of the Open Integration Hub. Currently, there are models for the domains addresses and products. In addition, two more models for the domains collaboration and documents will follow soon. More models are to be developed in the very near future. To elaborate further models and to make the Open Integration Hub even better - we need you! So join us and help us grow as an open source community!
Within the scope of the master data models of the Open Integration Hub you can contribute in two different ways. You can either request/propose a change to an already existing model or contribute a new model for an currently not existing domain.
An existing model can be change in different ways. The possibility exists to add or remove something from the model or to change an existing part, such as an attribute.
If you want to propose a model change please use the request for model change survey (Currently only available for the domain addresses).
The unified process for changing a model is explained in the following:
- Fill out the request for model change survey
- Submit the proposal
- The relating workgroup will check the proposal according to fix rules
- If the proposal is approved the change will be incorporated into the model
- A new model version will be published within the next release
If you want to contribute a new model for a currently not yet existing domain, please consider the following steps:
Before you start please read the Introduction into Open Integration Hub master data models and How to contribute a new data model.
Before you contribute please read our contribution guidelines.
To see how members of the community are expected to behave, please read the code of conduct. We apply the code of conduct defined by the Contributor Covenant, which is used across many open source projects, such as NodeJS, Atom and Kubernetes.
When looking for further information or support, please contact: [email protected] .
- Decisions: This folder contains all outstanding/made decisions by the workgroup categorized by open and closed decisions
- MasterDataModels: This folder contains general information about the data models, an explanation of the OIHDataRecord and all currently existing master data models
- Protocols: Contains meeting protocols of the workgroup meetings
- src: All JSON schemes can be found here. This includes JSON schemes for all existing master data models, the overarching OIHDataRecord and a generic example as a starting point for writing JSON schemes for the relating data model
- CONTRIBUTING: Gathers any rule considering the contribution for the Open Integration Hub project
- Onboarding: Describes how to proceed when developing a master data model and a connector. It lists the most important documents from the connectors repository and the data and domain models repository, to simplify the onboarding process.
- CODE_OF_CONDUCT: Contains an explanation of the expected behavior of the community members, following the code of conduct defined by the Contributor Covenant
- Each workgroup has atleast one status call every two weeks
- Every committer must attend the status call
- The governance model defines the workgroup members' roles into managers, committers or contributors
| Member Name | GitHub Alias | Company | Role |
|---|---|---|---|
| Hansjörg Schmidt | hschmidthh | Wice | Manager |
| Philipp Hoegner | philecs | Cloud Ecosystem | Committer |
| Patrick Levie | plevie | Interact.io | Contributor |
| Roman Okon | ROKON1987 | 1&1 Internet SE | Contributor |
| Member Name | GitHub Alias | Company | Role |
|---|---|---|---|
| Philipp Hoegner | philecs | Cloud Ecosystem | Manager |
| Elke Altendorf | ealtendorf | StoneOne | Committer |
| Andreas Giloj | ag737 | Fraunhofer IESE | Committer |
| Franz Degenhardt | FranzDegenhardt | X-Integrate | Committer |
| Member Name | GitHub Alias | Company | Role |
|---|---|---|---|
| Peter Heimig | heimig | Agindo | Manager |
| Dennis Steiniger | dennisCES | Cloud Ecosystem | Committer |
| Patrick Levie | plevie | Interact.io | Committer |
| Member Name | GitHub Alias | Company | Role |
|---|---|---|---|
| Nils Mosbach | nils-mosbach | ELO Digital Office | Manager |
| Philipp Hoegner | philecs | Cloud Ecosystem | Committer |
| Matthias Thiele | MatthiasThiele | ELO Digital Office | Contributor |
| Benoit Clernet-Gurnaud | bclerget | ELO Digital Office | Contributor |
| Member Name | GitHub Alias | Company | Role |
|---|---|---|---|
| Hans Eggert | heggert | Basaas | Manager |
| Nils Mosbach | nils-mosbach | ELO Digital Office | Committer |
| Philipp Hoegner | philecs | Cloud Ecosystem | Committer |
| Hansjörg Schmidt | hschmidthh | Wice | Committer |
| Peter Heimig | heimig | Agindo | Committer |
Within the project different terms and abbreviations are frequently used. All terms and abbrevations are explained within the glossary and our list of abbrevations.