KR101393247B1 - Apparatus and method for automatic annotation and publication of semantic information of web services based soap and rest - Google Patents

Abstract

There is provided an apparatus and method for automatically annotating and registering semantic information of a web service based on SOAP and REST. The apparatus and method automatically categorize semantic information at a URL where Web service portals and services registered with the service are registered, annotate the service, and register the result of the annotation in the service registry.

Description

[0001] APPARATUS AND METHOD FOR AUTOMATIC ANNOTATION AND PUBLICATION OF SEMANTIC INFORMATION OF WEB SERVICES [0002] BACKGROUND OF THE INVENTION [0003] The present invention relates to a method and apparatus for automatically annotating and registering semantic information of a web service based on SOAP and REST,

The following embodiments relate to an apparatus and method for automatically annotating and registering semantic information of a web service based on SOAP and REST.

As mashups for Web services become more popular, mechanisms for unifying and discovering and combining Web services based on SOAP (Simple Object Access Protocol) and REST (RESTRESENTAL STATE TRANSFER) are becoming more important.

SOAP-based Web services follow Service Oriented Architecture (SOA). The service infrastructure includes a service provider that publishes and publishes a Web service specified in a Web Services Description Language (WSDL) format in a UDDI (Universal Description, Discovery and Integration) registry, Discovery, binding, and so on.

REST-based Web services follow a resource-oriented architecture (ROA). A resource-based representation, delivery, and access structure is one in which a resource provider registers a URI for a resource and the resource provider directly provides a resource-type service to the resource requester.

SOAP-based Web services and REST-based Web services have evolved into different structures. However, technologies for converting SOAP-based services into REST-based services or converting REST-based services into SOAP-based services for mashup have been developed .

The Web service discovery according to the related art performs semantic annotation in the form of Semantic Markup for Web Services (OWL-S) or Semantic Annotations (WSDL) for a SOAP-based Web service described in WSDL, Results.

Therefore, when a SOAP-based service and a REST-based service are to be mash-up, there is a problem that the conventional technology needs to perform annotation after converting a REST-based service to a SOAP-based service.

According to an aspect of the present invention, there is provided an information processing system including an annotation block for generating an annotated service by crawling semantic information about a service in a URL specifying a service, a web service portal registered with the service, And an edition block for receiving the service annotation and registration request to invoke the annotation block and calling the publication block, wherein the semantic information of the web service based on the SOAP and REST based web service Is automatically annotated and registered.

The semantic information for the service may include data semantic information, functional semantic information, and non-functional semantic information.

The edition block may send the service profile information to the management portal.

The annotation block accesses the URL and the service URI of the WSDL to extract data semantic information and functional service information of the service described in the service description, and performs annotation based on the extracted data semantic information and functional service information .

The annotation block accesses a web service portal where service information is registered, and can perform automatic annotation by crawling data semantic information, functional semantic information, and non-functional semantic information registered by a service provider.

The web service portal may include one or more of Seekda and ProgrammableWeb.

The functional semantic information may include at least one of a service name, a service category, a service provider, a service location, a service description, and a service providing country.

The non-functional semantic information may include at least one of a protocol used in a service, a price, availability of a service, safety, a preference for service utilization, a service type, and a response time.

According to another aspect of the present invention, there is provided a method for providing an annotated service, the method comprising: receiving a service annotation and a registration request; crawling semantic information at a web service portal where a service is registered and a URL specifying the service; A method for automatically annotating and registering semantic information of a web service based on SOAP and REST including a step of storing the generated annotated service and a step of delivering service profile information to a management portal are provided.

The present invention provides an apparatus and method for automatically registering a Web service portal and a service in which a service is registered, and annotating the service by automatically crawling the semantic information in the URL, and registering the result of the annotation in the service registry.

The SOAP-based web service and the REST-based web service are registered in the web service portal unlimitedly in formats in which the service specification is different from each other. Accordingly, the apparatus and method disclose an integrated annotation and mashup for SOAP-based services and REST-based services.

The semantic information is useful for user-based service discovery.

The apparatus and method according to an exemplary embodiment of the present invention annotate data semantic information and functional semantic information used in a general semantic annotation and provide non-functional semantic information by annotating it. Non-functional semantic information includes service availability, security, rating for service utilization, and response time, which are statistical information of the log type accumulated in the runtime.

The non-functional semantic information can be usefully used for object-based service discovery, which may vary depending on the user's situation.

The present invention makes it possible to use the SOAP and REST-based web services, which have been specified in the related art, by performing annotation without restriction on the format for specifying a service, thereby enabling service mesh up.

1 is a structural diagram of a web service system according to an embodiment of the present invention.
2 is a configuration diagram of an annotation registration apparatus according to an embodiment of the present invention.
3 is a detailed block diagram of an annotation block according to an exemplary embodiment of the present invention.
4 is a user interface that provides annotations and registration in accordance with an example of the present invention.
FIG. 5 illustrates semantic information of a service according to an exemplary embodiment of the present invention.
FIG. 6 illustrates an annotation registration method according to an embodiment of the present invention.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to or limited by the embodiments. Like reference symbols in the drawings denote like elements.

1 is a structural diagram of a web service system 100 according to an embodiment of the present invention.

The web service system 100 includes a management portal 110, an annotation registration apparatus 120, and a web service portal 130.

The management portal 110 sends the service annotation and registration request to the annotation registration device 120.

The annotation registration device 120 is a device for automatically annotating and registering the semantic information of the integrated web service.

The annotation registration device 120 receives the service annotation and the registration request, performs annotation, and delivers the service profile information to the management portal 110.

A Web service is registered in the Web service portal 130. Web service portal 130 may be, for example, a Seekda or ProgrammableWeb web service portal. The web service portal 130 provides information necessary for the annotation to the annotation registration device 120. [

2 is a configuration diagram of an annotation registration apparatus 120 according to an embodiment of the present invention.

The annotation registration apparatus 120 includes an edition block 210, an annotation block 220, a publication block 230, and a registry 240.

The edition block 210 performs an interface function for annotation and registration.

The edition block is a block that receives the service annotation and registration request from the management portal 210, and is activated by the reception.

The edition block 210 provides a user interface. The user interface receives the service annotation and registration request, invokes the annotation block 220 to perform the annotation, and invokes the publishing block 230 to register the annotation execution result in the registry 240.

The edition block 210 performs annotation and then transmits information on the service profile managed by the management portal 110 among the annotated semantic information to the management portal 110. [

The service profile managed at the management portal 210 includes functional semantic information and non-functional semantic information of the service.

The functional semantic information may include one or more of a service name, a service category, a service provider, a service URL, and a service description.

The non-functional semantic information may include a protocol and a price.

The annotation block 220 is a block for performing actual annotation, and annotates semantic information about a service.

The annotation block 220 performs annotation by crawling data semantic information, functional semantic information, and non-functional semantic information for a service, at a URL at which a service is registered and a service is registered.

First, the annotation block 220 accesses the URL of the WSDL and the REST-based service URI, which are specifications for the SOAP-based service, and extracts the data semantic information and the functional semantic information of the service described in the service description.

Secondarily, the annotation block 220 accesses a web service portal (for example, Seekda or ProgrammableWeb) in which service information is registered, and crawls data semantic information, functional semantic information, and non-functional semantic information registered by the service provider, Perform annotations.

The configuration of the annotation block 220 will be described later with reference to FIG.

The publishing block 230 registers the semantic information of the annotated service in the registry 240. The registered semantic information is used for service discovery and combination.

The registry 240 stores the semantic information of the annotated service.

3 is a detailed block diagram of an annotation block according to an exemplary embodiment of the present invention.

The annotation block includes a primary crawler 310 and an additional crawler 320.

The basic crawler 310 performs automatic annotation by crawling mandatory semantic information among the above-described semantic information.

The additional crawler 320 performs automatic annotation by crawling optional semantic information among the semantic information described above.

4 is a user interface that provides annotations and registration in accordance with an example of the present invention.

The import service 410 receives a WSDL URL and a REST-based service URI, which are specifications of a SOAP-based service from a user, and stores the SOAP and REST-based web service registered in the remote URL or URI as a local i.e., the annotation registration device 120, and stores it. The above load operation can be performed by the annotation block 220. At this time, the semantic information and the functional semantic information of the service described in the service specification are extracted. The annotation block 220 performs automatic annotation using the result of the extraction. The result of the extraction can be displayed on the interface screen.

The crawl service information 420 receives a signal including information on the selection when the user selects a web service portal (for example, Seekda and ProgrammableWeb) to which the web service information is registered. The annotation registration device 120 accesses the selected web service portal in which the service information is registered according to the signal, extracts data semantic information, functional semantic information and non-functional semantic information registered by the service provider, and outputs the automatic annotation .

The field of the service information 430 is filled with the result of the executed annotation.

Therefore, an automatic annotation is performed in which fields of the service information 430 are filled by using the import service 410 and the crawl service information 420.

The fields of the service information 430 include a Functional Semantics information field 440 for the function of the service, a Non-Functional Semantics information field 450 and a data semantic information field 450 for the input / Field 460. < / RTI >

The functional semantic information field 440 may include a service name field, a service category field, a service provider field, a service URL field, a service description field, effect field, and a service providing country field.

The non-functional semantic information field 450 includes a protocol field, a cost field, a service availability field, a security field, a rating field for service utilization, A type field, and a response time field.

When the automatic annotation is completed and the user selects the annotation result entry 470, the annotation registration device 120 outputs the annotation result generated in the XML form to a display unit (not shown).

When the user selects the publish item 480, the annotation registration device 120 registers the created annotation result in the registry 240.

FIG. 5 illustrates semantic information of a service according to an exemplary embodiment of the present invention.

The semantic information is defined as a service that can be used for service discovery and combination according to the purpose of the user.

Semantic information to be annotated is defined for each of the data semantic information 510, the functional semantic information 520, and the non-functional semantic information 530. The field names of the respective semantic information are displayed in the second column 540 of the table shown in FIG. 5, and each of the semantic information is displayed as a row of the table shown in FIG.

The third column 550 and the fourth column 560 of the table show the name of each semantic information in the web service portals (Seekda and ProgrammableWeb) that crawls the service information. The third column 550 is for Seekda and the fourth column 560 is for ProgrammableWeb.

In the fifth column (570) of the table, 'O' is selected as the basic consideration target and '(optional)' as the selective consideration target. In the basic crawler 310, which is a basic consideration object of the semantic information, the optional crawler 320 can be crawled by the additional crawler 320.

The data semantics 510 is information on the input / output parameters of the service. Seekda defines the input / output field "In / Output" and provides related information through "In / Output".

The functional semantic information 520 of the service may include at least one of a service name, a service category, a service provider, a service URL, a service description, a country of service, Service effects. ≪ / RTI >

The service name is defined as the "Title" field in Seekda and the "API name" field in ProgrammableWeb. The service category is undefined in Seekda and defined in the "category" field in ProgrammableWeb. The service provider is defined in the "provider" field in Seekda and ProgrammableWeb. The service location (service URL) is defined as the "WSDL file" field in Seekda and the "API home" field in ProgrammableWeb. The service description is defined as the "description" field in Seekda and the "summary" field in ProgrammableWeb. The country of service is a field defined only by Seekda, but it is defined as optional since it is semantic information useful in providing local service. The service effect is defined as optional because Seekda and ProgrammableWeb do not define the field but can be extracted through crawling at the URL (URI) where the Web service is described and semantic information useful for service discovery.

The functional semantic information 520 of the service as described above is a mostly defined field in Seekda and ProgrammableWeb. Thus, the functional semantic information of the service can be easily crawled.

The non-functional semantic information 530 of the service includes information such as protocol used in the service, cost, availability of the service, security, rating of the service utilization, service type and response time ) Information. The service type specifies whether the service is a simple service or a complex service.

The protocol was defined in the "protocol" field in Seekda and ProgrammableWeb. The protocol indicates whether the service uses SOAP or HTTP as a REST-based service. The cost is defined in the "usage fees" field only in ProgrammableWeb. The availability of the service is defined in the "availability" field only in Seekda. The security field is defined in the "security" field only in ProgrammableWeb. The "security" field provides an authentication model and SSL support information. The rating for service use is defined in the "user rating" field only in Seekda. The "user rating" field provides information on the usage and rating of the user. The service type and response time are undefined fields in Seekda and ProgrammableWeb, but they are defined for use because they are useful semantic information. The service type specifies whether the service is an atomic service or a composite service.

Some of the above non-functional information 530 of the service is not defined in Seekda and ProgrammableWeb. Thus, the fields of the non-functional semantic information 530 are mostly defined as additional subject semantics that are not subject to consideration.

FIG. 6 illustrates an annotation registration method according to an embodiment of the present invention.

In step S610, a service annotation and a registration request are received.

In step S620, the annotated service is generated by crawling the semantic information at the URL where the service is registered and the Web service portal in which the service is registered and performing annotation.

The semantic information may include data semantic information, functional semantic information, and non-functional semantic information.

In step S630, the generated annotated service is stored.

In step S640, the service profile information is transmitted to the management portal.

The service profile information is managed in the management portal among the semantic information of the annotated service.

The technical contents according to one embodiment of the present invention described above with reference to Figs. 1 to 5 may be applied to this embodiment as it is. Therefore, a more detailed description will be omitted below.

The method according to an embodiment of the present invention can be implemented in the form of a program command which can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions recorded on the medium may be those specially designed and constructed for the present invention or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. This is possible.

Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined by the equivalents of the claims, as well as the claims.

100: Annotation registration device
210: Edition Block
220: Annotation block
230: publishing block
240: Registry

Claims (11)

delete A registry to store information;
An annotation block for generating an annotated service by performing annotation by crawling semantic information on a service in a URL for which a service is registered and a service specified URL;
An edition block for receiving the service annotation and registration request and calling the annotation block; And
A publishing block for registering the semantic information of the annotated service in the registry,
/ RTI >
Wherein the edition block receives the service annotation and the registration request and invokes the publishing block, automatically annotating the semantic information of the web service. A registry to store information;
An annotation block for generating an annotated service by performing annotation by crawling semantic information on a service in a URL for which a service is registered and a service specified URL; And
A service annotation and an edition block for receiving the registration request and calling the annotation block
/ RTI >
Wherein the semantic information for the service includes at least one of data semantic information, functional semantic information, and non-functional semantic information. The method of claim 3,
Wherein the functional semantic information includes at least one of a service name, a service category, a service provider, a service location, a service description, and a service providing country. The method of claim 3,
The non-functional semantic information includes at least one of a protocol used in the service, a price of the service, availability of the service, stability of the service, preference for use of the service, service type of the service, And automatically annotating the semantic information of the web service. A registry to store information;
An annotation block for generating an annotated service by performing annotation by crawling semantic information on a service in a URL for which a service is registered and a service specified URL; And
A service annotation and an edition block for receiving the registration request and calling the annotation block
/ RTI >
Wherein the edition block automatically transmits information of a service profile to a management portal, and automatically annotates the semantic information of the web service. The method according to claim 6,
Wherein the edition block automatically receives the service annotation and registration request from the management portal and is activated by receiving the service annotation and the registration request. 8. The method of claim 7,
Wherein the service profile information is information managed in the management portal among the annotated semantic information, automatically annotating the semantic information of the web service. A registry to store information;
An annotation block for generating an annotated service by performing annotation by crawling semantic information on a service in a URL for which a service is registered and a service specified URL; And
A service annotation and an edition block for receiving the registration request and calling the annotation block
/ RTI >
The annotation block accesses a Uniform Resource Locator (URL) and a Uniform Resource Identifier (URI) of a Web Services Description Language (WSDL) And automatically annotates the semantic information of the web service by crawling at least one of the data semantic information, the functional semantic information, and the non-functional semantic information of the web service. A method of automatically annotating semantic information of a web service in an electronic device,
Receiving a service annotation and a registration request; And
A step of generating an annotated service by performing annotation by crawling semantic information at a web service portal in which a service is registered and a URL in which the service is specified
Including the
Wherein the semantic information for the service includes at least one of data semantic information, functional semantic information, and non-functional semantic information, wherein the electronic device annotates the semantic information of the web service automatically. delete

Images