[Css-csts] RE: Procedure identification (new idea)

[Ray, Timothy J. (GSFC-5830)]

Dear Working Group members,

If this idea meets a lot of resistance I'll back off, but I can't resist speaking up...

Here is an approach for identifying procedures that, in my opinion, is more straightforward than our current specification or my email from earlier today:

First, we must identify the type of the procedure (e.g. BufferedDataDelivery).

Second, since there may we multiple instances of the same procedure-type, we must identify the instance of this procedure-type (e.g. first instance of BufferedDataDelivery or second instance of BufferedDataDelivery, etc).

Third, assuming that it is necessary to mark the Prime Procedure, then include a boolean flag: "IsThisThePrimeProcedure?".

Note: In the current specification, there is redundant information - we've agreed that an instance of 0 will always indicate a Prime Procedure, so there is no need to have a CHOICE in procedureInstanceNumber.

Best regards,
Tim



From: css-csts-bounces at mailman.ccsds.org [mailto:css-csts-bounces at mailman.ccsds.org] On Behalf Of Ray, Timothy J. (GSFC-5830)
Sent: Tuesday, August 18, 2009 10:26 AM
To: css-csts at mailman.ccsds.org
Subject: [Css-csts] Procedure identification (new idea)

Dear WG members,

I find our current method of identifying procedures to be more complex than necessary (for example, the second instance of the Primary procedure is instance #1, while the second instance of Secondary procedures is instance #2).  May I suggest this new mechanism?

3.3.2.5.3  Prime/Secondary
This field shall be set to 'prime' if the procedure-type is the prime procedure for the service that is currently being run; otherwise, it shall be set to 'secondary'.

3.3.2.5.4  Procedure Instance Id
This field shall indicate the particular instance of the procedure-type; for the first instance of each procedure type this field shall be set to 1, for the second instance of each procedure type this field shall be set to 2, etc.

Best regards,
Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20090818/d9f2295c/attachment.htm