Smart Transducer Web Services Based on the IEEE 1451.0 Standard

Exchanging and sharing scientific results are essential for researchers in the field of computational modelling. BioModels.net defines agreed-upon standards for model curation. A fundamental one, MIRIAM (Minimum Information Requested in the Annotation of Models), standardises the annotation and curation process of quantitative models in biology. To support this standard, MIRIAM Resources maintains a set of standard data types for annotating models, and provides services for manipulating these annotations. Furthermore, BioModels.net creates controlled vocabularies, such as SBO (Systems Biology Ontology) which strictly indexes, defines and links terms used in Systems Biology. Finally, BioModels Database provides a free, centralised, publicly accessible database for storing, searching and retrieving curated and annotated computational models. Each resource provides a web interface to submit, search, retrieve and display its data. In addition, the BioModels.net team provides a set of Web Services which allows the community to programmatically access the resources. A user is then able to perform remote queries, such as retrieving a model and resolving all its MIRIAM Annotations, as well as getting the details about the associated SBO terms. These web services use established standards. Communications rely on SOAP (Simple Object Access Protocol) messages and the available queries are described in a WSDL (Web Services Description Language) file. Several libraries are provided in order to simplify the development of client software. BioModels.net Web Services make one step further for the researchers to simulate and understand the entirety of a biological system, by allowing them to retrieve biological models in their own tool, combine queries in workflows and efficiently analyse models.

In this chapter, we provide an overview of the Web services technology, together with the set of standard specifications for Web services transactions. The core components of the Web services technology include eXtensible Markup Language (XML), HyperText Transfer Protocol (HTTP), Simple Object Access Protocol (SOAP), and Web Services Description Language (WSDL). Both SOAP and WSDL are based on XML. All these protocols and languages have the characteristic of strong extensibility, which lays a solid foundation for the success of the Web services technology. Due to the extensibility design, the protocols specified in the Web services transactions standards can be plugged into the Web services core seamlessly to provide the additional coordination needed for business transactions. Furthermore, we point out the need to protect the business transactions from the hardware failures and malicious faults, and for more robust coordination for Web services transactions.

Simple object access protocol (SOAP) is the communication protocol used by web services to communicate between systems. Since SOAP messages have the ability to bypass firewalls and directly get processed by web servers, their security is critical to the security of the web servers. Secure transit of SOAP messages plays a critical role for the applicability of web services. At present, internet users authenticate themselves using credential are vulnerable to security threats in presence of active attackers. This imposes a burden on users to manage their credentials in different ways. Along with the thorough development and application for web services, the security of it has taken people's attention more and more. While web services security (WSS) can exchange safe SOAP message and enhance the security of web services, it will also have certain influence to the performance of web services. This paper explore the security vulnerability of SOAP message transaction and taking advantage of the existing technologies and solutions related to SOAP and web services, we developing a highly developed security model. This model is useful for solving the problem between security and performance contradiction.

Web service is a technological solution for software interoperability that supports the seamless integration of diverse applications. In the vision of web service architecture, web services are described by the Web Service Description Language (WSDL), discovered through Universal Description, Discovery and Integration (UDDI) and communicate by the Simple Object Access Protocol (SOAP). Such a divination has never been fully accomplished yet. Although it was criticized that WSDL only has a syntactic definition of web services, but was not semantic, prior initiatives in semantic web services did not establish a correct methodology to resolve the problem. This paper examines the distinction and relationship between the syntactic and semantic definitions for web services that characterize different purposes in service computation. Further, this paper proposes that the semantics of web service are neutral and independent from the service interface definition, data types and platform. Such a conclusion can be a universal law in software engineering and service computing. Several use cases in the GIScience application are examined in this paper, while the formalization of geospatial services needs to be constructed by the GIScience community towards a comprehensive ontology of the conceptual definitions and relationships for geospatial computation. Advancements in semantic web services research will happen in domain science applications.

Web services via wireless technologies, mobile services (M-services), HTTP, and XML have become important for conducting business. W3C XML Protocol Working Group has been developing standard techniques such as Web Services
\nDescription Language (WSDL), simple object access protocol
\n(SOAP), universal description discovery and integration (UDDI). However, at this stage, there is no standard technique for access control in M-services.
\nThis paper describes a secure and flexible access control scheme and protocol for M-services based on role based access control (RBAC). The access control architecture involves a Trusted Credential Center (TCC), a Trusted Authentication and Registration Center (TARC) and a secure ticket based mechanism for service access. Users and service providers register with the TARC and are authenticated. Based on this, tickets are issued by the
\nTCC to users. Tickets carry authorization information needed
\nfor the requested services. In particular, we are able to specify access control polices based on roles. The protocols between the various entities in the model are protected using appropriate security mechanisms such as signatures which are used to verify correctness of the requested service, as well as to direct billing information to the appropriate user. Our architecture supports efficient
\nauthentication of users and service providers over different
\ndomains and provides a secure access model for services to users. Our model is also able to support anonymity of users. Only the TARC is able to identify misbehaving users. We believe that the proposed architecture forms a good basis for achieving a secure and flexible M-service system.

A Web service is a software system that supports interoperable application-to-application interactions over a network. Web services are based on a set of XML standards such as Universal Description, Discovery and Integration (UDDI), Web Services Description Language (WSDL), and Simple Object Access Protocol (SOAP). Recently, there have been increasing demands and discussions about Web services privacy technologies in the industry and research community. To enable privacy protection for Web service consumers across multiple domains and services, the World Wide Web Consortium (W3C) published a document called “Web Services Architecture (WSA) Requirements” that defines some fundamental privacy requirements for Web services. However, no comprehensive solutions to the various privacy issues have been so far defined. For these reasons, this chapter will focus on privacy technologies by first discussing the main privacy issues in WSA and related protocols. Then, this chapter illustrates the standardization efforts going on in the context of privacy for Web services and proposes different technical approaches to tackle the privacy issues.

The advent of Web Services (WS) has signaled a true revolution in the way service-oriented computing and remote procedure invocation over the Web are conducted. Web Services comprise of a set of loosely coupled specifications to coordinate process execution from distance, based on common and widely accepted Web protocols such as HTTP, FTP, and XML, and therefore, providing increased development flexibility. Since the WS Framework was built on top of those protocols, Web Services have been widely acclaimed by the Web development community and paradoxically; they have marked one of the few examples in the history of computer protocols where a global consensus has been reached. The Web Service framework consists of essentially three basic components: 1. The Web Service Description Language (WSDL), a language that allows formal functional characterization of the provided functionalities; 2. The Simple Object Access Protocol (simply SOAP from its version 1.2), a protocol that defines the format of the information interchange; and 3. The UDDI (Universal Description, Discovery and Integration) is a catalog of Web Service descriptions. All three of these components are specified using XML markup. The elegance of the WS architecture lies in the fact that every WS transaction is taking place over established Web protocols such as HTTP and FTP. As remarked in Ballinger (2003, p. 5): “A Web Service is an application logic that is accessible using Internet standards.” This very fact has accounted for the rapid and universal adoption of Web Services. This work is organized as follows: First, a review of underlying technologies and tools is presented. Consequently, existing techniques for design methodologies are described. Next, an overview of storage and retrieval techniques for Web Services is given followed by real-world applications of Web Services. We conclude with open issues and discussion.

Chapter 11 - Web Services

Softwareengineersareincreasinglyadoptingserviceorientedar-chitectures (SOAs) for the automation of business processes andthe integration of IT systems, both within and across organisa-tional boundaries. These service oriented architectures frequentlyrely on web service standards, such as the Web Service Descrip-tion Language (WSDL) [5] and the Simple Object Access Protocol(SOAP) [10] for the implementation of service invocations acrossmachine boundaries.The combination of several web services into a more complexweb service is a crucial building block for service oriented archi-tectures. Peltz refers to such compositions that integrate the in-vocation of two or more services into a more complex executableworkflow as web service orchestration and contrasts this with webservice choreography, which tracks message exchanges betweendifferent autonomous domains [13]. Web service orchestration isappealing as it facilitates compositionality and reuse of the compo-nents that implement these services without necessarily having todeploy these services locally.Web service orchestration is supported by the Business ProcessExecution Language for Web Services (BPEL) [1]. BPEL emergedthrough consolidation of earlier work on IBM’s Web Service FlowLanguage (WSFL) [11] and XLANG [14] developed by Microsoft.BPELwas proposedas astandardby Microsoft, IBM,Siebel, BEA

Web services are a technology that has gained enormous popularity in the industry over the past two years. Web services introduce a new paradigm in the field of distribute computing where the emphasis is on the protocol that’s used rather than how the technology is implemented. The main advantage Web services have over other technologies that support distributed computing is that Web services are based on open standards such as Extensible Markup Language (XML), Simple Object Access Protocol (SOAP), Web Services Description Language (WSDL), Hypertext Transfer Protocol (HTTP), and so on, and hence are widely accepted in the industry. More than any other distributed computing technologies in the past, Web services promote interoperability between heterogeneous and incompatible systems.

Standards provide critical benefits across a wide variety of contexts, including safety and health, environmental protection, and quality of products and services. However, while these benefits are generally acknowledged, estimating the social and economic value of standards and determining how specific entities and activities influence their development require careful analysis. In October of 2018, the National Institute of Standards and Technology (NIST) asked the RAND Corporation to estimate the benefit of NIST’s research contributing to particular fire safety standards. The original objectives of the project were to (1) document the role of the NIST in the standards development process, (2) estimate the value these standards provide to society, and (3) thereby inform the economic value of NIST’s contribution to these standards. This report presents results for the first two objectives. Given that NIST’s contribution is one of several inputs combining to create these standards, NIST’s share of the credit for their value could not be quantified. Our analysis focused on case studies in standards for home smoke alarms and for protecting structures at the wildland-urban interface (WUI). Our analysis draws on a wide variety of qualitative and quantitative methods to holistically describe the impacts of these standards and NIST’s role in their development. The intended audience of this report includes those who work on fire safety research, fire safety standards, building codes, and technology transfer. The conclusions presented here may also be of interest for broader resource allocation and federal budget justification purposes. Finally, this report was written to be accessible to any interested members of the general public.

The Clean Air Mercury Rule (CAMR) which was published in the Federal Register on May 18, 2005, requires that calibration of mercury continuous emissions monitors (CEMs) be performed with NIST-traceable standards. Western Research Institute (WRI) is working closely with the Electric Power Research Institute (EPRI), the National Institute of Standards and Technology (NIST), and the Environmental Protection Agency (EPA) to facilitate the development of the experimental criteria for a NIST traceability protocol for dynamic elemental mercury vapor generators. The traceability protocol will be written by EPA. Traceability will be based on the actual analysis of the output of each calibration unit at several concentration levels ranging from about 2-40 ug/m{sup 3}, and this analysis will be directly traceable to analyses by NIST using isotope dilution inductively coupled plasma/mass spectrometry (ID ICP/MS) through a chain of analyses linking the calibration unit in the power plant to the NIST ID ICP/MS. Prior to this project, NIST did not provide a recommended mercury vapor pressure equation or list mercury vapor pressure in its vapor pressure database. The NIST Physical and Chemical Properties Division in Boulder, Colorado was subcontracted under this project to study the issue in detail and to recommend a mercury vapormore » pressure equation that the vendors of mercury vapor pressure calibration units can use to calculate the elemental mercury vapor concentration in an equilibrium chamber at a particular temperature. As part of this study, a preliminary evaluation of calibration units from five vendors was made. The work was performed by NIST in Gaithersburg, MD and Joe Rovani from WRI who traveled to NIST as a Visiting Scientist.« less

Chapter 7 - Writing SOAP Servers

With the advent of distributed technologies and related Integrated Development Environments (IDEs), business collaborations across the world irrespective of the platforms in which applications were built.The underlying technology is Web Services which is based on XML standard and the architecture is SOA (Service Oriented Architecture).Many SOA frameworks came in to existence.However, their primary focus is discovering, composition of services in order to make flexible service oriented distributed enterprise applications.Such systems without human expertise may be incomplete.To overcome this problem, this paper proposes techniques to collaborate services based software with human experts thus forming a knowledgeintensive and people centric web besides sharing and reusing software components in distributed environment.To achieve this, we propose a flexible and adaptive approach which facilitates software services and humans to collaborate using Web Services and its important standards like SOAP (Simple Object Access Protocol), WSDL (Web Services Description Language) and UDDI (Universal Description Discovery Integration).This kind of human centric enterprise web has far reaching implications and it can attract the human experts to participate in rendering their best possible services.Interaction monitoring techniques that are adaptive thus realizing standards based people-centric systems.

A Look at its Past Decade and a Gaze towards its Future. As the National Metrology Institute (NMI) for the United States, the National Institute of Standards and Technology (NIST), formerly the National Bureau of Standards, has provided measurement services, both calibrations and reference materials, for more than 100 years. Through these services, our customers have benefitted from our measurement capabilities and expertise in many areas, including amount of substance; dimensional metrology; electricity and magnetism; ionizing radiation; mass and related quantities; photometry and radiometry; thermodynamics; and time and frequency. NIST’s customers have also had access to some of the lowest measurement uncertainties available and a dependable way to establish traceability to the International System of Units (SI) [http://www.nist.gov/pml/wmd/metric/si-units.cfm].In response to the signing of the International Committee for Weights and Measures (CIPM) Mutual Recognition Arrangement (MRA), NIST first established an institution-wide quality system for the measurement services 10 years ago [http://www.bipm.org/en/cipm-mra/objectives.html]. NIST’s Quality System for Measurement Services has advanced the quality of service and measurements we provide our customers by fostering an environment in which NIST management and staff work towards continual improvement in the development and delivery of NIST measurement services. This paper describes NIST’s Quality System for the Measurement Services and its relevance to international standards of quality, such as the International Organization for Standardization and the International Electrotechnical Commission (ISO/IEC) 17025 standard and ISO Guide 34 [http://www.nist.gov/nistqs/]. It also provides a history of this quality system and a glimpse of future goals for improving its implementation.