Provide the actual mapping table of SilverERP

[RaphaelKomander]

Mapping example of the proprietary data model towards the current standard data model.

Proprietary data model	Direction	Standard data model - address
name	>	person.firstName
name	>	person.lastName
street	>	person.address.street
street	>	person.address.number
note	?	-

As seen on @ealtendorf her contribution, dot notation allows to explain nested data structured in a readable form - with columns left aligned.

---

Regarding nested objects, a data point mapping at a two-dimensional table isn't practical.

Rather document your application's data model as JSON format via doca's web interface - suited to present nested structures. @JosefBraeuer

JSON STRUCTURE (object.json)

"definition": {
  "datapoint": {
    "type": "string",
    "description" : "Important for the semantic data point mapping"
    "example" : "An entity would look like"
    }
},
"required": ["datapoint"],
"properties": {
   "datapoint": {"$ref": "#/defintions/datapoint"},
   "NestedObject": {"$ref": "./source.json"},
   "FetchedDefinition": {"$ref": "./source.json#/definitions/datapoint"},
   "FetchedProperty": {"$ref": "./source.json#/propterties/datapoint"}
}

In this example the source.json has a proper object defined. The "$ref:" attribute is a name space - link.