Revision as of 18:59, 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!

You can find the object graph for VME here, in order to have an idea of the model.

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

TemplateEditor

The Target, in this case the VME-DB, is an object graph. Every object in the target is represented in iMarine through a KeyType. Of course an object has attributes, therefore also a KeyType has attributes.

• KeyType: This is the name of the object in the VME-DB
• Attribute: is the name of the attribute of a certain object

• TODO: Engineer and explain better the concept of Parent and Child.

KeyValue

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: see above TemplateEditor
• id: is the id of the object in the in the VME-DB of a certain type(keyType).
• attribute: see above TemplateEditor
• value: the value for that attribute

Target

The target is from a iMarine point of view a collection of KeyValue(s)

Webservice