Uploaded image for project: 'OASIS Open Building Information Exchange (oBIX) TC'
  1. OASIS Open Building Information Exchange (oBIX) TC
  2. OBIX-71

Table 4-2 - Unacked Alarm Confusion

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: OBIX 1.1 WD20
    • Fix Version/s: OBIX 1.1 WD28
    • Component/s: OBIX 1.1 Specification
    • Labels:
      None
    • Environment:

      Chris Bogen

    • Proposal:
      Hide

      Repharse the definitions for unackedAlarm and unacked. Order the definitions in Table 4-2 so that alarm appears first, then unacked, then unackedAlarm.

      Show
      Repharse the definitions for unackedAlarm and unacked. Order the definitions in Table 4-2 so that alarm appears first, then unacked, then unackedAlarm.

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              chris.bogen Chris Bogen (Inactive)
              Reporter:
              chris.bogen Chris Bogen (Inactive)
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: