Below EntryData [1..n] under the headline ReasonCode - reason for inclusion: The second sentence reads "The value for the reason for inclusion shall be set according to the TrgOp that caused the creation of the report" with the values "data-change, ...".
This is O.K., but in table 24 ReasonCode is of type TriggerConditions with boolean attribute values false or true (see table 10).
Proposal
Change type TriggerConditions of ReasonCode in table 24 to a new type XY enumeration (data-change, ...). This is just an extension of the TrgOp type in DataAttribute with renaming (data-change instead of dchg, ..) and two additional values integrity and general-interrogation.
Why not keep in this new type XY enumeration the TrgOp values in DataAttribute (dchg instead of data-change, ..)? So an distinction can be made between TriggerOptions of TrgOp in DataAtribute and TriggerConditions of BRCB.
This is true also for URCB, LOG.
Discussion
Created
Status
Final proposal accepted.
Changed status to green.
13 Apr 07
In Force (green)
See Tissue 453 for revised model.
acppeted; ReasonForInclusion definition changed to PACKEDLIST.
"The values conveyed by ReasonForInclusion shall be a PACKEDLIST as defined as follows...."
Table revised
14 Dec 06
Ballot Period
Agree in priciple. Propose the text found in Tissue 339.doc to define TriggerConditions. Added pointer to the definition in the URCB and LOG sections.