MTConnect Devices - Amendment 1: Conditions

This amendment removes the use of branches to differentiate individual Condition activation and relies on the ConditionType Event mechanism to
manage the Condition states.
The solution separates out the MTConnditionType representing metadata and the MTConditionEventType that represents the information reported when a Warning or Fault occurs.
Each unique condition invocation, usually distinguished by the nativeCode will become a new MTConditionEventType with a unique ConditionId given as the NodeId of the Event and a composed unique ConditionName composed from the unique attributes of the Condition in the stream document.