If true, URI-encoding should be applied to the property value before substitution in the template. This is not as fine-grain as per-variable-per-template control of encoding but it avoids creating a cvt. this could become an enumeration rather than a boolean later if other encoding styles must be specified. client code should default to no encoding if this property is missing.