Just ran into this myself, actually. I wanted to create a resourceType that standardized a specific set of resources that are repeated at several levels of resource hierarchy. Sort of like the following (i've omitted everything but the resource paths for clarity):
It's going to be an incredible pain to have to redeclare every one of those resources without the benefit of being able to use a template of some kind. Maybe traits is the answer? but I don't think those support templating like <>, or do they?
If none of the above are going to work, where do I +1 nested resource types (or child resources in a resource type)?