338   Type of TrgOp in DATA is wrong

Created: 08 Jul 2006

Status: In Force (green)

Part: Part 7-2 (2003)

Links:

Page: 043, table 16

Clause: 10.2

Paragraph: 10.2.1, 10.2.2.4.3

Category: Issue for edition 2 of this part

Issue

Table 16 shows a DataAttribute sub-attribute TrgOp [1..n] of type TriggerConditions defined in table 10. This is wrong because TrgOp is according to table 19 in 10.2.2.4.3 of type XY enumeration with the three values dchg, qchg, dupd, wheras type TriggerConditions has attributes of type boolean.

This means TrgOp [1..n] is NOT of type TriggerConditions but is only associated to the attributes of TriggerConditions for reports and logs. E.g. this means, if the TriggerConditions attribute data-change = true reports and logs with DataAttributes with sub-attribute TrgOp = dchg are enabled.

From this follows that the text in 14.2.2.11. is confusing and partly wrong.

The same word "TrgOp" for both TrgOp in DATA and TrgOp in BRCB/UBCB is confusing because the meaning is related but not the same! TrgOpts (plural) for the configuration of BRCB/UBCB does not help much with different semantics.

Proposal

Please change:
1. Type TriggerConditions in table 16 to a new XY enumeration type (table 19?).

2. Replace in 10.2.2.4.3 the first sentence "The attribute TrgOp of type TriggerConditions (see table 10) ..." by "The attribute TrgOp of type TriggerOptions (see table 19) ..."

3. Replace the last sentence "The service associated with TriggerConditions ..." by "The service associated with TriggerOptions and there corresponding TriggerConditions ...".

4. In 14.2.2.11 the first sentence should be "The attribute TrgOp of type TriggerConditions (see table 10) shall .. ". The second sentence "The following values are defined" should read "The following attributes are defined:".

5. Change attribute name TrgOp (or TrgOps) in BRCB/UBCB to TrgCon, meaning trigger conditions in line with its type TriggerConditions.

Discussion Created Status
Status set to green. 17 Mar 07 In Force (green)
ballot date added
14 Feb 07 Ballot Period
To start with the text in 14.2.2.11: The attribute has been changed to TrgOps (plural).

Table 10 serves two pusposes: (1) the types (booleans) (2) the TrgOp in the third column. The first, third and fourth columns is used in table 16.

Revised text in 10.2.24.3
"The attribute TrgOp of type TriggerConditions (see Table 10; only the first, third and fourth columns are relevant) shall define the trigger conditions"

"The services associated with the TrgOp shall be as specified in Table 19."

Changed the table name from "Trigger option" to "TrgOp"

Changed the multiplicity of TrgOp [0..n] to [0..1] because only one trigger option per data attribute is allowed.
14 Feb 07 Ballot Period

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1