1370   Mod/Beh definition of value=2 "on-blocked" is contradictory to part 6

Created: 15 Apr 2015

Status: Not Applicable

Part: Part 7-4 (2010; Edition 2)

Links: #1331 Mod, Beh and Health with q=TEST, client can't receive their states , #686 New annex H - enums types in XML


Clause: 6 (Beh) and Annex A


Category: Issue for edition 2 of this part


In part 6 the BehKind is defined as:
<EnumType id="BehKind">
<EnumVal ord="1 ">on</EnumVal>
<EnumVal ord="2">blocked</EnumVal>
<EnumVal ord="3">test</EnumVal>
<EnumVal ord="4">test/blocked</EnumVal>
<EnumVal ord="5">off</EnumVal>

But in part 7-4 the value 2 is defined as "on-blocked" which is contradictory to part 6 and also Edition 1.


As proposed in TISSUE #686 in an internal comment also in Edition 2 the value=2 should be "blocked" to be interoperable to Edition 1. Define/name also in 7-4 value=2 as "blocked".

Discussion Created Status
Already considered in other tissues (e.g.#686) and will corrected in amd 2.1. Because tissue #686 is of category "interop", the value=2 "blocked" must be used in ed.2 implementations. 15 Apr 15 Not Applicable


Privacy | Contact | Disclaimer

Tissue DB v.