The Experts below are selected from a list of 76635 Experts worldwide ranked by ideXlab platform
Antonia Albani - One of the best experts on this subject based on the ideXlab platform.
-
An Enterprise Ontology-Based Approach to Service Specification
IEEE Transactions on Services Computing, 2013Co-Authors: Linda I. Terlouw, Antonia AlbaniAbstract:In recent years, the Web Service Definition Language (WSDL) and Universal Description Discovery Integration (UDDI) standards arose as ad hoc standards for the Definition of Service interfaces and Service registries. However, even together these standards do not provide enough basis for a Service consumer to get a full understanding of the behavior of a Service. In practice, this often leads to a serious mismatch between the provider's intent and the consumer's expectations concerning the functionality of the corresponding Service. Though additional standards have been proposed, a holistic view of what aspects of a Service need to be specified is still lacking. This paper proposes a Service Definition, a Service classification, and Service specification framework, all based on a founded theory, the $(\Psi)$-theory. The $(\Psi)$-theory originates from the scientific fields of Language Philosophy and Systemic Ontology. According to this theory, the operation of organizations is all about communication between and production by social actors. The Service specification framework can be applied both for specifying human Services, i.e., Services executed by human beings, and IT Services (i.e., Services executed by IT systems).
-
Enterprise Ontology Based Service Definition
2009Co-Authors: Antonia Albani, G.c. Hardjosumarto, Linda Terlouw, Jan L. G. DietzAbstract:Economists and business scientists have been debating about the ‘Service' notionfor more than two centuries [9]. Often, the Definitions in business literature limitthe Service notion to the delivery of immaterial goods. The adoptation of thenotion of ‘Service' by computer scientists and IT practitioners has been morerecent. In both the business science field [19, 10, 14, 12] and the computer sciencefield [16, 15, 13, 17] a Service is regarded as an interaction between a requestingparty (often called consumer or customer) and an offering party (often calledprovider or supplier). The offering party is able to produce a certain value thatis requested by the other party. But even with this common notion a preciseDefinition and mutual understanding of the term Service is missing. Let us havea look at the Definition given by the Open Group [13]. It states that a Serviceis a logical representation of a repeatable business activity that has a specifiedoutcome (e.g., check customer credit; provide weather data, consolidate drillingreports), is self-contained, may be composed of other Services, and is a "black-box'to consumers of the Service. This Definition is as vague as the other Definitionsand one could discuss every single statement of the Definition. E.g., what is abusiness activity? The Open Group mentions "check customer credit' or "provideweather data' as business activities, but are these really business activities orare they only computational acts? What about a business activity concerningthe "manufacturing of a car'? Such a business activity has a completely differentgranularity as the ones mentioned in the Definition. What is self-contained? If aService is composed of other Services is it still self-contained? What is preciselymeant by a black-box when a Service is also defined to be an activity? Whatabout communication activities e.g., to call the Service or to accept/reject therequested result?According to the -theory [4, 7], the theory that underlies the notion of EnterpriseOntology [4], the operation of organizations is all about communicationbetween and production by social actors. Is not the main concern of Serviceorientationto support the operation of an organization and therefore also tosupport the communication between and production by social actors? Becausethe -theory describes the interaction between the requesting party and the offeringparty in a very formal way, it provides a perfect basis for formalizing thenotion of Service.
Steven Tuecke - One of the best experts on this subject based on the ideXlab platform.
-
modeling and managing state in distributed systems the role of ogsi and wsrf
Proceedings of the IEEE, 2005Co-Authors: Ian Foster, Karl Czajkowski, D E Ferguson, Jaime Frey, S Graham, T Maguire, D Snelling, Steven TueckeAbstract:We often encounter in distributed systems the need to model, access, and manage state. This state may be, for example, data in a purchase order, Service level agreements representing resource availability, or the current load on a computer. We introduce two closely related approaches to modeling and manipulating state within a Web Services (WS) framework: the Open Grid Services Infrastructure (OGSI) and WS-Resource Framework (WSRF). Both approaches define conventions on the use of the Web Service Definition language schema that enable the modeling and management of state. OGSI introduces the idea of a stateful Web Service and defines approaches for creating, naming, and managing the lifetime of instances of Services; for declaring and inspecting Service state data; for asynchronous notification of Service state change; for representing and managing collections of Service instances; and for common handling of Service invocation faults. WSRF refactors and evolves OGSI to exploit new Web Services standards, specifically WS-addressing, and to respond to early implementation and application experiences. WSRF retains essentially all of the functional capabilities present in OGSI, while changing some syntax (e.g., to exploit WS-addressing) and also adopting a different terminology in its presentation. In addition, WSRF partitions OGSI functionality into five distinct composable specifications. We explain the relationship between OGSI and WSRF and the related WS-notification specifications, explain the common requirements that both address, and compare and contrast the approaches taken to the realization of those requirements.
-
grid Service specification
2002Co-Authors: Steven Tuecke, Karl Czajkowski, Steve Graham, Jeffrey Frey, Ian Foster, Carl KesselmanAbstract:Building on both Grid and Web Services technologies, the Open Grid Services Architecture (OGSA) defines mechanisms for creating, managing, and exchanging information among entities called Grid Services. Succinctly, a Grid Service is a Web Service that conforms to a set of conventions (interfaces and behaviors) that define how a client interacts with a Grid Service. These conventions, and other OGSA mechanisms associated with Grid Service creation and discovery, provide for the controlled, fault resilient, and secure management of the distributed and often long-lived state that is commonly required in advanced distributed applications. In a separate document, we have presented in detail the motivation, requirements, structure, and applications that underlie OGSA. Here we focus on technical details, providing a full specification of the behaviors and Web Service Definition Language (WSDL) interfaces that define a Grid Service.
Linda I. Terlouw - One of the best experts on this subject based on the ideXlab platform.
-
An Enterprise Ontology-Based Approach to Service Specification
IEEE Transactions on Services Computing, 2013Co-Authors: Linda I. Terlouw, Antonia AlbaniAbstract:In recent years, the Web Service Definition Language (WSDL) and Universal Description Discovery Integration (UDDI) standards arose as ad hoc standards for the Definition of Service interfaces and Service registries. However, even together these standards do not provide enough basis for a Service consumer to get a full understanding of the behavior of a Service. In practice, this often leads to a serious mismatch between the provider's intent and the consumer's expectations concerning the functionality of the corresponding Service. Though additional standards have been proposed, a holistic view of what aspects of a Service need to be specified is still lacking. This paper proposes a Service Definition, a Service classification, and Service specification framework, all based on a founded theory, the $(\Psi)$-theory. The $(\Psi)$-theory originates from the scientific fields of Language Philosophy and Systemic Ontology. According to this theory, the operation of organizations is all about communication between and production by social actors. The Service specification framework can be applied both for specifying human Services, i.e., Services executed by human beings, and IT Services (i.e., Services executed by IT systems).
D Martin - One of the best experts on this subject based on the ideXlab platform.
-
context modeling to enforce interoperability in web Service Definition
IEEE International Conference on Services Computing, 2007Co-Authors: Xiaofeng Wang, D MartinAbstract:Context modeling using a UML profile facilitates interoperability of web Service Definitions. While model-driven methodologies are a generally accepted practice for generating web Service artifacts such as XSDs and WSDLs, they do not guarantee that the artifacts will be interoperable. To avoid interoperability issues, transformations from logical to physical models must be accomplished with an awareness of implementation context. An example case study based on our experience in using the IEC CIM model demonstrates the concept.
Ian Foster - One of the best experts on this subject based on the ideXlab platform.
-
modeling and managing state in distributed systems the role of ogsi and wsrf
Proceedings of the IEEE, 2005Co-Authors: Ian Foster, Karl Czajkowski, D E Ferguson, Jaime Frey, S Graham, T Maguire, D Snelling, Steven TueckeAbstract:We often encounter in distributed systems the need to model, access, and manage state. This state may be, for example, data in a purchase order, Service level agreements representing resource availability, or the current load on a computer. We introduce two closely related approaches to modeling and manipulating state within a Web Services (WS) framework: the Open Grid Services Infrastructure (OGSI) and WS-Resource Framework (WSRF). Both approaches define conventions on the use of the Web Service Definition language schema that enable the modeling and management of state. OGSI introduces the idea of a stateful Web Service and defines approaches for creating, naming, and managing the lifetime of instances of Services; for declaring and inspecting Service state data; for asynchronous notification of Service state change; for representing and managing collections of Service instances; and for common handling of Service invocation faults. WSRF refactors and evolves OGSI to exploit new Web Services standards, specifically WS-addressing, and to respond to early implementation and application experiences. WSRF retains essentially all of the functional capabilities present in OGSI, while changing some syntax (e.g., to exploit WS-addressing) and also adopting a different terminology in its presentation. In addition, WSRF partitions OGSI functionality into five distinct composable specifications. We explain the relationship between OGSI and WSRF and the related WS-notification specifications, explain the common requirements that both address, and compare and contrast the approaches taken to the realization of those requirements.
-
grid Service specification
2002Co-Authors: Steven Tuecke, Karl Czajkowski, Steve Graham, Jeffrey Frey, Ian Foster, Carl KesselmanAbstract:Building on both Grid and Web Services technologies, the Open Grid Services Architecture (OGSA) defines mechanisms for creating, managing, and exchanging information among entities called Grid Services. Succinctly, a Grid Service is a Web Service that conforms to a set of conventions (interfaces and behaviors) that define how a client interacts with a Grid Service. These conventions, and other OGSA mechanisms associated with Grid Service creation and discovery, provide for the controlled, fault resilient, and secure management of the distributed and often long-lived state that is commonly required in advanced distributed applications. In a separate document, we have presented in detail the motivation, requirements, structure, and applications that underlie OGSA. Here we focus on technical details, providing a full specification of the behaviors and Web Service Definition Language (WSDL) interfaces that define a Grid Service.