When creating the data definition for a new list type, if there was a data type of 'list' that could then be configured to show the contents of another list it would enable list nesting and one could assemble a quite complex application using nothing more than lists, templates, workflow and forms.

James,
Along this idea, it would also be nice to be able to build a new datalist based on an existing one. Many of our datalist forms ask for the same 'header' questions, name, address, location, etc. It would be nice to have a base list that could be inserted within the new list and any changes reflected in the base list would be reflected in the new list (could have an option to 'Enable Update' if the user did want changes or deselected if only using as a starting point.

@James I agree. That's definitely something that will be added sooner or later. Of course, contributions are welcome

@Randy, that's also a good idea. One similar option that has been added for 6.2 (you can check it in the milestone) is the ability to have inheritance of definitions.