Engineering platform syntax expression and interpretation method

Abstract

The invention discloses a syntactic expression and interpretation method for an engineering platform. The interpretation method comprises the steps that a demand model is converted into a syntactic script, the syntactic script is converted into an XML script, and the XML script is loaded to an ASP platform. A script language is designed to describe the digital platform and can become a unified abstraction layer of the digital platform, the configuration complexity in platform engineering is remarkably reduced, and meanwhile control over a bottom layer technology is reserved.

Description

Technical Field

[0001] This invention relates to the field of digital platform engineering, and in particular to a method for expressing and interpreting the syntax of an engineering platform. Background Technology

[0002] Digital platform engineering is a systematic concept that integrates digital technologies and platform architecture. Its core lies in building a standardized, modular technology platform to provide underlying support and efficient solutions for enterprise digital transformation. Digital platform engineering uses a "platform" as a carrier to integrate digital technologies such as cloud computing, big data, artificial intelligence, and the Internet of Things, creating a reusable and scalable technical foundation. Essentially, it abstracts complex technical capabilities into modular services through standardized architectural design, allowing business departments to quickly call upon them in a "ready-to-use" manner, thereby accelerating the development, deployment, and iteration of digital applications.

[0003] With the deepening of enterprise digital transformation, Application System Platforms (ASPs) have become a crucial infrastructure supporting the informatization of scientific research, production, business management, and other fields. ASP platforms integrate basic components such as data models, workflows, app registration, buttons, permissions, personnel, organizations, roles, and data dictionaries. They support the rapid construction of application system frameworks through visual configuration and the customized development of business processing logic through program code. However, with the continuous expansion of application scenarios and the increasing complexity, traditional ASP platforms have gradually exposed a series of problems and bottlenecks in areas such as unified modeling, collaboration efficiency, and intelligent capabilities.

[0004] Application system development scripting languages ​​for platform engineering are not only scripting languages, but also engineering expression tools. They aim to achieve a leap from "low code + programming" to "model-driven development", and promote the platform from "configuration-based" to "language-based", thereby comprehensively improving the construction efficiency, collaborative capabilities and intelligence level of application systems.

[0005] Currently, ASP platforms are widely used in various business areas such as scientific research, production, operation, and management. Their core value lies in reducing development barriers and improving delivery efficiency through modularization and visualization. However, in practical applications, these platforms face many deep-seated problems, such as a lack of unified modeling standards, serious duplication of component development, difficulties in system evolution, complex permission and process configuration, high costs of cross-team collaboration, and weak intelligent capabilities. Especially during the process of promoting the intelligent transformation of platforms, effectively introducing new technologies such as prompt word engineering, AI-assisted modeling, and intelligent generation has become a key challenge for platform upgrades. These problems not only affect the platform's usability and scalability but also limit its in-depth application in a wider range of business scenarios.

[0006] (1) Problems have arisen in the platform application model of visual configuration + program development. Currently, ASP platforms generally adopt a hybrid development model of "visual configuration + program development". Although this model lowers the development threshold to some extent, the following problems still exist in practice: ① In terms of semantics, the lack of a unified semantic system between visual configuration and program code leads to inconsistencies between configuration logic and code logic, resulting in semantic fragmentation. ② In terms of maintenance, configuration items are scattered, difficult to version, and hard to trace change history, making maintenance difficult. ③ In terms of collaboration, different roles (business personnel, developers) use different tools and languages, resulting in high communication costs and collaboration barriers. ④ In terms of automation, a large amount of logic requires manual coding, making it difficult to achieve automated generation and deployment, resulting in low automation. ⑤ In terms of reusability, configurations are difficult to reuse, leading to frequent repetitive work and low reusability.

[0007] Therefore, a unified language system is urgently needed to bridge the gap between visualization and code, and to achieve integrated expression and management of the platform's internal logic.

[0008] (2) Problems have arisen in the application system development platform in terms of business expansion. As the platform is promoted and applied in multiple industry sectors, its business adaptability issues are becoming increasingly prominent: ① Limited modeling capabilities: Existing platforms struggle to flexibly support the business models and process requirements of different industries; ② Insufficient extension mechanisms. Platform component extensions rely on plugins or custom development, and the standardization of interfaces is insufficient; ③ Weak multi-tenancy support. In multi-customer, multi-organizational architectures, it lacks sufficient capabilities for access control, data partitioning, and other functionalities. ④ Difficulty in industry adaptation. The platform is highly versatile but lacks industry-specific features, making it difficult to meet the deep customization needs of vertical industries; ⑤ Integration is difficult. When interfacing with other systems (such as ERP, MES, CRM), the interfaces are not uniform and the data formats are inconsistent.

[0009] This limits the platform's deployment in a wider range of business scenarios, making it imperative to enhance its flexibility and scalability by introducing a unified modeling language and platform scripts.

[0010] (3) Problems with the introduction of prompt word engineering in the intelligent transformation of application system development platform In recent years, with the development of large-scale model technology, more and more platforms have attempted to introduce prompt engineering as a new path for intelligent development. However, the following problems still exist in practical applications: ① The prompts are disconnected from the platform logic. Natural language commands are difficult to accurately map to platform components and operations; ② The intent recognition is ambiguous. The lack of a unified semantic framework leads to unstable and uncontrollable AI-generated results; ③ Poor controllability. The generated content lacks structural constraints and is difficult to use directly for platform execution; ④ Lack of feedback mechanism: Users cannot verify or correct the generated results; ⑤ Security and compliance risks: AI-generated content may violate platform guidelines or data privacy policies.

[0011] To truly achieve deep integration between the platform and AI, it is necessary to build an intermediate language layer that can both understand natural language and accurately execute platform operations. This is where platform-level scripting languages ​​play a crucial role.

[0012] In summary, current ASP platforms face severe challenges in areas such as unified modeling, component reuse, collaborative development, and intelligent transformation. The lack of a unified language system leads to a disconnect between visual configuration and program development, difficulties in component reuse, and challenges in system evolution. Furthermore, the lack of structured semantic support hinders the implementation of AI technologies. Therefore, designing an application system development scripting language for platform engineering is a key breakthrough in solving these problems. Summary of the Invention

[0013] In view of the above problems, the present invention is proposed to provide an engineering platform syntax expression and interpretation method that overcomes or at least partially solves the above problems.

[0014] According to one aspect of the present invention, an engineering platform syntax expression and interpretation method is provided, the interpretation method comprising: converting a requirement model into a syntax script, converting the syntax script into an XML script, and loading the XML script into an ASP platform.

[0015] Optionally, the requirement model is converted into a syntax script, specifically including: an ASP lexical processor; an ASP syntax processor; and an ASP semantic checker.

[0016] Optionally, the conversion of the syntax script into an XML script specifically includes: an ASP XML generator; and an ASP error report generator.

[0017] Optionally, loading the XML script into the ASP platform specifically includes: Upload the generated XML script to the target server; The XML script is loaded by the engine to generate application import records; The loading engine first imports the root data, then deconstructs the data layer by layer, and imports it into the ASP platform. The server application is updated, and application data update records are generated simultaneously.

[0018] Optionally, the ASP lexical processor specifically includes: The demand model is decomposed into lexical units to construct a dictionary based on Chinese characters that are retained. Identify keywords, identifiers, constants, operators, and punctuation marks as lexical units; It supports Chinese punctuation marks as syntax delimiters and outputs a token stream.

[0019] Optionally, the ASP syntax processor specifically includes: Identify modules, components, processes, permissions, component definitions, and cross-domain calls in the requirements model; Construct grammatical expressions that begin with a Chinese character and may contain Chinese characters, numbers, and underscores; Reserved words are prohibited as variable names; (1) Operation priority analysis: The computational priorities are determined from the requirements model, and a priority list and syntax expression are output. (2) Data input / output organization: Organize the data inputs from the requirements model and output a list of data inputs and their grammatical expressions; Organize the data output from the requirements model, and output a list of data outputs and their grammatical expressions; (3) Grammatical Structure Analysis: (3.1) Organize the sequential structure: Organize the sequential structure from the requirement model and output the sequential structure list and grammatical expression; (3.2) Organize the branch structure: Organize the branch structure from the requirement model and output the branch structure list and syntax expression; (3.3) Organize the loop structure: Organize the loop structure from the requirement model and output a list of loop structures and their syntax; (4) Functional block sorting: sort out the functional blocks from the requirement model and output the function structure, function call and syntax expression; sort out the built-in ASP functional blocks from the requirement model and output the function call list and syntax expression.

[0020] Optionally, the ASP semantic checker specifically includes: extracting syntactic expressions from the requirements model, and using component libraries and third-party library calls supported by the ASP platform to perform necessary semantic checks; (1) Record component and variable metadata; compare the syntax with the component library and third-party library call sequences supported by the ASP platform, output errors or suspected errors, and have them identified manually; (2) Type checking, checking data type consistency, handling type checking and dependency resolution; (3) Permission verification: supports dynamic loading of component metadata, verification of component interface compatibility, and verification of permission model compliance.

[0021] Optionally, the ASP XML generator specifically includes: Load the symbol table, including the global component table, local variable table, and temporary data table, to record metadata such as components, variables, functions, data models, roles, and dictionaries; Call the symbol table to match keywords and reserved words in the syntax script; Based on the symbol table, the XML generator directly converts the syntactic expression nodes into structured XML files. It adopts a template-based generation strategy, supports XML Schema validation, and the generated XML contains component definitions, data models, flow control, and permission configuration content.

[0022] Optionally, the ASP error report generator specifically includes: Load the symbol table, including the global component table, local variable table, and temporary data table, to record component, variable, function, data model, role, and dictionary metadata; Call the symbol table to match keywords and reserved words in the syntax script; Based on the symbol table, the ASP error report generator performs error checking and report output using XML scripts. (1) Supports cross-scope reference resolution, recording component version information and dependency relationships; (2) Provide cross-reference verification functionality to ensure correct component dependencies and data consistency; (3) Multi-level error checking of XML scripts, checking for illegal character lexical errors, missing structure syntax errors, and type mismatch semantic errors, and outputting a report; (4) Provide the error location, error type and possible repair suggestions to locate and correct the error in the script.

[0023] This invention provides a method for expressing and interpreting the syntax of an engineering platform. The interpretation method includes: converting a requirement model into a syntax script, converting the syntax script into an XML script, and loading the XML script into an ASP platform. Designing a scripting language to describe a digital platform can serve as a unified abstraction layer for the digital platform, significantly reducing the configuration complexity in platform engineering while retaining control over the underlying technologies.

[0024] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and in order to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description

[0025] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0026] Figure 1 A flowchart illustrating an engineering platform syntax expression and interpretation method provided in this embodiment of the invention; Figure 2 This is an overall diagram of the requirement model transformation syntax script provided in the embodiments of the present invention; Figure 3 The ASP lexical processor logic diagram provided in this embodiment of the invention; Figure 4 A logic diagram of the ASP syntax processor provided in this embodiment of the invention; Figure 5 A general diagram of converting a syntax script into an XML script, as provided in the embodiments of the present invention. Detailed Implementation

[0027] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

[0028] The terms "comprising" and "having," and any variations thereof, in the specification, embodiments, claims, and drawings of this invention are intended to cover non-exclusive inclusion, such as including a series of steps or units.

[0029] The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings and embodiments.

[0030] like Figures 1-5 As shown, this paper provides a method for expressing and interpreting the syntax of an engineering platform scripting language, which solves the problems existing in the development mode, cross-business domain and intelligence aspects of application system development platforms.

[0031] This invention proposes a novel platform-level application system development scripting language, ASL (Application System Language), a domain-specific language designed specifically for the ASP application system development platform. It employs a natural language-like Chinese syntax and uses a unified abstraction layer to describe the components, data, processes, and permissions of the application system.

[0032] ASL adopts a "model-driven + language-based" paradigm, unifying the traditional "configuration + programming" approach into a single, evolvable Chinese script. The script is scanned once by the interpreter, generating semantically tagged XML metadata, which is then executed by the ASP engine. ASL and ASP visual configuration are bidirectionally synchronized, supporting an interpretation chain of "model → script → XML". ASL includes a built-in prompt lexical syntax, serving as a structured interface for large models.

[0033] 2.2 Transforming the requirement model into a syntax script 2.2.1 Overview The requirement model is translated into a syntax script. First, the ASP lexical processor is executed; second, the ASP syntax processor is executed; and third, the ASP semantic checker is executed. All steps use Chinese keywords as tokens and are compatible with Chinese punctuation. All reserved words in the syntax script are prefixed with "ASP::".

[0034] 2.2.2 ASP Lexical Processor The ASP lexical processor decomposes the requirement model into lexical units (tokens), constructs a dictionary based on reserved Chinese characters, identifies lexical units such as keywords, identifiers, constants, operators, and punctuation marks, and supports Chinese punctuation marks (such as the comma and colon) as syntax delimiters. It outputs a token stream.

[0035] (1) Keyword recognition Identify core keywords Extract core keywords from the requirement model and output a list of core keywords and their grammatical expressions. Core keywords include: create / register / configure / call / bind / map, define / query / transform / index / associate, permission / process / event, if / then / otherwise / loop / select / traverse / interrupt / when / according to, assign / undo / validate, component / data / model / role / organization / dictionary / prompt words, return / output / read / write / update / delete, etc.

[0036] (1.2) Identify ASP platform reserved words Extract first-level reserved words from the requirements model and output the ASP platform reserved word list and syntax expression. First-level reserved words include: portal, platform management, tenant management, three-person management, context management, business management, object modeling, interface modeling, process modeling, event listening, category management, job management, file management, code management, low-code service, and system monitoring.

[0037] Extract secondary reserved words from the requirement model and output the ASP platform reserved word list and syntax expressions. Secondary reserved words include: System Management, Service Management, Tenant Management, Data Source Management, Organization Management, Role Management, Permission Management, Online Users, Audit Logs, Preference Management, Dictionary Management, Attribute Management, Dimension Management, Template Management, Data Permissions, Functional Modeling, Model Management, Search, Graph Database, Buttons, Button Groups, Pages, Tabs, Tab Groups, Interfaces, Process Models, Process Monitoring, Process Handling, Event Management, Listener Management, Event Monitoring, Listener Monitoring, Category Definition, Category Association Query, Job Management, Executor Management, Scheduling Logs, Runtime Reports, Development Center, Public Services, Service Monitoring, Data Monitoring, Interface Documentation, etc.

[0038] (1.3) Identify special control words Identify special control words from the requirement model and output a list of special control words and their syntax. Cross-business system calls are identified as "ASP::Cross-domain"; intelligent feature configurations are identified as "ASP::Enabled"; and large model inputs are identified as "ASP::Prompt Word".

[0039] Constant value identification. (2.1) Identify digits.

[0040] Identify numbers from the demand model and output a list of numbers and their grammatical expressions. "0-9" are identified as "ASP::zero" to "ASP::nine"; combinations of larger numbers are identified as strings such as "ASP::ten", "ASP::hundred", etc.

[0041] (2.2) Identifying Boolean values Identify Boolean values ​​from the requirements model and output a list of Boolean values ​​and their syntax. Boolean true and false values ​​are identified as "ASP::true" and "ASP::false" respectively.

[0042] (2.3) Identifying null values Identify null values ​​from the requirement model and output a list of null values ​​and their syntax. The null value status is identified as "ASP::Null".

[0043] (3) Data type identification. Identify data types from the requirements model and output a list of data types and their syntax. Data types include ASP::Numerical (integer, decimal), ASP::Character, ASP::Boolean, ASP::Date, ASP::Component Reference (model, workflow, role), ASP::Dataset (list, mapping, struct), ASP::Vector, and ASP::Graph.

[0044] (4) Operator recognition. (4.1) Recognizing number bases Identify number systems from the requirement model and output a list of number systems and their syntax. For decimal, add the prefix "ASP::decimal"; for binary, add the prefix "ASP::binary"; for hexadecimal, add the prefix "ASP::hexadecimal".

[0045] (4.2) Identifying arithmetic operators Identify arithmetic operators from the requirements model and output a list of arithmetic operators and their syntax. Extract the arithmetic operators (+), (-), (×), (÷), and (%), and identify them as addition, subtraction, multiplication, division, and modulo.

[0046] (4.3) Recognizing relational operators Identify relational operators from the requirements model and output a list of relational meta-operators and their syntax. Extract the relational operators (=), (≠), (>), (<), (≥), and (≤), and identify them as equal to, not equal to, greater than, less than, greater than or equal to, and less than or equal to.

[0047] (4.4) Identify logical operators Identify logical operators from the requirements model and output a list of logical operators and their syntax. Extract the logical operators and identify them as AND, OR, and NOT.

[0048] (5) String recognition. Identify strings from the demand model and output a list of strings and their grammatical representations. Extract Chinese characters, numbers, and combinations of finite symbols enclosed in full-width double quotes (“”) and recognize them as strings.

[0049] 2.2.3 ASP Syntax Processor The ASP syntax processor identifies modules, components, processes, permissions, component definitions, and cross-domain calls in the requirements model, constructs syntactic expressions, and requires that the expression begin with a Chinese character. It may contain Chinese characters, numbers, and underscores. Reserved words are prohibited as variable names.

[0050] (1) Operation priority sorting From the requirements model, identify the operation priorities and output a priority list and syntax expression. Identify parentheses, multiplication and division, addition and subtraction, relational operations, and logical operations, and rank them according to priority: parentheses > multiplication and division > addition and subtraction > relational operations > logical operations.

[0051] (2) Data input / output organization Organize data inputs from the requirements model and output a data input list and syntax expression. Organize data inputs to support platform data sources (databases, APIs), user input (forms), and file import.

[0052] Organize the data output from the requirements model, and output a list of data outputs and their syntax. Organize the result outputs, including generating configuration files, returning calculation results, and triggering platform events.

[0053] (3) Grammatical Structure Analysis (3.1) Organize the sequential structure Extract the sequential structure from the requirements model, and output a list of sequential structures and their grammatical expressions. Explain the sequential structure by writing statements, executing them sequentially, and separating them with line breaks.

[0054] (3.2) Analyze the branch structure Identify the branching structure from the requirements model and output a list of branching structures and their syntax. The branching structure can be categorized into single-branch (if...then...), double-branch (if...then...otherwise...), and multi-branch (choose...when...).

[0055] (3.3) Analyze the loop structure Identify loop structures from the requirements model and output a list of loop structures and their syntax. The identified loop structures support repetitive execution (looping until...) and conditional loops (looping while...; looping conditional execution...).

[0056] (4) Functional block organization From the requirements model, identify functional blocks and output their structure, function calls, and syntax. The functional blocks are structured as "define function name, parameter list, return type". They are used as "call function name, parameter list" structures.

[0057] Identify and extract ASP's built-in functional blocks from the requirements model, and output a list of function calls and syntax expressions. This includes identifying internal component (creation) and (binding) operations.

[0058] 2.2.4 ASP Semantic Checker The semantic checker extracts syntactic expressions from the requirements model and uses component libraries and third-party libraries supported by the ASP platform to perform necessary semantic checks. (1) Record meta-information such as components and variables. Compare the syntax with the call sequences of the component library and third-party library supported by the ASP platform, output errors or suspected errors, and have them identified manually.

[0059] (2) Type checking. Checks data type consistency, handles type checking and dependency resolution.

[0060] (3) Permission verification. Supports dynamic loading of component metadata, verification of component interface compatibility, and verification of permission model compliance.

[0061] 2.3 Converting Syntax Scripts to XML Scripts The syntax script is converted into an XML script. First, an ASP XML generator is executed based on the symbol table; second, an ASP error report generator is executed based on the symbol table. All steps use Chinese keywords as tokens, ensuring compatibility with Chinese punctuation.

[0062] 2.3.1 ASP XML Generator Load the symbol table, including the global component table, local variable table, and temporary data table, recording metadata such as components, variables, functions, data models, roles, and dictionaries. Invoke the symbol table to match keywords and reserved words in the syntax script.

[0063] Based on the symbol table, the XML generator directly converts the syntactic expression nodes into structured XML files. It adopts a template-based generation strategy, supports XML Schema validation, and the generated XML contains component definitions, data models, flow control, permission configurations, and other content.

[0064] 2.3.2 ASP Error Report Generator Load the symbol table, including the global component table, local variable table, and temporary data table, recording metadata such as components, variables, functions, data models, roles, and dictionaries. Invoke the symbol table to match keywords and reserved words in the syntax script.

[0065] Based on the symbol table, the ASP error report generator performs error checking and report output using XML scripts.

[0066] (1) Supports cross-scope reference resolution, recording component version information and dependency relationships.

[0067] (2) Provide cross-reference verification function to ensure that component dependencies are correct and data is consistent.

[0068] (3) Multi-level error checking of XML scripts, checking for illegal character lexical errors, missing structure syntax errors, and type mismatch semantic errors, and outputting a report.

[0069] (4) Provide error location, error type and possible repair suggestions to quickly locate and correct errors in the script.

[0070] 2.4 Loading XML scripts into the ASP platform (1) Upload the generated XML script to the target server.

[0071] (2) The XML script is loaded by the engine to generate the "Application" import record.

[0072] (3) The loading engine first imports the root data, then deconstructs the data layer by layer, and imports it into the ASP platform.

[0073] (4) The server’s “Application” is updated, and an “Application” data update record is generated at the same time.

[0074] A scientific research project management system can be quickly built using the ASP platform to manage the entire process of project application, approval, execution, and completion.

[0075] (1) Basic Information Script code; Generate the following XML file; (4) ASP loading This XML file can be loaded by the ASP platform runtime engine to automatically create the database table structure, deploy the process engine, configure permission policies, and generate the front-end interface.

[0076] Beneficial effects: Design a scripting language (ASL) for describing digital platforms that balances simplicity, scalability, and readability while covering the platform's core elements (such as resources, services, policies, and dependencies). ASL can serve as a unified abstraction layer for digital platforms, significantly reducing configuration complexity in platform engineering while retaining flexible control over the underlying technologies.

[0077] (1) ASL reshapes the ASP platform development model: It pioneers a "model-driven + language-based" development paradigm, using declarative syntax to uniformly describe the components of an application system. It achieves an organic integration of visual configuration and code development, supporting bidirectional conversion. It provides intelligent prompts and error prevention mechanisms, lowering the development threshold. This represents a leap from "visual configuration + program development" to "model-driven + language-based." It is not only a descriptive language but also a platform interaction language, enabling developers to call platform components and organize business processes in a unified way, thereby improving development efficiency and system consistency. It unifies "visual configuration" and "program code" into a single Chinese script; through language-based description, configuration is code, and code is documentation. Visual modifications automatically update the script, and script changes are reflected in the UI in real time. It focuses on business semantics rather than implementation details, providing structured targets for AI generation and prompts. The script is converted into standardized XML to drive ASP platform execution while retaining the flexibility of visual editing and code expansion. Developers can use natural language syntax to describe the entire application system, from data models to business processes, achieving "describe once, run everywhere," significantly improving development efficiency and system consistency.

[0078] (2) ASL provides a new way for platforms to cross business domains. Scripting languages ​​support cross-business domain application development through flexible component models and data manipulation instruction sets. Whether it's scientific research and production, business management, or supply chain collaboration, a single language framework can be used for description, automatically handling differences in data models and processes between different business domains and reducing cross-domain development costs. A single syntax describes systems across multiple domains, including scientific research, production, and business management; through business domain context injection, corresponding component packages and data dictionaries are automatically loaded. The same syntax queries relational and vector data. Business domain semantic mapping is supported, allowing the use of a unified syntax to manipulate heterogeneous system components. Multi-business domain modeling and adaptation are supported; through modular design, component reuse mechanisms, and data abstraction capabilities, the platform's adaptability in fields such as scientific research and manufacturing is enhanced.

[0079] (3) Intelligent transformation of ASL support platform The scripting language provides a structured interface layer for large-scale model prompt word engineering, allowing for easy embedding of AI-generated code snippets through pre-reserved "prompt word syntax." The interpreter intelligently recognizes and processes these prompt words, converting natural language descriptions into platform-executable instructions. This design enables seamless integration of AI technology into the development process, helping developers quickly implement complex functions and accelerating the platform's intelligent transformation. Pre-reserved prompt word keywords can be directly embedded with natural language requirements. For example, the prompt word "generate a procurement process, including application, review, and payment steps." The platform calls the large model to expand the prompt word into a complete script in real time, then generates XML. Large-scale model call templates can be embedded in the script. Parameterized prompt word engineering is supported, enabling enhanced intelligent decision-making in business processes.

[0080] The above specific embodiments further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for syntax expression and interpretation in an engineering platform, characterized in that, The interpretation method includes: The requirement model is converted into a syntax script, the syntax script is converted into an XML script, and the XML script is loaded into the ASP platform.

2. The method for engineering platform syntax expression and interpretation according to claim 1, characterized in that, The requirement model is transformed into a syntax script, specifically including: ASP lexical processor; ASP syntax processor; ASP semantic checker.

3. The method for engineering platform syntax expression and interpretation according to claim 1, characterized in that, The conversion of the syntax script into an XML script specifically includes: an ASP XML generator; and an ASP error report generator.

4. The method for engineering platform syntax expression and interpretation according to claim 1, characterized in that, The loading of the XML script into the ASP platform specifically includes: Upload the generated XML script to the target server; The XML script is loaded by the engine to generate application import records; The loading engine first imports the root data, then deconstructs the data layer by layer, and imports it into the ASP platform. The server application is updated, and application data update records are generated simultaneously.

5. The method for engineering platform syntax expression and interpretation according to claim 2, characterized in that, The ASP lexical processor specifically includes: The demand model is decomposed into lexical units to construct a dictionary based on Chinese characters that are retained. Identify keywords, identifiers, constants, operators, and punctuation marks as lexical units; It supports Chinese punctuation marks as syntax delimiters and outputs a token stream.

6. The method for engineering platform syntax expression and interpretation according to claim 2, characterized in that, The ASP syntax processor specifically includes: Identify modules, components, processes, permissions, component definitions, and cross-domain calls in the requirements model; Construct grammatical expressions that begin with a Chinese character and may contain Chinese characters, numbers, and underscores; Reserved words are prohibited as variable names; (1) Operation priority analysis: The computational priorities are determined from the requirements model, and a priority list and syntax expression are output. (2) Data input / output organization: Organize the data inputs from the requirements model and output a list of data inputs and their grammatical expressions; Organize the data output from the requirements model, and output a list of data outputs and their grammatical expressions; (3) Grammatical Structure Analysis: (3.1) Organize the sequential structure: Organize the sequential structure from the requirement model and output the sequential structure list and grammatical expression; (3.2) Organize the branch structure: Organize the branch structure from the requirement model and output the branch structure list and syntax expression; (3.3) Organize the loop structure: Organize the loop structure from the requirement model and output a list of loop structures and their syntax; (4) Functional block sorting: sort out the functional blocks from the requirement model and output the function structure, function call and syntax expression; sort out the built-in ASP functional blocks from the requirement model and output the function call list and syntax expression.

7. The method for engineering platform syntax expression and interpretation according to claim 2, characterized in that, The ASP semantic checker specifically includes: extracting syntactic expressions from the requirements model, and using component libraries and third-party library calls supported by the ASP platform to perform necessary semantic checks; (1) Record component and variable metadata; compare the syntax with the component library and third-party library call sequences supported by the ASP platform, output errors or suspected errors, and have them identified manually; (2) Type checking, checking data type consistency, handling type checking and dependency resolution; (3) Permission verification: supports dynamic loading of component metadata, verification of component interface compatibility, and verification of permission model compliance.

8. The method for engineering platform syntax expression and interpretation according to claim 3, characterized in that, The ASPXML generator specifically includes: Load the symbol table, including the global component table, local variable table, and temporary data table, to record metadata such as components, variables, functions, data models, roles, and dictionaries; Call the symbol table to match keywords and reserved words in the syntax script; Based on the symbol table, the XML generator directly converts the syntactic expression nodes into structured XML files. It adopts a template-based generation strategy, supports XML Schema validation, and the generated XML contains component definitions, data models, flow control, and permission configuration content.

9. The method for engineering platform syntax expression and interpretation according to claim 3, characterized in that, The ASP error report generator specifically includes: Load the symbol table, including the global component table, local variable table, and temporary data table, to record component, variable, function, data model, role, and dictionary metadata; Call the symbol table to match keywords and reserved words in the syntax script; Based on the symbol table, the ASP error report generator performs error checking and report output using XML scripts. (1) Supports cross-scope reference resolution, recording component version information and dependency relationships; (2) Provide cross-reference verification functionality to ensure correct component dependencies and data consistency; (3) Multi-level error checking of XML scripts, checking for illegal character lexical errors, missing structure syntax errors, and type mismatch semantic errors, and outputting a report; (4) Provide the error location, error type and possible repair suggestions to locate and correct the error in the script.

Images