DDSRPC_ — Clarifications and simple technical corrections

This issue is a subset of the DDSRPC-1 issue reported by Remedy.

IDL zip (mars/14-11-05)
rpc_types.idl:
Uses the RTI specific top-level annotation. Also top-level is illegal according to the IDL grammar.
Uses anonymous types
robot.idl:

In the 4rd paragraph it mentions “asynchronous invocations”, but this is not mentioned in 8.2.2.1, how do asynchronous invocations look like with the function call style in the basic profile?

Section 8.2.3
Where in this document is the API defined to get the request id at both sides for implicit or explicit?

Section 8.2.1
Why include space as part of user_def_alpha_num?

Section 8.5.1.1.1
Why is SequenceNumber_t not using an “unsigned long long”. It is now a struct but there is no explanation in the specification about high and low

Section 8.5.1.1.2
Why not put the implied types into a nested module so that they don't pollute the user IDL module and resulting code, doxygen documentation, etc

Section 8.5.1.1.4
Why not put the implied types into a nested module so that they don't pollute the user IDL module and resulting code, doxygen documentation, etc

What is the error when the remote service is not there (for example not running or not reachable), which exception do I get back?
What when the service crashes during handling of the request, what kind of error do I get back, what is the timeout? How can configure timeouts etc?

Section 8.7.1.3
What about changing the exception specification of an operation?
Section 8.8.2
Not a legal IDL struct definition, struct has to be removed from its members
Section 8.10.1
What about the library name RTI DDS currently supports. It is very helpful to have multiple QoS profiles in one file and the spec should define how this works

Added clarifications to the spec document or provided justifications

Added clarifications to the spec document or provided justifications below.