| ID | 2.2.1 |
| Title | Service Repository for Semantically Described Services |
| Expert | Anthony Tarlano (DOCOMO) Jussi Riihela (NOKIA SIEMENS NETWORKS) Stian Alapnes (TELENOR) |
| Priority | mandatory |
| Description | Service discovery requires a service repository capable of storing semantic service descriptions, using specifications (formal languages), that allow a service's developer to semantically describing all relevant aspects of the service. |
| Rationale | Many semantic service description specifications exists that depending on the formal language used allow a service to be semantically describe services at varying levels of specificity the platform should support the developers intention. |
| Type | functional |
| Depends on | 2.2.2 - Service Description 2.2.4 - Multi-domain Service Repository Architecture |
| Child dependencies | 2.2.3 - Query Evaluation by the Service Description Repository |
| Environment | The SPICE service repository should be based on standardized protocols and frameworks |
| Other_info | dependency - Service descriptions are formal and processable by the service repository. |
| Category | technical;open market |
| Subcategory | |
| Subcategory2 | |
| Scenario_scene | unified.scene2 unified.scene3 |
| SPICE_value | service matching |
| Demo | |
| Keywords | discovery;publication;matching |
| Home |