Difference between revisions of "Ecosystem Approach Community of Practice: VME iMarine"
(→UML) |
(→UML) |
||
| Line 10: | Line 10: | ||
=UML= | =UML= | ||
| + | |||
| + | ==concept== | ||
This diagram describes conceptually the model of the Report Editor as the format of a Delta. | This diagram describes conceptually the model of the Report Editor as the format of a Delta. | ||
| Line 20: | Line 22: | ||
* value: the value for that attribute | * value: the value for that attribute | ||
| + | ==target== | ||
[[File:Content.jpg]] | [[File:Content.jpg]] | ||
| Line 25: | Line 28: | ||
[[File:Target.jpg]] | [[File:Target.jpg]] | ||
| − | + | ==TemplateEditor== | |
[[File:TemplateEditor.jpg]] | [[File:TemplateEditor.jpg]] | ||
| + | ==Webservice== | ||
[[File:Webservice.jpg]] | [[File:Webservice.jpg]] | ||
Revision as of 18:49, 20 August 2013
Introduction
The VME project has started to investigate how the iMarine infrastructure could work in combination with the VME-DB on FAO side. This page tries to make all assumptions explicit and therefore will probably be heavily used for discussion!
The big picture
Stateful or Stateless?
The above picture assumes that the iMarine infrastructure will not hold state regarding the VME-DB. Content will flow from the VME-DB to iMarine, will be subject to manipulation and a stream of deltas will flow from iMarine into the VME-DB trough the webservice.
UML
concept
This diagram describes conceptually the model of the Report Editor as the format of a Delta.
A Report is a collection of KeyValue(s). The Delta is a collection of KeyValue(s), representing a change of content.
KeyValue has the following attributes:
- keyType: This is the name of the object in the VME-DB
- id: is the id of the object in the in the VME-DB of a certain type(keyType).
- attribute: is the name of the attribute of a certain object
- value: the value for that attribute
target
The target is from a iMarine point of view a collection of KeyValue(s)
TemplateEditor
Webservice
