China
Africa
Explore chapters and articles related to this topic
State of the Art in Smart Homes and Buildings
Published in Richard Zurawski, Industrial Communication Technology Handbook, 2017
Wolfgang Kastner, Lukas Krammer, Andreas Fernbach
DPWS does not offer a metamodel that can be used for information modeling. As the name implies, it is a profile that defines a subset of WS-* standards for the usage on resource constraint devices. For information modeling, DPWS does not come with a custom metamodeling language. For representing devices, process control variables, process data points, or the topology of a BAS XML schema can be used. XML schema is a metamodel that allows to define the structure of XML documents. It uses basic types, which are common in many other information modeling languages like xs:string, xs:decimal, xs:integer, xs:float, xs:float, xs:date, and xs:time, and further some XML-schema-specific basic types, which are QName, anyURI, language, ID, and IDREF. Basic types are neither allowed to contain subelements nor attributes. Furthermore, there are complex types, which may contain nested elements and attributes. It is possible to define value restrictions on XML types and also some requirements regarding the structure.
Extensible Markup Language Basics
Published in Giovanni Bartolomeo, Tatiana Kováčiková, Identification and Management of Distributed Data: NGN, Content-Centric Networks and the Web, 2016
Giovanni Bartolomeo, Tatiana Kováčiková
To avoid mixing elements from different sources that could potentially have the same name, namespaces are introduced. In this way elements’ and attributes’ names are pairs (namespace, localname). The namespace is in the form of a Uniform Resource Identifier (URI) with a prefix used to avoid repeating the URI throughout the whole XML document. The prefix is bound to the namespace URI through a declaration that appears in the document in the form of an attribute, either on the top element or another element inside the document (in the latter case the namespace has a scope limited to the element and any subelements appearing hierarchically under that element). The pair (namespace, localname) is referred to as the fully qualified name (FQN) and is expressed in the form namespace:localname
Intelligent Sensor Systems
Published in David C. Swanson, ®, 2011
A better approach is to use an existing extensible markup language (XML) schema or create/publish a specific XML schema to organize all the sensor data for use by web pages and automated network programs called ebots (electronic robot agents or an unattended network service). An XML schema is a master document template that defines all the structured elements, their types (numerical, text, etc.), and can even enumerate the allowable ranges for each element and whether the element is required or optional [17]. The sensor manifest describing all the data and features the sensor offers can be part of this XML schema. A person can read the schema to see what is available, translate the data to map to another XML schema if desired, or write an ebot program to automatically harvest the sensor XML data. In addition, the sensor “thin server” can be programmed to connect to another web node and send its data periodically as an XML-formatted message. We use the term “thin” server because the sensor has very limited services compared to a typical PC server. It is really an embedded computer with sensor(s) on one end and communication ports on the other end. The key step here is to organize the sensor data using XML and publish the schema document. The sensor web page can be tied directly to the XML data so that gauges and dials can have their graphics respond “live” to the sensor data. Using the XML data from the sensor, another web page combining many sensors together (a dashboard) can easily integrate the XML from each sensor and update it continuously.
Design, modelling, optimisation and validation of condition-based maintenance in IoT enabled hybrid flow shop
Published in International Journal of Computer Integrated Manufacturing, 2022
Badri Narayanan, Muthusamy Sreekumar
Communication protocol is one of the critical factors to be considered in the design and realisation of an IoT-enabled flow shop, which allows the flow shop to collect data from each machine and organise it in a database for further analysis. Communication among machines is achieved through a standard protocol called open platform communication (OPC), as shown in Figure 2. The interaction between various machines and manufacturing execution systems (MES) occurs through Extensible Mark-up Language (XML). XML provides readable formats to both humans and machines. In addition, the industrial control system protocol interfaces the machines with an industrial PC in place of Human Machine Interface (HMI), Programmable Logic Controller (PLC) and Supervisory Control and Data Acquisition (SCADA).
An investigation on adaptive HTTP media streaming Quality-of-Experience (QoE) and agility using cloud media services
Published in International Journal of Computers and Applications, 2021
Selvaraj Kesavan, E. Saravana Kumar, Abhishek Kumar, K. Vengatesan
The authors [10,11] proposed client driven rate adaptation algorithm to deliver the media contents over HTTP and minimize the end to end transport delay by selecting appropriate bit rate at right time. The evaluation performed on conventional client–server and cloud-based client-server environment. However, experiment mainly concentrate of algorithm performance and not considering the performance improvement due to cloud-based service and architecture. There are two types of web services widely used in the industry: SOAP web services [12] and RESTful Web services [13]. SOAP is XML-based protocol used to communicate between two applications and it is independent to programing language, platform. RESTful web services are an architectural design and uses HTTP for communication. RESTful architecture permits to use different data format such as Text, HTML, XML and JSON. REST relies on addressability, uniform interface and statelessness. The web services in multimedia streaming allows applications to communicate with other applications or platforms using exposed control and data interfaces.
Application of the Internet of Things in the textile industry
Published in Textile Progress, 2019
Hitesh Manglani, George L. Hodge, William Oxenham
Data-exchange format-related standards ensure inter-operability in real industrial environments, interconnecting heterogeneous legacy hardware devices such as robots and Programmable Logic Controllers (PLCs), and software applications (for example, Supervisory Control and Data Acquisition (SCADA), Manufacturing Execution Systems (MES), and databases) [32]. These standards help determine data format to allow a seamless flow of data from enterprise resource planning (ERP) to MES and MES to SCADA and are thus mostly based on eXtensible Markup Language (XML). XML is a file format used to create standard information formats and to share both the format and the data on the World Wide Web, intranets, and elsewhere using standard ASCII text. The emergence of data formats for industrial automation, similar to the worldwide web, is key to the integration of the internet and industry to create IoT. Security-related standards include IEC 62443, which is network and system security standard for industrial-process measurement and control, ISO/IEC 27000 family is the standard related to information security management systems, and VDI/VDE 2182 is the standard for security in industrial automation established by the Association of German Engineers.