Every SAIL/Repository defines it own vocabulary in Java. This should be
extended to also include an RDF file describing the user editable
predicates in the vocabulary, this would include rdfs:label,
rdfs:comment, and rdfs:range. Only the predicates that the user would
edit should be included. The workbench/server should defined its own
vocabulary for controlling how fields should be shown, such as the width
of the field or a list of possible values.

The repository template is the default repository config. The
console/workbench will scan the template for known predicates that are
defined by the SAIL/Repository vocabularies (included in the class-path)
and use the information in the vocabulary to prompt the user to change
the default values.

This works for any template format. It allows benchmark tools to create
configs directly from the templates. It is extensible for rich UI, like
the workbench, and is straight forward enough for the console. It
reduces the role of the template and allows localization to be done by
the SAIL/Repository maintainers in a reusable manor, and can be extended
by any one with access to the class-path.