Method and apparatus for providing API service and making API mash-up, and computer readable recording medium thereof

1. A method of providing an Application Program Interface (API) service, the method comprising:

generating meta-data for executing an API;

generating resource data for generating a mash-up of the API;

generating description data corresponding to the API, the meta-data, and the resource data;

generating an API package comprising the API, the meta-data, the resource data, and the description data; and

storing the API package in memory,

wherein the description data comprises information about one of components of the API package, a version of the API, and a library function for executing the API, and

wherein the generating the API package comprises:

analyzing an input/output data format of the API;

searching for another API package to perform the mash-up with the API package selectively on the basis of the input/output data format of the API; and

generating the mash-up by using the API package and the other API package,

wherein the analyzing the input/output data format of the API is performed using tagging information of the resource data.

2. The method of claim 1 , wherein the API comprises one of an open API and a local API.

3. The method of claim 1 , further comprising transmitting the API package to a package providing server or an apparatus for producing the mash-up of the API.

4. The method of claim 3 , wherein the meta-data comprises information about a communication protocol to communicate with the package providing server or the apparatus for producing the mash-up of the API, and information about a data format of the API.

5. The method of claim 4 , wherein the meta-data further comprises at least one of user account information and a user certification key for using the API.

6. The method of claim 1 , wherein the resource data comprises a configuration data of a user interface to generate the mash-up and a tagging information representing the input/output data format of the API.

7. The method of claim 6 , wherein the resource data further comprises information about an icon or a thumb nail for executing the mash-up of the API in the user interface.

8. The method of claim 1 , wherein the description data further comprises details about the meta-data and the resource data.

9. A method of generating an Application Program Interface (API) mash-up, the method comprising:

obtaining at least two API packages which respectively comprise an API, meta-data for executing the API, resource data for generating a mash-up of the API, and description data corresponding to the API, the meta-data, and the resource data;

extracting the API, the meta-data, and the resource data from each of the at least two API packages by using the description data;

generating a mash-up of the at least two API packages by using the API, the meta-data, and the resource data; and

storing the mash-up of the at least two API packages in memory,

wherein the description data comprises information about one of components of the API package, a version of the API, and a library function for executing the API, and

wherein the generating the mash-up of the at least two API packages comprises:

analyzing an input/output data format of the API;

searching for another API package to perform the mash-up with an API

package selectively on the basis of the input/output data format of the API;

and

generating the mash-up by using the API package and the other API package,

wherein the analyzing the input/output data format of the API is performed using tagging information of the resource data.

10. The method of claim 9 , wherein the API comprises one of an open API and a local API.

11. The method of claim 9 , wherein the obtaining of the API packages comprises:

receiving the at least two API packages from a package providing server or an apparatus for providing an API service.

12. The method of claim 11 , wherein the meta-data comprises information about a communication protocol to communicate with the package providing server or the apparatus for producing the API mash-up and information about a data format of the API.

13. The method of claim 12 , wherein the meta-data further comprises at least one of user account information and a user certification key for using the API.

14. The method of claim 9 , wherein the resource data comprises a configuration data of a user interface to generate the mash-up and a tagging information representing the input/output data format of the API.

15. The method of claim 9 , wherein the resource data further comprises information about an icon or a thumb nail for executing the mash-up of the API in the user interface.

16. The method of claim 9 , further comprising:

replacing one of the at least two API packages in the mash-up with another API package.

17. The method of claim 9 , further comprising:

adding another API package to the mash-up.

18. The method of claim 9 , further comprising:

removing a part of the API packages from the mash-up.

19. An apparatus for providing an Application Programming Interface (API) service, the apparatus comprising:

a meta-data generating unit which generates meta-data for executing an API;

a resource data generating unit which generates resource data for generating a mash-up of the API;

a description data generating unit which generates description data corresponding to the API, the meta-data, and the resource data; and

an API package generating unit which generates an API package comprising the API, the meta-data, the resource data, and the description data,

wherein the description data comprises information about one of components of the API package, a version of the API, and a library function for executing the API,

wherein the API package generating unit analyzes an input/output data format of the API, searches for another API package to perform the mash-up with the API package selectively on the basis of the input/output data format of the API, and generates the mash-up by using the API package and the other API package,

wherein the API package generating unit analyzes an input/output data format of the API by using tagging information of the resource data, and

wherein a processor configures at least one of the meta-data generating unit, the resource data generating unit, the description data generating unit, and the API package generating unit.

20. An apparatus for producing an Application Programming Interface (API) mash-up, the apparatus comprising:

an API package obtaining unit which obtains at least two API packages which respectively comprise an API, meta-data for executing the API, resource data for generating a mash-up of the API, and description data corresponding to the API, the meta-data, and the resource data;

a data extracting unit which extracts the API, the meta-data, and the resource data from each of the API packages by using the description data; and

a mash-up generating unit which generates a mash-up of the API packages by using the API, the meta-data, and the resource data,

wherein the description data comprises information about one of components of the API package, a version of the API, and a library function for executing the API,

wherein the mash-up generating unit analyzes an input/output data format of the API, searches for another API package to perform the mash-up of the API packages selectively on the basis of the input/output data format of the API, and generates the mash-up by using the API package and the other API package,

wherein the mash-up generating unit analyzes an input/output data format of the API by using tagging information of the resource data, and

wherein a processor configures at least one of the API package obtaining unit, the data extracting unit, and the mash-up generating unit.

21. The apparatus for producing an API mash-up according to claim 20 , the apparatus further comprising:

a package download unit which downloads the API packages from a service provider or a server of a specified location; and

a storing unit which stores the downloaded API packages, wherein

the API package obtaining unit obtains the at least two API packages from the storing unit.

22. A non-transitory computer-readable recording medium having embodied thereon a program for executing a method of providing an Application Programming Interface (API) service, the method comprising:

generating meta-data for executing an API;

generating resource data for generating a mash-up of the API;

generating description data corresponding to the API, the meta-data, and the resource data; and

generating an API package comprising the API, the meta-data, the resource data, and the description data,

wherein the description data comprises information about one of components of the API package, a version of the API, and a library function for executing the API, and

wherein the generating the API package comprises:

analyzing an input/output data format of the API;

searching for another API package to perform the mash-up with the API package selectively on the basis of the input/output data format of the API; and

generating the mash-up by using the API package and the other API package,

wherein the analyzing the input/output data format of the API is performed using tagging information of the resource data.

23. A non-transitory computer-readable recording medium having embodied thereon a program for executing a method of producing an Application Programming Interface (API) mash-up, the method comprising:

obtaining at least two API packages which respectively comprises an API, meta-data for executing the API, resource data for generating a mash-up of the API, and description data corresponding to the API, the meta-data, and the resource data;

extracting the API, the meta-data, and the resource data from each of the at least two API packages by using the description data; and

generating a mash-up of the at least two API packages by using the API, the meta-data, and the resource data,

wherein the description data comprises information about one of components of the API package, a version of the API, and a library function for executing the API, and

wherein the generating the mash-up of the at least two API packages comprises:

analyzing an input/output data format of the API;

searching for another API package to perform the mash-up with an API package selectively on the basis of the input/output data format of the API; and

generating the mash-up by using the API package and the other API package,

wherein the analyzing the input/output data format of the API is performed using tagging information of the resource data.

24. A method of generating an Application Program Interface (API) mash-up, the method comprising:

obtaining at least two API packages;

extracting data from each of the at least two API packages;

generating a mash-up of the at least two API packages by using the extracted data; and

storing the at least two API packages in memory,

wherein the at least two API packages respectively comprise an API, meta-data for executing the API, resource data for generating a mash-up of the API, and description data corresponding to the API, the meta-data, and the resource data,

wherein the description data comprises information about one of components of the API package, a version of the API, and a library function for executing the API, and

wherein the generating the mash-up of the at least two API packages comprises:

analyzing an input/output data format of the API;

searching for another API package to perform the mash-up with an API package selectively on the basis of the input/output data format of the API; and

generating the mash-up by using the API package and the other API package,

wherein the analyzing the input/output data format of the API is performed using tagging information of the resource data.

25. The method of generating an Application Program Interface mash-up according to claim 24 , wherein the extracted data comprise an API, meta-data for executing the API, resource data for generating a mash-up of the API, and

wherein the description data corresponds to the API, the meta-data, and the resource data.