Standardization is an important factor in restricting technology development, and it is also a deep understanding of a large number of heterogeneous and incompatible issues.
At present, EAI is the main method of enterprises for information transformation.
Web Services technology is based on standardity and openness.
Traditional safety certification, the inconsistency of access control architecture framework makes the entire security authentication, and the standardization of access control systems is difficult to obtain.
The service is packaged in a certain business logic, completes a certain functional processing unit, and the full description of the amount information required for service resources includes:
(1) Physical information: The interface information of the URL address information of the specific program associated with the service is mainly described, and the interface information of the service provided by the service, and the format, number, order, and sequential sequential information of the parameters of the inputs and outputs required.
(2) Performance information: Mainly describe the performance indicators such as service quality (QoS) and other non-functional performance. For example, complete the service needs, the service level, service level, security, etc.
(3) Semantic information: Mainly describe the semantics of the function completed by the service, which is convenient for computer understanding, utilization, and processing. In order to provide support for semantic description, the author establishes a domain knowledge induction library to describe unified domain knowledge, providing a semantic basis for understanding and interaction between different entities in the system.
The body is an abstraction and description of the domain knowledge concept. In the early 1990s, the body became a hotspot in many artificial intelligence groups in knowledge engineering, natural language processing and knowledge, which was that the body was based on the exchange of exchanges between the machines on the consensus of the communication.
Using the body to guide the registration, management and discovery process of the service to help the service more accurately describe the service more accurately, the administrators of the service organize and manage all relevant service resources, the service process definition personnel can More specifically, the designation of the services involved in the business process, while the intermediary server can also perform dynamic lookup, binding and adjustment of the service based on the body.
In Daml-S, the basic information of the description service mainly has the following three types:
(1) Service profile: What is the description of the service? It gives a set of information that the service query agent needs to be used to determine if the service is suitable for it.
(2) Service model: How do I work? It describes what happens when the service is executed, the specific logic execution order.
(3) Service GROUNDING: Describe how to access the service? It describes communication protocols when accessing services and other specific details.
However, DAML-S focuses on the semantic description model of the service, for how to generate the WSDL description file from the specific service to the generation of various semantic description files, especially the mapping relationship between Servicegrounding to WSDL is not defined. In order to adapt to the actual needs of Web Service's dynamic application integration, it is also necessary to simplify and scalable for the DAML-S service description model.
