GB/T 19256.5-2022 English PDFUS$694.00 ยท In stock
Delivery: <= 5 days. True-PDF full-copy in English will be manually translated and delivered via email. GB/T 19256.5-2022: Electronic business extensible markup language (ebXML) - Part 5: Core components specification Status: Valid GB/T 19256.5: Historical versions
Basic dataStandard ID: GB/T 19256.5-2022 (GB/T19256.5-2022)Description (Translated English): Electronic business extensible markup language (ebXML) - Part 5: Core components specification Sector / Industry: National Standard (Recommended) Classification of Chinese Standard: L67 Classification of International Standard: 35.040 Word Count Estimation: 34,314 Date of Issue: 2022-12-30 Date of Implementation: 2023-07-01 Older Standard (superseded by this standard): GB/T 19256.9-2006 Issuing agency(ies): State Administration for Market Regulation, China National Standardization Administration GB/T 19256.5-2022: Electronic business extensible markup language (ebXML) - Part 5: Core components specification---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. ICS 35.040 CCSL67 National Standards of People's Republic of China Replace GB/T 19256.9-2006 XML-Based Electronic Commerce Part 5.Core component specification Posted on 2022-12-30 2023-07-01 implementation State Administration for Market Regulation Released by the National Standardization Management Committee table of contentsPreface I Introduction III 1 Scope 1 2 Normative references 1 3 Terms and Definitions 1 4 Core component framework 5 4.1 Overview 5 4.2 Core components 5 4.3 Data types 7 4.4 Business Information Entity 7 4.5 Naming rules 8 4.6 CC Library (CCL) 12 5 context 12 5.1 Overview 12 5.2 Context overview 12 5.3 Approved context categories 13 6 Standards compliance15 Appendix A (Normative) Basic Type 16 Appendix B (Normative) Approved CCT 17 Appendix C (Normative) Approved CCT Content Components and Supplementary Components 19 Appendix D (Normative) Permitted expressions 23 Reference 24forewordThis document is in accordance with the provisions of GB/T 1.1-2020 "Guidelines for Standardization Work Part 1.Structure and Drafting Rules for Standardization Documents" drafting. This document is part 5 of GB/T 19256 "E-Commerce Based on XML". GB/T 19256 has published the following parts. --- Part 5.Core component specification; --- Part 8.Message design rules. This document replaces GB/T 19256.9-2006 "XML-Based Electronic Commerce Part 9.Core Components and Business Information Entities Specification", GB/T 19256.9-2006 shall be abolished from the date of implementation of this document. Compared with GB/T 19256.9-2006, this document except the structure In addition to adjustments and editorial changes, the main technical changes are as follows. a) The "Introduction" has been subdivided, and the key concepts of the.2006 edition have been changed and included (see the introduction, GB/T 19256.9-2006 "Introduction", Chapter 5); b) Changed the definitions of some terms in "Terms and Definitions" (see Chapter 3, 3.1 of GB/T 19256.9-2006), added "library Class" terms and definitions (see 3.30); c) Deleted "symbol" (see 3.2 of GB/T 19256.9-2006), deleted "consistency" (see GB/T 19256.9-2006 Chapter 4); d) Added a description of the rules that the core components should follow (see 4.1); e) The definition rules of the core components of the elements (see 4.5.2.4), the rules of the number of occurrences (see 4.5.2.6) are added, and the element "BIE" is added Rules for the number of occurrences (see 4.5.3.5), rules for the number of "DT" occurrences (see 4.5.4.4) and allowed values (see 4.5.4.5); f) The general rules of element CC (see 6.1.4.1.2 of GB/T 19256.9-2006), defined rules (see 6.1.4.1.3 of GB/T 19256.9-2006), the rules for deleting redundant words in characteristic words (see GB/T 19256.9-2006 C28 in 6.1.4.1.4), delete the general rules of the element BIE (see 6.1.4.2.2 of GB/T 19256.9-2006), DT General rules (see 6.1.4.3.2 of GB/T 19256.9-2006) and CC catalogs (see GB/T 19256.9-2006 6.1.5) and BIE catalog (see 6.1.6 of GB/T 19256.9-2006); g) Changed the rules for the entry names of the element core component dictionary (see 4.5.2.5, 6.1.4.1.4 of GB/T 19256.9-2006), CC Rules for item names (see 4.5.2.3, 6.1.4.1.4 of GB/T 19256.9-2006), BIE definition rules (see 4.5.3.3, 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. This document is proposed and managed by the National Electronic Business Standardization Technical Committee (SAC/TC83). This document is drafted by. China Jiliang University, China National Institute of Standardization, Weikai Testing Technology Co., Ltd., Shenzhen International Research Institute of Tsinghua University Graduate School, Langda Network Technology (Zhejiang) Co., Ltd., Shenzhen Academy of Inspection and Quarantine, Shenzhen University, Jiangxi Quality and Standardization Research Institute Research Institute, Chengdu Libang System Engineering Technology Co., Ltd. The main drafters of this document. Hu Chenxia, Zhang Jianfang, Chen Yongqiang, Liu Ying, Zhou Lijun, Su Shaorui, Bao Xianyu, Yang Yujiu, Liu Weili, Wang Jian, Miao Yanhui, Wang Junya. The previous versions of the documents replaced by this document are as follows. ---First published as GB/T 19256.9-2006 in.2006; --- This is the first revision, and the document number is adjusted to GB/T 19256.5.Introduction0.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 specification1 ScopeThis document specifies the core component design method for expressing business data, and provides the methods for creating new business vocabulary and reconstructing existing business vocabulary. table method. This document applies to the sharing and exchange of business information between enterprises, government agencies and/or other organizations in an open environment. core The user groups of components include business personnel who interoperate business information between different organizations, modelers of business documents/data/processes, and system System developers, where interoperability includes both Internet-based and network-based (Web) information exchange, as well as traditional EDI systems Interactive and batch business data exchange between. Note. This document is the basis for business analysts to conduct standard development work, and is also information for business users and the use of core component libraries to develop application content The basis for the work of technologists.2 Normative referencesThe contents of the following documents constitute the essential provisions of this document through normative references in the text. Among them, dated references For documents, only the version corresponding to the date is applicable to this document; for undated reference documents, the latest version (including all amendments) is applicable to this document. GB/T 18391.4-2009 Information Technology Metadata Registration System (MDR) Part 4.Formation of Data Definitions (ISO / IEC 11179-4.2004, IDT)3 Terms and DefinitionsThe following terms and definitions apply to this document. 3.1 A collection of several pieces of interrelated business information expresses a clear business meaning in a specific context. Note. If expressed in modeling terms, it can be expressed as an object class in a specific business context. 3.2 A set composed of several pieces of interrelated business information expresses a clear business meaning and has nothing to do with a specific business context. 3.3 In a specific business context, it expresses a business information entity with complex business characteristics of a specific object class. NOTE. It has a unique definition of business semantics. ASBIE represents the attribute of the associated business information entity and is associated with the ABIE describing its structure (ASBIE and ABIE has the same structure). ABIE is derived from ACC. 3.4 A Business Information Entity attribute whose value is expressed in the complex structure of another Aggregate Business Information Entity (ABIE). ......Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 19256.5-2022_English be delivered?Answer: Upon your order, we will start to translate GB/T 19256.5-2022_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 19256.5-2022_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 19256.5-2022_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+ countriesQuestion 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 Sales@ChineseStandard.net. 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.Question 5: Should I purchase the latest version GB/T 19256.5-2022?Answer: Yes. Unless special scenarios such as technical constraints or academic study, you should always prioritize to purchase the latest version GB/T 19256.5-2022 even if the enforcement date is in future. Complying with the latest version means that, by default, it also complies with all the earlier versions, technically. |
