When working with parameters in ISML, which format should the variable names NOT be passed as?

In the context of ISML (Interchangeable Server-side Markup Language) used within Salesforce Commerce Cloud (SFCC), parameters are typically passed in a manner that facilitates their recognition and proper processing within the template. When variable names are passed as strings, they may not be recognized or interpreted correctly as dynamic variables. Instead, ISML expects variable names to be presented in formats that maintain their identity as dynamic content, ensuring that they can be processed and rendered properly within the template.

Passing variables as direct variable names allows ISML to evaluate and inject the values correctly during rendering. Similarly, using attributes within HTML tags or encapsulating variables in JSON objects maintains the intended dynamic interaction with the data. These methods ensure that the parameters are treated as dynamic entities rather than static strings, which could lead to rendering issues.

In summary, the ideal approach is to use direct variable names, JSON objects for structured data, or attributes within tags to ensure that the parameters are accurately processed in ISML, making passing them as strings the unsuitable format that the question seeks to highlight.