Naming guidelines

It’s a good practice to establish a naming convention for Mix.nlu elements in your Mix projects. This will help you avoid names that might conflict with keywords commonly found in programming languages. Inadvertent use of such keywords could generate errors at runtime in your client applications.

Reserved keywords

Don’t use JavaScript reserved words  and Java keywords  .

The words in this list are also reserved, within the Mix platform—don’t use them in your Mix projects:

• _
• appsessionID
• AUTO_INTENT_… (that is, anything prefixed with AUTO_INTENT_ cannot be used as an entity or intent name)
• ConfigurationModel
• id
• inputmodes
• library
• odm
• SLOTS
• version

Intent names

Intent names are limited to 500 characters, must not start with a number or hyphen (-), or nuance_, and cannot include spaces. Use underscores (_) or hyphens (-) as separators if desired. The name must be unique across all intents, entities, and Dialog variables in your project.

Naming restrictions apply when giving an initial name and when renaming.

You cannot rename the NO_INTENT predefined intent.

Entity names

Entity names must not start with a number or hyphen (-), or nuance_, and cannot include spaces. Use underscores (_) or hyphens (-) as separators if desired. The name must be unique across all intents, entities, and Dialog variables in your project.

Naming restrictions apply when giving an initial name and when renaming.

You cannot rename rule-based entities.