In Network Rates - Schema Update - In Network Object - 2 dimensional Array?

[jonberkery-work]

Since there have been recent schema updates to the In Network Rates file. I would like to propose another one for consideration.

Could the "in_network" array on the root, be redefined as a 2-Dimensional Array (aka - an array of in_network object arrays)?

What I am recommending in terms of a schema definition change would be what is below and starts at line 245 of the current .json Schema definition

 "array_of_in_network_arrays": {                <----- new 2-dimensional array definition
      "type": "array",                          <----- type definition
      "items": {                                <----- items of array definition
        "in_network": {
          "type": "array",
          "items": {
            "$ref": "#/definitions/in_network"
          },
          "default": []
        }
      },                                            <----- closes the items definition of the outer array
      "default": []                                 <----- default setting for the outer array
    }                                               <----- closes the definition of the outer array
  },                                                
  "required": [
    "reporting_entity_name",
    "reporting_entity_type",
    "reporting_plans",
    "last_updated_on",
    "array_of_in_network_arrays"      <----- reference the new named 2-dimensional array as required 
  ]

This adjustment to the schema would aid in any file merge process an entity might have to do to when building each public file. It could also help group in_network rates in "logical ways" (i.e. geographical areas) for research within the file.

I realize this does not reduce the file size and that it actually will add a small increase in file size. However, the benefit it provides with concatenating multiple in_network arrays far outweighs the file size increase for my scenario.

I would love to hear other opinions.

[jonberkery-work]

@shaselton-usds
I am curious if this adjustment to the schema was being considered. I believe there is a benefit to this design.