[OASIS Issue Tracker] Created: (OBIX-71) Table 4-2 - Unacked Alarm Confusion

Table 4-2 - Unacked Alarm Confusion
-----------------------------------

                 Key: OBIX-71
                 URL: http://tools.oasis-open.org/issues/browse/OBIX-71
             Project: OASIS Open Building Information Exchange (oBIX) TC
          Issue Type: Improvement
          Components: OBIX 1.1 Specification
    Affects Versions: OBIX 1.1 WD20
            Reporter: Chris Bogen
            Priority: Minor


The definition for unackedAlarm and unacked is confusing - "The difference between unackedAlarm and unacked is that the Object has returned to a normal state."  The definition for "unacked" says - The unacked state is used to indicate a past alarm condition which remains unacknowledged.  This seems like a circular definition if unackedAlarm is instructing us to consider the concept of unacked independent of alarm.  Also, unackedAlarm references "unacked" and "alarm," neither of which have been defined yet.

Also, it would be preferred to use positive terminology such as "ackedAlarm" since negated logical terms can lead to confusion.  However, it is understood that changing that terminology is not feasible at this point in time.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira