Usermodel which looks like:
ReactivePropertyhere which is specifically an rx related class, so if you dont know about that it is well worth reading up on in the Reactive Extensions chapter.
NameUIso when someone changes the value in there (be it in code or from UI) it will update the VM, and we have also got an action where we let the VM randomize the name, which would then filter down to the view.
MonoBehaviourwhich acts as the binding layer for the Scene objects and the view model.
PlayerViewModelwhich has a view for displaying the players avatar in the game as well as a view for displaying the players stats/score on a UI.
IViewinterface we made up, however it is important to look at the binding mechanisms which will often vary per framework.
someTextPropertyInViewModel, it just varys how they do it based upon the platform/framework you are using.
Vector3 Positionto the characters position you should be able to, as you want these reactions to drive anything in the view regardless of if its a UI element or not.