Re: [COAS-List] Proposed ObservationData IDL

[charles.carman@philips.com]

The information contained in this message is confidential and may be legally privileged. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, dissemination, or reproduction is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.

Hello, All.
I guess it is time for me to add my two cents
(particularily after reviewing the COAS IDL as part of editing the submission document for the FTF).

I think we have two issues here:
	to what extent should the IDL reflect the information model?
	how similar should the two access mechanisms be?
(the two access mechanisms are structure based vs. interface based, i.e. struct ObservationData vs. interface ObservationRemote).
BTW - the IDL for the ObservationRemote interface never made it into the "CompleteIDL" section of the submission,
but that is a different issue for the FTF :-)

My answer to the first question is: I think the IDL should reflect the data model as closely as is practical.