Capability (C041):— representing_state_observed Date: 2007/06/22 12:22:11
Revision: 1.36
CoverContentsIntro.Overview Info. modelTemplatesCapabilities.Ref. dataIssues

Issue raised against: representing_state_observed

GENERAL issues

Open issue Issue: SB-2 by Sean Barker (03-06-05) minor_technical issue
Resolution: Accept. Status: open

In order to track task lifecycle, the task (as part of the support solution) needs to be associated to a state identifying its lifecycle stage. These states are asserted by an approval, rather than by observation, and this case needs to be covered by representing_state_observed.
Comment: (Rob Bodington 05-03-08)
This comments needs to take into account the changes to the Task model that were implemented in the IS version of Ap239. The comment should be reviewed once the task capability has been re written.

GENERAL issues

Closed issue Issue: RBN-1 by Rob Bodington (04-01-15) minor_technical issue
Resolution: Accept. Status: closed

The usage section is repeating a number of modules that are identified in the dependent capabilities. E.g. Date time. Also, bringing in entities that are part of the example.
Comment: (Rob Bodington 04-05-05)
Reference is made to the capabilities and the entities have been removed from the usage section.

Closed issue Issue: RBN-2 by Norwegian Pilot (04-05-05) minor_technical issue
Resolution: Accept. Status: closed

2 Information model overview. "Observed state" section. Writing error? Reference to Figure 1 below Рshould be above?
Comment: (Rob Bodington 04-05-05)
Agreed - fixed

Closed issue Issue: RBN-2 by Norwegian Pilot (04-05-05) minor_technical issue
Resolution: Accept. Status: closed

3 Characterization of Observed states The section describes some entities to be used in relation to an observed state. All of them belong to defined capabilities as C010, C007, C036 and C074/C016. Should they be referenced instead?
Comment: (Rob Bodington 04-05-05)
Agreed - added reference to the capabilities and changed instance diagrams to show which capabilities are being used.

Closed issue Issue: RBN-2 by Norwegian Pilot (04-05-05) minor_technical issue
Resolution: Accept. Status: closed

4 Characterization of Observed states References to other capabilities Figure 2. The related capabilities should be market out to clarify what is in scope of C041 and not. See Figure 1 below. Figure 3 and 4. Same comment as for Figure 2.
Comment: (Rob Bodington 04-05-05)
Agreed and corrected.

Closed issue Issue: RBN-2 by Norwegian Pilot (04-05-05) minor_technical issue
Resolution: Accept. Status: closed

5 Characterization of Observed states "Rules" for using different colours in Figure 2-6 The rules should be pointed out in the documentation. For example, Figure 4: Why are some external class entities black and some grey?
Comment: (Rob Bodington 04-05-05)
Agreed and corrected.

Closed issue Issue: RBN-2 by Norwegian Pilot (04-05-05) minor_technical issue
Resolution: Accept. Status: closed

7 State and activity Referring to C032? Does the entity "activity_actual" and "applied_activity_assignment" belong to C032? If so, should this capability be listed in "Dependent capabilities"?
Comment: (Rob Bodington 04-05-05)
No. They are in referencing_activities. Dependent capabilities updated.

Closed issue Issue: RBN-2 by Norwegian Pilot (04-05-05) minor_technical issue
Resolution: Accept. Status: closed

8 Dependent capabilities Illustrations of related capabilities Capability C037, C001, C010 and C016 are listed. Are all included in illustrations on Figure 2-6?
Comment: (Rob Bodington 04-05-05)
yes

Closed issue Issue: RBN-2 by Norwegian Pilot (04-05-05) minor_technical issue
Resolution: Accept. Status: closed

9 Capability EXPRESS information model Two models as basis for this capability? Both "state_observed" and "state_defined" are listed as part of C041. Why both? Isn't "state_defined" basis for C007, and C007 is only referenced by C041?
Comment: (Rob Bodington 04-05-05)
representing_state_type is specified as a related capability.

Closed issue Issue: RBN-2 by Norwegian Pilot (04-05-05) minor_technical issue
Resolution: Accept. Status: closed

10 Capability EXPRESS information model Which entities belong to this capability? Entities in module "state_observed" 7 out of 13 entities from this module are illustrated in Figure 2-6. Do the 6 remaining entities belong to this capability too? If so, is it up to the implementer to decide where and how to apply them? See Table 2 below. Entities in module "state_definition" Part of this capability or C007?
Comment: (Rob Bodington 04-05-05)
Decided to bring ALL the entities in from module "state_observed" and only "state_definition" from module "state_definition" Also removed all the entities that are not directly used by this capability. The rest will be brought in by the dependent and related capabilities

Closed issue Issue: RBN-2 by Norwegian Pilot (04-05-05) minor_technical issue
Resolution: Accept. Status: closed

11 Reference data No reference data?
Comment: (Rob Bodington 04-05-05)
Added.

Closed issue Issue: RBN-2 by Norwegian Pilot (04-05-05) minor_technical issue
Resolution: Accept. Status: closed

12 General comment Complete overview of C041. Would it add some value to the documentation if all information in Figure 2-6 was merged together into one Figure? Related capabilities should then only be referred to with number or name.
Comment: (Rob Bodington 04-05-05)
A style issue I guess. My opinion is that the diagrams make more sense separated.

Closed issue Issue: TJT-1 by Tim Turner (04-09-17) minor_technical issue
Resolution: Accept. Status: closed

This capability currently uses ENTITY State_assertion; name : STRING; description : OPTIONAL STRING; asserted_state : State; conformance_state : State_definition; END_ENTITY; Hence this entity depends upon State_definition. Either this should be added to the usage section (via the modules) or representing_state_type (which is where this entity is defined) should be listed as a dependant capability.
Comment: (Rob Bodington 04-09-29)
Made representing_state_type a dependent capability

Closed issue Issue: TJT-2 by Tim Turner (04-09-17) minor_technical issue
Resolution: Accept. Status: closed

This capability currently uses ENTITY State_assessment; name : STRING; description : OPTIONAL STRING; assessed_state : State; comparable_state : State_definition; END_ENTITY; Hence this entity depends upon State_definition. Either this should be added to the usage section (via the modules) or representing_state_type (which is where this entity is defined) should be listed as a dependant capability.
Comment: (Rob Bodington 04-09-29)
Made representing_state_type a dependent capability

Closed issue Issue: RBN-5 by Rob Bodington (05-01-13) minor_technical issue
Resolution: Accept. Status: closed

The classification of a state is about how the observation that something in the state was made. The definition of the state that something is observed to be in is made by the state_definition. The state_observed, refers to that state_definition. The definition of the state is then provided by a classification of the state_definition
Comment: (Rob Bodington 05-03-08)
This issues is still being discussed in the OASIS TC
Comment: (Rob Bodington 05-03-08)
Changed capability to say that the classification is of the state_definition, not the state_observed.

Closed issue Issue: RBN-6 by Rob Bodington (05-03-08) minor_technical issue
Resolution: Accept. Status: closed

Need to explain the use of applied_state_assignment.
Comment: (Rob Bodington 05-03-08)
Added section.

Closed issue Issue: NN-1 by Nigel Newling (05-11-17) minor_technical issue
Resolution: Accept. Status: closed

Update instantiation diagrams with template shorthand notations for assigning_reference data in particular.
Comment: (Rob Bodington 06-06-15)
Most diagrams have been edited - however, some still have comments. Adding templates would make the diagram too complex to be comprehensible.

Closed issue Issue: RBN-7 by Rob Bodington (05-11-23) minor_technical issue
Resolution: Accept. Status: closed

Two templates should be added to the capability: TEMPLATE: assigning_asserted_state TEMPLATE: assigning_assessed_state
Comment: (Rob Bodington 06-05-17)
Added

Closed issue Issue: RBN-8 by Rob Bodington (06-06-14) minor_technical issue
Resolution: Accept. Status: closed

The section "State and activity" does not really add any value - recommend that it is deleted.
Comment: (Rob Bodington 06-06-14)
deleted

Closed issue Issue: EML-1 by ed McNeil (06-06-23) minor_technical issue
Resolution: Accept. Status: closed

Template Assigning_assessed_state Reference parameter state_def is used in the instantiation path but not declared in the Reference Parameters section.
Comment: (Rob Bodington 06-06-23)
Corrected

Closed issue Issue: RBN-9 by Rob Bodington (06-07-03) minor_technical issue
Resolution: Accept. Status: closed

Template: assigning_asserted_state and assigning_assessed_state The input parameter state_class_name specifies that a State_identification_code (urn:plcs:rdl:std:State_identification_code) should be used. A State_definition is being classified, not an identification_assignment, therefore the use of a State_identification_code is inappropriate. The class should be a sub class of State_definition.
Comment: (Rob Bodington 06-07-03)
Changed to subclases of State_definition