1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. _data-formats:
Data Formats
============
Data formats are descriptions of data; they are the data contract
between your component and other components. When the components are
‘composed’ into services in the Design tool, they can only be matched with
components that have compatible data formats. Data formats will be
onboarded to Design tool and assigned a UUID at that time. This UUID is then
used to ensure compatibility amoung components. (If component X outputs
data format ‘DF-Y’, and another component Z specifies ‘DF-Y’ as its
input data format, then X is said to be ``composable`` with component
Z).
Since data formats will be shared across components, the onboarding
catalog should be checked first to see if the desired data format is
available before creating one. The vision is to have a repository of
shared data formats that developers and teams can re-use and also
provide them the means to extend and create new custom data formats. A
data format is referenced by its data format id and version number.
JSON schema
-----------
The data format specification is represented (and validated) against
this `Data Format json schema <https://git.onap.org/dcaegen2/platform/plain/mod/component-json-schemas/data-format/dcae-cli-v1/data-format-schema.json>`__
and described below:
Meta Schema Definition
~~~~~~~~~~~~~~~~~~~~~~
The “Meta Schema” implementation defines how data format JSON schemas
can be written to define user input. It is itself a JSON schema (thus it
is a “meta schema”). It requires the name of the data format entry, the
data format entry version and allows a description under “self” object.
The meta schema version must be specified as the value of the
“dataformatversion” key. Then the input schema itself is described as
one of the four types listed below:
+------------------+---------------------------------------------------+
| Type | Description |
+==================+===================================================+
| jsonschema | inline standard JSON Schema definitions of JSON |
| | inputs |
+------------------+---------------------------------------------------+
| delimitedschema | delimited data input using a JSON description and |
| | defined delimiter |
+------------------+---------------------------------------------------+
| unstructured | unstructured text, and reference that allows a |
| | pointer to another artifact for a schema. |
+------------------+---------------------------------------------------+
| reference | allows for XML and Protocol Buffers schema, |
| | but can be used to reference other JSON, |
| | delimitedschema and unstructured schemas as well. |
+------------------+---------------------------------------------------+
Example Schemas
---------------
By reference example - Common Event Format
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
First the full JSON schema description of the Common Event Format would
be loaded with a name of “Common Event Format” and the current version
of “25.0.0”.
Then the data format description is loaded by this schema:
::
{
"self": {
"name": "Common Event Format Definition",
"version": "25.0.0",
"description": "Common Event Format Definition"
},
"dataformatversion": "1.0.0",
"reference": {
"name": "Common Event Format",
"format": "JSON",
"version": "25.0.0"
}
}
Simple JSON Example
~~~~~~~~~~~~~~~~~~~
::
{
"self": {
"name": "Simple JSON Example",
"version": "1.0.0",
"description": "An example of unnested JSON schema for Input and output"
},
"dataformatversion": "1.0.0",
"jsonschema": {
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"raw-text": {
"type": "string"
}
},
"required": ["raw-text"],
"additionalProperties": false
}
}
Nested JSON Example
~~~~~~~~~~~~~~~~~~~
::
{
"self": {
"name": "Nested JSON Example",
"version": "1.0.0",
"description": "An example of nested JSON schema for Input and output"
},
"dataformatversion": "1.0.0",
"jsonschema": {
"$schema": "http://json-schema.org/draft-04/schema#",
"properties": {
"numFound": {
"type": "integer"
},
"start": {
"type": "integer"
},
"engagements": {
"type": "array",
"items": {
"properties": {
"engagementID": {
"type": "string",
"transcript": {
"type": "array",
"items": {
"type": {
"type": "string"
},
"content": {
"type": "string"
},
"senderName": {
"type": "string"
},
"iso": {
"type": "string"
},
"timestamp": {
"type": "integer"
},
"senderId": {
"type": "string"
}
}
}
}
}
}
}
},
"additionalProperties": false
}
}
Unstructured Example
~~~~~~~~~~~~~~~~~~~~
::
{
"self": {
"name": "Unstructured Text Example",
"version": "25.0.0",
"description": "An example of a unstructured text used for both input and output for "
},
"dataformatversion": "1.0.0",
"unstructured": {
"encoding": "UTF-8"
}
}
An example of a delimited schema
--------------------------------
::
{
"self": {
"name": "Delimited Format Example",
"version": "1.0.0",
"description": "Delimited format example just for testing"
},
"dataformatversion": "1.0.0",
"delimitedschema": {
"delimiter": "|",
"fields": [{
"name": "field1",
"description": "test field1",
"fieldtype": "string"
}, {
"name": "field2",
"description": "test field2",
"fieldtype": "boolean"
}]
}
}
Note: The referenced data format (in this case, a schema named “Common
Event Format” with version of “25.0.0”) must already exist in the
onboarding catalog.
Working with Data Formats
-------------------------
Data Formats can be validated using `schema <https://git.onap.org/dcaegen2/platform/plain/mod/component-json-schemas/data-format/dcae-cli-v1/data-format-schema.json>`__
Once validated, the dataformat can be onboarded using :doc:`DCAE-MOD <../DCAE-MOD/DCAE-MOD-User-Guide>`
|
