Simplify the structure of optical data sets

[christoph-maurer]

opticalData.json has been using a tree structure to allow complex optical data which may share one or more componentCharacteristics. For software developers, this tree is more complicated to implement than a simple array. We therefore exchange the tree structure by a simple array.

[christoph-maurer]

@simon-wacker I don't like the structure

"optical": [
  {
    "data": [
      {
        "data": [
          {
            "dataPoints": [

in the examples. But I don't see a better solution especially when the property serverSpecific is added.

"optical": [
  {
    "data": [
      {
        "data": [
          {
            "dataPoints": [...]
          }
        "serverSpecific":[...]

We could rename "optical:[{"data": to "optical:[{"opticalData":, but that doesn't solve it.

You can make changes and merge this pull request when you think that it is ok.

[simonwacker]

I don't like the structure

I'd leave it like that for now. In practice there is a GraphQL response conforming essentially to optical.json and a GET HTTPS resource conforming to opticalData.json. The latter is not inlined with the former, unless someone does it manually. So the case data { data { ... does not really occur in practice. We could name the data in opticalData.json something like node or group or section or ... but I wouldn't do so now as that would invalidate all existing data that conforms to the current schema.

[simonwacker]

Superficial comments (integrate or leave as is and then just merge). The changes are solid 🥇

Thanks for the comments! I resolved them.