output simulation duration information to the CIM

[rupert]

The CIM currently has a couple of places where it can put the simulation duration information. This is being sorted out by Allyn (duration is going to become calendar). However, the CIM curnently only has a start and end date. It does not have a duration. Allyn is looking at how to fix this. Once this has been sorted out I need to output simulation information to the CIM.

[allyn]

As of r1987 added Duration class and used it in SimulationRun? and SimulationComposite?. A Duration is based on xs:duration and can be used instead of endPoint to specify the simulation length. It can be used as either an "absolute" or "relative" length (specified as an attribute of duration)

[rupert]

Hi Allyn, a couple of things

1: the questionnaire duration (quite rightly) provides units ('Years' or 'Days' are the options). Could you also add this to the simulation/Duration type?

2: Isn't a duration, with the type set to absolute, logically the same as an endPoint, or is there a meaning of relative and absolute that I am missing?

Cheers

[allyn]

Rupert,

1. The APPCIM duration is of type xs:duration, which allows you to specify the units in the string [look about 2/3 down the page here:  http://www.w3schools.com/Schema/schema_dtypes_date.asp]. Is this overkill?

2. An absolute duration is the same as an endPoint. I noticed that too. I had written down the following cryptic note from our discussion yesterday:

<snip> add a "duration" to simulationRun which includes length & units; look into treating this as an offset rather than an absolute length (or choose between duration and absolute "types") </snip>

Can you verify what you meant here?

[rupert]

Hi Allyn,

I should have checked the type! I like the use of the duration type. It is exactly what should be there in my opinion. I will create the appropriate string.

As for an explanation of our discussion, it was me wondering whether, rather than having two optional elements (an endPoint and a duration), we could have a single element with the attribute absolute or relative. However, this would require the type of this element to support both an absolute time and a duration which is not nice. I am happy with the current solution which means we can drop the type attribute (as the duration will always be relative). If you are happy to do this I'll close this ticket as I've implemented the mapping in the v1.0_devel branch as of revision 2015

[allyn]

The complexType Duration with the "type" attribute has been eliminated in favour of just using xs:duration directly as of r2016. I had to add that mapping to the concim2appcim.xsl file. This ticket can now be closed.