GB/T 32392.7-2018Information technology -- Metamodel framework for interoperability (MFI) -- Part 7: Metamodel for service model registration (English PDF)

3.1 Terms and definitions

The following terms and definitions apply to this document.

3.1.1

Atom expression atomicexpression

A logical expression with a cell granularity (3.1.5).

3.1.2

Combined expression composite expression

A logical expression (3.1.5) composed of connectors, in which connectors such as conjunction, disjunction, and negation contain multiple atomic expressions

Equation (3.1.1) or other combination expression (3.1.2).

3.1.3

Entity service entityservice

A business-centric Web service (3.1.22) whose functional boundaries and context are based on one or more related business entities.

3.1.4

Exit condition exitcondition

If true, it will result in a constraint that the operation ends abnormally.

Note. An action can be a process or service operation.

3.1.5

Expression expression

A sentence described by a special symbol is used to represent a logical symbol, or to express a clause applied to a service operation (3.1.18)

Piece, or the quality of the service (3.1.17) applied to a service.

3.1.6

Target goal

The expected result when the user interacts with the process (3.1.13) or the service (3.1.17).

3.1.7

Enter the message inputmessage

The service operation (3.1.18) is the information contained within the message consumed by the execution.

3.1.8

Participation type inflationtype

A statement that indicates the type of role (3.1.16) when participating in the process (3.1.13) or service (3.1.17).

Examples. performers, beneficiaries, customers.

3.1.9

Message type messagetype

The classification of messages consumed or generated during the execution of a service operation (3.1.18).

3.1.10

Output message outputmessage

Service operation (3.1.18) The information contained within the message generated after execution.

3.1.11

Postcondition postcondition

The operation should be true when the operation is complete.

Note. An action can be a process or service operation.

3.1.12

Precondition

The operation should be a true constraint before being called.

Note. An action can be a process or service operation.

3.1.13

Process

A set of structured and interrelated activities or tasks that are used to achieve a specific goal (3.1.6).

3.1.14

Quality of Service Assertion QoSassertion

Service (3.1.17) Specification of one or more quality of service types (3.1.15).

3.1.15

Quality of Service Type QoStype

Service (3.1.17) specific non-functional attributes such as availability, response time, etc.

3.1.16

Role role

The specific responsibilities of an entity involved in a situation.

3.1.17

Service service

An application that encapsulates one or more computing modules that can be accessed through a specific interface.

3.1.18

Service operation

The execution action of the service (3.1.17).

3.1.19

Task service taskservice

Functional boundaries are directly related to a specific process model for Web services (3.1.22).

3.1.20

User tag usertag

A label annotated by an individual or organization to describe the service (3.1.17) in accordance with the understanding of the label creator.

3.1.21

Utility service utilityservice

Committed to providing reusable Web services (3.1.22) with cross-cutting features, such as transaction logs, notifications, and

Often processed.

3.1.22

Web service Webservice

A service designed to support machine-to-machine interactions that are interoperable on a network (3.1.17).

3.2 Abbreviations

The following abbreviations apply to this document.

ebXMLRegRep ebXML registry and repository (ebXMLRegistry

IRI International Resource Locator (InternationalizedResourceIdentifier)

MFI Interoperability Metamodel Framework (Metamodelframeworkforinteroperability)

OWL-S Web Service Ontology Language (WebOntologyLanguageforServices)

QoS Quality of Service (QualityofService)

SWRL Semantic Web Rule Language (SemanticWebRuleLanguage)

WADL Web Application Description Language (WebApplicationDescriptionLanguage)

WSDL Web Service Description Language (WebServiceDescriptionLanguage)

WSML Web Services Modeling Language (WebServiceModelingLanguage)

4.1 Overview

Implementations that claim to be consistent with this section should support the metamodel specified in Chapter 5, which relies on the degree of conformity described below.

4.2 Compliance

4.2.1 Overview

In order to meet the needs of interoperability and scalability at the same time, the "strict compliance" and "compliance" implementations should be distinguished. This section describes the promotion

The specification of interoperability. Extensions are based on the needs of users, developers, organizations, and industry, and are not specified in this section.

Strict compliance with implementation is limited, but can maximize the interoperability associated with this section. Compliance with implementation

More extensive, but the ability to achieve interoperability associated with this section is weak.

4.2.2 Strictly consistent with implementation

Strictly consistent with the implementation.

a) should support the metamodel specified in Chapter 5;

b) Any extensions to the metamodel specified in Chapter 5, including use, testing, access or investigation, are not supported.

4.2.3 Compliance with implementation

Compliance with implementation.

a) should support the metamodel specified in Chapter 5;

b) Extensions consistent with the metamodel specified in 5.3 may be supported, including use, testing, access or investigation.

Note 1. All strict conformance implementations are consistent with implementation.

Note 2. Extending the metamodel may result in undefined behavior.

4.3 Implementing a Declaration of Conformity

An implementation claiming compliance with this section should include an implementation compliance statement stating the following.

a) is strictly consistent with implementation (4.2.2) or with implementation (4.2.3);

b) Which extensions are supported and used if they are compliant.

5.1 MFI Service Model Registration Overview

This section specifies a metamodel for registering functional and non-functional information for Web services (hereafter abbreviated as services). Appendix A

Some of the service description languages that can be registered with this metamodel are listed.

Note. Metaclasses with names in italics are abstract metaclasses.

Figure 2 Service model registration metamodel

Figure 2 shows the metamodel of the service registration. This metamodel allows registration of common and non-functional features of the service.

It is described using a set of service description languages. Each service model is expressed using a specific service description language. This model can

Used to describe one or more services. A service is described by zero or one quality of service assertion. Quality of service assertions are used to quantify or

Qualitatively express non-functional attributes of services such as response time, price, reliability, etc. Each quality of service assertion utilizes a unique expression

To define, an expression can be a combined expression or an atomic expression. Each quality of service assertion has one or more quality of service types.

Services are independent modular components and can only be accessed through interfaces. Therefore, the capabilities of the service are represented by service operations, each

A service operation represents an executable action of a service. Each service consists of zero, one or more service operations. Each service operation

Described by zero or one precondition, zero or one postcondition, and zero or one exit condition. Among them, the preconditions are defined in detail

The constraint should be true before a service operation is called. The postcondition defines in detail that a service operation should be true after the call is completed.

The constraint, the exit condition, details the constraints that are true when an operation is not successfully completed. Each precondition, postcondition, and exit

A condition is defined using one and only one expression, which can be a combined expression or an atomic expression. At the same time, every

Service operations are also described by zero, one or more input messages, zero, one or more output messages. Each input message

The information required for the execution of the operation is determined. Each output message specifies the information that is generated after the operation is successfully executed. Each message type

a description of a message or a group of messages, each of which is consumed during the execution of a service operation or

produce. Each input message can be constrained by zero, one or more preconditions, and each output message can be zero, one or more

A postcondition constraint. Each service can be labeled by one or more user tags, and each tag can be used by the service.

What one user created.

5.2 Relationship between MFI Service Model Registration and other parts of MFI

In this section, the rest of the MFI refers to ISO /IEC 19763-5, ISO /IEC 19763-8, and ISO /IEC 19763-10.

Figure 3 depicts the relationship between this part and ISO /IEC 19763-5 and ISO /IEC 19763-8.

Note. The metaclass represented by the gray background is the metaclass defined in other parts of the MFI.

Figure 3 Relationship between ISO /IEC 19763-5, ISO /IEC 19763-7 and ISO /IEC 19763-8

Each service implements zero, one or more goals. Each goal is implemented by zero, one or more services. Implementation of each service operation

Zero, one or more goals. Each target is implemented by zero, one or more service operations. Each service operation can fully implement zero

, one or more processes. Each process can be fully implemented by zero, one or more service operations. Each service includes zero, one

Participation in one or more services, where each service participation refers to the participation of a role accompanying a service, such as a participant or beneficiary. Each

Service participation indicates a role that is involved in the execution of a service.

Figure 4 depicts the relationship between the metaclasses in ISO /IEC 19763-7 and the metaclasses in ISO /IEC 19763-10.

Figure 4 Relationship between ISO /IEC 19763-7 and ISO /IEC 19763-10

The Service_Description_Language metaclass in this section is a subclass of the Modeling_Language metaclass in ISO /IEC 19763-10. The service in this section

The service _ model metaclass is a subclass of the model metaclass in ISO /IEC 19763-10. The other metaclasses in this section are ISO /IEC 19763-10

A subclass of the model_element metaclass.

All subclasses have an association that inherits from their superclass. Some inherited associations are specialized in this section, and the details are detailed.

See section 5.3 for definitions.

5.3 Metaclasses in the service model registration metamodel

5.3.1 Atomic_Expression

An atomic expression is a metaclass, and each instance of it represents a logical expression of unit granularity.

Super class

expression

Attribute data type multiplicity description

Expression_Text String 1.1 The text of a logical expression, described by an expression symbol.

Reference class multiplicity description reverse reference priority

constraint

5.3.2 Combination _ expression

A combined expression is a metaclass, and each instance of it represents a logical expression that uses such things as conjunction, disjunction, and

Negative combinations, including multiple atomic expressions and/or other combined expressions.

Super class

expression

Attribute data type multiplicity description

Combine_type string type 1.* A symbol used to join two or more logical expressions.

Reference class multiplicity description reverse reference priority

Combine _expression expression 1.* a series of expressions used to compose

This combined expression.

Being combined _ expression is

constraint

5.3.3 Combination_Type

The composite type is an enumerated type, including the following types.

Value description

The conjunction indicates that the combined expression is true and only if all the expressions that make up the combined expression are true.

The disjunction indicates that the combined expression is false and only if all the expressions that make up the combined expression are false.

Negation indicates whether the combined expression is true or false, depending on the atomic expression that makes up the combined expression.

Boolean value.

5.3.4 Exit_Conditions

An exit condition is a metaclass, and each instance of it specifies a state that should exist after a service operation terminates abnormally.

Super class

Model_Element (see ISO /IEC 19763-10)

Attribute data type multiplicity description

Name String The name of the service exit condition.

Reference class multiplicity description reverse reference priority

Exit_condition_

Logical expression

Expression 1.1 uses logical symbols to express facts

A sentence.

Is indicated _ exit _ condition is

Contains _service_

operating

Service_Operation 1.1 The execution activity of the service. Is included_exit_condition no

constraint

5.3.5 Expression

An expression is an abstract metaclass, and each instance of it uses a logical symbol to represent a sentence, thereby expressing a fact.

Super class

Model_Element (see ISO /IEC 19763-10)

Attribute data type multiplicity description

Symbol string type 1.* is a logical language or label used to declare quality assertions, services before

Set conditions and post conditions.

Reference class multiplicity description reverse reference priority

Expressed _ front

condition

Precondition 0.* should be true before the operation is called

constraint.

Precondition _ Logic _

expression

Is indicated _ post

condition

Postcondition 0.* should be true after the operation is called

constraint.

Postcondition_Logic_

expression

Expressed

Out_condition

Exit_condition 0.* causes the operation to not complete successfully

Should be true constraints.

Exit_condition_logic_

expression

Expressed _ service

Quality assertion

Quality of Service_Assertion 0.* Description of non-functional attributes of the service.

Quality of Service_Logic_

expression

Combined _ table

Da

Combination_expression 0.1 is one of the expressions

Combination table formed by elements

Da style.

Combination_expression is

constraint

5.3.6 Entering _Message

The input message is a metaclass, and each instance of it is contained in the message consumed by the execution of the service operation.

Super class

Model_Element (see ISO /IEC 19763-10)

Attribute data type multiplicity description

Name String 1.1 The name of the message consumed before the service operation is executed.

Reference class multiplicity description reverse reference priority

Contains _service_

operating

Service_Operation 1.1 The action execution of the service. Is consumed _ message no

Constraint_preposition

Precondition 0.* Before the service is successfully called

status.

Constrained_input is

Be involved in _ input_

Message_type

Message_Type 1.1 Service Operation Execution Consumption or Health

The type of message.

Participate in _input_message is

constraint

5.3.7 Message_Type

A message type is a metaclass, and each instance of it represents the type of message that is consumed or generated when the service operation is executed.

Super class

Model_Element (see ISO /IEC 19763-10)

Attribute data type multiplicity description

Name String 1.1 The name of the message type.

Message_type_

description

Character 0.1 message type description.

Reference class multiplicity description reverse reference priority

Participate in _ input _

Message

Enter message 0.* Messages for service execution consumption

Information contained.

Be involved in _ input_消

Interest_type

Participate in _output_

Message

Output message 0.* Message generated by service execution

Information contained.

Be involved in _output_消

Interest_type

constraint

5.3.8 Output_Message

The output message is a metaclass, which is a message containing an instance of the protocol information generated after the service operation is executed.

Super class

Model_Element (see ISO /IEC 19763-10)

Attribute data type multiplicity description

Name String 1.1 The name of the message generated after the service operation is executed.

Reference class multiplicity description reverse reference priority

Contains _service_

operating

Service_Operation 1.1 Service that generates this output message

operating.

Generated_message no

Constraint_post

condition

Postcondition 0.* After the service is successfully called

status.

Constrained_output is

Be involved in _output_

Message_type

Message_Type 1.1 Service Operation Execution Consumption or

The type of message generated.

Participation_output_message is

constraint

5.3.9 Postconditions

The postcondition is a metaclass, and each instance of it specifies a constraint that should be true after a successful call to the operation.

Super class

Model_Element (see ISO /IEC 19763-10)

Attribute data type multiplicity description

Name String The name of the service postcondition.

Reference class multiplicity description reverse reference priority

Post condition _ logic

Edit expression

Expression 1.1 uses logical symbols to express facts

A sentence.

Is indicated _ postcondition is

Constrained_output output_message 0.* The message contains the service operation

Information generated after execution.

Constraint_postcondition

Contains _service_

operating

Service_Operation 1.1 Service with this postcondition

Execution action.

Is included _ post condition no

constraint

5.3.10 Preconditions

A precondition is a metaclass whose instance specifies a constraint that should be true before an operation is successfully called.

Super class

Model_Element (see ISO /IEC 19763-10)

Attribute data type multiplicity description

Name string type 0.1 The name of this precondition.

Reference class multiplicity description reverse reference priority

Precondition _ logic

Edit expression

Expression 1.1 uses logical symbols to express facts

A sentence.

Is indicated _ precondition...