Structured editing method and system for aircraft operation manual and medium

Abstract

The invention discloses a structured editing method and system for an aircraft operation manual and a medium, and the method comprises the steps: receiving a structured aircraft operation manual which is an xml format file; analyzing the aircraft operation manual, displaying the analyzed tree structure in a first window in a form of operating tree nodes, and displaying the analyzed data content in a second window; when any editing object is selected for editing in a first window or a second window in response to a mouse, the edited data content is immediately presented in the second window, and the first window and the second window are located in the same display interface. According to the method, the double-screen display mode is presented in the same display interface, so that a user focuses on the data content and does not need to pay attention to the data structure when editing the structured data, what you see is what you get during editing, the work task of structured editing of a flight operation manual is reduced, and the editing efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of manual editing, and in particular to a structured editing method, system and medium for aircraft operation manuals. Background Art

[0002] Flight operations manuals are compiled using Schema data specifications customized based on S1000D and ATA2300 specifications. The existing flight operations manual compilation system is customized and developed in accordance with the flight operations manual data specification requirements for structured content writing tools, common source database (CSDB) management systems, publishing systems and other functions. However, since there is still a large gap between the flight operations manual services provided by domestic aircraft manufacturers and the service models of mainstream foreign aircraft manufacturers, they can only meet simple editing needs and cannot meet customers' personalized application needs for deep structural editing and secondary publishing of manuals. It is also unable to provide airlines with customized professional editing tools for manual data editing, management and publishing, which affects the editing efficiency of airlines' flight operations manuals.

[0003] Based on the above problems, the applicant proposed the technical solution of this application. Summary of the invention

[0004] In view of the above-mentioned defects of the prior art, the present invention provides a structured editing method, system and medium for aircraft operation manuals. By presenting a dual-screen display mode in the same display interface, the user can focus on the data content when editing structured data without paying attention to the data structure. What you see is what you get during editing, which reduces the workload of structured editing of flight operation manuals and improves editing efficiency.

[0005] In order to achieve the above object, the present invention discloses a structured editing method for aircraft operation manuals, comprising the following steps:

[0006] Receiving a structured aircraft operation manual, wherein the aircraft operation manual is an XML format file;

[0007] Parsing the aircraft operation manual, displaying the parsed tree structure in the form of operation tree nodes in the first window, and displaying the parsed data content in the second window;

[0008] In response to the mouse selecting any editing object in the first window or the second window for editing, the edited data content is immediately presented in the second window, and the first window and the second window are located in the same display interface.

[0009] Preferably, in response to the mouse selecting the doctype plug-in in the first window or the second window for dynamic expansion, the following steps are implemented:

[0010] Add the configuration of ATA2300 plug-in in the file with the suffix spd in the doctype directory to realize automatic loading of the ATA2300 plug-in to be added;

[0011] Add a new file with the suffix sdt in the doctype directory, configure the reference relationship of the ATA2300 plug-in in the sdt file, and reference the xsd file in the sdt file;

[0012] Add a new file with the suffix py in the doctype directory, and configure the ATA2300 plug-in class and the business function logic implemented by the class in the py file.

[0013] Among them, the xsd file defines the structure and specifications of the flight operation manual data. The data specifications are modified by modifying the xsd file. There is an XSL file in the doctype directory. The XSL file is used to define the style of the edited data content displayed in the second window. The style is modified by modifying the XSL file.

[0014] Preferably, in response to the mouse selecting the current element in the first window or the second window as the editing object to be added or modified, the following steps are implemented:

[0015] Get the current element as the editing object and record the element ID of the added element or the position information of the modified element;

[0016] Obtain the xsd file in the doctypes directory, and use the xsd file to perform schema verification on the input content to ensure that the input content complies with the flight operations manual data standard;

[0017] Traverse to see if the parent node has been modified, and check whether the current tag supports the changeMark attribute. If it does, add the changeMark attribute and changeType attribute to the current node and assign values ​​to them respectively. If it does not, get the parent node, add the changeMark attribute and changeType attribute to the parent node and assign values ​​to them respectively.

[0018] Preferably, in response to the mouse selecting the current element as the editing object for deletion in the first window or the second window, the following steps are implemented:

[0019] Get the current element as the editing object;

[0020] In response to deleting the change summary, clearing the referenced rfuId attribute;

[0021] In response to deleting the applicability, clearing the applicRefId attribute of the reference;

[0022] Get the name of the current XSD file and the node attributes of the node changeMark;

[0023] Get the change summary id and pop up a text input box for the change summary.

[0024] Preferably, in response to the mouse modifying the attributes in the first window or the second window, the following steps are performed:

[0025] Get the current element as the editing object;

[0026] Get the location information for attribute modification;

[0027] Get the current XSD file name;

[0028] Traverse to see if the parent node has been modified, and check whether the current tag supports the changeMark attribute. If it does, add the changeMark attribute and changeType attribute to the current node and assign values ​​to them respectively. If it does not, take the parent node, add the changeMark attribute and changeType attribute to the parent node and assign values ​​to them respectively.

[0029] Preferably, in response to the mouse performing applicability editing in the first window or the second window, the following steps are performed:

[0030] For adding applicability, obtain the service announcement data, the current editing object and the applicability node in the current DM, add the attribute id, add the node element displayText, add the node element evaluate and the corresponding attributes, add the node element assert and the corresponding attributes and perform the update operation, obtain the current XSD file name, traverse whether the parent node has been modified, and check whether the current tag supports the changeMark attribute. If it does, add the changeMark attribute and changeType attribute to the current node and assign values ​​respectively. If it does not support, get the parent node, add the changeMark attribute and changeType attribute to the parent node and assign values ​​respectively.

[0031] For deleting applicability, get the current editing object, clear the referenced applicRefId, get the current XSD file name, get the node attribute of the node changeMark, get the change summary id, and pop up a text input box for the change summary;

[0032] For modification applicability, obtain the current editing object and modification location information, obtain the current XSD file name, traverse to see if the parent node has been modified, and check whether the current tag supports the changeMark attribute. If supported, add the changeMark attribute and changeType attribute to the current node and assign values ​​to them respectively. If not supported, get the parent node, add the changeMark attribute and changeType attribute to the parent node and assign values ​​to them respectively.

[0033] Preferably, in response to the mouse editing the copy table in the first window or the second window, the following steps are performed:

[0034] Read and process the clipboard table, obtain the label position information selected by the mouse, and determine the label insertion position information;

[0035] Read non-pure text information in the clipboard content, calculate the number of table columns and obtain cell text and cell properties;

[0036] The first row of information in the table is determined as thead information, and the information after the first row is determined as tbody information, and an update operation is performed.

[0037] Preferably, in response to the mouse editing the summary in the first window or the second window, the following steps are performed:

[0038] Get the current summary as the editing object and generate the change summary id;

[0039] Get the content of the update reason, and the current cursor references the content of the update reason;

[0040] Get the current XSD file name;

[0041] Traverse to see if the parent node has been modified, and check whether the current tag supports the changeMark attribute. If it does, add the changeMark attribute and changeType attribute to the current node and assign values ​​to them respectively. If it does not, get the parent node, add the changeMark attribute and changeType attribute to the parent node and assign values ​​to them respectively.

[0042] The present invention also discloses a structured editing system for aircraft operation manuals, comprising the following modules:

[0043] A file receiving module, used to receive a structured aircraft operation manual, wherein the aircraft operation manual is a file in XML format;

[0044] A file parsing module, used for parsing the aircraft operation manual, displaying the parsed tree structure in the form of operation tree nodes in the first window, and displaying the parsed data content in the second window;

[0045] The editing response module is used to respond to the mouse selecting any editing object in the first window or the second window for editing, and the edited data content is immediately presented in the second window. The first window and the second window are located in the same display interface.

[0046] The present invention also discloses a computer-readable storage medium, on which a computer program is stored. When the computer program is processed and executed, the structured editing method for aircraft operation manuals is implemented.

[0047] Compared with the prior art, the present invention has the following beneficial effects:

[0048] The present invention presents a dual-screen display mode in the same display interface, so that users can focus on the data content when editing structured data, without paying attention to the data structure. What you see is what you get during editing, which reduces the workload of structured editing of flight operation manuals and improves editing efficiency. The multiple editing methods for structured elements provided realize various personalized editing requirements for data editing of structured manuals, which facilitates customized editing and publishing of structured manuals by airlines.

[0049] The concept, specific structure and technical effects of the present invention will be further described below in conjunction with the accompanying drawings to fully understand the purpose, characteristics and effects of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 It is a schematic flow diagram of the method of the present invention. DETAILED DESCRIPTION

[0051] In order to make the technical means, creative features, objectives and effects of the invention easier to understand, the invention is further described below with reference to specific diagrams. However, the invention is not limited to the following implementation cases.

[0052] It should be noted that the structures, proportions, sizes, etc. illustrated in the drawings in this specification are only used to match the contents disclosed in the specification so as to facilitate understanding and reading by persons familiar with this technology. They are not used to limit the conditions under which the present invention can be implemented, and therefore have no substantive technical significance. Any structural modification, change in proportion or adjustment of size, without affecting the effects and purposes that can be achieved by the present invention, should still fall within the scope of the technical contents disclosed by the present invention.

[0053] The present invention provides a WYSIWYG editing method for structured manuals. Based on C++ technology, it presents a real visual editing view to users. Customized functional plug-in development is performed through Python to meet users' structured editing of aircraft operation manuals. Most structured standards on the market are supported. Different effects are displayed by specifying different DocTypes. In addition, by cooperating with CCMS, CCMS communicates with the WEB end by using the WebDAV protocol to interact with data.

[0054] The structured manual content editing involved in the present invention not only has functions such as text editing, tag insertion, attribute modification, table entry, reference modification, image citation, Schema verification, etc., but also includes complex editing functions such as copying tables, adding applicability, and changing summaries.

[0055] The structured editing method for aircraft operation manuals disclosed in the present invention is a professional tool for data editing, management and publishing of structured manuals provided to airlines, and the purpose is to facilitate airlines to customize and publish structured manuals. When an aircraft manufacturer publishes a customized flight manual format, it will provide a PDF paper manual and a structured data package. The PDF paper manual is only for viewing. If the airline needs to perform secondary editing and modification on the manual before publishing, it needs to perform secondary editing on the structured data package.

[0056] like Figure 1 As shown in the flowchart of the structured editing method for aircraft operation manual disclosed in the present invention, the following steps are included:

[0057] Step S1, receiving a structured aircraft operation manual, wherein the aircraft operation manual is a file in XML format.

[0058] Step S2, parsing the aircraft operation manual, displaying the parsed tree structure in the form of operation tree nodes in the first window, and displaying the parsed data content in the second window.

[0059] Specifically, the structured aircraft operation manual is a structured data packet issued by the aircraft manufacturer. The data packet contains an XML format file. The user imports the aircraft operation manual through the front-end interface. After the aircraft operation manual is received, data parsing begins according to the XML format requirements, and the parsed structured data is converted into a tree structure. The converted operation tree nodes are displayed in the first window, and the corresponding data content in each operation tree node is displayed in the second window. The first window and the second window can be displayed horizontally or vertically. When the user selects an operation tree node with the mouse in the first window, the corresponding data content is highlighted in the second window.

[0060] In this embodiment, the manual file in XML format is displayed in the first window as an operation tree node by converting it into HTML through a transformer, and the effect of displaying the data content in the second window is determined by the XSL style file.

[0061] Step S3, in response to the mouse selecting any editing object in the first window or the second window for editing, the edited data content is immediately presented in the second window, and the first window and the second window are located in the same display interface.

[0062] When the user selects an object with the mouse for editing, the edited result is displayed truthfully in the second window, and the first window and the second window form a corresponding dual-screen mode, jointly displaying the content of the aircraft operation manual and the process of content changes.

[0063] It should be noted that when the user is editing, the user can choose to right-click in the first window to pop up the editing window, or right-click at an appropriate position in the second window to pop up the editing window for the user to edit. This will make the editing mode more flexible and convenient for users.

[0064] Specifically, when the user needs to extend the doctype plug-in, the user can edit the edit object through the toolbar of the display interface with the mouse, and the following steps are run in the background:

[0065] (1) Add the configuration of ATA2300 plug-in in the file with the suffix spd in the doctype directory to realize automatic loading of the ATA2300 plug-in to be added.

[0066] (2) Add a new file with the suffix sdt in the doctype directory, configure the reference relationship of the ATA2300 plug-in in the sdt file, and reference the xsd file in the sdt file.

[0067] (3) Add a file with the suffix py in the doctype directory, and configure the ATA2300 plug-in class and the business function logic implemented by the class in the py file.

[0068] Among them, the xsd file defines the structure and specifications of the flight operation manual data. The data specifications are modified by modifying the xsd file. There is an XSL file in the doctype directory. The XSL file is used to define the style of the edited data content displayed in the second window. The style is modified by modifying the XSL file.

[0069] In an example, first add the following to the cms_airbus_exch.spd file in the \doctypes\airbus directory:<template> <category>ATA2300< / category> < / template> , the front-end editor will automatically load the spd file plug-in in the doctype, and a new plug-in label will be added in Tools-Preferences in the editor's navigation bar. Then, add the plug-in name in .sdt (\doctypes\ata2300) to add the plug-in reference: <t:load-plugins>DoctypePublisher_Py DataWindow SDL-Trados-Translate-Tool Remove_w3c_attrs< / t:load-plugins> , realize the addition of new function menu. After that, add new py files, add button processing, menu positioning, etc., realize the logic processing of new functions, add new classes and class implementation, and the class implementation includes specific file directories.

[0070] When the user needs to add or modify an element, the following steps are performed:

[0071] (1) Get the current element as the editing object and record the element ID of the added element or the location information of the modified element.

[0072] (2) Obtain the xsd file in the doctypes directory, and use the xsd file to perform schema verification on the input content to ensure that the input content complies with the flight operations manual data standard.

[0073] (3) Check whether the parent node has been modified and whether the current tag supports the changeMark attribute. If so, add the changeMark attribute and changeType attribute to the current node and assign values ​​to them respectively. If not, get the parent node of the current node, add the changeMark attribute and changeType attribute to the parent node and assign values ​​to them respectively.

[0074] When the user needs to delete an element, it is implemented through the following steps:

[0075] (1) Get the current element as the editing object;

[0076] (2) in response to deleting the change summary, clearing the referenced rfuId attribute;

[0077] (3) in response to deleting the applicability, clearing the applicRefId attribute of the reference;

[0078] (4) Get the name of the current XSD file and the node attributes of the node changeMark;

[0079] (5) Get the change summary id and pop up a text input box for the change summary.

[0080] When the user needs to modify the properties, follow these steps:

[0081] (1) Get the current element as the editing object;

[0082] (2) Obtaining location information for attribute modification;

[0083] (3) Get the current XSD file name;

[0084] (4) Check whether the parent node has been modified and whether the current tag supports the changeMark attribute. If so, add the changeMark attribute and changeType attribute to the current node and assign values ​​to them respectively. If not, take the parent node, add the changeMark attribute and changeType attribute to the parent node and assign values ​​to them respectively.

[0085] When the user needs to add, delete or modify adaptability, it can be achieved through the following steps:

[0086] For adding applicability, obtain the service announcement data, the current editing object and the applicability node in the current DM, add the attribute id, add the node element displayText, add the node element evaluate and the corresponding attributes, add the node element assert and the corresponding attributes and perform the update operation, obtain the current XSD file name, traverse whether the parent node has been modified, and check whether the current tag supports the changeMark attribute. If supported, add the changeMark attribute and changeType attribute to the current node and assign values ​​respectively. If not supported, take the parent node, add the changeMark attribute and changeType attribute to the parent node and assign values ​​respectively.

[0087] For deleting applicability, get the current editing object, clear the referenced applicRefId, get the current XSD file name, get the node attribute of the node changeMark, get the change summary id, and pop up a text input box for the change summary.

[0088] For modification applicability, obtain the current editing object and modification location information, obtain the current XSD file name, traverse to see if the parent node has been modified, and check whether the current tag supports the changeMark attribute. If supported, add the changeMark attribute and changeType attribute to the current node and assign values ​​to them respectively. If not supported, get the parent node, add the changeMark attribute and changeType attribute to the parent node and assign values ​​to them respectively.

[0089] Applicability includes DM-level applicability and DM-internal applicability. The expression generated by DM-level applicability is located in the state identification part of DM, and the expression generated by DM-internal applicability is located in the content part of DM. In the front-end page, you can change the two through Tools-Applicability. When modifying the internal applicability, you can add further references to the element attributes that need to use the applicability.

[0090] When the user needs to modify the image reference, select the property window of the corresponding element in the structure tree of the first window, select the image to be replaced in the pop-up property box to complete the illustration replacement, and after the replacement is submitted, the new illustration will be displayed in the second window.

[0091] When the user needs to modify the reference, he can quickly add references to relevant technical content in the current document through Tools-References on the front page. A pop-up window for selecting reference content will be generated on the front page. After the reference is successfully modified, the corresponding reference link will be generated.

[0092] When the user needs to copy a table, it can be achieved in the following way:

[0093] Read and process the clipboard table, obtain the label position information selected by the mouse, and determine the label insertion position information;

[0094] Read non-pure text information in the clipboard content, calculate the number of table columns and obtain cell text and cell properties;

[0095] The first row of information in the table is determined as thead information, and the information after the first row is determined as tbody information, and an update operation is performed.

[0096] When the user needs to change the mark, the changeMark program control method is adopted. That is, when the writer makes changes to the technical content, the attribute changeMark=2 is automatically added to the current element or the parent node closest to the current element that allows the insertion of the changeMark tag. This attribute is used to identify the content that has been changed by the airline itself.

[0097] When the user needs to edit the summary, it can be achieved in the following ways:

[0098] Get the current summary as the editing object and generate the change summary id;

[0099] Get the content of the update reason, and the current cursor references the content of the update reason;

[0100] Get the current XSD file name;

[0101] Traverse to see if the parent node has been modified, and check whether the current tag supports the changeMark attribute. If it does, add the changeMark attribute and changeType attribute to the current node and assign values ​​to them respectively. If it does not, get the parent node of the current node, add the changeMark attribute and changeType attribute to the parent node and assign values ​​to them respectively.

[0102] When deleting the change summary, the referenced rfuId needs to be cleared at the same time.

[0103] In order to make the content entered in the editing process conform to the technical publication data standard (i.e., S1000D specification and ATA Spec2300 specification), this embodiment also has a verification function. When verifying, first obtain the XSD file name, then obtain the storage directory of the local style, and then splice the XSD file directory, and then automatically verify the document according to the constraints of the Schema. When content that does not comply with the Schema constraints is found, an error prompt will be automatically given, and the corresponding error location can be located by clicking the error prompt. Before saving and submitting the document, it is necessary to ensure that all content passes the integrity check.

[0104] A second embodiment of the present invention discloses a structured editing system for aircraft operation manuals, including a file receiving module, a file parsing module and an editing response module.

[0105] A file receiving module, used to receive a structured aircraft operation manual, wherein the aircraft operation manual is a file in XML format;

[0106] A file parsing module, used for parsing the aircraft operation manual, displaying the parsed tree structure in the form of operation tree nodes in the first window, and displaying the parsed data content in the second window;

[0107] The editing response module is used to respond to the mouse selecting any editing object in the first window for editing, and the edited data content is immediately presented in the second window. The first window and the second window are located in the same display interface.

[0108] Since the first embodiment corresponds to this embodiment, this embodiment can be implemented in conjunction with the first embodiment. The relevant technical details mentioned in the first embodiment are still valid in this embodiment, and the technical effects that can be achieved in the first embodiment can also be achieved in this embodiment. In order to reduce repetition, they are not repeated here. Accordingly, the relevant technical details mentioned in this embodiment can also be applied in the first embodiment.

[0109] The third embodiment of the present invention relates to a computer-readable storage medium having a computer program / instruction stored thereon, wherein the computer program / instruction implements the steps of the method in the first embodiment when executed by a processor.

[0110] The preferred specific embodiments of the present invention are described in detail above. It should be understood that ordinary technicians in the field can make many modifications and changes based on the concept of the present invention without creative work. Therefore, all technical solutions that can be obtained by technicians in the technical field based on the concept of the present invention through logical analysis, reasoning or limited experiments on the basis of the prior art should be within the scope of protection determined by the claims.

Claims

1. A structured editing method for aircraft operation manuals, characterized in that: The following steps are involved: Receiving a structured aircraft operation manual, wherein the aircraft operation manual is an XML format file; Parsing the aircraft operation manual, displaying the parsed tree structure in the form of operation tree nodes in the first window, and displaying the parsed data content in the second window; In response to the mouse selecting any editing object in the first window or the second window for editing, the edited data content is immediately presented in the second window, and the first window and the second window are located in the same display interface.

2. The structured editing method for aircraft operation manual according to claim 1, characterized in that: In response to the mouse selecting the doctype plug-in in the first window or the second window for dynamic expansion, the following steps are implemented: Add the configuration of ATA2300 plug-in in the file with the suffix spd in the doctype directory to realize automatic loading of the ATA2300 plug-in to be added; Add a new file with the suffix sdt in the doctype directory, configure the reference relationship of the ATA2300 plug-in in the sdt file, and reference the xsd file in the sdt file; Add a new file with the suffix py in the doctype directory, and configure the ATA2300 plug-in class and the business function logic implemented by the class in the py file. Among them, the xsd file defines the structure and specifications of the flight operation manual data. The data specifications are modified by modifying the xsd file. There is an XSL file in the doctype directory. The XSL file is used to define the style of the edited data content displayed in the second window. The style is modified by modifying the XSL file.

3. The structured editing method for aircraft operation manual according to claim 1, characterized in that: In response to the mouse selecting the current element in the first window or the second window as the editing object to be added or modified, the following steps are implemented: Get the current element as the editing object and record the element ID of the added element or the position information of the modified element; Obtain the xsd file in the doctypes directory, and use the xsd file to perform schema verification on the input content to ensure that the input content complies with the flight operations manual data standard; Traverse to see if the parent node has been modified, and check whether the current tag supports the changeMark attribute. If it does, add the changeMark attribute and changeType attribute to the current node and assign values ​​to them respectively. If it does not, get the parent node, add the changeMark attribute and changeType attribute to the parent node and assign values ​​to them respectively.

4. The structured editing method for aircraft operation manual according to claim 1, characterized in that: In response to the mouse selecting the current element in the first window or the second window as the editing object for deletion, the following steps are implemented: Get the current element as the editing object; In response to deleting the change summary, clearing the referenced rfuId attribute; In response to deleting the applicability, clearing the applicRefId attribute of the reference; Get the name of the current XSD file and the node attributes of the node changeMark; Get the change summary id and pop up a text input box for the change summary.

5. The structured editing method for aircraft operation manual according to claim 1, characterized in that: In response to the mouse modifying the properties in the first window or the second window, the following steps are performed: Get the current element as the editing object; Get the location information for attribute modification; Get the current XSD file name; Traverse to see if the parent node has been modified, and check whether the current tag supports the changeMark attribute. If it does, add the changeMark attribute and changeType attribute to the current node and assign values ​​to them respectively. If it does not, take the parent node, add the changeMark attribute and changeType attribute to the parent node and assign values ​​to them respectively.

6. The structured editing method for aircraft operation manual according to claim 1, characterized in that: In response to the mouse performing applicability editing in the first window or the second window, the following steps are performed: For adding applicability, obtain the service announcement data, the current editing object and the applicability node in the current DM, add the attribute id, add the node element displayText, add the node element evaluate and the corresponding attributes, add the node element assert and the corresponding attributes and perform the update operation, obtain the current XSD file name, traverse whether the parent node has been modified, and check whether the current tag supports the changeMark attribute. If it does, add the changeMark attribute and changeType attribute to the current node and assign values ​​respectively. If it does not support, get the parent node, add the changeMark attribute and changeType attribute to the parent node and assign values ​​respectively. For deleting applicability, get the current editing object, clear the referenced applicRefId, get the current XSD file name, get the node attribute of the node changeMark, get the change summary id, and pop up a text input box for the change summary; For modification applicability, obtain the current editing object and modification location information, obtain the current XSD file name, traverse to see if the parent node has been modified, and check whether the current tag supports the changeMark attribute. If supported, add the changeMark attribute and changeType attribute to the current node and assign values ​​to them respectively. If not supported, get the parent node, add the changeMark attribute and changeType attribute to the parent node and assign values ​​to them respectively.

7. The structured editing method for aircraft operation manual according to claim 1, characterized in that: In response to the mouse editing the copy table in the first window or the second window, the following steps are implemented: Read and process the clipboard table, obtain the label position information selected by the mouse, and determine the label insertion position information; Read non-pure text information in the clipboard content, calculate the number of table columns and obtain cell text and cell properties; The first row of information in the table is determined as thead information, and the information after the first row is determined as tbody information, and an update operation is performed.

8. The structured editing method for aircraft operation manual according to claim 1, characterized in that: In response to the mouse performing summary editing in the first window or the second window, the following steps are performed: Get the current summary as the editing object and generate the change summary id; Get the content of the update reason, and the current cursor references the content of the update reason; Get the current XSD file name; Traverse to see if the parent node has been modified, and check whether the current tag supports the changeMark attribute. If it does, add the changeMark attribute and changeType attribute to the current node and assign values ​​to them respectively. If it does not, get the parent node, add the changeMark attribute and changeType attribute to the parent node and assign values ​​to them respectively.

9. A structured editing system for aircraft operation manuals, characterized in that: Includes the following modules: A file receiving module, used to receive a structured aircraft operation manual, wherein the aircraft operation manual is a file in XML format; A file parsing module, used for parsing the aircraft operation manual, displaying the parsed tree structure in the form of operation tree nodes in the first window, and displaying the parsed data content in the second window; The editing response module is used to respond to the mouse selecting any editing object in the first window or the second window for editing, and the edited data content is immediately presented in the second window. The first window and the second window are located in the same display interface.

10. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, which, when processed and executed, implements the structured editing method for aircraft operation manuals according to any one of claims 1 to 8.

Images