Clarification of Representation of Task Sequences

[dr-cgf-home]

C2SIM Problem Report / Change Request Submitter Name(s): Douglas Reece Contact email address: dreece@mak.com Submitter Organization(s): MAK Technologies Date of Submission: 21 March 2023 Type (Problem Report or Change Request): Problem Report Product: C2SIM core , SMX, LOX Description: Mark Pullen has requested clarification on how to represent a sequence of tasks in a C2SIM message. His desire is not to use the PlanPhase class for simple sequences. Note also Issue #40, which requests clarification or a change to represent tasks that start as soon as possible. Note also Issue #34, which discusses the use of task end Events as the starting point of other tasks.

[dr-cgf-home]

Original email from Mark Pullen:

Doug,

CWIX OPORD has cases where one task is to start at end of another.

I see two ways this might be expressed in C2SIM:

1. Second task has an ActionTemporalRelationship (where the UUID is that of first task):

   
   <ActionTemporalRelationship>
   <ActionTemporalAssociationCode>STREND</ActionTemporalAssociationCode>
   <TemporalAssociationWithAction>00000000-0001-0001-1000-001000000000</TemporalAssociationWithAction>
        </ActionTemporalRelationship>

2. Second task use Relative StartTime (where th UUID is that of first task):

   P00Y00M00DT00H00M00S 00000000-0001-0001-1000-001000000000 IntervalEndTime

Am I reading this right? Is one of them preferred?

Mark