JP4588731B2 - Service connection information generation system, method, and program - Google Patents

Description

  The present invention relates to a service connection information generation system, method, and program suitable for use in generating service connection information used to link services in a system that executes a plurality of services distributed on a network in cooperation with each other. .

  In recent years, service cooperation technology has attracted attention as one of the technologies for realizing SOA (Service Oriented Architecture). Services used in service linkage technology define, for example, a web service interface based on technical specifications defined by WSDL (Web Services Description Language) and a service interface based on UPnP (Universal Plug and Play) specifications, and SOAP (Simple Object Access Protocol) , * Technical specifications established by the international standardization organization W3C), etc. A workflow that executes these interface-defined services sequentially or in parallel, that is, a cooperation scenario, is executed by a scenario execution engine. The interface-defined service that is referred to and called in the cooperation scenario is referred to as an element service in the present invention.

  Generally, BPEL (Business Process Execution Language) or the like is used as a workflow description language for describing a complex workflow (cooperation scenario) using a Web service. A scenario execution engine that executes a workflow based on the BPEL description is called a BPEL engine.

  In addition to the BPEL system, a system having a function of discovering an intermediary service and synthesizing a service including this when the interface between the scenario execution engine and the element service cannot be obtained (for example, Patent Document 1), service There is a system (for example, Patent Document 2) that enables dynamic adaptation to other service elements having equivalent functions in the same area. By using these systems, it is possible to use a cooperation scenario combining element services.

  When creating a collaboration scenario, in the technology under consideration by the inventors of the present invention, by creating a data flow (data transfer) between element services in the collaboration scenario as element service connection information and holding it in the system, It has been found that it is possible to increase the reusability of data flow definitions, reduce manpower, and efficiently create linkage scenarios.

  In addition, it is considered that automatically generating element service connection information in a system for creating a cooperation scenario contributes to further reduction of labor for creating the cooperation scenario. Here, the element service connection information defines the interface of the element service, that is, the relationship between the input and output parameters.

  As a method for defining the relationship between input and output parameters, there is a method using a parameter form (Patent Document 3). However, in this method, both a semantic difference between parameters and a schema difference are mixed and mechanical. It is considered that there is a problem in the reusability of the definition.

JP-A-2005-71052 JP-A-2005-250844 Japanese Patent Laying-Open No. 2005-332122

  The present invention has been made in view of the above-described background, and is used when creating a cooperation scenario representing a cooperation service, and defines a relationship between interfaces, that is, input / output parameters. It is an object of the present invention to provide a service connection information generation system, method, and program capable of automatically generating information with high reusability.

To solve the above problems, a first aspect of the present invention, there is used when linking a plurality of elements service predetermined metadata is configured granted respectively to the input and output, said plurality A system for generating element service connection information, which is information for connecting input or output of element services, and interrelationships between entities indicated by the metadata respectively assigned to the plurality of element services and said information do Ranaru ontology representing a storage means for storing element SLI, first entity corresponding to the first metadata assigned to the output of the first element service of said element service If, vs. the second metadata assigned to the input of a second element service different from the first component service of the element service Correlates within said ontology of the second entity, if conditions are met that indicates the inclusion relation linking between the input of the output and the second element service of the first element service, the first first means for searching an element SLI from the storage means indicating that the output of the element service is semantically assignable to the input of the second element service, the storage unit based on the search result without the element service connection information stored within, if it is the semantically assignable, the correspondence when assigning an output of the first element service to the input of the second element service, the the schema of the input of the output and the second element service of the first element service generates a definition formula shown in view, element service linking information including information the defining equation shown Generated and, a second means for storing in the storage means, any of the metadata corresponding to one or more of the entities in the ontology, the entity of all hands, the first meta is an element SLI generation system which is a one of the subclasses of whether the second entity corresponding to the first entity or the second metadata corresponding to the data.

According to a second aspect of the invention, in the ontology, all the entities belonging to any of the lower class of the physical entity and abstract entities, all said entities belonging to lower classes of the abstract entity, the physical entities of are given the constraint that belongs to the lower of all entities belonging to lower classes, the first means is a semantically physical event output of the first element service and the when the input of the second element service is semantically abstract events, characterized by that it is possible semantically substituting the output to the input.

The invention of claim 3 wherein the, there is used when linking the input and a plurality of elements service predetermined metadata is configured granted respectively output, the input of the plurality of element service Or a method of generating element service connection information, which is information for connecting outputs, wherein the information represents a mutual relationship between entities indicated by the metadata respectively given to the plurality of element services . A process of storing element service connection information using an ontology, a first entity corresponding to first metadata assigned to an output of the first element service among the element services, and the element service second entity corresponding to the second metadata assigned to the input of a second element service different from the first component service of Interrelationships within the ontology of the I is, if conditions are met that indicates the inclusion relation linking between the input of the output and the second element service of the first element service, the output of the first element service a first step of searching for elements SLI indicating that but is semantically assignable to the input of the second element service, without the element service connection information stored is based on the search result, If it is the semantically assignable, when substituting the output of said first element service to the input of the second element service association, output and said second of said first element service generating a definition formula shown in view of the schema of the input element service generates a component service connection information including information the defining equation shows, and a second process to be stored, any pre Metadata corresponding to one or more of the entities in the ontology, all of the entity, the first metadata corresponding the first entity or the second metadata corresponding the second entity The element service connection information generation method is characterized in that it is defined as any one of the subclasses.

The invention of claim 4 is, there is used when linking the input and a plurality of elements service predetermined metadata is configured granted respectively output, the input of the plurality of element service or a method of generating an element service connection information that is information for linking between the output a program for execution by a computer, while the entities represented by the metadata assigned to each of the plurality of element service using the information or Ranaru ontology representing the interrelationship of the steps of storing element SLI, the corresponding first metadata assigned to the output of the first element service of said element service a first entity, granted to the input of a second element service different from the first component service of the element service If correlation within the ontology of the second entity corresponding to the second metadata satisfies showing the inclusion relation linking between the input of the output and the second element service of the first element service in a first step of searching for elements service connection information indicating that the output of the first element service is semantically assignable to the input of the second element service, stored on the basis of the search result without said element SLI which is, in the case of the semantically assignable, the correspondence when assigning an output of the first element service to the input of the second element service, the first outputs of the element service and generates the second definition formula shown in view of the schema of the input element service generates a component service connection information including information the defining equation shown A second step to be stored include a description for executing a computer, any of the metadata corresponding to one or more of the entities in the ontology, all of the entity, the first metadata it is the first entity or the second of the second entity of any element SLI generation program, characterized in that defined as a subclass that corresponds to the metadata that corresponds to.

  According to the present invention, the output of the first element service is semantically input to the input of the second element service with reference to an ontology composed of a plurality of entities associated with metadata and information representing the interrelationship between them. Definition formula that asks for substitutableness and shows the correspondence when substituting the output of the first element service to the input of the second element service in consideration of the schema of the output and input The element service connection information including the information indicated by the definition expression is generated, so that the interface of the element service is matched, the relationship between the interfaces, that is, the input / output parameters is automatically defined, and the linkage service is A scenario to represent can be generated.

  In particular, considering that the entities that exist in the semantic ontology are appropriately applied as metadata to be given to the element service contract, the entities in the semantic ontology are highly reusable, and conversely, the service contract. It is possible to give a semantically easy-to-understand guideline on how to add metadata to the. In addition, by using the inclusion relationship of an abstract entity to a physical entity, it is possible to map a parameter representing a concrete object to a parameter indicating an abstract event, which was impossible with conventional mapping. It becomes.

  The best mode for carrying out the present invention will be described below with reference to the drawings. FIG. 1 shows a system diagram of a cooperation scenario creation system including a service connection information generation system according to the present invention. The cooperation scenario creation system shown in FIG. 1 is realized by executing a predetermined program using a computer and its peripheral devices, and is a configuration characterized by the present invention as a part of its constituent elements. However, a service connection information generation system including at least the element service connection information generation unit 300 is included.

A plurality of element services ES constituting the element service group 202 shown in FIG. 1 is a user 210 (meaning a terminal or an operator who operates the terminal) via the network 201 and other various terminals (computers not shown). Terminal, portable information terminal, etc.). The element service ES is an entity (also referred to as an entity) that can handle a target in a computer environment, and represents a set of data provided by a service providing apparatus connected to the network 201. Includes available processes or data. As the element service ES, for example, the provision of weather information and stock price information by web services using technologies used between systems connected via the web such as the Internet communication network, and integration of enterprise applications between companies are realized. ing. In addition, programs that provide various services using a network using JXTA, which is a general-purpose peer-to-peer (P2P) platform, are distributed over the network.

Other examples of the element service ES include components realized by EJB (enterprise Java (registered trademark) Beans) constituting Web services, content such as video that can be accessed via the network, and network 201. Connected printers and displays, CPU resources that indicate how much the computer is operating, computer environmental resources such as the network bandwidth that indicates how much network is being used, and multiple resources for realizing services on the network There are service templates that describe the order in which element services are provided. Also, software that runs on a constantly connected server is not the only element service . For example, software that operates on a portable terminal capable of a limited number of communications with other physically close users is also an element service . The network 201 includes public and private information communication networks including the Internet.

  As described above, the arbitrary element service ES shown in FIG. 1 can be used via the network 201, and the scenario execution engine 111 executes a scenario for linking the element services ES (cooperation scenario), thereby executing a plurality of elements. Make the service available. In addition, the scenario creation unit 102 and the element service connection information creation unit 106 can be used by the user 210 via the network 201.

  When the scenario execution engine 111 inputs output information from the service providing apparatus that provides the Nth (N is a natural number) element service according to the order described in the collaboration scenario that is the workflow of the element service ES, the next service execution request Is transmitted as input information of the service providing apparatus that executes the (N + 1) -th service element described in the cooperation scenario. Here, the scenario execution engine 111 is a core module of the platform, and after reading the cooperation scenario, the validity is checked by an XML (Extensible Markup Language) parser and the cooperation scenario is executed. Also, when applied in an event-driven system, it is possible to execute the corresponding linkage scenario according to the event, and wait for execution when delegating the processing to the upper application process during execution.

  The scenario creation unit 102 refers to the element service connection information stored in the element service connection information storage unit 109 in accordance with an instruction from the user 210, and sequentially or sequentially selects a plurality of element services, that is, a plurality of services defined by interfaces. Create a collaboration scenario that is a workflow to be executed in parallel. A conceptual configuration example of the cooperation scenario is shown in FIG.

  The element service connection information storage unit 109 stores the element service connection information automatically generated by the element service connection information generation unit 300, and can also be generated by the element service connection information generation unit 106 in accordance with an instruction from the user 210. it can.

Next, the flow of processing for creating the cooperation scenario ST1 of FIG. 2 will be described with reference to the flowchart of FIG. The cooperation scenario ST1 in FIG. 2 is a cooperation scenario in which the element service A is called after the element service A is called, then the element service C is called, and then the element service D is called. Here, the element services A to D correspond to the element service ES of FIG.

  The user 210 accesses the scenario creation unit 102, and the cooperation scenario creation process shown in FIG. 3 is executed. In step S101, the user 210 logs into the scenario creation unit 102, and in step S102, a screen for creating a scenario is displayed on the display surface of the user 210.

  The user 210 selects an icon corresponding to the element service representing the cooperation scenario ST1 on the GUI (graphical user interface) flow diagram according to the screen guidance in step S103.

  For each combination of element service A to element service B, element service B to element service C, and element service C to element service D as shown in the collaboration scenario ST1 of FIG. If no element service connection information is held (the determination result is “yes” in step S104), the element service connection information generation unit 300 generates service connection information in the processing after step S201.

  In steps S201 to S203, the element service connection information generation unit 300 sets the output parameters of the element service A for all of the input parameters of the element service B, all of the input parameters of the element service C, and all of the input parameters of the element service D. One of the output parameters of the element service B or the output parameter of the element service C is used to calculate whether data cannot be acquired.

  Hereinafter, as an example, a case where element service A and element service B are selected in step S201, that is, a case where the input parameters of element service B can be obtained from the output parameters of element service A will be described. To do. In the following description, the case where the input parameters of the element service B can be acquired from the output parameters of the element service A will be described as an example. On the other hand, if it cannot be acquired, information indicating that is stored in the element service connection information storage unit 109 and notified to the user 210 via the scenario creation unit 102 or the like.

  As illustrated in FIG. 5, the element service A has an input I_A1, an input I_A2, an output O_A3, and an output O_A4, and the element service B has an input I_B1, an input I_B2, an output O_B3, and an output O_B4. In this case, the input parameter of the element service B can be acquired from the output parameter of the element service A. The data obtained from the output O_A3 and the output O_A4 is directly or after performing some conversion processing, and then the input I_B1 and This means that it can be passed to input I_B2.

In step S202, the element service connection information generation unit 300 performs processing for matching various interfaces, such as appropriate mapping of parameter names, and stores a definition formula indicating the relationship between the matched parameters in the element service connection information storage. Store in the unit 109. Here, take the appropriate mapping for the parameter name, for example, when sequentially calling a plurality of element service, the fifth eyes return value of the parameters of the first to the calling element service, the next call of the element service parameters 3 It means the setting of necessary parameters when calling an element service such as calling in the second. Step S202 includes step S202-1 followed by step S202-2. First, step S202-1 will be described.

  In step S202-1, the semantic relationship between the metadata (data for data) assigned to the output / input of each element service (here, element service A and element service B) is represented by the semantic ontology storage unit 301. To obtain a semantic substitution relationship between output and input.

  Every element service ES has a contract describing information on what input / output the element service has. The rules are described according to a format such as WSDL. Parameters described in the conventions such as WSDL format have different names, granularities, and roles for each domain. Here, one domain relates to one provider that provides one or more element service groups (for example, the element service group 202 in FIG. 1). That is, if the domain is different, the name, granularity, and role of the parameter are different. Hereinafter, the parameter name, granularity, and role are referred to as a schema, and the schema of the parameter x is denoted as S {x}.

  As described above, for example, different domains have different schemas even if the parameters are semantically the same. Even if the parameters are semantically the same, if the schema is different, the output of one element service cannot be substituted as it is into the input of another element service. Therefore, the definition formula that defines the relationship between the input and output parameters used for assignment must be one that takes into account not only the semantic interrelationship of parameter x but also the interrelationship of schema S {x}. It will be.

In order to cope with different domains in this system, it is assumed that metadata including semantic information (semantics) is attached to the parameters described in the above-mentioned rules for input / output. For example, as shown in FIG. 5, for input I_A1, input I_A2, output O_A3, output O_A4, input I_B1, input I_B2, output O_B3, and output O_B4, i_A1, i_A2, o_A3, o_A4, i_B1, i_B2, o_B3, It is assumed that metadata of o_B4 is given.
If the element service is a web service that has WSDL contracts, this metadata is added by SAWSDL (Semantic Annotations for Web Services Description, standardization work in W3C, http://www.w3.org/2002/ws/sawsdl It is realized by annotating WSDL according to /). Alternatively, if the element service is defined more abstractly than the web service, that is, the contract is defined according to OWL-S (http://www.daml.org/services/owl-s/), which is an extension format of OWL. If it is, the parameters described in the rules themselves correspond to metadata.

  In metadata including semantic information, a logical relationship between entities is held as an ontology (semantic ontology) according to a format such as RDF (Resource Description Framework) or OWL (Web ontology language). An ontology (semantic ontology) is a clarification of a premise concept in a certain knowledge base about vocabulary and the mutual relationship between the concepts. In this system, predetermined metadata is assigned to the input and output of the element service, respectively, and the ontology is composed of a plurality of entities associated with the metadata and information indicating their interrelationships. ing.

  Any one metadata corresponds to one or more entities in the semantic ontology. Assume that all entities are subclasses of either abstract entities or concrete entities. In the present invention, the presence / absence / content of a semantic correlation between input and output parameters is recognized using a semantic ontology, and a definition formula that defines the relationship between the input and output parameters is generated based on the recognition result. The semantic ontology used at that time is stored in the semantic ontology storage unit 301.

  For example, as shown in FIG. 6, in the semantic ontology stored in the semantic ontology storage unit 301, “food” is a subclass of “product”, and “product” is a subclass of “physical entity”. That is, the relationship between the entities is the relationship of “food, product, physical entity”. Here, “X⊆Y” represents that the set X is a subset of the set Y. “Owl: subClassOf” is a property that defines a subclass in OWL.

  For example, as shown in FIG. 6, in the semantic ontology stored in the semantic ontology storage unit 301, “event” is a subclass of “notification”, and “notification” is a subclass of “abstract entity”. In other words, the relationship is “event⊆notification⊆abstract entity”.

  In step S202-1, for example, the output metadata of the first element service (element service A in this example) and the input metadata of the second element service (element service B in this example) mean When corresponding to the same entity in the target ontology, it can be recognized that the output is a semantically substituting relationship for the input. For example, as shown in FIG. 5, when both the metadata o_A3 and the metadata i_B1 are the entity X shown in FIG. 7, a relationship of i_B1 <= o_A3 is obtained. However, m <= n means that n can be semantically substituted for m.

  Specifically, for example, when the output O_A3 and the input I_B1 are both human names, and metadata o_A3 = “human” and metadata i_B1 = “human” are assigned to them, further semantic ontology storage is performed. When the entity X = “human” is held in the semantic ontology in the part 301, in step S202-1, the metadata o_A3 of the output O_A3 of the first element service (element service A in this example), The metadata i_B1 of the input I_B1 of the two element services (element service B in this example) is determined to be an entity of the same semantic ontology, and the output O_A3 can be semantically substituted for the input I_B1. The relationship with is required.

  Next, the process of step S202-2 will be described. In step S202-2, the schema DB (database) 302 is referred to based on the semantic relationship obtained in step S202-1 to generate an output / input transfer definition expression.

  For example, when the metadata o_A3 and the metadata i_B1 are “i_B1 <= o_A3”, the element service connection information generation unit 300 refers to the schema DB302, and the schema S {O_A3 corresponding to the metadata o_A3 is included in the schema DB302. } And whether or not the relationship between the schema S {I_B1} corresponding to the metadata i_B1 is already held. If not, the relationship between the schema S {O_A3} and the schema S {I_B1} must be registered in the schema DB 302. In general, when metadata o_A3 = metadata i_B1, the schema S {O_A3} = Schema S {I_B1} is typical.

  When schema S {O_A3} = scheme S {I_B1} is obtained, the element service connection information generation unit 300 can generate a definition formula that means that the input I_B1 is obtained from the output O_A3. The generated definition formula is stored in the element service connection information storage unit 109. In this case, the information represented by the definition formula is that the output O_A3 corresponds to the input I_B1, and the schema thereof has a relationship of S {O_A3} = S {I_B1}. Further, information indicating the relationship of the obtained schema S {O_A3} = schema S {I_B1} is stored in the schema DB 302.

  By performing the above steps for input I_B1 and input I_B2, calculate and recognize that the input parameters of element service B are obtained from the output parameters of element service A, and generate a definition formula that shows the relationship between them I can do it. Thus, step S202-2 ends.

  Next, according to the condition determination in step S203, steps S201 to S203 are executed for all of the input parameters of element service B, all of the input parameters of element service C, and all of the input parameters of element service D.

  In this manner, a definition formula for acquiring data can be obtained from any of the output parameters of the element service A, any of the output parameters of the element service B, or any of the output parameters of the element service C.

  Next, in step S105, it is determined whether or not the user has instructed the end of scenario creation. If instructed, in step S106, the scenario creation unit 102 generates a scenario sentence representing the cooperation scenario ST1. Scenario text can follow BPEL format, but is not limited to this. At this time, a scenario sentence is generated so as to refer to the definition formula for the data exchange between the scenario creating unit 102 and the element service.

  By causing the scenario execution engine 111 to read the generated cooperation scenario ST1, the scenario execution engine 111 can control the element service according to the contents described in the cooperation scenario ST1.

  The above description explains the best mode for carrying out the present invention. In step S202-1 above, the output of a certain element service and the input of another element service can be substituted semantically. In addition to following the example described with reference to FIG. 7 as a condition for obtaining the relationship, there is the following example according to any of the conditions illustrated in FIGS. That is, in step S202-1, there is a mutual relationship in the semantic ontology between the entity corresponding to the metadata given to the output of the element service A and the entity corresponding to the metadata given to the input of the element service B. When the predetermined condition is satisfied, it is determined that the output of the element service A can be semantically substituted for the input of the element service B. In step S202-2, if the element service A can be substituted, the element service A A definition formula is created that shows the mapping when assigning the output of A to the input of that element service B, taking into account the schema of the output and input, and element service connection information including the information indicated by the definition formula is generated It was supposed to be.

  In the above embodiment, the predetermined condition at that time is that the entity corresponding to the metadata of the output of the element service A and the entity corresponding to the metadata of the input of the element service B are the same. there were. On the other hand, in the following example, the entities are equivalent, one is a subclass of the other, and when combined with multiple metadata entities, The predetermined conditions are that corresponding entities are formed and that these entities are the same or equivalent at the instance level.

  In the case shown in FIG. 8, the metadata o_A3 of the output O_A3 of the element service A is the entity X, the metadata i_B1 of the input I_B1 of the element service B is the entity Y, and X and Y are equivalent (owl: equivalentClass ( = If the relationship between two classes is equivalent in OWL))), set “i_B1 <= o_A3”. Specifically, when the output O_A3 and the input I_B1 both represent “food”, and metadata o_A3 = “food” and metadata i_B1 = “food” are assigned to each, X is equivalentclass of in the semantic ontology This can happen if Y or Y is equivalentclass of X is retained. In this case, typically, the definition formula is S {O_A3} = S {I_B1}.

  Alternatively, due to transitivity, it can occur when X is equivalentclass of m and m is equivalentclass of Y (m is an arbitrary entity).

  In the case shown in FIG. 9, the metadata o_A3 is the entity X, the metadata i_B1 is the entity Y, and in the semantic ontology X and Y are in a lower class relationship (owl: subClassOf (= one class is a subclass of another class in OWL) If there is a property))), it is assumed that “i_B1 <= o_A3”. Specifically, when output O_A3 and input I_B1 both represent “food”, and metadata o_A3 = “food” and metadata i_B1 = “product” are assigned to each, X is in the semantic ontology Can occur when subclass of Y is preserved. In this case, typically, the definition formula is S {O_A3} = S {I_B1}. Alternatively, due to transitivity, it can occur when X is subclass of m and m is subclass of Y (m is an arbitrary entity).

  In the case illustrated in FIG. 10, the metadata o_A3 is the entity X, the metadata o_A4 of the output O_A4 of the element service A is the entity Y, the metadata i_B1 is the entity Z, and owl: unionOf, rdf: Seq (owl: "unionOf" is a property that represents the union of reference classes by OWL, and rdf: Seq is a container model that represents an ordered (Sequence) list by RDF. If "i_B1 <= o_A3 +" T Assume that it is “+ o_A4”.

  Specifically, the output O_A3 is in the xsd: date format (= data type representing the calendar date according to the XML schema), and the output O_A4 is the xsd: time format (= data type representing the time that is regularly repeated every day according to the XML schema) ) And I_B1 represent the date and time in xsd: dateTime format (= type that represents an instance of a specific time according to XML Schema), metadata o_A3 = “date” and metadata o_A4 = “time” This can occur when Z is union of {X + "T" + Y} is held in the semantic ontology when metadata i_B1 = “date and time” is given. In this case, typically, the definition formula is S {I_B1} = S {O_A3} + "T" + S {O_A4}. The xsd: String format is a data type that represents a character string according to an XML schema.

  The pattern of “xsd: date” is “CCYY-MM-DD”. The pattern of “xsd: time” is “hh: mm: ss.sss”. And the pattern of “xsd: dateTime” is “CCYY-MM-DDThh: mm: ss”. Where “CC” is the century, “YY” is the year, “MM” is the month, “DD” is the day, “T” is the date / time separator, “hh”, “mm”, and “Ss” represents hour, minute, and second, respectively.

  In the case as shown in FIG. 11, the metadata o_A3 is the entity X and the metadata i_B1 is the entity Y. In the semantic ontology, the equivalence relationship between each individual of X and Y (owl: sameAs (= the instance of the reference source by OWL) )) Is retained semantically, it is semantically "i_B1 <= o_A3", but S {I_B1} and S {O_A3} A definition formula that describes the corresponding relationship for each individual (instance) is generated.

  Specifically, when both the output O_A3 and the input I_B1 represent “month”, and metadata o_A3 = “month_number” and metadata i_B1 = “month” are assigned to each, the X individual in the semantic ontology (Instance) This may occur when the relationship of “1” and Y individual “January” are the same, X individual “2” and Y individual “February” are the same, and so on. Owl: DataRange and owl: oneOf shown in FIG. 11 are properties that define an enumeration class by OWL, and a class can be described by enumerating individuals that form the class.

  The above description explains the best mode for carrying out the present invention, but another embodiment in step S202-1 in FIG. 3 will be further described.

In step S202 of FIG. 3, may also be added restriction that "physical entity ⊇ abstract entities." That is, in the semantic ontology in the semantic ontology storage unit 301, all entities belong to a lower class of either a physical entity or an abstract entity, and all entities belonging to a lower class of the abstract entity are It is possible to give a constraint that it belongs to the lower level of all entities belonging to the lower class of the physical entity. By adding this restriction, step by step
In S202-1, all entities in the subclass of “physical entity” can be assumed to be semantically assignable to all entities in the subclass of “abstract entity”. Here, the metadata of the parameter representing a specific thing belongs to the “physical entity”. Also, metadata of parameters indicating abstract events belong to the “abstract entity”.

  For example, as shown in FIG. 6, when the semantic ontology of the physical entity and the abstract entity is simultaneously held in the semantic ontology storage unit 301, an output parameter indicating the “product” of the element service B belonging to the physical entity is set. It is possible to semantically substitute for a parameter representing an “event” in another element service 属 す る belonging to an abstract entity. In step S202-2, a definition formula is generated by maintaining the correspondence between the “product” schema of the element service B in the schema DB 302 and the “event” schema in the element service IV. For example, by adding an additional character string for associating a physical entity with an abstract entity, a definition formula such as “event” = “product” + “purchase” can be considered.

  According to the above-described embodiment, it is possible to automatically create a scenario representing a linked service by matching the interfaces of element services and defining the interface, that is, the relationship between input and output parameters. In particular, considering that the entities that exist in the semantic ontology are appropriately applied as metadata to be given to the element service contract, the entities in the semantic ontology are highly reusable, and conversely, the service contract. It is possible to give a semantically easy-to-understand guideline on how to add metadata to the. In addition, by using the inclusion relationship of an abstract entity to a physical entity, it is possible to map a parameter representing a concrete object to a parameter indicating an abstract event, which was impossible with conventional mapping. It becomes.

  The system configuration described with reference to FIG. 1 includes a scenario creation unit 102 and an element service connection information creation unit 106 in a device such as a PC (personal computer) in the user 210, as shown in FIG. Also good. The contents and processing steps of each function in the configuration shown in FIG. 4 are the same as those in the above-described embodiment described with reference to FIG.

  The embodiment of the present invention is not limited to the above-described one. For example, each configuration may be further divided and distributed via the network 201 or the like, or each component such as each storage unit and DB may be arranged as one. Changes can be made as appropriate. In addition, the service connection information generation system of the present invention has the element service connection information generation unit 300 as a main component, but other component elements such as the scenario generation unit 102 and the element service connection information generation unit 106 It can also be configured in an integrated manner. The system of the present invention can be configured as a program executed using a computer and its peripheral devices, and the program can be distributed via a computer-readable recording medium or a communication line.

The system figure which shows the general structure in the best embodiment for implementing this invention The figure which shows an example of the cooperation scenario used in the structure of FIG. The flowchart which shows the flow of the process in the structure of FIG. System diagram showing a modification of the configuration shown in FIG. Diagram showing metadata assigned to parameters of element services A and B The figure showing the structure of the semantic ontology memorize | stored in the semantic ontology storage part 301 of FIG. The figure showing an example of the relationship between the entities hold | maintained at the semantic ontology memorize | stored in the semantic ontology storage part 301 of FIG. The figure showing the other example of the relationship between the entities hold | maintained at the semantic ontology memorize | stored in the semantic ontology storage part 301 of FIG. The figure showing the other example of the relationship between the entities hold | maintained at the semantic ontology memorize | stored in the semantic ontology storage part 301 of FIG. The figure showing the other example of the relationship between the entities hold | maintained at the semantic ontology memorize | stored in the semantic ontology storage part 301 of FIG. The figure showing the other example of the relationship between the entities hold | maintained at the semantic ontology memorize | stored in the semantic ontology storage part 301 of FIG.

Explanation of symbols

102 Scenario creation department
106 Element Service Linkage Information Creation Department
111 Scenario execution engine
201 network
210 users
ST1 linkage scenario
ES, A ~ D element service
I_A1, I_A2 Element service A has inputs
O_A1, O_A2 Element service A has output
I_B1, I_B2 Element service B has input
O_B1, O_B2 Element service B output
Step numbers of the flowcharts in the embodiments S101 to S203

Claims (4)

A predetermined metadata for input and output be those used when linking a plurality of elements service configured granted respectively, the information for connecting between the input or output of said plurality of element service A system for generating certain element service connection information,
And said information do Ranaru ontology representing the mutual relationship between the entities represented by the metadata assigned to each of the plurality of element service,
Storage means for storing element SLI,
First a first entity corresponding to the metadata, the input of the second element service different from the first component service of the element service granted to the output of the first element service of said element service The inclusion relationship between the output of the first element service and the input of the second element service is the interrelationship in the ontology with the second entity corresponding to the second metadata assigned to If conditions are satisfied shown, the first first means output element service searches the element service linking information indicating semantically assignable to the input of the second element service from the storage means When,
The search results without the element service connection information stored in the storage means based on, in the case of the semantically assignable, the output of the first element service to the input of the second element service associating a first and a component service output and considering the schema of the input of the second element service generates a definition formula shown in, element service connection information including information the defining equation shown in the case of substituting And a second means for storing in the storage means ,
Any of the metadata corresponding to one or more of the entities in the ontology, the entity of all hand, corresponding to the first entity or the second metadata corresponding to the first metadata An element service connection information generation system characterized by being a subclass of any one of the second entities. In the ontology, belongs to one of the lower class of all the entities to physical entities abstract entity, wherein all entities belonging to lower classes of the abstract entity, the belonging to lower classes of the physical entity Is given the constraint that it belongs to the bottom of all entities,
It said first means, when the output of the first element service is semantically input physical an event and the second element service is semantically abstract events, the output The element service connection information generation system according to claim 1 , wherein the input can be semantically substituted. A predetermined metadata for input and output be those used when linking a plurality of elements service configured granted respectively, the information for connecting between the input or output of said plurality of element service A method of generating element service connection information,
Using the information or Ranaru ontology representing the mutual relationship between the entities represented by the metadata assigned to each of the plurality of element service,
Storing element service connection information;
First a first entity corresponding to the metadata, the input of the second element service different from the first component service of the element service granted to the output of the first element service of said element service interrelated within said ontology of the second entity corresponding to the second metadata is granted, the inclusion relation linking between the input of the output and the second element service of the first element service If conditions are satisfied illustrating a first process of searching the element service connection information indicating that the output of the first element service is semantically assignable to the input of the second element service,
The search results without the element service connection information stored is based on, in the case of the semantically assignable, when substituting the output of said first element service to the input of the second element service associating said first and of element service output and considering the schema of the input of the second element service generates a definition formula shown in, generates the element service linking information includes information the defining equation shown A second process of storing , and
Any of the metadata corresponds to one or more of the entities in the ontology, and all of the entities correspond to the first entity corresponding to the first metadata or the second metadata corresponding to the second metadata . An element service connection information generation method, characterized in that it is defined as a subclass of any of the two entities. A predetermined metadata for input and output be those used when linking a plurality of elements service configured granted respectively, the information for connecting between the input or output of said plurality of element service A program for executing on a computer a method for generating certain element service connection information,
Using the information or Ranaru ontology representing the mutual relationship between the entities represented by the metadata assigned to each of the plurality of element service,
Storing element service connection information;
First a first entity corresponding to the metadata, the input of the second element service different from the first component service of the element service granted to the output of the first element service of said element service interrelated within said ontology of the second entity corresponding to the second metadata is granted, the inclusion relation linking between the input of the output and the second element service of the first element service If conditions are satisfied illustrating a first process of searching the element service connection information indicating that the output of the first element service is semantically assignable to the input of the second element service,
The search results without the element service connection information stored is based on, in the case of the semantically assignable, when substituting the output of said first element service to the input of the second element service associating said first and of element service output and considering the schema of the input of the second element service generates a definition formula shown in, generates the element service linking information includes information the defining equation shown A second process to be stored and a description for executing on the computer,
Any of the metadata corresponds to one or more of the entities in the ontology, and all the entities correspond to the first entity or the second metadata corresponding to the first metadata. An element service connection information generation program characterized in that it is defined as a subclass of any one of the second entities.

Images