Discussion: Ways of model integration - Revision history

Eva Wiechers at 13:48, 22 February 2016

2016-02-22T13:48:59Z

Eva Wiechers at 21:51, 8 February 2016

2016-02-08T21:51:44Z

Eva Wiechers at 21:50, 8 February 2016

2016-02-08T21:50:08Z

Eva Wiechers at 21:16, 8 February 2016

2016-02-08T21:16:57Z

Eva Wiechers: Created page with " ... "

2016-02-08T20:22:17Z

Created page with " ... "

New page

...

@@ Line 2: / Line 2: @@
 (platform.openmod-initiative.org/modelintegration)
-<u>'''Use Case of model developers:'''</u>
 In this part of the platform the model developers discuss different ways of model integration e.g.
@@ Line 12: / Line 12: @@
 Moreover, the users can discuss and refer to challenges, solutions and models for which the integration already succeed.
-In order to be able to define the interfaces between different models correctly, a clear understanding of the meaning of used terms and (input) parameters as well as information about the functionalities of different models are required. The overall nomenclature ("übergreifendes Bergiffssystem") is based on the analyse of existing models and saved as a common ontology (see [[Wiki_for_collaborative,_open_source_modelling|glossary]].)
+In order to be able to define the interfaces between different models correctly, a clear understanding of the meaning of used terms and (input) parameters as well as information about the functionalities of different models are required. The overall nomenclature ("übergreifendes Bergiffssystem") is based on the analyse of existing models and saved as a common ontology (see [[Wiki for collaborative, open source modelling|glossary]].)
 <u>'''Implementation:'''</u>
 Starting with a wiki like set-up.

@@ Line 12: / Line 12: @@
 Moreover, the users can discuss and refer to challenges, solutions and models for which the integration already succeed.
-In order to be able to define the interfaces between different models correctly, a clear understanding of the meaning of used terms and (input) parameters as well as information about the functionalities of different models are required. The overall nomenclature ("übergreifendes Bergiffssystem") is based on the analyse of existing models and saved as a common ontology (see glossary.)
+In order to be able to define the interfaces between different models correctly, a clear understanding of the meaning of used terms and (input) parameters as well as information about the functionalities of different models are required. The overall nomenclature ("übergreifendes Bergiffssystem") is based on the analyse of existing models and saved as a common ontology (see [[Wiki_for_collaborative,_open_source_modelling|glossary]].)
 <u>'''Implementation:'''</u>
 Starting with a wiki like set-up.

@@ Line 6: / Line 6: @@
 In this part of the platform the model developers discuss different ways of model integration e.g.
-*Connecting models (integration light): In order to connect different models the users store input and output data of the models they apply into the provided databases (oedb and wdb; see above). Standards to ensure the collaboration of the models will be discussed and documented here or in the Github beloning to the database.
+*Connecting models (integration light): In order to connect different models the users store input and output data of the models they apply into the provided [[Database|databases]] (oedb and wdb). Standards to ensure the collaboration of the models will be discussed and documented here or in the Github beloning to the database.
-*Integration modules: A (meta) model is made up of a certain selection of models and the joining integration module (“meta module” for model communication) as well as additional programme code, if required (see figure 1-3). Integration modules might be written in programming language of the model it wants to connect.
+*Integration modules: A (meta) model is made up of a certain selection of models and the joining integration module (“meta module” for model communication) as well as additional programme code, if required. Integration modules might be written in programming language of the models it wants to connect.
 *Integration tool with GUI: In the long-run the model developers might develop for a selection of models an integration tool, which can be used to assemble a model from different models by clicking (GUI).

← Older revision		Revision as of 21:16, 8 February 2016
Line 1:		Line 1:

−	...	+	(platform.openmod-initiative.org/modelintegration)
		+
		+	<u>'''Use Case of model developers:'''</u>
		+
		+	In this part of the platform the model developers discuss different ways of model integration e.g.
		+
		+	*Connecting models (integration light): In order to connect different models the users store input and output data of the models they apply into the provided databases (oedb and wdb; see above). Standards to ensure the collaboration of the models will be discussed and documented here or in the Github beloning to the database.
		+	*Integration modules: A (meta) model is made up of a certain selection of models and the joining integration module (“meta module” for model communication) as well as additional programme code, if required (see figure 1-3). Integration modules might be written in programming language of the model it wants to connect.
		+	*Integration tool with GUI: In the long-run the model developers might develop for a selection of models an integration tool, which can be used to assemble a model from different models by clicking (GUI).
		+
		+	Moreover, the users can discuss and refer to challenges, solutions and models for which the integration already succeed.
		+
		+	In order to be able to define the interfaces between different models correctly, a clear understanding of the meaning of used terms and (input) parameters as well as information about the functionalities of different models are required. The overall nomenclature ("übergreifendes Bergiffssystem") is based on the analyse of existing models and saved as a common ontology (see glossary.)
		+
		+	<u>'''Implementation:'''</u>
		+
		+	Starting with a wiki like set-up.