Open resource discovery of entity types
The disclosure generally describes methods, software, and systems for open resource discovery protocol describing entity types. An identifier of a first entity type is received. The first entity type defines a relation between an application programming interface (API) and event information. A reference for the first entity type is generated based on the identifier of the first entity type. The reference links the first entity type to the API. A description of the first entity type is provided for storage using the reference for the first entity type. the description includes a structure of an underlying data model. A request to provide the first entity type based on the description of the first entity type is received. The first entity type is provided using an exposed API and the reference for the first entity type.
1 . A computer-implemented method comprising:
receiving, by one or more processors, an identifier of a first entity type, the first entity type defining a relation between an application programming interface (API) and event information;
generating, by the one or more processors, based on the identifier of the first entity type, a reference for the first entity type, the reference linking the first entity type to the API;
providing, by the one or more processors, a description of the first entity type for storage using the reference for the first entity type, the description comprising a structure of an underlying data model;
receiving, by the one or more processors, a request to provide the first entity type based on the description of the first entity type; and
in response to the received request, providing, by the one or more processors, the first entity type using an exposed API and the reference for the first entity type, wherein the exposed API comprises an adapted version of the API extended to provide a communication protocol comprising navigation to the first entity type.
2 . The computer-implemented method of claim 1 , further comprising:
generating, by the one or more processors, a mapping of the first entity type to a second entity type.
3 . The computer-implemented method of claim 2 , wherein the mapping comprises information indicative of local data models that are supported by the first entity type and the second entity type.
4 . The computer-implemented method of claim 2 , further comprising:
deriving, by the one or more processors, a data flow based on the mapping of the first entity type to the second entity type.
5 . The computer-implemented method of claim 2 , wherein the first entity type comprises a root entity and the second entity type comprises a sub-entity.
6 . The computer-implemented method of claim 1 , wherein the underlying data model is stored as metadata information.
7 . The computer-implemented method of claim 1 , wherein the reference comprises external files or locations.
8 . The computer-implemented method of claim 1 , wherein the description comprises properties of the first entity type and data types the first entity type.
9 . A computer-implemented system comprising:
a memory storing application programming interface (API) information; and a server performing operations comprising:
receiving an identifier of a first entity type, the first entity type defining a relation between an application programming interface (API) and event information;
generating based on the identifier of the first entity type, a reference for the first entity type, the reference linking the first entity type to the API;
providing a description of the first entity type for storage using the reference for the first entity type, the description comprising a structure of an underlying data model;
receiving a request to provide the first entity type based on the description of the first entity type; and
in response to the received request, providing the first entity type using an exposed API and the reference for the first entity type, wherein the exposed API comprises an adapted version of the API extended to provide a communication protocol comprising navigation to the first entity type.
10 . The computer-implemented system of claim 9 , wherein the operations further comprise:
generating a mapping of the first entity type to a second entity type.
11 . The computer-implemented system of claim 10 , wherein the mapping comprises information indicative of local data models that are supported by the first entity type and the second entity type.
12 . The computer-implemented system of claim 10 , wherein the operations further comprise:
deriving a data flow based on the mapping of the first entity type to the second entity type.
13 . The computer-implemented system of claim 10 , wherein the first entity type comprises a root entity and the second entity type comprises a sub-entity.
14 . The computer-implemented system of claim 9 , wherein the underlying data model is stored as metadata information.
15 . The computer-implemented system of claim 9 , wherein the reference comprises external files or locations.
16 . The computer-implemented system of claim 9 , wherein the description comprises properties of the first entity type and data types the first entity type.
17 . A non-transitory computer-readable media encoded with a computer program, the computer program comprising instructions that when executed by one or more computers cause the one or more computers to perform operations comprising:
receiving an identifier of a first entity type, the first entity type defining a relation between an application programming interface (API) and event information;
generating based on the identifier of the first entity type, a reference for the first entity type, the reference linking the first entity type to the API;
providing a description of the first entity type for storage using the reference for the first entity type, the description comprising a structure of an underlying data model;
receiving a request to provide the first entity type based on the description of the first entity type; and
in response to the received request, providing the first entity type using an exposed API and the reference for the first entity type, wherein the exposed API comprises an adapted version of the API extended to provide a communication protocol comprising navigation to the first entity type.
18 . The non-transitory computer-readable media of claim 17 , wherein the operations further comprise:
generating a mapping of the first entity type to a second entity type, wherein the mapping comprises information indicative of local data models that are supported by the first entity type and the second entity type.
19 . The non-transitory computer-readable media of claim 17 , wherein the underlying data model is stored as metadata information.
20 . The non-transitory computer-readable media of claim 17 , wherein the description comprises properties of the first entity type and data types the first entity type.