| ID | 2.2.2 |
| Title | Service Description |
| Expert | Anthony Tarlano (DOCOMO) Jussi Riihela (NOKIA SIEMENS NETWORKS) Stian Alapnes (TELENOR) |
| Priority | mandatory |
| Description | A description of a service may contain three main aspects: Functional metadata of the services operations, non-functional metadata of the services operation, and semantic annotations that provide a semantic grounding to the functional and non-functional metadata. |
| Rationale | Service descriptions allow for a service to expose a profile of a service. |
| Type | functional |
| Depends on | 4.0.1 - Mobile Ontology |
| Child dependencies | 2.2.1 - Service Repository for Semantically Described Services 2.2.3 - Query Evaluation by the Service Description Repository 5.3.2 - Service Publication & Discovery with syntactical, semantical and pragmatic annotations |
| Environment | SPICE service descriptions must be unambiguous and machine readable. |
| Other_info | |
| Category | technical;open market |
| Subcategory | |
| Subcategory2 | |
| Scenario_scene | unified.scene5 unified.scene7 |
| SPICE_value | service matching |
| Demo | |
| Keywords | ontology;vocabulary |
| Home |