2005
DOI: 10.1109/mic.2005.96
|View full text |Cite
|
Sign up to set email alerts
|

A semantic Web services architecture

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
89
0
5

Year Published

2005
2005
2021
2021

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 188 publications
(94 citation statements)
references
References 9 publications
0
89
0
5
Order By: Relevance
“…There is no Optional Or feature in our 1 For brevity, definitions of Rule classes are omitted from here.…”
Section: E Optional Ormentioning
confidence: 99%
See 1 more Smart Citation
“…There is no Optional Or feature in our 1 For brevity, definitions of Rule classes are omitted from here.…”
Section: E Optional Ormentioning
confidence: 99%
“…Semantic Web Services emphasizes enabling dynamic, execution-time discovery, composition, and invocation of Web Services [1] allowing automated ad-hoc interaction between web-based applications [2]. It builds on the existing Web Services technology that provides software developers a framework for accurate documentation of services to allow the development-time discovery, composition, and statically coded invocation of services in the Web.…”
Section: Introductionmentioning
confidence: 99%
“…A research area, referred to as Semantic Web Services (SWSs), has emerged to apply Semantic Web technologies to Web services (Burstein et al 2005;McIlraith et al 2001;Sycara et al 2003). OWL-S (Martin et al 2007), WSMF/WSMO (Fensel and Bussler 2002;Lausen et al 2005) and METEOR-S (Patil et al 2004;Sivashanmugam et al 2003) are three major initiatives that have developed languages and frameworks to explicitly add semantics into the Web services descriptions.…”
Section: Related Work and Comparisonmentioning
confidence: 99%
“…This is particularly the case for data mediators, which typically work as transformation functions from one domain into the other and hence can be easily described as atomic processes by specifying appropriate input and output types. We comply with this approach since we believe that the view of mediators as web services naturally fits into the Semantic Web Services Architecture [21] and allows us, for example, to use the same discovery and invocation mechanisms for mediators as for any other services.…”
Section: Data Level Mismatchesmentioning
confidence: 99%