The Thermo SIG met from 10:40 am till 12:30 pm (Central European Time).


Review the Custom Data interface in light of the modifications imposed by the new design of the Chemical Reactions interface specification.


Sergej BLAGOV (BASF), Jasper van BATEN (AmsterCHEM), Mark STIJNMAN (Shell Global Solutions), Michel PONS (CO-LaN)


Custom Data was so far designed as a piece of data (CapeVariant) stored on the Material Object by a PMC having used for such data in order to keep aside information expensive to re-obtain. Now we defined Custom Data as a Custom Data object which is a secondary CAPE-OPEN object belonging to a PMC. As such it will carry an ICapeIdentification interface, mostly to simplify the analysis of any logging made of the communication between that object and both the PME and the PMC.

Was discussed at some length the copying of a Material Object and how it impacts Custom Data. The merits of various solutions regarding custom data attached to the source Material Object being copied were explored. The solution outlined is to design an interface ICapeThermoCustomDataCopy on any Custom Data Object in order to let know to the PME that the Custom Data Object can be copied together with the Material Object.

It seems necessary to retain from the previous design the key created by the PME at the PMC request and uniquely attached to a Custom Data object. Using the name property carried by ICapeIdentification would be unreliable and would be using ICapeIdentification beyond its purpose.

Next conference call is scheduled for December 19, 2017.