This switches to the RFC6570 syntax for URI templates, as suggested in #39 by @Robsteranium.
This has the benefit of not forcing URL encoding of the identifiers when inserting them in the template, and allowing for a much wider range of use cases. This is a significant change since the syntax used so far ({{id}} in most places, ${id} for the flyout template) are not compatible with RFC6570. However I think it is really important to support the use case of services using a full URI as identifier (since that is already happening in the wild), or parts of URI which should be inserted without escaping.
Closes #39.
This switches to the RFC6570 syntax for URI templates, as suggested in #39 by @Robsteranium. This has the benefit of not forcing URL encoding of the identifiers when inserting them in the template, and allowing for a much wider range of use cases. This is a significant change since the syntax used so far (
{{id}}
in most places,${id}
for the flyout template) are not compatible with RFC6570. However I think it is really important to support the use case of services using a full URI as identifier (since that is already happening in the wild), or parts of URI which should be inserted without escaping.