It acts exactly like a normal SC.Binding so you can pass a string or you can pass an SC.Binding protocol like:

 namePath: SC.Binding.from('myApp.myRecordController.name').oneWay()

But you should probably do this at the internal to the view to for better control.

You’re right there is no magic here…it is just a naming convention. The convention is more for readability and to make sure you DON’T pass bindings around with the ‘-Binding’ convention which is a performance hit. ‘-Binding’ convention should ONLY be used when you are actually setting a binding up not to pass the string.

The composite view is a the more important construct. This is very helpful when you have to make views that have popups or other special characteristics

All you’re doing is making the (name) coupling between views weaker (by passing it to the parent which is in turn responsible for creating its child views). The -Paths are only strings, so the bindings will be set up for each child view anyway, right? Or am I missing something here?