352   Use of values is not defined

Created: 26 Jul 2006

Status: Not Applicable

Part: Part 7-2 (2003)

Links:

Page: 145

Clause: 17.

Paragraph: 17.5.2.2

Category: Issue for edition 2 of this part

Issue

17.5.2.2 says ".. Value shall include values for all implemented DATA Attributes of a controllable common DATA class that are accessed by various control services".

It is not clear what is meant with "all" or are e.g. in POS only the DataAttributes ctlVal, operTm, origin, ctlNum with FC = CO meant:

1. ALL DataAttribute values? Why all?
2. Only DataAtributes with FC = CO?
2. All or ALL with FC = CO for ALL CONTROL services?
3. Only selected DataAttributes specific to a service?

The purpose of "Value" in request and response of SelectWithValue is not defined. In general, which DataAttributes are needed for which purpose?

Is in 17.5.3 "Value" (DataAttribute types, not values) in response identical with Value in request?

The definition should be independent of the mapping in 8-x!

Proposal

Please add a table about the used DataAttributes specific to the services in request and response and describe its purpose where needed (e.g. Value DataAttributes for SelectWithValue).

Discussion Created Status
The TISSUE resolution is already part of TISSUE # 173 - Ctl Model harmonization.
The control parameters replace the control attribute.
7-3 deals with the control parameters.
18 Apr 07 Not Applicable
In principle accepted. However, as the 'meaning' of some attributes also depends on the CDC, this detailled meaning of attributes will be explained in 7-3. This is already under way due to some other tissues. 08 Aug 06 Discussion (red)

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1