[雙語翻譯]外文翻譯--restful架構(gòu)應(yīng)用程序的物聯(lián)網(wǎng)框架及其在智慧城市中的試驗(yàn)

1、8400 英文單詞， 英文單詞，4.7 萬英文字符，中文 萬英文字符，中文 1.4 萬字 萬字文獻(xiàn)出處 文獻(xiàn)出處: Paganelli F, Turchi S, Giuli D. A Web of Things Framework for RESTful Applications and Its Experimentation in a Smart City[J]. IEEE Systems Journal, 2017, 10(4):1

2、412-1423.A Web of Things Framework for RESTful Applications and Its Experimentation in a Smart CityFederica Paganelli, Member, IEEE, Stefano Turchi, and Dino GiuliAbstract—The Web of Things is an active research field wh

3、ich aims at promoting the easy access and handling of smart things’ digital representations through the adoption of Web standards and technologies. While huge research and development efforts have been spent on lower lev

4、el networks and software technologies, it has been recognized that little experience exists instead in modeling and building applications for the Web of Things. Although several works have proposed Representational State

5、 Transfer (REST) inspired approaches for the Web of Things, a main limitation is that poor support is provided to web developers for speeding up the development of Web of Things applications while taking full advantage o

6、f REST benefits. In this paper, we propose a framework which supports developers in modeling smart things as web resources, exposing them through RESTful Application Programming Interfaces (APIs) and developing applicati

7、ons on top of them. The framework consists of a Web Resource information model, a middleware, and tools for developing and publishing smart things’ digital representations on the Web. We discuss the framework compliance

8、with REST guidelines and its major implementation choices. Finally, we report on our test activities carried out within the SmartSantander European Project to evaluate the use and proficiency of our framework in a smart

9、city scenario.Index Terms—Internet of things (IoT), representational state transfer (REST), sensors, smart city, smart things, web, web of things, web services.I. INTRODUCTIONTHE WEB OF Things is an active research area

10、that focuses on the specific challenge of making smart things accessi-ble and manageable through open Web standards. This vision is correlated with the broader Internet of Things (IoT) research area aiming at enabling co

11、mmunication with and among smart objects, leveraging Internet standards and technologies [1].As argued by the European Expert Group on Services in the Future Internet [2], huge research and development efforts have focus

12、ed on lower level networks and software technologies, while “there is currently little experience with building applications for this new, emerging ecosystem of IP-enabled devices and objects.” As the Web facilitated bot

13、h application development and use for the traditional Internet, it is now expected to “unleash the potential of the IoT by making it accessible and programmable by developers who are not necessarily experts in ubiquit

14、ous computing” [2].The Web of Things is expected to ease the access to smart things’ capabilities and promote novel value-added services based on the combination of traditional web resources with those representing entit

15、ies from the physical world (smart things, sensors, appliances, etc.) [3]. This has the big advantage of allowing the integration of smart things with the impressive amount of information resources and services already o

16、n the Web, as well as exploiting available technologies and best practices for web resource publishing and management.building large-scale distributed hypermedia systems. By the REST vision, data sets and objects handled

17、 by client–server application logic are modeled as resources. REST key principles are fivefold [12].1) URIs as resource identifiers. Resources are exposed by servers through URIs. Since URIs belong to a global addressing

18、 space, resources identified with URIs have a global scope.2) Uniform interface. The interaction with the resource is fully expressed with four primitives, i.e., create, read, update, and delete. These operations can be

19、 mapped onto HTTP methods: GET reads the resource state, PUT updates the resource state, DELETE deletes a resource, and POST extends a resource by creating a child resource.3) Self-descriptive messages. Each message cont

20、ains the information required for its management.4) Stateless interactions. Each request from client to server must contain the information required to fully understand it and is independent of any previous request.5) Hy

21、permedia As the Engine Of Application State (HA- TEOAS). A hypermedia system is characterized by participants transferring resource representations that contain links; the client can progress to the next step in the inte

22、raction by choosing one of these links [13].Historically, two styles opposed in the Web services field: Service-Oriented Architecture (SOA) and Resource-Oriented Architecture (ROA), i.e., WS-* and REST. Pautasso et al.

23、 [14] compare RESTful and WSDL/SOAP-based Web services, using architectural principles and decisions. The authors conclude that RESTful services are more suited for tactical ad hoc integration over the Web (à la Mas

24、hup). Adamczyk et al. [11] evaluated some key questions regarding the real and perceived distinctions between the two styles and carried out a thorough analysis of Web services exposed by four repositories:1) xmethods.ne

25、t; 2) webservicex.net; 3) webservicelist.com; and 4) programmableweb.com reporting a very fast-pace growth of REST popularity. Moreover, in a study led in 2012 by Guinard et al. [7] involving 69 novice developers in im-p

26、lementing IoT client applications exploiting WS-? and REST approaches, results reported that REST is statistically significantly easier and faster to learn than WS-? . In addition, a considerable number of volunteers agr

27、eed that REST was more suited for Web applications requiring to integrate Web content: “[for] Web Mashups, REST services compose easily.”Although RESTful APIs are deemed to be relatively simple, developing RESTful system

28、s is difficult, and existing frameworks fail to support developers in conforming to REST constraints [10], [11]. The analysis provided by Zuzak and Shreier [10] highlights some weaknesses of existing general-purpose REST

29、 frameworks, such as the lack of structural and behavioral models for resource types, poor support of flexible mapping between resource representations and stored data entities, and the lack of support for scripting func

30、tions for read–write access to the application state at the client side. Adamczyk et al. [11] argue that current frameworks do not support well the “hypermedia constraint” or HATEOAS principle, and most of them do not fu

31、lly support HTTP caching.B. Middleware and Frameworks for the Web of ThingsZeng et al. provide a survey on research works in the WoT domain [8], where they highlight two main analysis criteria: the approach for integrati