Fandom

VroniPlag Wiki

Saa/Fragment 052 01

< Saa

31.388Seiten in
diesem Wiki
Seite hinzufügen
Diskussion0 Teilen

Störung durch Adblocker erkannt!


Wikia ist eine gebührenfreie Seite, die sich durch Werbung finanziert. Benutzer, die Adblocker einsetzen, haben eine modifizierte Ansicht der Seite.

Wikia ist nicht verfügbar, wenn du weitere Modifikationen in dem Adblocker-Programm gemacht hast. Wenn du sie entfernst, dann wird die Seite ohne Probleme geladen.


Typus
Verschleierung
Bearbeiter
Hindemith
Gesichtet
Yes.png
Untersuchte Arbeit:
Seite: 52, Zeilen: 1 ff. (komplett)
Quelle: Vazquez 2007
Seite(n): 40, 43-45, Zeilen: 40: 8 ff.; 43: 7 ff.; 44: 1 ff.; 45: 1 ff.
A client implementing the Presentation Layer is usually referred to as Task Computing Client (TCC) and makes use of well-defined interfaces to the Middleware Layer.

Task Computing is implemented in concrete Task Computing Environments (TCEs), which are computational systems able to perform Task Computing functionality and composed of Task Computing Clients, Semantic Service Descriptions, Semantic Service Discovery Mechanisms and Service Controls. The detailed information about all of these components is given in the afore-mentioned literature.

3.4.2 Conclusion

Task Computing is primarily a framework for services orchestration, composition, and execution. All the mechanisms it features are aimed at service publishing and discovery, semantic descriptions, service-ization of resources to make them available to any requester, and so forth. These features can be implemented in multiple environments, not being specially addressed for Ubiquitous Computing scenarios. In fact, Task Computing applies well-known Internet-wide technologies such as UDDI for discovery or traditional Web Services at external servers as endpoints. In order to assume a more context-aware nature, Task Computing has embraced some pervasive computing technologies to complement existing ones, such as UPnP's Simple Service Discovery Protocol (SSDP) for discovery, so services can be found both at a global level via UDDI and at a local level via the group by subnet discovery range.

The following sections provide analysis of Task Computing technology against our defined evaluation criteria, and the conclusion is summarized in Table 3.4.

  • Decentralization: Task Computing is not aimed at creating a network of interconnected devices. The TCEs are intended to run in desktop computers or servers that can be connected to UPnP or Jini networks if device control is required. Low.
  • Lightness: The processes such as semanticization and serviceization as well as the need of the Task Computing Client result in complex and heavy software components. The devices need an amount of computing resources (i.e. processing power and screen size) presently not available in every embedded platform. Low.
  • Standards Adherence: In general, Task Computing honors the existing standards and technologies, i.e. OWL-S, WSDL, HTTP, UDDI, and even industry de facto standards such as SSDP. High.
  • Technological Consistency: Task Computing applies Web Services and Semantic Web technologies in a coherent and synergistic manner. High.
  • Reasoning Capability: Task Computing uses semantic information to annotate service descriptions and perform service composition, but neither reasoning nor domain ontologies are provided to understand context information. Low.
  • Context Awareness: No form of capturing context or sensing environmental conditions are provided directly by Task Computing, except for service discovery mechanisms which is a technical issue and not related to context-awareness. Low.
A client implementing the Presentation layer is usually referred to as Task Computing Client (TCC) and makes use of well-defined interfaces to the Middleware layer.

Task Computing is implemented in concrete TCEs (Task Computing Environments), which are computational systems able to perform Task Computing functionality and composed of Task Computing Clients, Semantic Service Descriptions, Semantic Service Discovery Mechanisms and Service Controls.

[Seite 43]

2.3.3 Conclusion

Task Computing is primarily a framework for services orchestration, composition, and execution. All the mechanisms it features are aimed at this goal: service publishing and discovery, semantic descriptions, service-ization of resources to make them available to any requester, and so forth. These features can be implemented in multiple environments, not being specially addressed for Ubiquitous Computing scenarios. In fact, Task Computing

[Seite 44]

applies well-known Internet-wide technologies such as UDDI for discovery or traditional Web Services at external servers as endpoints.

In order to assume a more context-aware nature, Task Computing has embraced some pervasive computing technologies to complement existing ones, such as SSDP for discovery, so services can be found both at a global level via UDDI and at a local level via the group by subnet discovery range. [...]

[...]

An analysis of Task Computing against the evaluation criteria leads to the following results:

Decentralisation: Task Computing is not aimed at creating a network of interconnected devices. The TCEs are intended to run in desktop computers or servers that can be connected to UPnP or Jini networks if device control is required. Low.

Reasonability: Task Computing uses semantic information to annotate service descriptions and perform service composition, but neither reasoning nor domain ontologies are provided to understand context information. TC only is aimed at matching required and offered services. Low.

[Seite 45]

Context-awareness: except for service discovery mechanisms (which strictly is a technical issue, not related to context-awareness), no other form of capturing context, sensing environmental conditions, and so forth, are provided directly by Task Computing. No form of automatic responsive behaviour is provided in the model, but user intervention is required. Low.

Technological Consistency: Task Computing applies web services and Semantic Web technologies in a coherent and synergistic manner. High.

Standards Adherence: in general terms, Task Computing honours standards and recommendations trying to reuse existing technologies. Standards such as OWL-S, WSDL, HTTP, UDDI, and even industry de facto standards such as SSDP are widely used. High.

[...]

Lightness: processes such as Semantic-ization and Service-ization as well as the need of the Task Computing Client, result in complex and heavy software components. Devices need an amount of computing resources (processing power and screen size, among others) not presently available in every embedded platform. Low.

Anmerkungen

Ein Verweis auf die Quelle fehlt.

Auch die "analysis of Task Computing technology against our defined evaluation criteria" ist identisch zur Quelle

Sichter
(Hindemith), SleepyHollow02

Auch bei Fandom

Zufälliges Wiki