Fandom

VroniPlag Wiki

Quelle:Saa/Zeeb et al 2007

< Quelle:Saa

31.377Seiten in
diesem Wiki
Seite hinzufügen
Diskussion0

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.

Angaben zur Quelle [Bearbeiten]

Autor     Elmar Zeeb, Andreas Bobek, Hendrik Bohn and Frank Golatowski
Titel    Lessons learned from implementing the Devices Profile for Web Services
Sammlung    Digital EcoSystems and Technologies Conference, 2007. DEST '07. Inaugural IEEE-IES
Herausgeber    IEEE
Datum    21-23. February 2007
Seiten    229-232
ISBN    1-4244-0470-3, 1-4244-0470-3
DOI    10.1109/DEST.2007.371975
URL    http://www.imd.uni-rostock.de/fileadmin/IEF_IMD/veroeff/Lessons%20learned%20from%20implementing%20the%20Devices%20Profile%20for%20Web%20Services.pdf, http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=4233709&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D4233709

Literaturverz.   

nein
Fußnoten    nein
Fragmente    2


Fragmente der Quelle:
[1.] Saa/Fragment 015 01 - Diskussion
Zuletzt bearbeitet: 2015-05-16 20:32:44 Hindemith
Fragment, Gesichtet, SMWFragment, Saa, Schutzlevel sysop, Verschleierung, Zeeb et al 2007

Typus
Verschleierung
Bearbeiter
Graf Isolan
Gesichtet
Yes.png
Untersuchte Arbeit:
Seite: 15, Zeilen: 1-17
Quelle: Zeeb et al 2007
Seite(n): III-2 (Internetversion), Zeilen: li.Sp. 13-22, 41-48, 51-52, 54-57
WS-Discovery

The WS-Discovery is a discovery protocol based on IP multicast for enabling services to be discovered automatically. Discovery introduces three different endpoint types: target service, client and discovery proxy. Target Services are Web Services offering themselves to the network, Clients may search for target services and discover them dynamically and Discovery Proxy is an endpoint enabling discovery in spanned networks since simple discovery is limited to a multicast group and hence to local managed networks only.

WS-MetadataExchange / WS-Transfer

WS-MetadataExchange is a specification that defines data types and operations to retrieve metadata associated with an endpoint. This metadata describes what other endpoints need to know to interact with the described endpoint, and defines the MetadataSection that divides the metadata into separate units of metadata with a dialect specifying its type. WS-Transfer is used to retrieve the metadata, which is structured as specifified in WS-MetadataExchange. MetadataExchange. There is a slight functional difference in WSMetadataExchange and WS-Transfer for retrieval of metadata. WS-MetadataExchange defines operations to retrieve all or parts of the metadata of an endpoint. WS-Transfer only can be used to retrieve all metadata of an endpoint.

WS-Discovery

WS-Discovery is a discovery protocol based on IP multicast for enabling services to be discovered automatically. Discovery introduces three different endpoint types: target service, client and discovery proxy. Target services are Web services offering themselves to the network. Clients may search for target services and discover them dynamically. Discovery proxy is an endpoint enabling discovery in spanned networks since simple discovery is limited to a multicast group and hence to local managed networks only.

[...]

WS-MetadataExchange / WS-Transfer

WS-MetadataExchange is a specification that defines data types and operations to retrieve metadata associated with an endpoint. This metadata describes what other endpoints need to know to interact with the described endpoint. WS-MetadataExchange defines the MetadataSection that divides the metadata into separate units of metadata with a dialect specifying its type.

Until the latest version of DPWS only WS-MetadataExchange was used for service and device description and retrieval. In the latest DPWS version of February 2006 WS-Transfer is used to retrieve the metadata. The structure of the metadata is still as specified in WS-MetadataExchange. The main difference is that WS-MetadataExchange defined operations to retrieve all or parts of the metadata of an endpoint, whereas WS-Transfer only can be used to retrieve all metadata of an endpoint.

Anmerkungen

Ohne Hinweis auf eine Übernahme.

Sichter
(Graf Isolan), Hindemith

[2.] Saa/Fragment 015 20 - Diskussion
Zuletzt bearbeitet: 2015-05-16 20:34:51 Hindemith
Fragment, Gesichtet, SMWFragment, Saa, Schutzlevel sysop, Verschleierung, Zeeb et al 2007

Typus
Verschleierung
Bearbeiter
Graf Isolan
Gesichtet
Yes.png
Untersuchte Arbeit:
Seite: 15, Zeilen: 20-26
Quelle: Zeeb et al 2007
Seite(n): III-2 (Internetversion), Zeilen: re.Sp. 2-12
WS-Eventing

WS-Eventing defines a protocol for managing subscriptions for a Web Services based eventing mechanism. This protocol defines three endpoints: subscriber, event source and subscription manager. Subscribers request subscriptions on behalf of event sinks to receive events from event sources. Subscription requests contain an event delivery mode and event filter mechanism to negotiate an event source with an event sink. Subscription Managers are responsible of holding subscriptions of event sources.

WS-Eventing

WS-Eventing defines a protocol for managing subscriptions for a Web services based eventing mechanism. This protocol defines three endpoints: subscriber, event source and subscription manager. Subscribers request subscriptions on behalf of event sinks to receive events from event sources. Subscription requests contain an event delivery mode and event filter mechanism to negotiate event delivery mechanisms and event filter mechanism. Subscription managers are responsible of holding subscriptions of event sources.

Anmerkungen

Ohne Hinweis auf eine Übernahme.

Sichter
(Graf Isolan), Hindemith

Auch bei Fandom

Zufälliges Wiki