Each field must have a unique name. It is this name that becomes the attribute's name when you access an element's attributes via the API.
For simplicity sake, we recommend you adopt a standard method for naming attributes. For example, we use lower case names and underscores to separate words. Perhaps you prefer camel case. Do whatever you wish, but be consistent—it'll be easier to work with the API that way!
There are some reserved words in our app. We won't worry about all of them, but we definitely don't want to clash with other attributes. This means you should avoid the following names:
There are a handful of others that will cause problems, but these are the most common.