Production Status Issues for the Buffered Data Delivery Procedure

1. Production Status Issues for the Buffered Data Delivery Procedure 15-19 April 2013 Bordeaux, France John Pietras Global Science and Technology, Inc, Greenbelt, MD, USA

2. Issues • ‘production status change’ Incoming Event in complete mode • Incoming Events/notifications defined by derived procedures • Role of Recording Buffer status in determination of Production Status • Declaration of capability of derived procedures to define their own procedure specific events

3. ‘production status change’ Incoming Event in Complete Mode (1 of 2) • Row 9 describes behavior of the production process when ‘production status change’ occurs while the procedure is in complete mode. This is inappropriate for the state table for the BDD procedure • The event that addresses the handling of a Service Production Event Notification by the BDD procedure is row 4, ‘data read form recording buffer’.

4. ‘production status change’ Incoming Event in Complete Mode (2 of 2) • MG and JP agree that row 9 does not affect the state of the BDD procedure itself. Options: • Delete row 9, or • Keep row 9, put in “[ignore]” for states 1 and 2, and add a note explaining why this doesn’t affect the state of the BDD. • In any case, ‘production status change’ is not constrained enough in row 8. It should be changed to something like “‘production status change’ while in real-time mode” • If row 9 is kept, it should be changed to something like “‘production status change’ while in complete mode”

5. Incoming Events/notifications Defined by Derived Procedures • Rows 8 & 9 include “derived procedure events” • MG and JP agree that the proper way to handle events that are specific to derived procedures is for each such procedure to have its own new row in the state table. • The derived event parts of the incoming events should be deleted

6. Role of Recording Buffer Status in Determination of Production Status • The Recording Buffer is formally defined to be a part of production processing. What happens if the Recording Buffer becomes disabled while the complete-mode user is transferring data? • The only notification that appears to be available is a change in production status, but in complete mode that notification gets put into the Recording Buffer • Is the user told anything “now”? • Should the behavior be defined for the core BDD procedure, or should it be deferred to derived services/procedures? • If the behavior is defined for the core BDD, how might it be realized? • As an additional use of the ‘end of data’ notification? • As a new notification type? • Other?

7. Declaration of Capability of Derived Procedures to Define their Own Procedure-Specific Events • 4.5.3.2.6 begins “The Service using this procedure or a derived procedure may define its own procedure specific events.” • Does this sentence just repeats the general concept of derivation (and therefore should be removed), or does it identifies a particular kind of derivation that is not obvious from the general statement of derivation?