URI Schema » History » Version 58
J. Wienke, 02/14/2013 02:54 PM
| 1 | 1 | J. Wienke | h1. URI Schema |
|---|---|---|---|
| 2 | 1 | J. Wienke | |
| 3 | 45 | J. Moringen | h2. Use Cases |
| 4 | 1 | J. Wienke | |
| 5 | 45 | J. Moringen | URIs or URLs are used in the following situations |
| 6 | 51 | J. Moringen | * Specifying how to connect to the bus (i.e. specifying a scope and transport configuration) |
| 7 | 45 | J. Moringen | * Naming a thing on the bus |
| 8 | 45 | J. Moringen | ** A channel |
| 9 | 48 | J. Moringen | ** Multiple participants |
| 10 | 48 | J. Moringen | ** A single participant |
| 11 | 1 | J. Wienke | *** A service |
| 12 | 45 | J. Moringen | |
| 13 | 58 | J. Wienke | h2. Specification |
| 14 | 45 | J. Moringen | |
| 15 | 58 | J. Wienke | http://docs.cor-lab.de//rsb-manual/trunk/html/specification-uris.html#specification-uris |
| 16 | 47 | J. Moringen | |
| 17 | 45 | J. Moringen | h3. Rationale |
| 18 | 42 | J. Wienke | |
| 19 | 57 | J. Moringen | * Transport-specific access is possible without naming service. |
| 20 | 57 | J. Moringen | * UUIDs should ideally not be required to keep URIs simple |