GB/T 47462-2026Digital standards - Architecture of the standard information model (English PDF)

2 Structural Information Unit Architecture

7.1.2 Previous Page Information The front page information includes the cover, preface, and introduction, each described as follows:

---The cover information includes key standard document information, such as standard name, standard category, standard number, publication date, implementation date, and standard document information. Authorized issuing agencies, etc.;

---The preface includes information on the standard's development and revision, appendix descriptions, the organization that proposed the standard, the organization responsible for the standard, and the organization that drafted the standard. The standard's drafters, its relationship with international standards, and the publication history of the document and any versions of the documents that it has replaced or repealed;

---The introduction section contains standard background information, usually expressed in paragraphs.

7.1.3 Main Text Information The main body of the standard generally includes its scope, normative references, terms and definitions, symbols and abbreviations, and technical elements. (Each section...) The explanation is as follows:

---Scope. This section covers information such as the standardized objects and their applicable scope; detailed information is presented in paragraphs.

---Normative references. These include information on other standards referenced in the clauses of this standard. The standard number and name should be clearly indicated. Line references and structured storage;

---Terms and Definitions. Covers entry numbers, terms, English equivalents, definitions, etc.;

---Symbols and Abbreviations. A data combination encompassing symbols and their explanations, abbreviations, full English names, and their Chinese meanings;

---Technical Elements. Covering the main technical requirements of the standard, expressed in a structured manner through chapters, clauses, paragraphs, lists, figures, tables, etc. For example, the information that needs to be processed and marked includes table number, table title, statements about units, table header, table body, footnotes, notes, etc. See Figure 3. Figure

3 Information Structure

7.1.4 Information on subsequent pages The following pages include appendices and references. The data presented in the appendix follows the same technical format as the main text. References... References mainly include information such as document number and document title.

4 Organization of semantic information units in metallic material standards

8.1.3 The domain model of standardized objects is centered on business scenarios, extracting typical business processes, rules, and interaction logic, and incorporating complex business requirements. The goal is to transform the logical framework into a hierarchical semantic representation (such as a concept layer, rule layer, and instance layer), and to ensure its alignment with business specifications through expert verification. Strong coupling. Example. Building standard semantic information units are organized using Building Information Modeling (BIM), which is a domain model for the construction industry. For example, GB 50016- In.2014, it was proposed that "exits should be distributed in a dispersed manner, with the horizontal distance between the nearest edges of adjacent exits >= 5m." In Building Information Modeling (BIM), this is achieved by defining safety exit components... The clause is embodied in attributes and spatial relationships. Emergency exits are set as specific model elements, given the semantic label "Emergency Exit," and their horizontal position is defined. Set geometric properties such as coordinates. Utilize the BIM model's rule engine to set constraints, specifically the horizontal distance between two model elements labeled "Emergency Exit". The distance attribute value is greater than or equal to 5m. The semantic information unit organization of building components is shown in Figure 5. Figure

5 Overall Architecture

The standard information model architecture is shown in Figure 1, and consists of the following four parts.

---Standard Management Shell. This is the entry point for accessing the standard information model, providing management metadata and indexes for digital standards, content interfaces, and... The functional interface, wherein the content interface defines the markup language used to acquire and interpret structural and semantic information units. The signature type and version, and the functional interface define the service entry point for the functional information unit;

---Structured Information Unit. Represents and stores structured standard information, supporting selective access to standard content;

---Semantic Information Unit. Represents and stores the semantic characteristics and requirements of standard structured information units. Structured information units are implemented through an ontology model. Semantic information units can be obtained by mapping from a domain model, supporting the processing of semantic information units according to standardized ontology characteristics or application domain characteristics. Meta-aggregation, intelligent reasoning, and push notifications;

---Functional information unit. This is a combination and diversified expression of structural information units and semantic information units, tailored to different business application scenarios. It provides executable standard service capabilities, presenting different application forms such as models, components, programs, and interfaces.

9 Functional Information Units

9.1 Information Organization Use functional information unit collection objects to manage the basic information of each functional unit and establish the association relationship with the functional unit entity. The digital representation label for each functional information unit is shown in A.4, and its contents include.

---Functional information unit coding is uniformly coded by the standardization management organization;

---Functional information unit types, such as models, data dictionaries, software, and components;

---A basic overview of the functional information unit, such as its function, usage rules, and recommendations;

---The development unit of the functional information unit;

---The certification and approval unit for functional information units;

---The release date of the functional information unit;

---Link information for functional information units;

---The basis for the development of functional information units, and related structural information units and/or semantic information units;

---Version of the functional information unit.