Change JSON format for data

[SebastianSchildt]

In VISS 2 data is not in a simple item "value", but in a structure that allwos returning several data points

 "data": {
            "description": "Data including path and one or more data point(s).",
            "type": "object/array",
            "properties": {
                "path": {
                    "description": "The path to the desired vehicle signal(s), as defined by the metadata schema.",
                    "type": "string"
                },
                "dp": {
                    "description": "Data point including one or more value and time samp",
                    "type": "object/array"                   
                    "properties": {
                        "value": {
                            "description": "The value related to the associated path.",
                            "type": "string"                    
                        },
                        "ts": {
                            "description": "Timestamp associated with the value capture.",
                            "type": "string"                    
                        }
                }
            }   
        },

[SebastianSchildt]

See also https://raw.githack.com/w3c/automotive/gh-pages/spec/VISSv2_Core.html#multiple-signals-request

[wenwenchenbosch]

according to the specification, response should look like this:

“data”:{“path”:”X”, “dp”:{“value”:”Y”, “ts”:”Z”}}
or
“data”:{“path”:”X”, “dp”: [{“value”:”Y1”, “ts”:”Z1”}, …, {“value”:”Yn”, “ts”:”Zn”}]}
or
“data”:[{“path”:”X1”, “dp”:{“value”:”Y1”, “ts”:”Z1”}}, …, {“path”:”Xm”, “dp”:{“value”:”Ym”, “ts”:”Zm”}}]
or
“data”:[{“path”:”X1”, “dp”:[{“value”:”Y11”, “ts”:”Z11”}, …, {“value”:”Y1n”, “ts”:”Z1n”}]}, …]

@SebastianSchildt: do we really need description, type and properties?

[SebastianSchildt]

I I do not quite get the question. Your examples are correct and they should all be in line with the JSON schema above. A single object or an array of dp where value and ts are mandatory properties.

You can also test here: https://www.jsonschemavalidator.net if you find a mismatch between schema and the examples I would consider this a bug in VISS