National foreword

This British Standard is the UK implementation of ISO/IEC 19763‑7:2026. It supersedes BS ISO/IEC 19763‑7:2015, which is withdrawn.

The UK participation in its preparation was entrusted to Technical Committee IST/40, Data management and interchange.

A list of organizations represented on this committee can be obtained on request to its committee manager.

Contractual and legal considerations

This publication has been prepared in good faith, however no representation, warranty, assurance or undertaking (express or implied) is or will be made, and no responsibility or liability is or will be accepted by BSI in relation to the adequacy, accuracy, completeness or reasonableness of this publication. All and any such responsibility and liability is expressly disclaimed to the full extent permitted by the law.

This publication is provided as is, and is to be used at the recipient’s own risk.

The recipient is advised to consider seeking professional guidance with respect to its use of this publication.

This publication is not intended to constitute a contract. Users are responsible for its correct application.

Compliance with a British Standard cannot confer immunity from legal obligations.

This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 October 2026.

Foreword

ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work.

The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives or www.iec.ch/members_experts/refdocs).

ISO and IEC draw attention to the possibility that the implementation of this document may involve the use of (a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any claimed patent rights in respect thereof. As of the date of publication of this document, ISO and IEC have not received notice of (a) patent(s) which may be required to implement this document. However, implementers are cautioned that this may not represent the latest information, which may be obtained from the patent database available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held responsible for identifying any or all such patent rights.

Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.

For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISO's adherence to the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www.iso.org/iso/foreword.html. In the IEC, see www.iec.ch/understanding-standards.

This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 32, Data management and interchange.

This second edition cancels and replaces the first edition (ISO/IEC 19763‑7:2015), which has been technically revised.

The main changes are as follows:

Additional metaclasses and enumerated datatypes have been introduced in the metamodel of MFI service model registration to support registration of heterogeneous services using multiple protocols, including Invocation_Way, Message_Exchange_Pattern, Protocol, and Message_Data_Format.
Additional metaclasses and enumerated datatypes have been introduced in the metamodel of MFI service model registration to support registration of service evolution, including Service_Evolution, Service_Change, Change_Type, and Change_Impact.
Annex B has been updated, providing registration examples, including an OpenAPI service registration example and a PROTO service registration example.

A list of all parts in the ISO/IEC 19763 series can be found on the ISO and IEC websites.

Any feedback or questions on this document should be directed to the user’s national standards body. A complete listing of these bodies can be found at www.iso.org/members.html and www.iec.ch/national-committees.

Introduction

With the rapid development of Service Oriented Computing (SOC), more and more computing resources are presented in the form of web services. Meanwhile, business integration based on web services is becoming a popular application development method. A web service is a kind of Web based application that encapsulates one or more computing modules and is designed to support interoperable machine-to-machine interaction over a network.

In Web Service registration and management, ebXML RegRep is a standard defining the Service interface, protocols and information model for an integrated registry and repository, which provides basic support for publishing and discovering Web Services within and across enterprises. Nevertheless, keyword matching is the basic service discovery method in ebXML RegRep, thus the discovery results will be inevitably inaccurate, and the discovery process will be time-consuming. When business information interchange and integration becomes increasingly frequent, major work in web service discovery should be processed by machine. This shift necessitates the semantic description of administrative and evolution-related metadata of services, along with the provision of corresponding registration and management mechanisms. Moreover, with the rapid growth of service networks and service ecosystems, where large numbers of heterogeneous services coexist and dynamically evolve, the demand for interoperability becomes increasingly critical. Services characterized by more diverse communication protocols, description languages, message exchange patterns, and data formats must be capable of sharing and interaction. To support this, service registration frameworks must be enhanced to ensure that services can be discovered, composed, and evolved within highly dynamic and diverse digital ecosystems.

This document intends to provide a generic framework for registering administrative and evolution information about web services in an explicit way. The relationship between MFI service model registration, the service registry, and service models expressed in different service description languages is illustrated in Figure 1.

1 Scope

The primary purpose of the ISO/IEC 19763 series is to specify a metamodel framework for interoperability. This document specifies a metamodel for registering administrative and evolution information of models of services, facilitating interoperability through the reuse of services.

This document is only applicable to web services whose capabilities are described by some web service description language (see Annex A for examples of such languages). Figure 1 shows the scope of this document.

2 Normative references

3 Terms and definitions

4 Abbreviated terms

5 Conformance

5.1 General

5.2 Degree of conformance

5.3 Implementation Conformance Statement (ICS)

6 MFI Service model registration

6.1 Overview of MFI Service model registration

6.2 Associations between MFI Service model registration and other parts in MFI

6.3 Structure of MFI Service model registration

Bibliography