Feature Request: Simpler Config files

[GoogleCodeExporter]

I would love to be able to declare internal static strings in my configs and 
reuse them in the config file (almost anywhere!)

ie have a static variable for the url path
api:uriTemplate  "/%REPONAME%/resource?uri={URI}" 

we have been reusing large portions of the config files, and having 
string/variable storage for the bits that need changing would be awesome

Original issue reported on code.google.com by terry.ra...@gmail.com on 10 Feb 2012 at 11:22

[GoogleCodeExporter]

I see the use-case. I'd suggest that a tool to specialise templated 
configurations would be a reasonable way to start -- no need to immediately put 
something like
this into Elda. It's pretty easy using Jena to write a utility that reads a 
config
file, changes strings by filling in templates, and writing the file out again. 
Or
as a brute-force solution an editor script would work. (Being careful to 
incorporate them into the project workflow, of course.)

Original comment by ehog.he...@googlemail.com on 24 Feb 2012 at 1:54

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Absent further use-cases, we won't pursue this issue, assuming it can be 
handled outside Elda by specialised substituters or scripts.

Original comment by ehog.he...@googlemail.com on 28 May 2012 at 2:14

• Changed state: WontFix