2006
DOI: 10.1007/11926078_43
|View full text |Cite
|
Sign up to set email alerts
|

Web Service Composition Via Generic Procedures and Customizing User Preferences

Abstract: Abstract. We claim that a key component of effective Web service composition, and one that has largely been ignored, is the consideration of user preferences. In this paper we propose a means of specifying and intergrating user preferences into Web service composition. To this end, we propose a means of performing automated Web service composition by exploiting generic procedures together with rich qualitative user preferences. We exploit the agent programming language Golog to represent our generic procedures… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
2

Citation Types

0
40
0

Year Published

2008
2008
2016
2016

Publication Types

Select...
6
2

Relationship

3
5

Authors

Journals

citations
Cited by 37 publications
(40 citation statements)
references
References 15 publications
0
40
0
Order By: Relevance
“…Such approach-used by Agarwal et al [8], Akkiraju et al [9], Klusch and Gerber [29], McIlraith and Son [23], Rodríguez-Mier et al [30], Sohrabi et al [31], Traverso and Pistore [24], Wu et al [25], among others-has a few practical obstacles in order to be put into production scenarios. There is the need for complete formal descriptions of each service, sometimes requiring a detailed description of service interactions, as in [23,24], for example.…”
Section: Automated Service Compositionmentioning
confidence: 99%
“…Such approach-used by Agarwal et al [8], Akkiraju et al [9], Klusch and Gerber [29], McIlraith and Son [23], Rodríguez-Mier et al [30], Sohrabi et al [31], Traverso and Pistore [24], Wu et al [25], among others-has a few practical obstacles in order to be put into production scenarios. There is the need for complete formal descriptions of each service, sometimes requiring a detailed description of service interactions, as in [23,24], for example.…”
Section: Automated Service Compositionmentioning
confidence: 99%
“…The adopted planning domain modeling relies solely on individual descriptions of decoupled device operations, described and implemented using existing protocol standards. This way, the domain representation is kept generic and can serve a variety of different user needs through the configuration of declarative goals, unlike most other approaches which use planning for Web service composition, and require the specification of procedural templates, for example, in HTN [Au et al 2005] or Golog [Sohrabi et al 2006]. The domain encoding is based on a variable-based rather than a predicate-based representation, thus maintaining a close relation to the actual way that device operations are realized, for example, adhering to a direct mapping between UPnP-and planning-level variables.…”
Section: Smartness Via Service Compositionmentioning
confidence: 99%
“…Most of the approaches to service composition via automated planning, however, require that the set of supported solutions is predefined in some form of procedural templates, such as in the form of HTN methods in Au et al [2005] or as Golog programs in Sohrabi et al [2006], and are therefore not easily reconfigurable in case of changes in the context, the domain, or the user requirements. Our approach, on the other hand, relies on a domain-independent planner (see Kaldeli et al [2011] for details) where the user just states what properties have to be satisfied, without having to anticipate how these can be fulfilled.…”
Section: Service Composition In Pervasive Systemsmentioning
confidence: 99%
“…In previous work (e.g., [15,20,19]) we have argued that for a number of WSC problems it is desirable to specify a flexible workflow, generic procedure, or composition template that specifies the basic steps of the composition at an abstract level, but has sufficient flexibility to support their customization for different stakeholders, scenarios, and applications. To this end, we have specified flexible workflows using Golog (e.g., [15,20]), or alternatively Hierarchical Task Networks (HTNs) [19], and developed associated machinery for WSC. We are not alone is proposing such a vision.…”
Section: Introductionmentioning
confidence: 99%
“…Similarly, in cases where customizations are desirable but not mandatory, customizations can be specified as preferences. This observation has led us to characterize the WSC task as a preference-based planning (PBP) task where actions (services, service parameters, and/or data) are selected not only to achieve the composition objective but to produce compositions that are of high quality with respect to quality of service, trust, or other composition-, service-, or data-oriented user preferences (e.g., [20,11,19,1,10,21]). …”
Section: Introductionmentioning
confidence: 99%