Visits: 122

The following is an excerpt from iso.org

ISO 15000-5:2014 Electronic Business Extensible Markup Language (ebXML) — Part 5: Core Components Specification (CCS)

ABSTRACT

ISO 15000-5:2014 describes and specifies the Core Component solution as a methodology for developing a common set of semantic building blocks that represent general types of business data, and provides for the creation of new business vocabularies and restructuring of existing business vocabularies.
ISO 15000-5:2014 can be employed wherever business information is being shared or exchanged amongst and between enterprises, governmental agencies, and/or other organizations in an open and worldwide environment. The Core Components user community consists of business and governmental users, business document modellers and business data modellers, Business Process modellers, and application developers of different organizations that require interoperability of business information. This interoperability covers both interactive and batch exchanges of business data between applications through the use of internet and web-based information exchanges, as well as traditional Electronic Data Interchange (EDI) systems.
ISO 15000-5:2014 forms the basis for standards development work of business analysts, business users and information technology specialists supplying the content for applications that will use a Core Component Library.

Forward

…
ISO 15000 consists of the following parts, under the general title Electronic Business Extensible Markup Language (ebXML):
— Part 5: Core Components Specification (CCS)
The following parts are under preparation:
— Part 1: Collaboration-protocol profile and agreement specification (ebCPP)
— Part 2: Message service specification (ebMS)
— Part 3: Registry information model specification (ebRIM)
— Part 4: Registry services specification (ebRS)

Introduction

0.1 General

This International Standard describes and specifies a new approach to the well-understood problem of the lack of information interoperability between applications in the e-business arena. Traditionally, standards for the exchange of business data have been focused on static message definitions that have not enabled a sufficient degree of interoperability or flexibility. A more flexible and interoperable way of standardizing Business Semantics is required. The Core Component solution described in this International Standard presents a methodology for developing a common set of semantic building blocks that represent the general types of business data in use today and provides for the creation of new business vocabularies and restructuring of existing business vocabularies.

1 Scope

This International Standard describes and specifies the Core Component solution as a methodology for developing a common set of semantic building blocks that represent general types of business data, and provides for the creation of new business vocabularies and restructuring of existing business vocabularies.
This International Standard can be employed wherever business information is being shared or exchanged amongst and between enterprises, governmental agencies, and/or other organizations in an open and worldwide environment. The Core Components user community consists of business and governmental users, business document modellers and business data modellers, Business Process modellers, and application developers of different organizations that require interoperability of business information. This interoperability covers both interactive and batch exchanges of business data between applications through the use of internet and web-based information exchanges, as well as traditional Electronic Data Interchange (EDI) systems.
This International Standard forms the basis for standards development work of business analysts, business users and information technology specialists supplying the content for applications that will use a Core Component Library.

ISO/IEC 19845:2015 Information technology — Universal business language version 2.1 (UBL v2.1)

ABSTRACT

ISO/IEC 19845:2015 specifies the OASIS Universal Business Language (UBL), which defines a generic XML interchange format for business documents that can be restricted or extended to meet the requirements of particular industries. Specifically, UBL provides the following:
– A suite of structured business objects and their associated semantics expressed as reusable data components and common business documents.
– A library of XML schemas for reusable data components such as “Address”, “Item”, and “Payment”, the common data elements of everyday business documents.
– A set of XML schemas for common business documents such as “Order”, “Despatch Advice”, and “Invoice” that are constructed from the UBL library components and can be used in generic procurement and transportation contexts.

Forward

…
ISO/IEC 19845 was prepared by the OASIS OpenDocument Technical Committee [as OASIS Open Document Format for Office Applications (OpenDocument) v1.0 (first edition)] and was adopted, under the PAS procedure, by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its approval by the national bodies of ISO and IEC. The content of ISO/IEC 19845 and OASIS OpenDocument UBL v2.1. is identical.

1 Introduction

Since its approval as a W3C recommendation in 1998, XML has been adopted in a number of industries as a framework for the definition of the messages exchanged in electronic commerce. The widespread use of XML has led to the development of multiple industry-specific XML versions of such basic documents as purchase orders, shipping notices, and invoices.
While industry-specific data formats have the advantage of maximal optimization for their business context, the existence of different formats to accomplish the same purpose in different business domains is attended by a number of significant disadvantages as well.
• Developing and maintaining multiple versions of common business documents like purchase orders and invoices is a major duplication of effort.
• Creating and maintaining multiple adapters to enable trading relationships across domain boundaries is an even greater effort.
• The existence of multiple XML formats makes it much harder to integrate XML business messages with back-office systems.
• The need to support an arbitrary number of XML formats makes tools more expensive and trained workers harder to find.
The OASIS Universal Business Language (UBL) is intended to help solve these problems by defining a generic XML interchange format for business documents that can be restricted or extended to meet the requirements of particular industries. Specifically, UBL provides the following:
• A suite of structured business objects and their associated semantics expressed as reusable data components and common business documents.
• A library of XML schemas for reusable data components such as “Address”, “Item”, and “Payment”—the common data elements of everyday business documents.
• A set of XML schemas for common business documents such as “Order”, “Despatch Advice”, and “Invoice” that are constructed from the UBL library components and can be used in generic procurement and transportation contexts.
A standard basis for XML business schemas provides the following advantages:
• Lower cost of integration, both among and within enterprises, through the reuse of common data structures.
• Lower cost of commercial software, because software written to process a given XML tag set is much easier to develop than software that can handle an unlimited number of tag sets.
• An easier learning curve, because users need master just a single library.
• Lower cost of entry and therefore quicker adoption by small and medium-size enterprises (SMEs).
• Standardized training, resulting in many skilled workers.
• A universally available pool of system integrators.
• Standardized, inexpensive data input and output tools.
• A standard target for inexpensive off-the-shelf business software.
UBL is designed to provide a universally understood and recognized syntax for legally binding business documents and to operate within a standard business framework such as ISO 15000 (ebXML) to provide a complete, standards-based infrastructure that can extend the benefits of existing EDI systems to businesses of all sizes. UBL is freely available to everyone without legal encumbrance or licensing fees.
UBL schemas are modular, reusable, and extensible in XML-aware ways. As the first standard implementation of ebXML Core Components Technical Specification 2.01, the UBL Library is based on a conceptual model of information components known as Business Information Entities (BIEs). These components are assembled into specific document models such as Order and Invoice. These document models are then transformed in accordance with UBL Naming and Design Rules into W3C XSD schema syntax. This approach facilitates the creation of UBL-based document types beyond those specified in this release.
UBL can also be regarded as a generic Open-edi Configuration in the perspective of the Open-edi Reference Model (ISO/IEC 14662:2010). This is described in more detail in Appendix H, The Open-edi reference model perspective of UBL (Non-Normative).

ISO/IEC 11179, Information technology — Metadata registries (MDR)

Foreword

…
Edition 3 of this part of ISO/IEC 11179 includes several enhancements to Edition 2, both in terms of the presentation of the metamodel, and its capabilities, as follows:
From a presentation perspective, these include:
use of UML 2.4.1 instead of UML 1.4 to describe the metamodel;
use of UML packages to show dependencies between various regions of the metamodel. (See 5.3.3 and 5.3.4.)
From a capability perspective, these include:
introduction of different types of metadata items (see 5.5);
support for registration of Concept Systems (see 9.1);
finer-grained conformance options (see 4.3).
ISO/IEC 11179 consists of the following parts, under the general title Information technology — Metadata registries (MDR):
Part 1: Framework
Part 2: Classification
Part 3: Registry metamodel and basic attributes
Part 4: Formulation of data definitions
Part 5: Naming and identification principles
Part 6: Registration
…

Part 3: Registry metamodel and basic attributes

Introduction

Data processing and electronic data interchange rely heavily on accurate, reliable, controllable and verifiable data recorded in databases. A prerequisite for correct and proper use and interpretation of data is that both users and owners of data have a common understanding of the meaning and representation of the data. To facilitate this common understanding, a number of characteristics, or attributes, of the data have to be defined. These characteristics of data are known as “metadata”, that is, “data that describes data”. This part of ISO/IEC 11179 provides for the attributes of data elements and associated metadata to be specified and registered as metadata items in a metadata registry (MDR).
The structure of a metadata registry is specified in the form of a conceptual data model. The metadata registry is used to keep information about data elements and associated concepts, such as “data element concepts”, “conceptual domains” and “value domains”. Generically, these are all referred to as “metadata items”. Such metadata are necessary to clearly describe, record, analyse, classify and administer data.
When considering data and metadata, it is important to distinguish between types of data/metadata, and instances of these types. Clause 5 through 11 of this part of ISO/IEC 11179 specify the types of metadata objects that form the structure of a metadata registry. A metadata registry will be populated with instances of these metadata objects (metadata items), which in turn define types of data, e.g. in an application database. In other words, instances of metadata specify types of application level data. In turn, the application database will be populated by the real world data as instances of those defined datatypes.
NOTE ISO/IEC 10027:1990, Information technology — Information resource dictionary system (IRDS) Framework and ISO/IEC TR 10032:2003, Information technology — Reference model for data management explain the concepts of different levels of modelling.
In this part of ISO/IEC 11179, clause 12 describes the basic attributes of metadata items for purposes where a complete metadata registry is not appropriate.
This part of ISO/IEC 11179 is of interest to information developers, information managers, data administrators, standards developers, application developers, business modellers and others who are responsible for making data understandable and shareable. ISO/IEC 11179 has broad applicability across subject area domains and information technologies.
This part of ISO/IEC 11179 applies to activities including:
a) the definition, specification and contents of metadata registries, including interchanging or referencing among various collections of data elements;
b) the design and specification of application-oriented data models, databases and message types for data interchange;
c) the actual use of data in communications and information processing systems;
d) interchange or reference among various collections of metadata;
e) the registration and management of semantic artifacts that are useful for data management, data administration, and data analysis;
f) the interrelation and mapping of concept systems with other concept systems, e.g., to support efforts to converge on consistency through harmonization and vetting activities;
g) the interrelation of concept systems with data held in relational databases, XML databases, knowledgebases, text, and possibly graph databases deriving from natural language text understanding systems;
h) the provision of services for semantic computing: Semantics Service Oriented Architecture, Semantic Grids, semantics based workflows, Semantic Web, etc.;
i) support for addressing semantic web considerations such as AAA (anyone can say anything about anything), non-unique names, and open world assumption;
j) the capture of semantics with more formal techniques (in addition to natural language) — First Order Logic (e.g., Common Logic), Description Logics (such as OWL-DL);
k) support of Application Development and Maintenance;
l) support of data migration, data mediation;
m) support of portals, data marts, and data warehouses;
n) support of data grids and online transaction networks;
o) ontological reasoning with metadata;
p) ontology entry point for browsing and searching metadata registries;
q) capture of associations between the published identifiers used in the ontology(s), and the concepts registered in the registry;
r) support for Ontology-driven Data Translation;
s) support for data integration & data interoperation.

1 Scope

1.1 Scope – Structure of a metadata registry

Clauses 5 through 11 specify the structure of a metadata registry in the form of a conceptual data model. While the model diagrams are presented in UML notation, this part of ISO/IEC 11179 does not assume nor endorse any specific system environment, database management system, database design paradigm, system development methodology, data definition language, command language, system interface, user interface, computing platform, or any technology required for implementation. This part of ISO/IEC 11179 does not directly apply to the actual use of data in communications and information processing systems.

1.2 Scope – Basic attributes of metadata items

Clause 12 specifies basic attributes which are required to describe metadata items, and which might be used in situations where a complete metadata registry is not appropriate (e.g. in the specification of other International

Part 4: Formulation of data definitions

Introduction

Data processing and electronic data interchange rely heavily on accurate, reliable, controllable and verifiable data recorded in databases. A prerequisite for correct and proper use and interpretation of data is that both users and owners of data have a common understanding of the meaning and representation of the data. To facilitate this common understanding, a number of characteristics, or attributes of the data have to be defined. These characteristics of data are known as “metadata”, that is, “data that describes data”. This part of ISO/IEC 11179 specifies requirements and recommendations on the formulation of data definitions that are specified in Metadata Registries. The purpose of these definitions is to specify, describe, explain, and clarify the meaning of data, to promote the standardization or reuse of data elements, and to promote data sharing and integration of information systems.
The structure of a Metadata Registry is specified in the form of a conceptual data model. The Metadata Registry is used to keep information about data elements and associated concepts, such as “data element concepts”, “conceptual domains”, and “value domains”. Generically, these are all referred to as “metadata items”. Such metadata are necessary to clearly describe, record, analyse, classify, and administer data.
The definitional requirements and recommendations specified in this part of ISO/IEC 11179 do not always apply to terminological definitions found in glossaries and language dictionaries. Differences exist between the requirements that apply in a language dictionary, and the requirements that apply in a metadata registry. The requirements for ISO/IEC 11179 are more restrictive than those for a natural language dictionary. For example, a language dictionary may have multiple definitions covering multiple senses of a term or word, whereas data definitions are developed for particular contexts and should not have multiple senses within any context. Data definitions are intended to explicate the concept or concepts, which are represented by a collection of data, a data value, a data element, or other metadata item. A single definition may be established as the reference definition, with other definitions asserted to be equivalent (e.g., a definition in one language may be established as a reference definition, with definitions in other languages asserted to be equivalent). Metadata items may have a single preferred definition within a particular context, with other deprecated definitions.
Many data definitions include terms that themselves need to be defined (e.g., “charge”, “allowance”, “delivery”). Some of these terms may have different definitions in different industrial sectors. Therefore, there is a need for most metadata registries to establish an associated glossary or terminology reference of terms used in the definitions.

1 Scope

This part of ISO/IEC 11179 specifies requirements and recommendations for constructing definitions for data and metadata. Only semantic aspects of definitions are addressed; specifications for formatting the definitions are deemed unnecessary for the purposes of ISO/IEC 11179. While especially applicable to the content of metadata registries as specified in ISO/IEC 11179-3, this part of ISO/IEC 11179 is useful broadly for developing definitions for data and metadata.
These definitional requirements and recommendations pertain to formulating definitions for data elements and other types of data constructs such as entity types, entities, relationships, attributes, object types (or classes), objects, composites, code entries, metadata items, and the data referred to by XML tags.

Part 5: Naming principles

Introduction

This part of ISO/IEC 11179 contains both principles and rules. Principles establish the premises on which the rules are based. Registry users may enforce rules as an application of this part of ISO/IEC 11179.
A naming convention is a convention (a set of rules) about names. Many naming conventions have much in common, whether it is defining a method of specifying names for common usage across application systems, or developing an organization’s internal policy on the choice of XML tags for data interchange. A naming convention may be based on principles. In addition, it may contain formal and informal inputs, such as guidelines, recommendations, company policies, programming conventions, specifications, procedures, and so on. The purpose of this part of ISO/IEC 11179 is to describe and specify these common features of naming conventions. This part of ISO/IEC 11179 is intended to have broad applicability, including areas outside of Metadata Registries.
The goal of any naming convention is to allow development of names for items that have maximum clarity and transparency of meaning, combined with concision, demanding minimal effort of interpretation by the end user, subject to the constraints of the system under which the items are processed. A naming convention can be used to form names by which information about the data is expressed, in a simplified but still understandable grammar compared to natural language rules. Ideally, the names resemble summaries of the formal definition of the information being named.
In a metadata registry, one name may be designated as the “registry name,” derived by describing the content of a metadata item in a structured way, using a set of rules, i.e. by application of a formalized naming convention. Other names for the same metadata entity may occur in any context. For example, these may be
— software system names,
— programming language names,
— report header names,
— data interchange (e.g. XML) names, and
— names in other natural languages.
Names may have varying levels of rigor applied to their formation and usage. The collection and display of all names used by any single metadata item can be a major benefit of a metadata registry. The process of deriving names from concept systems and arranging semantic components with a naming convention forms a set of consistent, meaningful registry names. Names from other contexts, which may or may not have been formed with naming conventions, and therefore may have little or no semantic content, are collected and related to the registry name, thus, contributing in a valuable way to enterprise data management.
Edition 3 of ISO/IEC 11179-3 uses the term designation in reference to most metamodel items except for the classes Namespace and Naming Convention. The designations for these classes were adopted in deference to commonly accepted usage. This part of ISO/IEC 11179 will continue to use the term name for constructs that, for purposes of this part of ISO/IEC 11179, are interchangeable with designation.
NOTE Items from the metamodel described in Edition 3 of ISO/IEC 11179-3 are italicized in this part of ISO/IEC 11179. Most multi-word designations also contain underscores between words in ISO/IEC 11179-3; the underscores have been omitted in this part of ISO/IEC 11179 for readability.
The naming principles and rules described in this part of ISO/IEC 11179 apply primarily to names of concepts, data element concepts, conceptual domains, data elements, and value domains, but can be extended to any registry content. Differing naming conventions may be applied to different sets of designatable items. This part of ISO/IEC 11179 should be used in conjunction with those which establish rules and procedures for attributing, classifying, defining, and registering items1.
This part of ISO/IEC 11179 may be used for applications that are unrelated to ISO/IEC 11179-3, i.e. this part of ISO/IEC 11179 has broad applicability for use in describing naming conventions for almost any need or purpose. The same principles apply.
In Annex A, all of the examples are given with English terminologies. However, there is an intention that those rules be effective in other natural languages, even in those languages that use ideographs such as Japanese, Chinese, or Korean, when the terminologies used in the name are controlled properly. Annex B contains a version of the rules for Asian languages.
It is out of scope of the naming rules to establish semantic equivalence of names among different languages. Naming must be supplemented by other methods such as ontologies or controlled vocabularies in establishing semantic equivalence.
This part of ISO/IEC 11179 may be applied to ISO/IEC 11179-3, i.e. describing naming conventions associated with designations of designatable items and other features of the metamodel. The following are examples of designations in the metamodel: the designation of a data element (class name: Designation; attribute: sign); the designation of classification scheme name; etc. Annex C contains a Concordance Table relating items in this part of ISO/IEC 11179 to items in ISO/IEC 11179-3.
This part of ISO/IEC 11179 does not make requirements on any specific set of conventions, e.g. specific semantic, syntactic, or lexical requirements for names.

1 Scope

This part of ISO/IEC 11179 provides instruction for naming of the following items, as defined in ISO/IEC 11179-3: concept, data element concept, conceptual domain, data element, and value domain. This part of ISO/IEC 11179 describes naming in a metadata registries (MDR); includes principles and rules by which naming conventions can be developed; and provides examples of naming conventions.

Part 6: Registration

Introduction

This part of ISO/IEC 11179 describes the procedure by which metadata items required in various application areas could be assigned an internationally unique identifier and registered in a metadata registry maintained by one or more Registration Authorities. This edition of this part of ISO/IEC 11179 supports multiple schemes for ensuring the uniqueness of the identification.
The metamodel of a metadata registry defined in ISO/IEC 11179-3 allows a metadata item to simply be identified or to be both identified and registered. A registered item may either be an administered item, meaning it has its own registration state, or it may be an attached item, which means it is attached to an administered item and shares the latter’s registration state. The registered items are included in Metadata Registries maintained by one or more Registration Authorities, to which the registered items logically and functionally belong. An organization wishing to become a Registration Authority may do so in accordance with the procedure prescribed in Annex A.
The registration process described in this part of ISO/IEC 11179 may be applied to any type of metadata item, such as those specified by ISO/IEC 11179-3: data elements, data element concepts, conceptual domains, value meanings, value domains, classification schemes, and concept systems; those specified by ISO/IEC 19763: ontologies, process models, service models, role and goal models, information models, mappings between models, and form designs; and/or custom types not specified by these standards. Each registered item is represented within a metadata registry by a registration record that documents the common administration and identification, naming and definition details together with their metadata item-specific details.
Within this part of ISO/IEC 11179, the use of “Metadata Registry” denotes an implementation of a metadata registry that is based upon ISO/IEC 11179 and that is managed by one or more Registration Authorities.

1 Scope

1.1 Statement of scope

This part of ISO/IEC 11179 defines the type of information to be specified, the conditions to be met, and the procedure(s) to be followed for each metadata item to be registered in a metadata registry. The requirements and procedures contained herein apply to all metadata items specified in ISO/IEC 11179-3 and those specified in ISO/IEC 19763. Some Registration Authorities may want to use this part of ISO/IEC 11179 to register and manage locally defined metadata item types that are not defined in ISO/IEC 11179-3 or ISO/IEC 19763.
This part of ISO/IEC 11179 addresses the common metadata that is used to document the common facilities of a metadata registry: administration, identification, naming and definition, details that can apply to any and all types of metadata items.

1.2 Exclusions

This part of ISO/IEC 11179 does not address the metadata that is specific to particular types of metadata items such as data elements and value domains. This part of ISO/IEC 11179 does NOT specify the registry’s system design, file organization techniques, storage media, programming languages, etc. to be used in its implementation.

ISO/IEC 19502:2005(en) Information technology — Meta Object Facility (MOF)

Foreword

…
ISO/IEC 19502 is related to
— ISO/IEC 19501, Information technology — Open Distributed Processing — Unified Modeling Language (UML) Version 1.4.2
— ISO/IEC 19503, Information technology — XML Metadata Interchange (XMI)
— ISO/IEC 14769, Information technology — Open Distributed Processing — Type Repository Function

Introduction

This International Standard defines a metamodel (defined using MOF), a set of interfaces (defined using ODP IDL (ITU-T Recommendation X.920 (1997) | ISO/IEC 14750:1999), that can be used to define and manipulate a set of interoperable metamodels and their corresponding models. It also defines the mapping from MOF to ODP IDL (ITU rec X920 | ISO 14750). These interoperable metamodels include the Unified Modeling Language (UML) metamodel (ISO/IEC 19501:2005), the MOF meta-metamodel, as well as future standard technologies that will be specified using metamodels. The MOF provides the infrastructure for implementing design and reuse repositories, application development tool frameworks, etc. The MOF specifies precise mapping rules that enable the CORBA interfaces for metamodels to be generated automatically, thus encouraging consistency in manipulating metadata in all phases of the distributed application development cycle. Mappings from MOF to W3C XML and XSD are specified in the XMI (ISO/IEC 19503) specification. Mappings from MOF to Java™ are in the JMI (Java Metadata Interchange) specification defined by the Java Community Process.
In order to achieve architectural alignment considerable effort has been expended so that the UML and MOF share the same core semantics. This alignment allows the MOF to reuse the UML notation for visualizing metamodels. In those areas where semantic differences are required, well-defined mapping rules are provided between the metamodels. The UML has been the subject of a separate PAS submission.
The OMG adopted the MOF (version 1.0) in November 1997. It was developed as a response to a request for proposal, issued by the OMG Analysis and Design Task Force, for Metadata repository facility (http://www.omg.org/cgi-bin/doc? cf/96-05-02). The purpose of the facility was to support the creation, manipulation, and interchange of meta models. The most recent revision of MOF, 1.4 was adopted in April 2002, and includes corrections and clarifications to the original 1.3 version, and minor modeling feature additions.
The rapid growth of distributed processing has led to a need for a coordinating framework for this standardization and ITU-T Recommendations X.901-904 | ISO/IEC 10746, Open Distributed Processing — Reference Model (RM-ODP) provides such a framework. It defines an architecture within which support of distribution, interoperability, and portability can be integrated. RM-ODP Part 2 (ISO/IEC 10746-2) defines the foundational concepts and modeling framework for describing distributed systems. RM-ODP Part 3 (ISO/IEC 10746-3) specifies a generic architecture of open distributed systems, expressed using the foundational concepts and framework defined in Part 2.
While not limited to this context, this International Standard is closely related to work on the standardization of Open Distributed Processing (ODP). In particular, the ODP Type Repository Function (ISO/IEC 14769 | Rec. X.960) references the OMG Meta Object Facility, version 1.3. This function specifies how to use the OMG MOF as a repository for ODP types.

1 Scope

This International Standard specifies the following:
a. An abstract language for specifying, constructing, and managing technology neutral metamodels: A metamodel is in effect an abstract language for some kind of metadata.
b. A framework for implementing repositories & integration frameworks (e.g., tool integration frameworks) that hold metadata (e.g., models) described by the metamodels and which uses standard technology mappings to transform MOF metamodels into metadata APIs.
This International Standard also provides the following:
a. A formal definition of the MOF meta-metamodel; that is, the abstract language for specifying MOF metamodels.
b. A mapping from arbitrary MOF metamodels to CORBA IDL that produces IDL interfaces for managing any kind of metadata.
c. A set of “reflective” CORBA IDL interfaces for managing metadata independent of the metamodel.
d. A set of CORBA IDL interfaces for representing and managing MOF metamodels.
e. An XMI format for MOF metamodel interchange (OMG XMI Specification).

2 Normative references

The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

2.1 Identical Recommendations | International Standards

ITU-T Recommendation X.902 (1996) | ISO/IEC 10746-2:1996, Open Distributed Processing — Reference Model: Foundations
ITU-T Recommendation X.903 (1996) | ISO/IEC 10746-3:1996, Open Distributed Processing — Reference Model: Architecture

2.2 International Standards

ISO/IEC 14769:2001, Information technology — Open Distributed Processing — Type Repository Function
ISO/IEC 19501:2005, Information technology — Open Distributed Processing — Unified Modeling Language (UML) Version 1.4.2
ISO/IEC 19503:2005, Information technology — XML Metadata Interchange (XMI)

ISO/IEC 19763, Information technology — Metamodel framework for interoperability (MFI)

Forward

…
The committee responsible for this document is ISO/IEC JTC 1, Information technology, SC 32, Data management and interchange. ISO/IEC 19763 consists of the following parts, under the general title Information technology — Metamodel framework for interoperability (MFI):
— Part 1: Framework
— Part 3: Metamodel for ontology registration
— Part 5: Metamodel for process model registration
— Part 6: Registry Summary
— Part 10: MFI Core model and basic mapping
— Part 12: Metamodel for information model registration
The following parts are under preparation:
— Part 7: Metamodel for service registration
— Part 8: Metamodel for role and goal registration
— Part 9: On demand model selection
— Part 13: Metamodel for forms registration
…

Part 10: MFI Core model and basic mapping

Introduction

Industrial consortia have engaged in the standardization of domain-specific business objects including business process models and software components using common modelling facilities and interchange facilities such as UML and XML. They are very active in standardizing domain-specific business process models and standard modelling constructs such as data elements, entity profiles, and value domains.
However, to promote interoperability across business domains, a generic framework for registering a variety of models and the mapping between them is required. This part of ISO/IEC 19763 provides a core metamodel as the basis for the other parts of ISO/IEC 19763 and a metamodel for registering the mappings between models registered in those other parts of ISO/IEC 19763.
NOTE UML is a trademark of the Object Management Group.

1 Scope

The primary purpose of this International Standard is to specify a metamodel framework for interoperability. This part of ISO/IEC 19763 specifies the metamodel that provides a facility to register administrative information and common semantics of models and mapping between two models.
This part of ISO/IEC 19763 does not specify the metamodel of models in a specific language, but provides a common core metamodel for the other parts of ISO/IEC 19763, each of which specifies a metamodel for a registry that can register models of a specific type, such as ontologies, process models or information models, in a number of different languages.
This part of ISO/IEC 19763 also provides a metamodel for registering the mappings between two models registered in those other parts of ISO/IEC 19763.
This part of ISO/IEC 19763 utilises the common facilities specified in ISO/IEC 11179-3. ISO/IEC 11179 (all parts) specifies a metadata registry (MDR). These common facilities provide the ability to identify and register models and their associated model elements and modelling languages within a metadata registry used to register models.

Part 12: Metamodel for information model registration

introduction

There is an increasing demand for systems to interoperate by exchanging data. For these data exchanges to be meaningful, it is essential that the business information requirements that are met by the data stored in these systems are understood so that suitable data exchange mechanisms can be developed.
Business information requirements, including the semantic meaning of the information, are often represented by information models before the databases that are an integral part of the systems are designed. These models are often called logical models. The subsequent design of the database structure can also be considered to be another form of information model.
Where there is an overlap of the universe of discourse of two systems, the information models for these two systems can be registered using the facilities specified by this part of ISO/IEC 19763. The mappings between these two models can then be registered using the facilities specified by ISO/IEC 19763-10. An interface between the two systems can then be designed, enabling the two systems to interoperate by exchanging information.

1 Scope

The primary purpose of the multipart standard ISO/IEC 19763 is to specify a metamodel framework for interoperability. This part of ISO/IEC 19763 specifies a metamodel for registering information models. This metamodel was developed taking into account two distinct types of information models such as
— those that are used to document the information requirements of a particular area of interest, and
— those that represent the structure of a database which are often expressed using a Database Definition Language (DDL).
Information models that represent information requirements can be developed using a number of different common diagramming techniques and notations. The metamodel specified in this part of ISO/IEC 19763 was developed to cover the registration of models expressed using the following techniques and notations:
— Express-G, an ISO standard entity-relationship modelling notation, as described in Reference [8];
— IDEF1X, a US Federal standard entity-relationship modelling notation, as described in References [6] and [12];
— the entity-relationship modelling notation first developed by Harry Ellis and Richard Barker and later adopted by Oracle for its CASE*Method and by the UK’s CCTA for SSADM (Structured Systems Analysis and Design Method), as described in Reference [2];
— the UML Class Diagram notation, as described in References [13] and [14];
— the original entity-relationship modelling notation proposed by Peter Chen, as described in Reference [4];
— the Information Engineering entity-relationship modelling notation, as described in Reference [11].
It is understood that these selected techniques represent all of the essential features of all information modelling techniques used to represent information requirements.
The registration of information models that represent the structure of a database is limited in the metamodel specified in this part of ISO/IEC 19763 to those database structures that conform to the Core SQL specification. Core SQL is the set of features defined in the conformance requirements specified in ISO/IEC 9075-2 and ISO/IEC 9075-11.
The registration of information models that are expressed using notations such as Object Role Modeling (ORM) and “Natural language Information Analysis Method” (NIAM), collectively known as fact-based models, is out of scope for this part of ISO/IEC 19763.

ISO 20022 Financial services — Universal financial industry message scheme

Forward

ISO 20022 consists of the following parts, under the general title Financial services — Universal financial industry message scheme:
— Part 1: Metamodel
— Part 2: UML profile
— Part 3: Modelling
— Part 4: XML Schema generation
— Part 5: Reverse engineering
— Part 6: Message transport characteristics
— Part 7: Registration
— Part 8: ASN.1 generation
ISO 20022-1:2013, ISO 20022-2:2013, ISO 20022-3:2013, ISO 20022-4:2013, ISO 20022-5:2013, ISO 20022-6:2013, ISO 20022-7:2013 and ISO 20022-8:2013 will be implemented by the Registration Authority by no later than the end of May 2013, at which time support for the concepts set out within them will be effective. Users and potential users of the ISO 20022 series are encouraged to familiarize themselves with the 2013 editions as soon as possible, in order to understand their impact and take advantage of their content as soon as they are implemented by the Registration Authority. For further guidance, please contact the Registration Authority.

Part 1: Metamodel

Introduction

This International Standard defines a scalable, methodical process to ensure consistent descriptions of messages throughout the financial services industry.
The purpose of this International Standard is to describe precisely and completely the externally observable aspects of financial services messaging in a way that can be verified independently against operational messaging.
The trigger for the creation of this International Standard was the rapid growth in the scale and sophistication of messaging within financial services during the 1990s using ISO 15022. The financial services industry (from hereon referred to as “the industry”) created the first version of this International Standard as the successor to ISO 15022 in response to that trigger. Since ISO 15022, the industry has broadened the scope from securities to the entire industry for this International Standard.
This International Standard is based on open technology standards, which historically have evolved more rapidly than the industry itself. Consequently, this International Standard adopted a model-driven approach where the model of the industry’s messaging can evolve separately from the evolution of the messaging technology standards. The period during which this International Standard has emerged followed the widespread adoption of the World Wide Web (the Web) for business. XML (eXtensible Mark-up Language) emerged as the de facto standard for document representation on the Web and it became the first syntax for ISO 20022.
The modelling process is further refined into three levels which, in addition to the messaging technology standard, is why this International Standard is based on four levels: the Scope level, the Conceptual level, the Logical level and the Physical level.
This four-level approach is based on the first four levels of the Zachman Framework. The remaining two levels of the Zachman Framework are equivalent to the implementations and the operational levels, respectively.
In this part of ISO 20022, the first, second and third levels are described in UML (Unified Modelling Language) because it is widely supported and supports multiple levels of abstraction. The models created in accordance with this International Standard are technology independent in that they do not require any particular physical expression or implementation. Such models aim to describe all parts of the message exchange. The models form the definition of the protocol between participants exchanging messages. This International Standard defines a method that describes a process by which these models can be created and maintained by the modellers.
The models and the Physical level artefacts are stored in a central repository, serviced by a Registration Authority. This International Standard’s repository is available on the World Wide Web and offers public access for browsing.
The Repository is organized into two areas:
— A DataDictionary containing the industry model elements likely to have further or repeated use.
— A BusinessProcessCatalogue that contains models describing specific message definitions and business processes, and physical syntax implementations.
This International Standard is organized into the following parts.
— This part of ISO 20022 describes in MOF (Meta-Object Facility) the metamodel of all the models and the Repository.
— ISO 20022-2 covers the UML profile, a grounding of general UML into a specific subset defined for this International Standard (to be used when UML is selected to define the models).
— ISO 20022-3 describes a modelling method to produce models for this International Standard.
— ISO 20022-4 covers XML schema generation rules to transform a Logical level model into a Physical level description in the syntaxes.
— ISO 20022-5 covers logical model alignment and reverse engineering of existing message syntaxes.
— ISO 20022-6 covers message transport characteristics that define the quality of service required by the business process definitions so that they can operate successfully.
— ISO 20022-7 describes the process of managing the registration of models and physical syntax implementations.
— ISO 20022-8 gives ASN.1 syntax generation rules to transform a Logical level model into a Physical level description in ASN.1.

1 Scope

This part of ISO 20022 consists of:
— the overall description of the modelling approach;
— the overall description of the ISO 20022 Repository contents;
— a high-level description of the input to be accepted by the Registration Authority to feed/modify the Repository’s DataDictionary and BusinessProcessCatalogue;
— a high-level description of the Repository output to be made publicly available by the Registration Authority.
BusinessTransactions and Message Sets complying with ISO 20022 can be used for electronic data interchange amongst any industry participants (financial and others), independently of any specific communication network. Network-dependent rules, such as message acknowledgement and message protection, are outside the scope of ISO 20022.

Part 2: UML profile

ABSTRACT

ISO 20022-2:2013 defines the UML Profile for ISO 20022. In essence, it defines how to use UML to create models that conform to the ISO 20022 Metamodel, which is defined in ISO 20022-1:2013. In so doing, it defines a UML-based concrete syntax for the Metamodel. It does not preclude the specification of additional concrete syntaxes for the Metamodel, such as a textual concrete syntax.
The Profile defines how to represent in UML each of the Metamodel’s Scope Level Elements (Level 1), Business Level Elements (Level 2) and Message Level Elements (Level 3), as well as Metamodel Elements that are scoped across the levels.
Therefore, the Profile covers all of the Metamodel’s Packages, except for the following:
· ISO20022::Metamodel::ConceptualLevel::MessageTransport
· ISO20022::Metamodel::LogicalLevel::Reversing
· ISO20022::Metamodel::LogicalToPhysicalTransformation
· ISO20022::Metamodel::PhysicalLevel
The Profile also covers the ISO20022::TypeLibrary Package, upon which the Metamodel has some dependencies.
ISO 20022-2:2013 is only applicable when UML is used.

Part 4: XML Schema generation

1 Scope

This part of ISO 20022 was prepared to complement the ISO 20022 Metamodel, as specified in ISO 20022-1, with the XML syntax transformation rules to be applied by the ISO 20022 Registration Authority in order to translate an ISO 20022 compliant MessageDefinition into an XML Schema for the description and validation of XML Messages.
It specifies the transformation rules from level 3 to level 4. It is a deterministic transformation, meaning that the resulting XML Schema is completely predictable for a given MessageDefinition. There is neither manual input to the transformation itself nor manual adjustment to the result of the transformation.