Hello,
we are working with the Alarm API specification and have 3 questions about some attributes:
1) Attribute id
The attribute
id is commonly a string definition (in any TmForum specifications I have seen yet). Only here in the alarm resource model, the id has been defined as an integer. Any reference id (for related resources) are again defined as string. So, this is not consistent in our view and we are also having trouble to reduce the id to integer values only.
Is this a defect or supposed to be?
2) Attribute state
For
state attributes we are normally expecting an enumeration field to support a life-cycle model. We cannot find a clear/strikt enumeration of allowed values in the PDF v4.0.1. user guide specification in contrast to other attributes like AlarmTye. On the other side the swagger definition v4.0.0 does show an enumeration list. So we will go with the swagger specification here, we like to see more clear description of possible values for any attribute with enum list in swagger.
3) Attribute plannedOutageIndicator
We cannot find any details about how to use the
plannedOutageIndicator attribute. An indicator sounds more like a boolean switch, but the definition again does allow arbitrary strings. So, is it foreseen that the model user defines its custom logic for this indicator?
Best Regards, Detlef
------------------------------
Detlef Kleinfelder
IBM Corporation
------------------------------