Name | Examples | Name Constraints | Recommended Naming Convention |
---|---|---|---|
thing | |||
thing property | temperature, lastTemperature, latestVoltageChangeDate |
The page Constraint - thing property name does not exist. |
Name provides information about content of property: <subject> |
thing method | getTemperature, getNumberOfProcessors |
The page Constraint - thing method name does not exist. |
Name of method consists of action and subject, like <action><Subject> |
thing event | temperatureChanged, motionDetected |
The page Constraint - thing event name does not exist. |
Name looks like <value><Action (VERB+ed, irreg. VERB)> |
thing trigger | sendAlertOnTemperatureChanged, alarmOnMotionDetected, onTemperatureChanged |
The page Constraint - thing trigger name does not exist. |
Name looks like <action><On><Event>, or <on><Event> in case of single trigger for the same event |
thing schedule | changeTemperature, changeTemperatureHourly, computeValue, computeValueDaily |
The page Constraint - thing schedule name does not exist. |
Name looks like <action><Optional Details><Optional Timing Details> |
thing connection | mqtt, tcp, tcpPort80 |
The page Constraint - thing connection name does not exist. |
Name looks like <protocol><Optional Specs> |
template | |||
template version | |||
product | |||
product serial number | 12ABC, 12-34-56, 1234ab |
|
|
structure data type | HddInformation, TemperatureStatistics, Location |
|
|
structure data type attribute | longitude, numberOfProcessors |
The page Constraint - structure data type attribute name does not exist. |
Name provides information about attribute subject: <subject> |
data type package | com.mypackage.util, org.m2m.device, com.gadgetkeeper.service |
|
it's advised for companies to use their reversed Internet domain name to begin their package names - for example, com.example.mypackage for a package named mypackage created by a programmer at example.com. |