Abstract: The disclosure generally describes methods, software, and systems for using open APIs. API and event information is received from plural API providers. The API and event information for each API provider is received in a format specific to the API provider. An open API format version of the API and event information is created for the API and event information of each API provider. The open API format version is stored in an open API format that provides a common ontology for expressing information about APIs and events available from the plural API providers. The open API format version of the API and event information is published.

Abstract: The present disclosure relates to computer-implemented methods and computer systems for providing user-friendly and understandable presentations of Open Data (OData) Protocol resources through an automatic translation and modification process. The present disclosure provides a user interface tool for presenting and browsing OData fees that can provide a visualization of an OData feed structure to users in an otherwise unavailable format. In particular, developers can view and modify resources outside of the underlying format in which such OData feeds are traditionally presented. The user interface tool can provide an out-of-box user interface with which a developer can view and modify resources associated with a feed, browse related entity sets, set filters, and perform other operations. In essence, the user interface tool can decrease user's efforts and difficult in understanding particular OData feeds and the entities associated therewith.

Abstract: One example is related to computer-implemented methods, computer-readable media and computer systems for interacting with resources exchanged using Open Data Protocol. A client computer system receives multiple resources defined according to a first data structure from a server computer system connected to the client computer system through a data network in response to an OData request for the resources. The resources are defined according to a first data structure. A resource is associated with a boundary that specifies resource operations performable on the resource. The resource is translated from the first data structure to a second data structure different from the first data structure, where, in the second data structure, the identified resource is editable to perform the resource operations on the identified resource. The identified resource is displayed in a user interface according to the second data structure and the resource operations that are performable on the identified resource.