A semantic extended report rendering method and system based on a third-party table engine

Abstract

This invention relates to the field of power information and visualization reporting technology, and provides a semantic extension report rendering method and system based on a third-party table engine. The method includes: establishing a non-intrusive semantic extension layer on the cell objects of the third-party table engine; reading the number of frozen rows and columns based on the semantic extension layer and performing four-zone segmentation; calculating an adaptive scaling scheme based on the four-zone structure; and performing placeholder replacement, formula evaluation, and result backfilling on each cell in the same row according to the topological order based on the formula fields of the semantic extension layer. If circular dependencies are detected, an exception flag is triggered, and the operation history is recorded after the evaluation is completed. This invention achieves high consistency in layout across resolution terminals through non-intrusive embedding of independent data keys, allowing for independent engine upgrades and significantly reducing maintenance costs; it improves rendering performance through four-zone segmentation and local redrawing; it reduces the pressure of backend serial calculations through dependency topology evaluation driven by the formula fields of the semantic extension layer.

Description

Technical Field

[0001] This invention relates to the field of visual reporting and interactive computing technology, and in particular to a semantically extended report rendering method and system based on a third-party table engine. Background Technology

[0002] In the development of enterprise-level visual reporting products, mature third-party spreadsheet engines (such as Luckysheet) are typically chosen as the underlying rendering component to reuse their existing capabilities in cell rendering, formula engines, and keyboard interaction. However, the data models of third-party spreadsheet engines are designed for general spreadsheets and do not natively support the semantic fields required for reporting (such as cell type, data-bound columns, parent-cell relationships, and expansion directions), which leads to the following technical problems:

[0003] (1) Existing solutions usually mix business semantic fields and engine display fields in the engine data structure, resulting in strong coupling between the business layer and the engine layer. When the engine is upgraded or replaced, the field mapping logic needs to be completely modified, resulting in extremely high maintenance costs.

[0004] (2) Third-party engines usually render all data in a single large table. In the scenario of frozen rows and columns, the scrolling linkage depends on the internal logic of the engine, resulting in a large redrawing range and poor performance.

[0005] (3) The engine does not have a built-in adaptive scaling mechanism for multi-terminal containers. The simple stretching scheme does not compensate for the height of the toolbar and the width of the scroll bar, resulting in poor display consistency across resolutions.

[0006] (4) The engine formula calculation is based on general cell address references and does not support the replacement of row number placeholders and the evaluation of row dependency in the filling scenario. The front end lacks an explicit topology evaluation mechanism.

[0007] Therefore, there is an urgent need for a non-intrusive extension mechanism that can establish business semantics and engine display without modifying third-party table engines. Summary of the Invention

[0008] The purpose of this invention is to provide a semantically extended report rendering method and system based on a third-party table engine, which can meet the requirements.

[0009] This invention is implemented as follows: a semantically extended report rendering method and system based on a third-party table engine, the method comprising:

[0010] S1: Establish a non-intrusive semantic extension layer on the cell objects of a third-party table engine: using independent data keys DATA KEYBusiness semantic fields are written to the engine cell object without overwriting the engine's native display fields. Business semantic fields include type fields, data fields, and extended fields. Type fields are used to identify data columns, text, formulas, charts, images, or diagonal lines. Extended fields include parent cell relationships, extension direction, control properties, conditional properties, and link properties. Bidirectional synchronization of display fields between the business layer and the engine layer is achieved through toSheetValue or toValue enumeration mapping rules.

[0011] S2: Based on the semantic extension layer, read the number of frozen rows and columns, and perform four-area segmentation: divide the report data into four independent data objects: row and column double-frozen area, frozen row area, frozen column area, and content area, to maintain the row height array, column width array, and size parameters of each area; when the content area scrolls horizontally, only the offset of the frozen row area is updated, and when it scrolls vertically, only the offset of the frozen column area is updated. The row and column double-frozen area is always fixed, realizing the linkage display of local redrawing;

[0012] S3: Based on the four-zone structure divided in step S2, read the visible width and height of the container, the scroll bar size, the toolbar height and the reserved width, calculate the horizontal scaling ratio and the vertical scaling ratio respectively, and perform synchronous scaling rendering on the four zones according to the adaptive mode, that is, according to the horizontal scaling ratio and the vertical scaling ratio, and recalculate in real time when the window size changes.

[0013] S4: Based on the formula field of the cell in the semantic extension layer, parse the row and column placeholders in the expression during the filling or adding of a row, register the currentRowNum class placeholder reference as a dependency node and build a dependency graph, and perform placeholder replacement, formula evaluation and result backfilling on each cell in the same row in topological order. If a circular dependency is detected, an exception flag is triggered. After the evaluation is completed, the operation history is recorded.

[0014] Preferably, the non-intrusive semantic extension layer is established using an independent data key DATA. KEY As a business semantic namespace, business semantic fields are stored in isolation from the native fields of the third-party table engine. When the fields displayed in the business layer change, the corresponding fields are written to the engine through the toSheetValue rule. When the engine triggers the sheetUpdated event, the engine fields are synchronized back to the business semantic object through the toValue rule. This ensures that the display is consistent between the design state and the runtime state, and that no native operation of the engine destroys the business semantic data.

[0015] Preferably, the toSheetValue or toValue enumeration mapping rule defines the conversion function between each business field and the engine field in an enumeration manner, supporting type conversion, formatting, and default value backfilling; when the engine version upgrade causes changes in internal fields, only the enumeration mapping rule needs to be updated, without modifying the engine source code or business logic code, thereby isolating the impact of engine version changes.

[0016] Preferably, the strategy for dividing the four areas is as follows: cells with a row index less than the number of frozen rows and a column index less than the number of frozen columns are assigned to the double-frozen row and column area; cells with a row index less than the number of frozen rows and a column index not less than the number of frozen columns are assigned to the frozen row area; cells with a row index not less than the number of frozen rows and a column index less than the number of frozen columns are assigned to the frozen column area; the remaining cells are assigned to the content area; when the content area scrolls horizontally, the offset of the frozen row area is updated synchronously via scrollLeft, and when scrolling vertically, the offset of the frozen column area is updated synchronously via scrollTop.

[0017] Preferably, when the adaptive mode is horizontal, the output scaling parameter (s) is... x ,s y )=(r x ,1), when the mode is bothway, the output is (s x ,s y )=(r x ,r y When the mode is none, the output is (s) x ,s y )=(1,1); Optionally, r is introduced min and r max Set upper and lower bounds for the scaling ratio to prevent excessive shrinking or enlarging that could render the content unreadable.

[0018] Preferably, the operation history includes operation type, data model identifier, field name and target value, supporting subsequent batch submission, operation replay or audit trace; the new row evaluation process is as follows: insert temporary row and initialize editable cell, build peer dependency graph, topology evaluation, backfill result and write operation history.

[0019] A non-intrusive semantically extended report rendering system based on a third-party table engine includes:

[0020] The semantic extension layer management module is used to create and maintain a non-intrusive semantic extension layer with independent data keys on cells of third-party table engines, and to perform bidirectional synchronization between toSheetValue and toValue.

[0021] The partitioned rendering module reads the frozen parameters based on the semantic extension layer, divides the data into four regions, and maintains an independent rendering queue and linked offset.

[0022] The adaptive calculation module calculates and distributes horizontal and vertical scaling parameters based on the data reading container and environmental parameters of the four zones;

[0023] The dependency evaluation module, based on the formula fields of the semantic extension layer, parses placeholders, constructs a dependency graph, and performs topological evaluation.

[0024] The operation history management module records the data entry operations and generates incremental data packets that can be submitted.

[0025] Preferably, the semantic extension layer management module realizes the data backflow from the engine to the business layer by listening to the sheetUpdated event of the third-party table engine. No modifications or patches need to be made to the engine source code, and the engine can be upgraded independently without affecting the integrity of the business semantic data.

[0026] A computer-readable storage medium having a computer program stored thereon.

[0027] Compared with the prior art, the beneficial effects of the present invention are:

[0028] 1. Through non-intrusive embedding of independent data keys, business semantics are completely decoupled from the engine data model, the engine can be upgraded independently, and maintenance costs are significantly reduced;

[0029] 2. By dividing the data into four zones and redrawing locally, the range of large report freeze scrolling redraw is reduced to single zone offset update, which greatly improves rendering performance;

[0030] 3. By compensating for the dual-axis scaling of the scroll bar and toolbar height, consistent layout height is achieved across resolution terminals;

[0031] 4. By using the semantic extension layer formula field-driven dependency topology evaluation, the results of chained formula calculations are reliable, reducing the pressure of backend serial calculations. Attached Figure Description

[0032] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0033] Figure 1 This is a flowchart of the overall method of the present invention; Figure 2 This is a schematic diagram of the non-intrusive semantic extension layer structure of the present invention; Figure 3 This is a schematic diagram of the frozen partition rendering and scrolling linkage of the present invention; Figure 4This is a flowchart of the adaptive scaling calculation of the present invention; Figure 5 This is a flowchart of peer dependency evaluation for this invention. Detailed Implementation

[0034] To better understand the technical content of this invention, the technical solutions of this invention are further described and explained below with reference to specific embodiments, but are not limited thereto. The technical solutions of the embodiments of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this invention, and not all embodiments. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention.

[0035] Example 1

[0036] like Figures 1 to 2 As shown, a semantically extended report rendering method and system based on a third-party table engine is disclosed. The method includes:

[0037] I. Non-intrusive semantic extension layer scheme

[0038] Create a non-intrusive semantic extension layer on the cell objects of a third-party table engine:

[0039] With independent data key DATA KEY As a business semantic namespace, business semantic fields are parasitically written into the cell objects of the third-party table engine, without reading or writing the engine's native display fields, thus isolating the business semantic fields from the native fields of the third-party table engine. The business semantic fields consist of three layers: a type layer (type) to identify the cell's functional type, a data layer (data) to store data binding identifiers and values, and an extension layer (extension) to store attributes such as parent cells, extension directions, controls, conditions, and links. Display fields are decoupled from engine fields through enumeration mapping rules: when a business layer display field changes, the toSheetValue rule is called to write the corresponding field to the engine; when the engine triggers the sheetUpdated event, the toValue rule is used to reverse-synchronize the engine field back to the business semantic object. This ensures consistency between design-state and runtime display. When the engine is upgraded, only the mapping rule enumeration needs to be updated, without modifying the engine source code or business logic, ensuring the integrity and maintainability of the semantic layer data. The toSheetValue or toValue enumeration mapping rules define the conversion function between each business field and the engine field in an enumeration manner, supporting type conversion, formatting, and default value backfilling. When the engine version upgrade causes changes in internal fields, only the enumeration mapping rules need to be updated, without modifying the engine source code or business logic code, thereby isolating the impact of engine version changes.

[0040] II. Freezing Partition Rendering Scheme Based on Semantic Extension Layer

[0041] Based on the semantic extension layer, read the number of frozen rows (fix) rows ) and the number of frozen columns (fix) cols The report data is divided into four independent data objects: a double-frozen row and column area (fixRowColumnTableData), a frozen row area (fixRowTableData), a frozen column area (fixColumnTableData), and a content area (contentTableData). These objects are used to maintain the row height array, column width array, and size parameters for each area. When the content area scrolls horizontally, the frozen row area offset is updated only via scrollLeft, and when scrolling vertically, the frozen column area offset is updated only via scrollTop. The double-frozen row and column areas remain fixed, enabling linked display during partial redraws and completely avoiding stuttering and misalignment caused by full table redraws. The specific strategy for dividing the four zones is as follows: cells with a row index less than the number of frozen rows and a column index less than the number of frozen columns are placed in the double-frozen row and column zone; cells with a row index less than the number of frozen rows and a column index not less than the number of frozen columns are placed in the frozen row zone; cells with a row index not less than the number of frozen rows and a column index less than the number of frozen columns are placed in the frozen column zone; the remaining cells are placed in the content zone. When the content zone scrolls horizontally, the offset of the frozen row zone is updated synchronously via scrollLeft; when scrolling vertically, the offset of the frozen column zone is updated synchronously via scrollTop. The triggering conditions for local redrawing include: scroll events, window / container size changes, and cell data or style changes. The system uses event merging and debouncing scheduling for high-frequency updates, performing local rendering according to the affected area to avoid repeated rendering and flickering. The double-frozen row and column zones are fixed, and the frozen row / column zones only undergo corresponding directional offset linkage, thereby reducing the redrawing range and rendering overhead.

[0042] III. Adaptive Scaling Scheme Based on Four-Zone Structure

[0043] Based on the four-zone structure, the visible width and height of the container, scroll bar size, toolbar height and reserved width are read, and the horizontal scaling ratio and vertical scaling ratio are calculated respectively. According to the adaptive mode, the four zones are synchronously scaled and rendered according to the horizontal scaling ratio and vertical scaling ratio, and the calculation is recalculated in real time when the window size changes.

[0044] Define variable: Total column width of the report Head Office Report .

[0045] in, , These represent the width of each column in the report and the row height of each row in the report, respectively.

[0046] Horizontal scaling ratio: (1)

[0047] Vertical scaling ratio: (2)

[0048] in, , These are the visible width and height of the container, respectively. To reserve width, , These are the width and height of the scroll bar, respectively. This is the height of the toolbar.

[0049] Optionally, upper and lower bound constraints can be introduced:

[0050] (3)

[0051] (4)

[0052] When no constraints are configured .

[0053] The output of scaling mode M satisfies a piecewise function:

[0054] (5)

[0055] The scaling parameters mentioned above are recalculated in real time when the window size changes and are applied synchronously to the four partitions to maintain cross-terminal layout stability.

[0056] The real-time recalculation when the window size changes includes: monitoring changes in the window or container size; re-collecting parameters (container visible size, scroll bar size, toolbar height, total column width / total row height of the report, etc.); and recalculating according to the above formula. / And apply it simultaneously to the four zones; if there is no significant difference between the old and new ratios, the rearrangement can be skipped to avoid invalid redrawing.

[0057] IV. Dependency Topology Evaluation Scheme Based on Semantic Extension Layer Formula Fields

[0058] Based on the formula fields of the cells in the semantic extension layer, row and column placeholders in the expression are parsed during the filling or adding of rows. Placeholder references of the `currentRowNum` class are registered as dependency nodes, and a dependency graph is constructed. Placeholder replacement, formula evaluation, and result backfilling are performed on each cell within the same row in topological order. If a circular dependency is detected, an exception flag is triggered. After evaluation, the operation history is recorded. `currentRowNum` refers to the row number of the current target row (actual row) during the adding / filling evaluation process, used to locate dependency references and placeholder replacements within the current row. The operation history includes the operation type, data model identifier, field name, and target value, supporting subsequent batch submissions, operation replay, or audit trails. The adding row evaluation process is as follows: insert a temporary row and initialize editable cells, construct the same row dependency graph, perform topological evaluation, backfill the result, and write the operation history.

[0059] When adding a new row or editing data, the system reads the currentRowNum and originRowNum placeholders from the formula fields of the semantic extension layer cells; registers the currentRowNum reference as a dependency node and constructs a peer dependency graph; uses topological sorting to determine the evaluation order, and executes "placeholder replacement → formula engine evaluation → result backfilling" sequentially; if a circular dependency is detected, an exception flag is triggered and the evaluation of that cell is aborted; after the complete process is completed, the operation record is written to the operation history, supporting batch submission and auditing.

[0060] During system initialization, DATA KEY Using independent namespace keys, business semantic fields (type, data binding, extended attributes) from the report configuration are written into the extended attributes of the cell object in the third-party spreadsheet engine (such as Luckysheet), without modifying the engine's native fields such as m (display value), v (calculated value), fc (font color), bg (background color), and fs (font size). When the design side modifies the cell style, the toSheetValue enumeration mapping is called to write the corresponding field into the engine; when the user edits in the engine and triggers the sheetUpdated event, the toValue enumeration mapping is called to synchronize the engine fields back to the business semantic object. When the engine is upgraded from v1 to v2, causing an internal field to be renamed, only the conversion logic of that field needs to be updated in the mapping enumeration; the rest of the business code remains unchanged.

[0061] The batch submission frontend continuously writes multiple cell changes to opHistory (aggregated by rowId + dataModel) during the editing process. When submitting, opHistory is serialized into an incremental data packet and sent to the backend all at once. The backend distributes the data to the add / update / delete logic according to operatorType and commits the transaction. After opHistory aggregation, submitUpdate is called uniformly. The operation replay reads the operation log in ascending order of ts; newValue is executed to backfill (or delete) the target row fields in sequence; if reverse replay (undo) is required, oldValue is used to restore in reverse time order. Therefore, it is recommended to replenish oldValue, otherwise only "forward replay" is possible, not "reverse restoration". The audit trail persists the operation packet as an audit record for each submission, which includes at least: report ID, dataModel, rowId, field, old / new, operatorId, ts, and request ID; the query is filtered by time, operator, and data model to form a field-level change chain; it can output audit evidence of "who changed which field from A to B when".

[0062] Example 2

[0063] like Figures 3 to 4 As shown, partitioned rendering and adaptive scaling work together:

[0064] The system reads reports from the semantic extension layer. , The configuration is frozen, dividing the data into four independent data objects: fixRowColumnTableData (top left 2 rows 1 column), fixRowTableData (top 2 rows and remaining columns), fixColumnTableData (leftmost first column and remaining rows), and contentTableData (the rest of the area). Each area maintains its own column width array and row height array, ensuring no interference between them.

[0065] Then read the container parameters and set... , , , , , Total column width of the report Head Office Substituting into formulas (1) and (2), we get:

[0066] .

[0067] when hour, This is applied synchronously to all four zones, ensuring that the content precisely fills the current container. These parameters are recalculated in real-time when the window size changes, ensuring consistent layout across different devices.

[0068] Example 3

[0069] like Figure 5 As shown, dependency evaluation based on the semantic extension layer:

[0070] Users can add a new row to the power line loss statistics report, which contains a formula field:

[0071] Cell A: Fixed value "Income" (no placeholder, fill directly)

[0072] Cell B: Expression "currentRowNum, Revenue" - "currentRowNum, Cost" (depends on A and C)

[0073] Cell C: Fixed value "Cost" (no placeholder, fill directly)

[0074] Cell D: Expression "currentRowNum, Gross Profit" / "currentRowNum, Revenue" (depends on B and A)

[0075] The system reads the semantic extension layer formula fields of each cell, extracts the currentRowNum placeholder, and constructs a dependency graph: D depends on B and A, B depends on A and C, and A / C have no dependency. After topological sorting, the evaluation order is: A→C→B→D. The system then replaces the placeholders, calls the formula engine to evaluate, and backfills the results. Finally, D (gross profit margin) obtains the correct calculated value and is written to the operation history for subsequent batch submissions to the backend.

[0076] The embodiments described above are only some embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. Any equivalent substitutions or modifications made by those skilled in the art within the technical scope disclosed in the present invention, based on the technical solution and inventive concept of the present invention, should be covered within the scope of protection of the present invention. Parts not covered in the present invention are the same as or can be implemented using existing technology.

Claims

1. A non-intrusive semantic extended report rendering method based on a third-party table engine, characterized in that, The method includes: S1: Establish a non-intrusive semantic extension layer on the cell objects of the third-party table engine: Write business semantic fields to the engine cell objects with independent data keys, without overwriting the engine's native display fields; business semantic fields include type fields, data fields, and extended fields. Type fields are used to identify data columns, text, formulas, charts, images, or diagonal lines. Extended fields include parent-cell relationships, extension direction, control properties, conditional properties, and link properties; achieve bidirectional synchronization of display fields between the business layer and the engine layer through toSheetValue or toValue enumeration mapping rules; S2: Based on the semantic extension layer, read the number of frozen rows and columns, and perform four-area segmentation: divide the report data into four independent data objects: row and column double-frozen area, frozen row area, frozen column area, and content area, to maintain the row height array, column width array, and size parameters of each area; when the content area scrolls horizontally, only the offset of the frozen row area is updated, and when it scrolls vertically, only the offset of the frozen column area is updated. The row and column double-frozen area is always fixed, realizing the linkage display of local redrawing; S3: Based on the four-zone structure divided in step S2, read the visible width and height of the container, the scroll bar size, the toolbar height and the reserved width, calculate the horizontal scaling ratio and the vertical scaling ratio respectively, and perform synchronous scaling rendering on the four zones according to the adaptive mode, that is, according to the horizontal scaling ratio and the vertical scaling ratio, and recalculate in real time when the window size changes. S4: Based on the formula field of the cell in the semantic extension layer, parse the row and column placeholders in the expression during the filling or adding of a row, register the currentRowNum class placeholder reference as a dependency node and build a dependency graph, and perform placeholder replacement, formula evaluation and result backfilling on each cell in the same row in topological order. If a circular dependency is detected, an exception flag is triggered. After the evaluation is completed, the operation history is recorded.

2. The non-intrusive semantic extended report rendering method based on a third-party table engine as described in claim 1, characterized in that, The non-intrusive semantic extension layer is established using an independent data key DATA. KEY As a business semantic namespace, business semantic fields are stored in isolation from the native fields of the third-party table engine. When the fields displayed in the business layer change, the corresponding fields are written to the engine through the toSheetValue rule. When the engine triggers the sheetUpdated event, the engine fields are synchronized back to the business semantic object through the toValue rule. This ensures that the display is consistent between the design state and the runtime state, and that no native operation of the engine destroys the business semantic data.

3. The non-intrusive semantic extended report rendering method based on a third-party table engine as described in claim 1, characterized in that, The toSheetValue or toValue enumeration mapping rules define the conversion function between each business field and the engine field in an enumeration manner, supporting type conversion, formatting, and default value backfilling. When the engine version upgrade causes changes in internal fields, only the enumeration mapping rules need to be updated, without modifying the engine source code or business logic code, thereby isolating the impact of engine version changes.

4. The non-intrusive semantic extended report rendering method based on a third-party table engine as described in claim 1, characterized in that, The specific strategy for dividing the content into four zones is as follows: cells with a row index less than the number of frozen rows and a column index less than the number of frozen columns are placed in the double-frozen row and column zone; cells with a row index less than the number of frozen rows and a column index not less than the number of frozen columns are placed in the frozen row zone; cells with a row index not less than the number of frozen rows and a column index less than the number of frozen columns are placed in the frozen column zone; and the remaining cells are placed in the content zone. When the content zone scrolls horizontally, the offset of the frozen row zone is updated synchronously via scrollLeft, and when it scrolls vertically, the offset of the frozen column zone is updated synchronously via scrollTop.

5. The non-intrusive semantic extended report rendering method based on a third-party table engine as described in claim 1, characterized in that, When the adaptive mode is horizontal, the output scaling parameter (s) is... x ,s y )=(r x ,1), when the mode is bothway, the output is (s x ,s y )=(r x ,r y When the mode is none, the output is (s) x ,s y )=(1,1); Optionally, introduce r min and r max Set upper and lower bounds for the scaling ratio to prevent excessive shrinking or enlarging that could render the content unreadable.

6. The non-intrusive semantic extended report rendering method based on a third-party table engine as described in claim 1, characterized in that, The operation history includes operation type, data model identifier, field name and target value, and supports subsequent batch submission, operation replay or audit trace; the new row evaluation process is as follows: insert temporary row and initialize editable cell, build peer dependency graph, topology evaluation, backfill results and write to operation history.

7. A non-intrusive semantic extended report rendering system based on a third-party table engine, characterized in that, Implementing any one of the methods as claimed in claims 1-6 includes: The semantic extension layer management module is used to create and maintain a non-intrusive semantic extension layer with independent data keys on cells of third-party table engines, and to perform bidirectional synchronization between toSheetValue and toValue. The partitioned rendering module reads the frozen parameters based on the semantic extension layer, divides the data into four regions, and maintains an independent rendering queue and linked offset. The adaptive calculation module calculates and distributes horizontal and vertical scaling parameters based on the data reading container and environmental parameters of the four zones; The dependency evaluation module, based on the formula fields of the semantic extension layer, parses placeholders, constructs a dependency graph, and performs topological evaluation. The operation history management module records the data entry operations and generates incremental data packets that can be submitted.

8. The non-intrusive semantic extended report rendering system based on a third-party table engine as described in claim 7, characterized in that, The semantic extension layer management module enables data backflow from the engine to the business layer by listening to the sheetUpdated event of the third-party table engine. No modifications or patches are required to the engine source code, and the engine can be upgraded independently without affecting the integrity of the business semantic data.

9. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements any one of the methods of claims 1 to 6.

Images