2010
DOI: 10.1007/978-3-642-17694-4_11
|View full text |Cite
|
Sign up to set email alerts
|

Telecommunication Mashups Using RESTful Services

Abstract: Abstract. Evolution in the telecommunications sector has led to companies within it providing APIs for their products and services, allowing others to build communication services into their own service offerings. In order to support mass adoption of this new approach, consumers of these APIs (many of which are RESTful) must be supported by a reduction in the complexity involved with describing, finding, composing and invoking them. Existing efforts to provide automation have, in general, focused on WSDL servi… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2011
2011
2019
2019

Publication Types

Select...
3
1

Relationship

1
3

Authors

Journals

citations
Cited by 4 publications
(3 citation statements)
references
References 11 publications
0
3
0
Order By: Relevance
“…It illustrates the benefits of getting meta-data on top of services to improve the definition of mashups and decrease the coupling between information system building blocks and the complexity of developing mature Semantic REST APIs. In [5], Duke et al propose an approach to reduce the complexity for describing, finding, composing and invoking semantic rest services. They mainly provide an approach where they show how they can combine services when they get semantic information.…”
Section: Related Workmentioning
confidence: 99%
“…It illustrates the benefits of getting meta-data on top of services to improve the definition of mashups and decrease the coupling between information system building blocks and the complexity of developing mature Semantic REST APIs. In [5], Duke et al propose an approach to reduce the complexity for describing, finding, composing and invoking semantic rest services. They mainly provide an approach where they show how they can combine services when they get semantic information.…”
Section: Related Workmentioning
confidence: 99%
“…Therefore, OmniVoke takes RDF data as input and returns RDF data as response data, thus enabling a seamless integration of Web APIs, as semantic data prosumers [20], into the RDF linked data space. In order to carry out concrete invocations, the envisaged scenario is for applications to issue SPARQL queries to derive the data required for invoking a particular Web API [2]. Alternatively appropriate user-interaction interfaces can be provided to allow the user to provide his/her input, which, together with response data, may be collected into shared data space for further manipulations like inspection, reuse etc.…”
Section: A Architecturementioning
confidence: 99%
“…The world of services on the Web has recently been marked by the proliferation of Web APIs, which seem to be preferred over "classical" Web services based on WSDL and SOAP [1][2][3]. Web APIs, also called RESTful services when they conform to REST principles [4] are used by most major Web sites such as Facebook, Flickr, Salesforce or Amazon to provide access to their data and functionality.…”
Section: Introductionmentioning
confidence: 99%