Open Data Protocol

Abstract: The disclosure generally describes computer-implemented methods, software, and systems for allowing provisioning of open data protocol (OData) services on top of a generic interaction layer (GenIL). One computer-implemented method includes receiving an OData-compliant request for data, determining a GenIL data provider to receive the OData-compliant request for data, determining the memory location of the data, requesting the data from the determined memory location, receiving the requested data from the determined memory location, converting, using at least one computer, the received data into an OData-compliant format, rendering an OData-compliant response, and transmitting the OData-compliant response.

Abstract: The World-Wide Sensor Web is generating tremendous amount of real-time sensor data streams and will enable scientists to observe phenomena that are previously unobservable. As the concept of sensor web is to connect all the sensors and their data to achieve shared goals, improving the openness and accessibility of sensor data is important. The Open Geospatial Consortium Sensor Observation Service (SOS) defines standard web service protocols for sharing sensor data online in an interoperable manner. However, SOS has a relatively weak ecosystem, which makes it difficult to build and consume, and it only supports predefined queries. On the other hand, the OASIS1 Open Data Protocol (OData) has a strong ecosystem and flexible query functions. But the soft-typing approach of OData requires it to have a commonly agreed data model to be interoperable. As we argue that the two standards can benefit from each other, we propose a sensor data mediator solution and define an SOS entity data model for OData (SOS-OData)...

Abstract: The Open Data Protocol (OData) is a data access protocol that is based on the REST principles. It is built upon existing and well-known technologies such as HTTP, AtomPub and JSON. OData is already widely-used in the industry. Many IT companies provide OData interfaces for their applications. The structure of the data that is provided by an OData service is described with the Conceptual Schema Definition Language (CSDL). To make this data available for the integration with the Semantic Web, we propose to semantically annotate CSDL-documents. This extension of CSDL allows the definition of mappings from the underlying Entity Data Model (EDM) to RDF graphs which is a first step towards the implementation of a SPARQL endpoint on top of existing OData services. Based on the OData interfaces of existing enterprise resource planning (ERP) systems, it is possible to realize a SPARQL endpoint for those systems which can lead to a great simplification in the retrieval of data.

Abstract: Techniques for providing an error log include establishing, by a hub computing system, a connection with a back-end computing system, the back-end computing system executing a first computer-implemented programming language; receiving, at the hub computing system, a request for an error log from an Open Data Protocol (OData) application that resides on a mobile communications device, the mobile communications device executing a second computer-implemented programming language different than the first computer-implemented programming language, and the error log including error log entries associated with a runtime processing of a data model; registering, on the hub computing system, the error log as an OData service configured to be provided over an OData channel between the hub computing system and the mobile communications device; and providing, by the hub computing system, the error log to the OData application as the OData service over the OData channel.