Update closed resource fields if null?
As we have been discussing and tightening up the properties in EconomicResource that can and can't be updated directly, it occurred to me that for some of these (currentLocation, inScopeOf, probably others), it seems like we could allow direct update if they are currently null, without harmful effect.
What do you all think? More work and complexity for the backend apps and for UI apps too. But maybe saves some user annoyance and confusion. Or maybe not, don't know.
Or, is it not a good time to consider this, and we let it sit for this round of development?