David especially addressed a number of points such as:
- COBIA: HTRI has expectations in particular with respect to their two new pieces of software. Since COBIA is not ready to be rolled out, seems that keeping to the current CAPE-OPEN approach will do.
- Threading: HTRI software is not relying, at the calculation level, on several threads. In that respect HTRI seems to follow a common pattern.
- Persistence scheme proposed for COBIA: the proposal made by CO-LaN M&T SIG seems reasonable to HTRI.
- Flowsheet Monitoring: at first HTRI was not interested by being able to retrieve and analyze information supplied by a set of heat exchangers could be advantageous. It is not a need which is expressed just the fact that Flowsheet Monitoring could come handy.
- Reactions: there will be no contribution from HTRI on the development of that interface specification since no use within HTRI software.
- Deprecating 1.0: no problem if the deprecation follows the meaning given in dictionaries. Thermo 1.0 would stay in HTRI software.
- Requests on new version of Thermo (Thermo 1.2 for example): HTRI is in favor of a solution to get access to an array of calculation points in one call.
- Regarding Unit Operations icons that would be nice since nowadays all Unit Operations are looking the same in a Flowsheet.
- Type Libraries/PIA installers: no usage ever made of them. Probably should be using them.
- COLTT: lots of use for troubleshooting. COLTT 64 bits is not required at this point. There is some move towards 64 bits at HTRI but no push so no need for COLTT 64 bits.
- Self certification: great idea. HTRI has taken many steps to ensure its software is CAPE-OPEN compliant but some aspects of CAPE-OPEN being optional, it opens the door to some interpretatiojn which is going in the way of interoperability.