REST URLs vs device names
Posted: Thu May 23, 2013 2:23 amHi all,
How are people dealing with mapping human-readable device/action names to URL-appropriate names so that REST URLs are valid?
Jack's Bedroom Light => jacks-bedroom-light
- Is there a way to add additional methods in the webserver that are just pointers to valid methods? If so, I could create my own variations on jacks-bedroom-light.
- Is there a separate field that can be used to specify url-safe text instead of using the device name?
- Any way to make the device ID work?
When integrating with Siri, iMessage, other voice controlled things, there really isn't a chance to go through and fix capitalization, spacing and other issues. Having additional URLs would be one workaround. Or I could run text through some logic to guess at the right device/action name.
Open to all suggestions...
How are people dealing with mapping human-readable device/action names to URL-appropriate names so that REST URLs are valid?
Jack's Bedroom Light => jacks-bedroom-light
- Is there a way to add additional methods in the webserver that are just pointers to valid methods? If so, I could create my own variations on jacks-bedroom-light.
- Is there a separate field that can be used to specify url-safe text instead of using the device name?
- Any way to make the device ID work?
When integrating with Siri, iMessage, other voice controlled things, there really isn't a chance to go through and fix capitalization, spacing and other issues. Having additional URLs would be one workaround. Or I could run text through some logic to guess at the right device/action name.
Open to all suggestions...