Robotics Service Bus

h1. URI Schema

h2. URI types

h3. Generic

Generic:
<pre>
rsb:///hierarchical/service/definition/further/to/participant
</pre>
This may resolve to:
* Service and/or Participant
** If there is only one of these entities this is enough for resolving it
** If multiple entities reside on this scope, a single instance can be selected using their UUID.
@rsb:///hierarchical/service/definition/further/to/participant#UniqueIDOfParticipant [UUID]@
* Nothing ;)

These generic URIs require a global naming service.

h3. Specific

Specific:
<pre>
transport://<location.transport.specific[:PORT]>/hierarchical/service/definition/further/to/participant
</pre>
Location uniquely identifies a single participant or service, hence an ID part is not required any more.

Specific IDs can be resolved by the respective connectors and do not require a global naming.

h2. Rationale

* generic: usually location transparency should be available
* specific: specific access without naming
* UUIDs should ideally not be required to keep URIs simple