2003
DOI: 10.1007/978-3-540-45229-4_5
|View full text |Cite
|
Sign up to set email alerts
|

A Web Services Matchmaking Engine for Web Services

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
17
0

Year Published

2005
2005
2024
2024

Publication Types

Select...
3
3
1

Relationship

0
7

Authors

Journals

citations
Cited by 28 publications
(18 citation statements)
references
References 2 publications
0
17
0
Order By: Relevance
“…It has been established that directory services, such as UDDI, are important but insufficient for this purpose [9] and need to be complemented with matchmaking facilities like symmetry of information exchange between services and their consumers, the ability of each party to describe requirements from the other party, a rich language to describe services' and consumer demands, and a methodology to choose efficiently among competing service instances.…”
Section: Representation Of Service Instances and Requirementsmentioning
confidence: 99%
See 2 more Smart Citations
“…It has been established that directory services, such as UDDI, are important but insufficient for this purpose [9] and need to be complemented with matchmaking facilities like symmetry of information exchange between services and their consumers, the ability of each party to describe requirements from the other party, a rich language to describe services' and consumer demands, and a methodology to choose efficiently among competing service instances.…”
Section: Representation Of Service Instances and Requirementsmentioning
confidence: 99%
“…To this end, we use the Web Services Matchmaking Engine (WSME) [9] -an engine capable of matching complex entities, and a Data Dictionary tool for defining the language for the matching process. Matching is performed between service instances and requirements specified by the consumer.…”
Section: Representation Of Service Instances and Requirementsmentioning
confidence: 99%
See 1 more Smart Citation
“…In the absence of the model differentiating service types from instances in OWL-S, we use ServiceProfile model to represent web service type definitions in our service composition system [11]. The task of providing descriptions for specific web service instances is done using the Web Services Matchmaking Engine (WSME) [12] as discussed later in Physical Composition.…”
Section: Classifying Types and Instancesmentioning
confidence: 99%
“…In our system, the instance-specific NFCs are stored using the Web Services Matchmaking Engine (WSME) [12] as discussed later in physical composition. NFCs at the service type level can be added using OWL-S.…”
Section: Modeling Non Functional Service Capabilitiesmentioning
confidence: 99%