We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mapping example of the proprietary data model towards the current standard data model.
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.
The text was updated successfully, but these errors were encountered:
JosefBraeuer
No branches or pull requests
Mapping example of the proprietary data model towards the current standard data model.
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)
The text was updated successfully, but these errors were encountered: