I would like feedback from additional RR SIG members on this. Suppressing the TypeInfo stuff seems to make sense based on the discussion so far but since TypeInfo was there at the start, it is better to check if we have missed something along the way.

I finally got around thinking about the TypeInfo issue. My preference is for keeping the interface and extend it to other specialized units, as Michel mentions above. I'd propose the folllowing, but since it modifies what we released, but never used, in 1.0 maybe some names need to be changed:

[
uuid(CapeUnitType_IID),
version(1.0)
]

typedef enum eCapeUnitType {
CAPE_CONVENTIONALOP = 0,
CAPE_REFINERYREACTOROP = 1
} CapeUnitType;

// ICapeUnitTypeInfo interface
[
object,
uuid(ICapeUnitTypeInfo_IID),
dual,
helpstring("ICapeUnitTypeInfo Interface"),
pointer_default(unique)
]

interface ICapeUnitTypeInfo : IDispatch
{
[propget, id(1), helpstring("property GetUnitType")]
HRESULT GetUnitType([out, retval] CapeUnitType* unitType);
};

A good argument to put it in the registry (CapeDescription) is so that you can find this out without loading the unit

Jasper, how would be specify that it should go in the registry? Would we just put in the Word document?

Yes, in the word document we would add a statement about registration requirements of petro-aware unit operations.