Ask HN: JSON storage format questions (tree-structure)/value of ordered keys

Hey, as I'm developing a storage format for JSON for a versioned, temporal storage system I have a few questions. First, I wonder if you'd value having object keys ordered. For instance that would even allow navigation as with the XPath-axis in XML. I likely will represent object keys as nodes, whereas each node has a reference to the next object key (by a unique ID). This design also allows our storage system to simply store the results of fine grained modifications (copy-on-write at the node level) without having to store an ever growing object-node (in contrast to storing all IDs of its object keys or even the Strings itself directly in the object-node). Furthermore, I'd love to know if the number of children and descendants of a node would be of any value, at least storing it optionally (I for instance used it for novel interactive visualizations of XML tree-structures once (Sunburst view or treemaps)). Furthermore would it be of some value if you could easily move around an object, array... in a tree-structure representation of the JSON data? Kind regards Johannes