Meetings2012-02-16 » History » Version 4
J. Moringen, 02/16/2012 04:59 PM
scope renaming
| 1 | 1 | J. Moringen | h1. Meetings 2012-02-16 |
|---|---|---|---|
| 2 | 1 | J. Moringen | |
| 3 | 1 | J. Moringen | h2. Configuration Service |
| 4 | 1 | J. Moringen | |
| 5 | 2 | J. Moringen | h3. Nomenclature |
| 6 | 2 | J. Moringen | |
| 7 | 2 | J. Moringen | * Configuration |
| 8 | 2 | J. Moringen | ** Framework level |
| 9 | 3 | J. Moringen | *** Converter [implemented] |
| 10 | 3 | J. Moringen | *** Transports (+ quality of service) [implemented] |
| 11 | 3 | J. Moringen | *** Error handling [implemented] |
| 12 | 3 | J. Moringen | *** Scope names [not implemented] |
| 13 | 4 | J. Moringen | **** Are these renaming rules, which are applied at participant creation time? |
| 14 | 4 | J. Moringen | **** Do they affect scopes or participants? |
| 15 | 2 | J. Moringen | ** Domain level |
| 16 | 2 | J. Moringen | *** Component parameters |
| 17 | 2 | J. Moringen | **** Changable at runtime? |
| 18 | 2 | J. Moringen | |
| 19 | 2 | J. Moringen | * Parameter Service? |
| 20 | 2 | J. Moringen | |
| 21 | 1 | J. Moringen | h3. Requirements |
| 22 | 2 | J. Moringen | |
| 23 | 4 | J. Moringen | * Remapping of scope names |
| 24 | 4 | J. Moringen | ** Remapping on the program-level is sufficient (i.e. participant level is not needed) |
| 25 | 4 | J. Moringen | ** Recursive renaming has be possible |
| 26 | 1 | J. Moringen | |
| 27 | 1 | J. Moringen | * must be suitable for component layer (e.g. CCA) |