return to the DDS Family of Standards

Note: The following is an excerpt from the actual document. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference.

Of primary concern to applications deploying DDS technology is the ability to integrate applications running on heterogeneous platforms, which may differ both in the programming language of use as well as in the underlying operating system. This should not be compromised by the introduction of additional programming language PSMs.

More specifically: The new PSM should be functionally equivalent to the existing PSMs. While the syntax may change, the application should be able to accomplish exactly the same tasks that can be accomplished with the existing PSMs. More specifically:

• Applications programmed using different PSMs should interoperate transparently; that is, an application that communicates with another application should have no awareness—other than informational—of what PSM the peer application is using.
• The new PSM should be derivable from the PIM by following a fairly small set of rules, which should be described in each submission.
• The new PSM should be designed such that it can coexist with other technologies. For example, it should not interfere with the namespaces used by other OMG specifications or commonly-used packages.

Lastly, the resulting PSM should make use of C# features, as appropriate and natural, to provide an API that is conformant with the most common programming idioms and patterns in the C# programming language.

* [nick]please review scope -- pasted direct from the RFP