COAS 1.0 NO IDEA Avatar
  1. OMG Issue

COAS — COAS operations that return ObservationData

  • Key: COAS-35
  • Legacy Issue Number: 3042
  • Status: closed  
  • Source: 2AB ( Tim Brinson)
  • Summary:

    The COAS operations that return ObservationData are locked into using a
    structuring mechanism that is defined as a stop gap solution due to the
    lack of extensive support for the ValueTypes by ORBs today. This
    proposal addresses that problem by suggesting a simple change that
    allows the same COAS operational interfaces to be used in the future
    with ValueTypes (or additional types that may be created for IDL in the

    I propose that the current ObservationData type be renamed to
    ObservationDataStruct. Any data types that reference ObservationData
    would then reference ObservationDataStruct (with the exception of
    ObservationDataSeq). A typedef for ObservationData being of the type
    "any" would be created as such:

    typedef any ObservationData;

    In this way observations are passed by value via the "any" type
    (actually a typedef to the "any" type) in the operations which frees up
    the possibility of using ValueType (and other type) definitions for
    observations in the future or by local agreement in specialized

    In addition a new Conformance class (e.g. "Structured COAS") should be
    created that indicates a server uses the ObservationDataStruct as the
    explicit type returned/passed in via the ObservationData in operations.
    This allows future standardization using value types in which additional
    conformance points can be made for other structuring used by servers.
    Note these conformance classes are independent of the conformance
    classes specifying which interfaces a server implements.

  • Reported: COAS 1.0b1 — Wed, 17 Nov 1999 05:00 GMT
  • Disposition: Resolved — COAS 1.0
  • Disposition Summary:

    resolved in COAS FTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT