China
Africa
Explore chapters and articles related to this topic
XML-Based Tools and Processes
Published in Cliff Wootton, Developing Quality Metadata, 2009
Binary XML, or Binary eXtensible Markup Language, describes any technique for encoding an XML document in a binary data format. A binary XML format reduces the verbosity and complexity of parsing but also gets in the way of casual text editing. The conversion between source and binary needs to be simple and lossless. On the plus side, a binary format can be accessed randomly and is easier to index.
Intelligent Sensor Interfaces and Data Format
Published in Fei Hu, Qi Hao, Intelligent Sensor Networks, 2012
Konstantin Mikhaylov, Joni Jamsa, Mika Luimula, Jouni Tervonen, Ville Autio
Binary XML is a set of specifications that defines the compact representation of XML in a binary format. At present, three binary XML compression formats have been introduced, although none of them has yet been widely adopted or accepted as a de facto standard [33].
Service-oriented invisible numerical control application: architecture, implementation, and test
Published in International Journal of Production Research, 2022
Lisi Liu, Yingxue Yao, Jianguang Li
A service exposes capabilities via a set of endpoints. An endpoint consists of three elements: address, binding, and contract (Lowy and Montgomery 2016). Specifically, the address points out its location which is often identified by uniform resources identifier (URI) or uniform resources location (URL). Binding points out transport protocol (e.g. HTTP, HTTPS, TCP, AMQP, etc.), encoding style (e.g. Text, Binary, XML, JSON, etc.), and other information corresponding to the message style. Contract can be broken down into a set of service capabilities, each expressing an operation (or method) offered by a service (Erl et al. 2017). Contract versioning allows developers to roll out new service features that involve contract changes and at the same time provide backward compatibility for service consumers who are still using prior contracts (Richards 2016). In a nutshell, services are independent, high-interoperable, loosely coupled, and backward-compatible. For instance, a service developed by .NET assembly and a service written in Java can work together by using HTTP/HTTPS as the transport protocol and XML as the message format, as if they were both developed by .NET assembly. Therefore, today, everything tends to shift to service. For instance, the OPC Foundation has released a service-oriented generation of OPC specifications called OPC Unified Architecture (OPC UA) (Mahnke, Leitner, and Damm 2009). OPC UA is the evolution of COM/DCOM-based classical OPC interfaces.
GEOSS Platform data content and use
Published in International Journal of Digital Earth, 2023
Enrico Boldrini, Stefano Nativi, Jiri Hradec, Mattia Santoro, Paolo Mazzetti, Max Craglia
The fundamental type of information is the Dataset object (i.e. resource record), which is shared on the GEOSS Platform by the GEOSS data Providers. These objects were utilized for the analysis of the GEOSS Platform content. According to the ISO standard technical committee (ISO 2003) on geomatics, Dataset can be defined as an ‘identifiable collection of data’ representing an observation of the Earth (e.g. in-situ or remote observation), or a model output (e.g. a simulation or forecast). As depicted in Figure 2, the GEOSS dataset resource type is characterized by a content and a metadata record: Content, containing the actual collected data, that is to say the values of the physical observation (or digital simulation) encoded using a different approach, depending on the data Provider interoperability policy (e.g. binary, XML, CSV, etc.).Metadata, a description of the dataset, composed of different metadata elements (i.e. distinct units of metadata, each documenting a specific aspect of the dataset). Presently, the GEOSS Platform provides different metadata elements (in keeping with the ISO 19115 model); for the purpose of this study, only a subset of significant elements was analyzed. The examination focused on the following metadata elements: [Mandatory] Dataset provider identifies the GEOSS dataset Provider – i.e. the organization held responsible for dataset sharing in GEOSS.[Optional] Dataset cited organization identifies an organization contributing to the dataset, under distinct roles (i.e. originator, publisher, contributor).[Optional] Dataset spatial extent identifies the geographic area covered by the dataset ‘content’ (i.e. the spatial geometry defining the data geographic position and shape).[Optional] Dataset temporal extent identifies the temporal period covered by the dataset ‘content’ (i.e. the temporal geometry defining the data temporal occurrence and duration).[Optional] Dataset keyword: identifies the commonly used word(s), formalized word(s), or phrase(s) used to describe the dataset.[Optional] Dataset keyword thesaurus identifies the source of utilized keywords.[Optional] Dataset title: defines the name by which the dataset is known.[Optional] Dataset abstract: defines a brief narrative summary of the dataset content.