Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Imports (or extension mechanism) in config XMLs #243

Open
marco-brandizi opened this issue Mar 2, 2017 · 0 comments
Open

Imports (or extension mechanism) in config XMLs #243

marco-brandizi opened this issue Mar 2, 2017 · 0 comments

Comments

@marco-brandizi
Copy link

I'm using a number of XML that have slightly different SPARQL queries, each working on different data sets, each returning the same projection of fields. This means the Duke XMLs have a lot in common, for what concerns general parameter and schema properties. It would be really useful to have some <import> element in the XML. At the moment, I'm using an XML template having a placeholder like ${dukeCommon}, which I instantiate from the invoker, but what I'm suggesting would be more practical.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant