ah, i think i get it now. you create a specific type of Menu Node that implements an interface to identify another menu by its name, then cycle back to the menu provider. i guess that makes sense, yes. for application provided menus, you would want to build an admin interface where the user can only chose from a list.

especially for multisite it could make sense to also reference a "common" menu fragement - the interface will work with that as the phpcr provider accepts a phpcr path as menu name - just don't have a node reference something in its own hierarchy or you get into an endless circle :-)