GB/T 19256.5-2022Electronic business extensible markup language (ebXML) - Part 5: Core components specification (English PDF)

6.1.4.2.3 of GB/T 19256.9-2006), rules for BIE dictionary entry names (see 4.5.3.4, GB/T 19256.9-

2006's 6.1.4.2.4), DT definition rules (see 4.5.4.2, GB/T 19256.9-2006's 6.1.4.3.3), DT dictionary entry

Rules for item names (see 4.5.4.3, 6.1.4.3.4 of GB/T 19256.9-2006) and allowed expressions (see 4.5.4.6,

6.1.4.3.5 of GB/T 19256.9-2006);

h) Delete the constraint language of context (see 6.2.1.2 of GB/T 19256.9-2006);

i) Changed the approved context category (see 5.3.1, 6.2.2 of GB/T 19256.9-2006), description rules of business process context

(see 5.3.2.1, 6.2.2.1 of GB/T 19256.9-2006), description rules for product classification context (see 5.3.2.2,

6.2.2.2 of GB/T 19256.9-2006), description rules of industry classification context (see 5.3.2.3, GB/T 19256.9-2006

6.2.2.3), the description rules of the official constraint context (see 5.3.2.5, 6.2.2.5 of GB/T 19256.9-2006), business process

The description rules of role context (see 5.3.2.6, 6.2.2.6 of GB/T 19256.9-2006), the description rules of supporting role context

(see 5.3.2.7, 6.2.2.7 of GB/T 19256.9-2006), description rules of system capability context (see 5.3.2.8,

6.2.2.8 of GB/T 19256.9-2006), changed the description rules of geopolitical context (see 5.3.2.4, GB/T 19256.9-

6.2.2.4 of.2006);

j) Change the value rules of the context value (see 5.3.3, 6.2.3 of GB/T 19256.9-2006);

k) Deleted the description rules of the CC context constraint language (see 6.2.4 of GB/T 19256.9-2006);

l) Delete the storage of CC context in the registration system/repository (see Chapter 7 of GB/T 19256.9-2006);

m) Increase the elaboration of standard compliance (see Chapter 6);

n) Changed "Approved CCT, Content Component Supplementary Components, and Allowed Designations" to "Approved CCT" "Approved

CCT Content Components and Supplementary Components" "Permissible Expressions" (see Appendix B, Appendix C, Appendix D, GB/T 19256.9-

Chapter 8 of.2006);

o) Added the definition of basic types (see Appendix A).

This document is equivalent to ISO 15000-5.2014 "XML-based e-commerce Part 5.Core Component Specification (CCS)".

The following minimal editorial changes have been made to this document.

--- In order to coordinate with existing standards, change the name of the standard to "XML-based e-commerce Part 5.Core Component Specification";

---Supplemented the attributes of "Participants.Details" in Figure 1 and "Trade Participants.Details" in Figure 3;

---Added examples in [C10], [C11], [C15], [C17] in 4.5.2.5.

---Changed references.

Please note that some contents of this document may refer to patents. The issuing agency of this document assumes no responsibility for identifying patents.

0.1 Summary

GB/T 19256 currently intends to include the following parts.

--- Part 1.Message Service Core Specification. The purpose is to provide various organizations with a method independent of the communication protocol to exchange

Electronic business messages.

--- Part 2.Statement of applicability of message services. The aim is to provide "just enough" to achieve ISO 15000-1.2021

The design principles and the B2B messaging specification for simpler Web services.

--- Part 3.Registration and repository. The purpose is to provide registration and storage mechanisms for metadata types and services.

--- Part 5.Core component specification. The purpose is to provide a core component design method for expressing business data.

--- Part 8.Message design rules. The purpose is to provide a set of methods for designing business messages for the business based on the core components.

New sections may be added in the future.

This document describes a new approach to interoperability between e-business domain applications. Traditional business data exchange standards

To focus on static information, this can not achieve satisfactory results. Therefore, a more flexible and interoperable business language is required

method of standardization.

The core components of this document provide a means of developing a common set of semantic building blocks that represent

common type of business data used), and also provides methods for generating new business vocabulary and reconstructing existing business vocabulary.

0.2 Overview

This document presents a method for identifying, documenting and maximizing the reuse of business information to support and enhance interoperability across business processes

active. This document is concerned with both human-readable and machine-processable representations of information.

The core component method of this document is to standardize semantics in a syntax-independent manner, so it is more flexible and convenient. core structure

As an integral part of the ebXML framework, it facilitates the application of different syntaxes such as XML and UN/EDIFACT

Partners use business semantics in the same way, and both syntaxes are based on the same core building blocks. This enables cross-grammar, cross-industry

A clear mapping is formed between different messages across different regions.

Solutions based on business processes and core components obtain information about the business reasons for changes in message semantics and structure.

In the past, these changes would have caused data model incompatibility and subsequent lack of interoperability, while the core component mechanism can recognize these models.

Therefore, the incompatibility between models will be reduced without abandoning the entire model due to incompatibility.

0.3 Key concepts

This document is based on two abstract concepts. core components and business information entities. Here we first introduce its concepts and definitions, and then give examples,

Its details will be described in Chapters 4 and 5.

Note. "Core Component (CC)" is a generic term that includes Basic Core Components (BCC), Associated Core Components (ASCC), Aggregate Core Components (ACC) and their

Associated Core Component Type (CCT). "Business Information Entity (BIE)" is also a general term, including Basic Business Information Entity (BBIE), Association

Service Information Entity (ASBIE) and Aggregated Service Information Entity (ABIE).

0.4 Key concepts of core components

The core concept of this document is CC. CC is a semantic building block and the basis for constructing all electronic business messages.

CC includes four different types. BCC, ASCC, CCT and ACC, whose concepts are described and defined in Chapter 3.

Figure 1 Example of ASCC

Figure 1 gives an example of an ASCC.

---3 ACC. participant.details, contact information.details, address.details;

---Each ACC has many attributes (that is, business characteristics);

---ACC "participant.details" has 5 attributes ("name", "role", "description", "main contact information", "post.address");

--- ACC "Contact.Detail" has 3 attributes ("Type" "Job Position" "Main");

---ACC "address.detail" has 4 attributes ("street name" "free form" "postal code" and "country").

These attributes are Basic Core Components (BCC), and each attribute represents a single business characteristic, and its allowed values are defined by data type.

row definition.

In the above example.

--- "Name" "Description" "Job Position" "Street Name" "Freeform" and "Zip Code" are "Text" data types;

--- "role" "type" is the "code" data type;

--- "Primary Contact" is the "Indicator" data type;

--- "Country" is the "Identifier" data type;

The other two attributes are associated core components, both of which express a complex set of business characteristics, and their structure is determined by another associated aggregate core

Heart components are defined. In the above example, "Participant.Main contact information" and "Participant.Post.Address" are the core components of the association,

Defined by ACC "Contact.Detail" and "Address.Detail" respectively.

Both CC and BIE have attributes defined by data types (DT).

DT represents the range of a core component attribute value. A DT is based on a CCT, but may contain content components and/or complements for that CCT

Constraints that fill the set of values for the component.

The relationship between various CC elements is shown in Figure 2.

Figure 2 CC overview

0.5 Key concepts of business information entities

The main difference between CC and BIE is the presence or absence of business context. The business context is when CC is used in a specific business environment

Mechanisms for qualifying semantics. Once the business context is identified, the CC can be distinguished, and the required constraints can be specified when using the CC.

The "business process" context describes the use of messages and their contents at a high level.

When using CC in a real business environment, it becomes BIE, and BIE is the result of using CC in a specific business context.

There is a specific relationship between CC and BIE. CC and BIE are complementary in many ways. CC is the process of creating interoperable business

It is also the key to creating business documents from controlled vocabularies.

ABIE is a piece of business data or a set of business data with unique semantics in a specific business context.

There are three types of BIE.

a) BBIE;

b) ABIE;

c) ASBIE.

BBIE is the most basic type, which is the use of BCC in a specific business context.

When an attribute of an ABIE is a complex attribute and has the structure of another ABIE, an ASBIE can be used to represent the attribute.

ASBIE is based on ASCC and based on a specific business context.

Figure 3 ASBIE

Figure 3 is an example of an ASBIE.

---3 ABIEs. trade participants.details, person in charge contact information.details, structured address.details;

---Each ACC has many attributes (that is, business characteristics);

--- ABIE "Trade Participants. Details" has 4 attributes ("Name", "Role", "Principal Contact Information", "Post. Structured

site");

--- ABIE "Person in Charge. Details" has 2 attributes ("Type" "Job Position");

--- ABIE "StructuredAddress.Detail" has 2 attributes ("Postal Code" and "Country").

These 6 attributes are BBIE, all represent a single business feature, and its allowable values are defined by data types.

--- "Name" "Job Position" and "Zip Code" are "Text" data types;

--- "role" and "type" are "code" data types;

--- "Country" is the "Identifier" data type;

The other two attributes are Associated Business Information Entities (ASBIEs), both expressing a complex set of business characteristics and whose structure is determined by another

Associated Aggregated Business Information Entities (ABIEs) to define.

--- "Trade participant. The main contact information of the person in charge" and "Trade participant. Post. Structured address" are related business information

entity;

---The structure of these two ASBIEs is determined by the two ABIEs "Contact Information.Details" and "Structured Address.Details" respectively

definition.

The relationship between CC and BIE is shown in Figure 4.

Figure 4 Relationship between CC and BIE

XML-Based Electronic Commerce

Part 5.Core component specification