China
Africa
Explore chapters and articles related to this topic
More Examples of Modules and Functions with APIs
Published in Amartya Mukherjee, Nilanjan Dey, Smart Computing with Open Source Platforms, 2019
Amartya Mukherjee, Nilanjan Dey
JSON stands for JavaScript Object Notation. It is very popular among developers for serializing data. It is used for most of the web Application Programming Interface (web API) and passing of data between programs. Before accessing and parsing JSON data file, we have to import JSON module in our program.
1
Published in Uwe Engel, Anabel Quan-Haase, Sunny Xun Liu, Lars Lyberg, Handbook of Computational Social Science, Volume 2, 2021
Stefan Bosse, Lena Dahlhaus, Uwe Engel
Depending on the research objective, two main approaches to data collection on the internet can be considered. Social network providers, companies, and organizations may allow users and researchers to access and download data via an API. Popular networks such as the Facebook and Instagram APIs are cases in point, where both the access to data and its scope and diversity have become more restricted for users and academic research. Providers increasingly lean toward requesting a summary of the research plan and further contact information before granting access to data (Perriam et al., 2020; Lomborg & Bechmann, 2014). Web data mining is engineered to access publicly available web content, whereas APIs, while requiring authentication, can provide access to otherwise non-public information too (Lomborg & Bechmann, 2014). Web APIs enable filtered access to the underlying database content, in contrast to web scraping that gets access to the meta-level of the data with a visual representation. The use of APIs offers advantages, for example legality of the obtained data, but, depending on the required data, also holds several drawbacks compared with the web scraping process addressed in this chapter primarily:Web API often causes monetary costs, and the amount to be paid determines the data filter (e.g., maximal number of messages that can be accessed, data quality, data variables)Web API can change without any notice and at any time, mostly changing the filter functionWeb API can be biased for commercial reasons (i.e., a source of error in sentiment analysis)Web API provides directly structured data based on an ontology or schema; getting structured data from web scraping is a challenge and requires user interactionWeb API can be accessed by any client software; web scraping can require a web browser and user interactionIn the following section, the web scraping basics are introduced.
Virtual earth cloud: a multi-cloud framework for enabling geosciences digital ecosystems
Published in International Journal of Digital Earth, 2023
Mattia Santoro, Paolo Mazzetti, Stefano Nativi
Several definitions exist for a Web service, essentially describing it as a service that is offered over the web, irrespective of the usage of specific protocols and message formats (Santoro et al. 2019; OASIS 2006; IBM 2020). The main difference between a Web Service and a Web API stems from their offering. A Web Service provides a service interface (i.e. an interface aimed at offering access to ‘high-level’ functionalities for end-users). A Web API offers a programming interface (i.e. a set of low-level functionalities that can be used and combined by software developers to deliver a higher-level service). Thus, Web Services and Web APIs differ at the design level but not necessarily at the technological level (Santoro et al. 2019).
Architecture and Governance of Digital Business Ecosystems: A Systematic Literature Review
Published in Information Systems Management, 2023
Abide Coskun-Setirek, Maria Carmela Annosi, William Hurst, Wilfred Dolfsma, Bedir Tekinerdogan
The integration and transmission strategy of an MDA model is related to multiple standards, such as meta-object facility (MOF), EXPRESS language, UML, Extensible Markup Language (XML), XML metadata interchange (XMI), the Web Ontology Language (OWL), and ATLAS Transformation Language (ATL) (Jardim-Goncalves et al., 2013). The integration strategy of SOA architectures is traditionally based on ESB, (Adi & Heripracoyo, 2018; Appio et al., 2018; Figay et al., 2012; Kuk & Janssen, 2013; Lombardi et al., 2020; Reforgiato Recupero et al., 2016). For web services, application program interfaces like Representational State Transfer Application Programming Interface (REST API), Simple Object Access Protocol (SOAP) interface, and Hypertext Transfer Protocol (HTTP)/WEB API are implemented. As the SLR authors also reported, these are supported by the architectural styles, and communication protocols and standards, such as REST (Aulkemeier et al., 2019; Autiosalo et al., 2021; Reforgiato Recupero et al., 2016), SOAP (Adi & Heripracoyo, 2018), HTTP (Adi & Heripracoyo, 2018; Autiosalo et al., 2021), Message Queuing Telemetry Transport (MQTT) (Lombardi et al., 2020), Open Messaging Interface (O-MI)/Open Data Format (O-DF) (Javed et al., 2020), Open Platform Communications Unified Architecture (OPC UA) (Autiosalo et al., 2021; Marmolejo-Saucedo, 2020), Security Assertion Markup Language (SAML) and OpenID Connect (Bazarhanova et al., 2020), XML (Adi & Heripracoyo, 2018; Jardim-Goncalves et al., 2013; Kannisto et al., 2018), Extensible Messaging and Presence Protocol (XMPP) (Shamsuzzoha et al., 2017), and OWL (Jardim-Goncalves et al., 2013). The most common protocols are SOAP and HTTP for Client/Server, MQTT for Pub/Sub, and O-MI/O-DF for both Pub/Sub and Client/Server architectural patterns.