Hi Chris,
I would suggest that extending the current module repository system would be a more natural approach, and would bring in some concepts that have parallels in other database applications.
It may turn out to be natural, if someone manages to specify and formalize a solution that fits to the architecture of BaseX. It could be long way, as I’m still struggling to understand what first steps might be required to achieve what you are looking for. Is your idea of an enhancement of the BaseX repository concept similar to what Luke proposed (i.e., having a REST call locate query scripts that belong to a specific database), or it is something on top, or bottom, of that? Would you propose to introduce new options that change the default behavior of BaseX; would you overwrite existing functionality or add new features on top of the existing functionality? What exactly would be the feature request you would ask for?
It’s a challenge to equate BaseX with relational database systems, or concepts residing in that systems. With BaseX, you can address an arbitrary number of databases, local documents, remote sources in any other format, etc., in a single query. You can write full web applications with XQuery, which is something you wouldn’t usually dare with SQL and its extensions. Maybe it helps if you regard BaseX and XQuery as a framework that allows you to *also* retrieve databases.
Cheers, Christian