Prefix Template Parameters to Avoid Conflicts

[pawel-kow]

7.2.2.4. Parameters/properties

For the "Name/Value Pairs", using a prefix such as "t-" would safely namespace
these parameter names to allow future addition of properties without concerns
about clashing with deployed template parameters.

OK, this is a fair point about potential conflicts between template variables and current and future built-in parameters.

Do you suggest to prefix only in the application, so to "t-foo" would be actually interpreted as "foo" in the template, or to say that all template-defined variables must always start with "t-" prefix?

[awwright]

Can keys be the empty string? If they must have at least one character, which appears to be an implicit requirement, then I would suggest using something like "t.foo" since in URI Templates, a "." must be followed by at least one character.

[pawel-kow]

worth considering @awwright thx

[pawel-kow]

Drafted a different back-compatible approach in #196