Semantic view Clause Samples

Semantic view. The semantic view describes the meaning of the services used in application design. Semantic information is required of: Functionality provided by the service, Quality properties of the service, Meaning of information/data provided by the service, Usage constraints of the service, and Context of a service, if it functional or quality properties can change according to the context. Although ▇▇▇▇▇ profile has great expressivity to describe real-time embedded applications, it does not include immediate mechanisms to distinguish a service from another from a semantic point of view apart from the plain service name. Semantic information is often very close to ontologies and taxonomies. In order to use ▇▇▇▇▇ to fully describe the services of the eDIANA platform it is necessary to define an ontology of the services that an embedded application can request/provide at the different integration levels. Once the ontology is defined, ▇▇▇▇▇ can be extended or adapted to support the inclusion of this ontological information. The <<RtFeature>> stereotype, defined in the HLAM sub-profile of ▇▇▇▇▇, has been widely used throughout this document to describe the eDIANA devices and applications. <<RtFeature>> includes a property called “utility” that may enable to add the semantics to service interfaces by specifying it in the <<RtFeature>> stereotypes applied to the signals. The UtilityType is defined as an abstract type in ▇▇▇▇▇ so that it can be refined into user defined types. By extending this stereotype it is possible to include information regarding reference ontologies, categories, etc. into ▇▇▇▇▇ compliant models.