HOME   Cart(0)   Quotation   About-Us Policy PDFs Standard-List
www.ChineseStandard.net Database: 189760 (18 Oct 2025)

GB/T 32392.7-2018 English PDF

US$644.00 · In stock
Delivery: <= 5 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 32392.7-2018: Information technology -- Metamodel framework for interoperability (MFI) -- Part 7: Metamodel for service model registration
Status: Valid
Standard IDContents [version]USDSTEP2[PDF] delivered inStandard Title (Description)StatusPDF
GB/T 32392.7-2018English644 Add to Cart 5 days [Need to translate] Information technology -- Metamodel framework for interoperability (MFI) -- Part 7: Metamodel for service model registration Valid GB/T 32392.7-2018

PDF similar to GB/T 32392.7-2018


Standard similar to GB/T 32392.7-2018

GB/T 39105   GB/T 38555   GB/T 37036.2   GB/T 32392.8   GB/T 32392.9   GB/T 32392.5   

Basic data

Standard ID GB/T 32392.7-2018 (GB/T32392.7-2018)
Description (Translated English) Information technology -- Metamodel framework for interoperability (MFI) -- Part 7: Metamodel for service model registration
Sector / Industry National Standard (Recommended)
Classification of Chinese Standard L72
Classification of International Standard 35.040
Word Count Estimation 34,322
Date of Issue 2018-03-15
Date of Implementation 2018-10-01
Issuing agency(ies) State Administration for Market Regulation, China National Standardization Administration

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


---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Information technology--Metamodel framework for interoperability(MFI)--Part 7. Metamodel for service model registration ICS 35.040 L72 National Standards of People's Republic of China Information Technology Interoperability Metamodel Framework (MFI) Part 7. Service model registration metamodel Part 7. Metamodelforservicemodelregistration (ISO /IEC 19763-7.2015, IDT) Published on.2018-03-15 2018-10-01 implementation General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China China National Standardization Administration issued

Content

Foreword I Introduction II 1 Scope 1 2 Normative references 1 3 Terms and definitions, abbreviations 2 3.1 Terms and Definitions 2 3.2 Abbreviations 3 4 Compliance 4 4.1 Summary 4 4.2 Compliance 4 4.3 Implementation of Declaration of Conformity 4 5 MFI Service Model Registration 4 5.1 MFI Service Model Registration Overview 4 5.2 Relationship between MFI Service Model Registration and other parts of MFI 6 5.3 Metaclass 7 in the service model registration metamodel Appendix A (informative) Service Description Language List 15 Appendix B (informative) Registration example of the service model registration metamodel 16 Reference 30

Foreword

GB/T 32392 "Information Technology Interoperability Metamodel Framework (MFI)" is divided into the following sections. --- Part 1. Reference model; --- Part 2. Core model; --- Part 3. Ontology registration metamodel; --- Part 4. Model mapping metamodel; --- Part 5. Process model registration metamodel; --- Part 7. Service model registration metamodel; --- Part 8. Role and target model registration metamodel; --- Part 9. On-demand model selection. This part is part 7 of GB/T 32392. This part is drafted in accordance with the rules given in GB/T 1.1-2009. This section uses the translation method equivalent to the ISO /IEC 19763-7.2015 Information Technology Interoperability Meta Model Framework (MFI) Part 7. Service Model Registration Metamodel. The documents of our country that have a consistent correspondence with the international documents referenced in this part are as follows. GB/T 32392.5-2018 Information technology interoperability metamodel framework (MFI) Part 5. Process model registration metamodel (ISO /IEC 19763-5.2015, IDT) GB/T 32392.8-2018 Information Technology Interoperability Metamodel Framework (MFI) Part 8. Role and Target Model Registration Metamodel (ISO /IEC 19763-8.2015, IDT) Please note that some of the contents of this document may involve patents. The issuing organization of this document is not responsible for identifying these patents. This part is proposed and managed by the National Information Technology Standardization Technical Committee (SAC/TC28). This section drafted by. Wuhan University, China Electronics Technology Standardization Institute, Kingdee Software (China) Co., Ltd. The main drafters of this section. He Keqing, Feng Zaiwen, Wang Wei, Wang Jian, He Fei, Wang Jing, Hu Bo.

Introduction

With the rapid development of service-oriented computing technology, more and more computing resources are reflected in the form of Web services. At the same time, base Business integration for services is also becoming a popular approach to application development. Service is a web-based application that packages Encloses one or more computing units that support interoperable interaction between machines and machines on the Internet. In Web services registration and management, ebXMLRegRep is a service interface, protocol and information model defined for integration. A specification for registry and repository that provides basic support for service registration and discovery within an enterprise or across a enterprise. However, ebXML The most basic service discovery method in RegRep is keyword-based query, which not only inevitably leads to inaccurate query results, but also makes The query process is very time consuming. When business information exchange and integration become frequent, the main work in service discovery should be carried out through machines. Automatic processing. Therefore, service information (including functional and non-functional information) needs to be described by semantics, and corresponding registration and management are provided. Mechanisms, through standardized registration information, help users find suitable services in a large number of service resources, while promoting various heterogeneous services Integration and semantic interoperability between descriptions. This section provides a general framework for registering functional and non-functional information of a service through a display, through specification registration. Information helps users discover the right service. Information Technology Interoperability Metamodel Framework (MFI) Part 7. Service model registration metamodel

1 Scope

The main goal of GB/T 32392 is to build a metamodel framework that supports interoperability. This section defines a registration service model in detail. The metamodel can facilitate interoperability between services through the reuse of services. This section only applies to Web services that can be described by a service description language (see Appendix A for examples of these languages). Figure 1 exhibition The scope of the study in this section is shown. Note. The model does not need to be stored in the registry before registration. Figure 1 The scope of this section

2 Normative references

The following documents are indispensable for the application of this document. For dated references, only dated versions apply to this article. Pieces. For undated references, the latest edition (including all amendments) applies to this document. Note. The terms and definitions of the following referenced international standards are used in Chapter 3 Terms and Definitions. ISO /IEC 19763-5 Information Technology Interoperability Metamodel Framework Part 5. Process Model Registration Metamodel (Information technology-Metamodelframeworkforinteroperability(MFI)-Part 5.Metamodelforprocessmodelregis- Tration) ISO /IEC 19763-8 Information technology interoperability metamodel framework - Part 8. Role and target model registration metamodel (In- formationtechnology-Metamodelframeworkforinteroperability(MFI)-Part 8.Metamodelforrole Andgoalmodelregistration) ISO /IEC 19763-10 Information technology interoperability metamodel framework Part 10. Core model and basic mapping (Infor- mationtechnology-Metamodelframeworkforinteroperability(MFI)-Part 10.Coremodelandbasic Mapping) 3 terms and definitions, abbreviations 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 Compliance

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 MFI Service Model Registration

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...

Tips & Frequently Asked Questions:

Question 1: How long will the true-PDF of GB/T 32392.7-2018_English be delivered?

Answer: Upon your order, we will start to translate GB/T 32392.7-2018_English as soon as possible, and keep you informed of the progress. The lead time is typically 3 ~ 5 working days. The lengthier the document the longer the lead time.

Question 2: Can I share the purchased PDF of GB/T 32392.7-2018_English with my colleagues?

Answer: Yes. The purchased PDF of GB/T 32392.7-2018_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet.

Question 3: Does the price include tax/VAT?

Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countries

Question 4: Do you accept my currency other than USD?

Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.