assuming default of cartesian vectorComponents is too risky #253
Description
A parameter that has vector components does not need to indicate that these are x,y,z components, but this makes it easy for data providers to make a mistake and accidentally advertise data as cartesian when it is otherwise.
It is not too difficult to add
"vectorComponents": [ "x", "y", "z"]
and it adds a lot of clarity.
I think we had it be the default so people could specify vectors quickly by just adding a coordinateSystemName, which implies that the parameter is a vector and comes with the default cartesian x,y,z assumption.
But now we are thinking it's too easy to accidentally leave that off, and if we require the components to be specified, then the data provider has to think about it and is more likely to put the right kinds of components, cartesian or otherwise.