VDM Abstraction Level

From @Yosuke Nakayama via slack

At which abstraction level is VDM (or VSS) primarily intended to define signals?

When I’m learning VSS, I feel that some nodes is defined from the perspective of end user(driver).
But on the other hand, some other nodes is define from the perspective of tier-1 or more low-layer software engineer.
For example, Vehicle.Cabin.Door has IsOpen and Position leaf nodes(=property).

* IsOpen is very useful and easy to understand, and highly abstracted information.(=the perspective of end user(driver))
* Position is very strict, less abstract information. (=the perspective of tier-1 or more low-layer software engineer)

These leaf nodes express essentially same HW status, from different perspective, abstraction level.
Therefore, VDM(VSS) server must sync these two nodes.

In this way, when the same state is represented on multiple nodes, it becomes necessary to consider complex cases such as data synchronization and atomic write control.
I asked the question to confirm whether this kind of defining nodes at multiple levels of abstraction and from different starting points is intended.