WO2008015787A1

WO2008015787A1 - Document processing apparatus and document processing method

Info

Publication number: WO2008015787A1
Application number: PCT/JP2007/000819
Authority: WO
Inventors: Tomoaki Fukura; Yoshiyuki Sakamoto; Hidehiko Yasutomi
Original assignee: Justsystems Corporation
Priority date: 2006-07-31
Filing date: 2007-07-31
Publication date: 2008-02-07
Also published as: JPWO2008015787A1

Abstract

A document processing apparatus (100) is provided with an AVC component (3010) for table display, which is a processing module to be used as a general purpose component for processing data in documents and operating prescribed functions; an AVC component (3020) for chart display; an AVC component (3030) for UI part display; and an AVC component (3040) for tree display. An AVC component switching section (3050) permits the AVC component to be applicable to data by switching a plurality of different AVC components for the same data.

Description

Specification

Document processing apparatus and document processing method

Technical field

[0001] The present invention relates to a document processing technique, and more particularly to a document processing apparatus and method for processing a document described in a markup language.

Background art

[0002] XML has been attracting attention as a format suitable for sharing data with others over networks, etc., and an application for creating, displaying, and editing XML documents has been developed ( For example, see Patent Document 1).

Patent Document 1: Japanese Patent Laid-Open No. 2 00 1 _ 2 90 80 4

Disclosure of the invention

Problems to be solved by the invention

[0003] A poch-library is allowed to be defined arbitrarily, and in theory, there can be an infinitely many pockies. It is impractical to provide a dedicated display and editing environment corresponding to all of these Poch libraries. In the past, when editing a document described in a library that does not have a dedicated editing environment, the source of the document composed of text data was directly edited using a text editor or the like. We have succeeded in developing an environment that can edit XML documents described in Pokémon. We are also aiming to develop more convenient XML document processing technology.

The present invention has been made in view of such circumstances, and an object of the present invention is to provide a technique for improving user convenience when processing a document described in a markup language. .

Means for solving the problem

[0005] One embodiment of the present invention relates to a document processing apparatus. This document processing apparatus includes a plurality of processing modules that can be used as general-purpose parts for processing data in a document to express a predetermined function, and a plurality of different previous modules for the same data. And a switching unit that can be applied by switching the processing module.

[0006] The document may include a tag set component that is described in a markup language and can be processed by the processing module. In order to process the component, the tag set to which the component belongs is selected. The processing module capable of processing may be activated.

[0007] When switching the processing module, the switching unit is configured to change the component from a tag set component that can be processed by the switching source processing module to a tag set configuration that can be processed by the switching destination processing module. It may be rewritten as an element.

[0008] The document processing apparatus may further include a property setting unit that receives a parameter setting necessary for the operation of the processing module, and the property setting unit receives the received parameter as the component element or its descendant. The element value or attribute value of the component may be described in the document.

[0009] When the processing module is switched, the property setting unit switches the setting of the parameter used in common between the switching source processing module and the switching destination processing module from the switching source processing module. It may be set automatically by inheriting to the previous processing module.

[0010] The property setting unit may accept a setting of a data type in the document processed by the processing module. The property setting unit accepts the setting of text data to be displayed as a label of the data when the processing module displays the data in the document on the screen, and the text data to be displayed as the label of the data is a user If not set from, the element name of the data may be set as a label.

[001 1] Another embodiment of the present invention relates to a document processing method. The document processing method includes a step of applying any one of a plurality of processing modules that can be used as general-purpose components for processing data in a document and expressing a predetermined function to the data in the document. And switching and applying another processing module to data in the same document. [0012] It should be noted that any combination of the above-described constituent elements, and a conversion of the expression of the present invention between a method, an apparatus, a system, and the like are also effective as an aspect of the present invention.

The invention's effect

[0013] According to the present invention, it is possible to provide a technique for appropriately processing data structured in a markup language.

Brief Description of Drawings

FIG. 1 is a diagram showing a configuration of a document processing apparatus according to a base technology.

FIG. 2 is a diagram showing an example of an XML document edited by a document processing apparatus.

FIG. 3 is a diagram showing an example of mapping the XML document shown in FIG. 2 to a table described in HTML.

[FIG. 4 (a)] is a diagram showing an example of a definition file for mapping the XML document shown in FIG. 2 to the table shown in FIG.

[FIG. 4 (b)] is a diagram showing an example of a definition file for mapping the XML document shown in FIG. 2 to the table shown in FIG.

FIG. 5 is a diagram showing an example of a screen displayed by mapping the XML document shown in FIG. 2 to the HTML file corresponding to the correspondence shown in FIG.

FIG. 6 is a diagram showing an example of a graphical user interface presented to the user by the definition file generation unit in order for the user to generate a definition file.

FIG. 7 is a diagram showing another example of the screen layout generated by the definition file generation unit.

FIG. 8 is a diagram showing an example of an XML document editing screen by the document processing apparatus.

FIG. 9 is a diagram showing another example of an XML document edited by the document processing apparatus.

FIG. 10 is a diagram showing an example of a screen displaying the document shown in FIG.

[FIG. 11 (a)] is a diagram showing a basic configuration of a document processing system.

[FIG. 11 (b)] is a diagram showing a block diagram of the entire document processing system.

[FIG. 11 (c)] is a block diagram of the entire document processing system.

FIG. 12 is a diagram showing details of the document management unit.

FIG. 13 is a diagram showing the details of the poker library connection subsystem. FIG. 14 is a diagram showing details of the relationship between the program starter and other components.

FIG. 15 is a diagram showing the details of the structure of the application service reloaded by the program startup unit.

FIG. 16 is a diagram showing details of the core component bowl.

FIG. 17 is a diagram showing details of a document management unit.

FIG. 18 is a diagram showing details of an undo framework and an undo command.

FIG. 19 is a diagram showing how a document is loaded in the document processing system.

FIG. 20 shows an example of a document and its expression.

FIG. 21 is a diagram showing a relationship between a model and a controller.

FIG. 22 is a diagram showing the details of the plug-in subsystem, the poker library connection, and the connector.

FIG. 23 is a diagram showing an example of a V CD file.

[FIG. 24] A diagram showing a procedure for loading a compound document in the document processing system. [FIG. 25] A diagram showing a procedure for loading a compound document in the document processing system. [FIG. 26] A compound document loading in the document processing system. FIG. 27 is a diagram showing a procedure for loading a compound document in the document processing system. FIG. 28 is a diagram showing a procedure for loading a compound document in the document processing system. It is a figure which shows the flow of.

[FIG. 30] FIGS. 30 (a), 30 (b), and 30 (c) are diagrams showing examples of the data structure of an XML document to be processed.

[FIG. 31] FIGS. 31 (a) and 31 (b) are diagrams showing examples of pointer information.

[Fig.32] Fig.32 (a) and (b) are diagrams for explaining the mechanism to notify the change of DOM. FIG. 33 is a diagram showing a configuration of a document processing apparatus according to the first embodiment.

FIG. 34 is a diagram showing an example of a document editing screen.

FIG. 35 is a diagram showing an editing screen in a state in which a view template for schedule is activated.

FIG. 36 is a diagram showing a configuration of a document processing apparatus according to a second embodiment.

[Fig. 37] A diagram showing an example of an XML document in which the property of the AV component is inserted.

FIG. 38 shows a procedure of a document processing method according to the second embodiment.

FIG. 39 is a diagram showing an example of a screen displayed by the AV component.

FIG. 40 is a diagram showing a configuration of a document processing apparatus according to a third embodiment.

FIG. 41 is a diagram showing a procedure of a document processing method according to the third embodiment.

FIG. 42 is a diagram showing a configuration of a document processing apparatus according to a fourth embodiment.

FIG. 43 is a diagram showing an example of a document in which the AV property of the AV component for table display is inserted.

[FIG. 44] A diagram showing the contents of the AV property described in the document shown in FIG.

[FIG. 45] A diagram showing the contents of the AV property described in the document shown in FIG.

FIG. 46 is a diagram showing an example of a screen on which the document shown in FIG. 43 is displayed.

FIG. 47 is a diagram showing a menu displayed when the mouse is right-clicked in the view area generated by the AV component.

FIG. 48 is a diagram showing an example of a dialog screen displayed by the A V C component switching unit.

FIG. 49 is a diagram showing an example of an AV property setting screen displayed by the AV property setting section.

FIG. 50 is a diagram showing an example of an A V C property setting screen displayed by the A V C property setting unit.

[Fig.51] AVC property setting screen displayed by AVC property setting section It is a figure which shows the example of a surface.

FIG. 52 is a diagram showing an example of an A V C property setting screen displayed by the A V C property setting section.

FIG. 53 is a diagram showing an example of an AV property setting screen displayed by the AV property setting section.

FIG. 54 is a diagram showing an example of a display screen when switching to a single display A VC component.

FIG. 55 is a diagram showing a state in which the document shown in FIG. 43 is changed by switching AV components.

FIG. 56 is a diagram showing the contents of the AV property described in the document shown in FIG. 55.

FIG. 57 is a diagram showing the contents of the AV property described in the document shown in FIG. 55.

FIG. 58 is a diagram showing the contents of the AV property described in the document shown in FIG. 55.

FIG. 59 is a diagram showing the contents of the AV property described in the document shown in FIG. 55.

FIG. 60 is a diagram showing a screen when the Y-axis data is changed on the screen for setting the scatter diagram data shown in FIG. 49.

FIG. 61 is a diagram showing a screen when the data type of Y-axis data is changed. Explanation of symbols

20 document processing device, 22 main control unit, 24 editing unit, 27 concept resolution engine, 28 notification unit, 30 DOM unit, 32 DOM providing unit, 34 DOM generation unit, 36 output unit, 40 CSS unit, 42 CSS analysis unit, 44 CSS providing unit, 46 rendering unit, 50 HT ML unit, 52, 62 control unit, 54, 64 editing unit, 56, 66 display unit, 60 SVG unit, 70 view template control unit, 7 1 acquisition unit, 72 Presentation department, 74 Reception department, 76 Editorial department, 78 Beauty Template, 80 VC unit, 82 mapping unit, 84 definition file acquisition unit, 86 definition file generation unit, 1 00 document processing device, 3000 A VC control unit, 3002 A VC property setting unit, 3004 AVC property generation unit, 3006 Definition file generator, 301 0 A VC component for table display, 3020 A VC component for chart display, 3030 AVC component for UI part display, 3040 tree — A VC component for display, 3050 A VC component switching unit. BEST MODE FOR CARRYING OUT THE INVENTION

[0016] (Base technology)

FIG. 1 shows the configuration of the document processing apparatus 20 according to the base technology. The document processing device 20 processes a structured document in which data in the document is classified into a plurality of structural elements having a hierarchical structure. In this prerequisite technology, an example of processing an XML document as an example of a structured document is described. To do. The document processing apparatus 20 includes a main control unit 22, an editing unit 24, a DOM unit 30, a CSS unit 40, an HTML unit 50, an SVG unit 60, and a VC unit 80 as an example of a conversion unit. These hardware components are realized by the CPU of any computer, memory, programs loaded in the memory, etc., but here we draw functional blocks realized by their cooperation. ing. Therefore, those skilled in the art will understand that these functional blocks can be realized in various forms by hardware only, software only, or a combination thereof.

[0017] The main control unit 22 provides a framework for loading plug-ins and executing commands. Editing unit 24 provides a framework for editing XML documents. The document display and editing functions in the document processing device 20 are realized by plug-ins, and necessary plug-ins are dictated by the main control unit 22 or the editing unit 24 according to the type of document. The main control unit 22 or the editing unit 24 refers to the name space of the XML document to be processed, and by which vocabulary the XML document is described. And the display or editing plug-in corresponding to the POB library is loaded to execute display or editing. For example, the document processing device 20 is plugged with a display system and an editing system for each platform (tag set), such as an HTML unit 50 that displays and edits HTML documents and an SVG unit 60 that displays and edits SVG documents. When editing HTML documents, it is loaded with 50 units of HTML unit. When editing SVG documents, it is loaded with 60 units of S VG unit. As will be described later, when a compound document including both HTML and SVG components is processed, both the HTML unit 50 and the SVG unit 60 are dictated.

[0018] According to such a configuration, the user can select and install only the necessary functions, and can add or delete functions later as appropriate. Therefore, a recording medium such as a hard disk for storing the program It is possible to effectively use the storage area of the memory, and it is possible to prevent memory from being wasted even during program execution. In addition, it has excellent function expandability, and as a development entity, it is possible to cope with new poker libraries in the form of plug-ins, so development is easy, and for users, it is easy and low-cost by adding plug-ins. Functions can be added.

[0019] The editing unit 24 accepts an editing instruction event from the user via the user interface, notifies the appropriate plug-in of the event, and re-executes the event or cancels the execution. Control processing such as (Undo).

[0020] The DOM unit 30 includes a DOM providing unit 32, a DOM generating unit 34, and an output unit 36, and is a document object model (Document) defined to provide an access method when handling an XML document as data. Implements functions that conform to Object Model: DO M). The DOM provider 32 is an implementation of DOM that satisfies the interface defined in the editing unit 24. The DOM generation unit 34 generates a DOM tree from the XML document. As will be described later, the XML document to be processed is transferred to other vocabulary by VC Unit 80. In the case of mapping, a source tree corresponding to the XML document of the mapping source and a destination tree corresponding to the XML document of the mapping destination are generated. The output unit 36 outputs the DOM tree as an XML document at the end of editing, for example.

[0021] The CSS unit 40 includes a 33 analysis unit 42, a CSS providing unit 44, and a rendering unit 46, and provides a display function compliant with CSS. The CSS analysis unit 42 has a function of a parser that analyzes CSS syntax. The CSS provider 44 is an implementation of CSS objects, and performs CSS force scheduling processing on the DOM tree. The rendering unit 46 is a CSS rendering engine, and is used to display a document described in a vocabulary such as HTML that is laid out using the CSS.

[0022] The HTML unit 50 displays or edits a document described in HTML. The SVG unit 60 displays or edits documents described in SVG. These display / editing systems are realized in the form of plug-ins. Each of them is a display unit (Canvas) 56, 66 for displaying a document, a control unit (Editlet) 52 for sending / receiving events including editing instructions, 62. Includes editing sections (Zone) 54 and 64 that receive editing commands and edit the DOM. When the control unit 52 or 62 receives a DOM tree editing command from the outside, the editing unit 54 or 64 changes the DOM tree, and the display unit 56 or 66 updates the display. These have a structure similar to a framework called MVC (Model-View-Control ler). Generally, the display units 56 and 66 are set to “View”, and the control units 52 and 62 force << Γ Control lerj. The editing parts 54 and 64 and the DOM entity correspond to “Model”, respectively. The document processing apparatus 20 of the base technology enables not only editing of an XML document in a single display format but also editing according to each vocabulary. For example, the HTML unit 50 provides a user interface for editing an HTML document in a manner similar to a word processor, and the SVG unit 60 provides a user interface for editing an SVG document in a manner similar to an image drawing tool. Provide one face. The VC unit 80 includes a mapping unit 8 2, a definition file acquisition unit 8 4, and a definition file generation unit 8 6, and mapping is performed by mapping a document described in a certain library to another one. Provides a framework for displaying or editing a document with a plug-in for display editing corresponding to the previous page library. In this base technology, this function is called Pocabulary Connection (VC). The definition file acquisition unit 84 acquires a script file describing the mapping definition. This definition file describes the correspondence (connection) between nodes for each node. At this time, whether to edit the element value or attribute value of each node may be specified. Also, an arithmetic expression using the element value or attribute value of the node may be described. These functions will be described in detail later. The mapping unit 82 refers to the scribble file acquired by the definition file acquisition unit 84, causes the DOM generation unit 34 to generate a destination tree, and manages the correspondence between the source tree and the destination tree. The definition file generator 86 provides a graphical user interface for the user to generate a definition file.

[0024] The VC unit 80 monitors the connection between the source tree and the destination tree, and receives an editing instruction from the user via the user interface provided by the plug-in responsible for display. Change the corresponding node. DOM unit 3 0 When a mutation event is issued to the effect that the source tree has changed, VC Unit 8 0 receives the mutation event and synchronizes the destination tree with the source tree change. Change the node of the destination tree corresponding to the changed node. Plug-ins that display / edit the destination tree, for example HTML unit 50, receives a mutation event that the destination tree has changed, and updates the display with reference to the changed destination tree To do. With such a configuration, even a document described by a local vocabulary used by a small number of users can be converted into another major vocabulary to display the document. An editing environment is provided.

An operation for displaying or editing a document by the document processing apparatus 20 will be described.

When the document processing apparatus 20 reads a document to be processed, the DOM generation unit 34 generates a DOM tree from the XML document. Further, the main control unit 2 2 or the editing unit 2 4 refers to the name space to determine the poker library describing the document. A plug-in corresponding to the vocabulary is installed in the document processing device 20! If so, load the plug-in to view / edit the document. If the plug-in is not installed, check whether the mapping definition file exists. If the definition file exists, the definition file acquisition unit 84 acquires the definition file, generates a destination tree according to the definition, and displays / edits the document by the plug-in corresponding to the mapping destination library. In the case of a compound document that contains multiple libraries, the corresponding parts of the document are displayed / edited by plug-ins corresponding to each library as described later. If the definition file does not exist, the source or tree structure of the document is displayed, and editing is performed on the display screen.

FIG. 2 shows an example of an XML document to be processed. This XML document is used to manage student performance data. The component “Grade”, which is the top node of the XML document, has multiple components “Student” provided for each student. The component “student” has an attribute value “name” and child elements “national language”, “mathematics”, “science”, and “society”. The attribute value “name” stores the name of the student. Constituent elements “National language”, “Mathematics”, “Science” and “Society” store the results of national language, mathematics, science and society, respectively. For example, a student with the name “A” has a national language grade of “9 0”, a mathematical grade of “5 0”, a scientific grade of “7 5”, and a social grade of “6 0”. In the following, the Pocabulary (tag set) used in this document will be referred to as the “Performance Management Pocabulary”.

[0027] Since the document processing apparatus 20 of the base technology does not have a plug-in that supports display / editing of the grade management vocabulary, this document is displayed in the source display, tree display, and so on. The VC function described above is used to display in other ways. In other words, it is necessary to prepare a definition file for mapping the grade management library to another library with plug-ins, such as HTML and SVG. The user interface for creating a definition file by the user himself will be described later. Here, the explanation will proceed assuming that a definition file has already been prepared.

FIG. 3 shows an example of mapping the XML document shown in FIG. 2 to a table described in HTML. In the example shown in Figure 3, the “Student” node of the Grade Management Platform is mapped to a row (“TR” node) of a table (“TABLE” node) in HTML, and the attribute value “name” is assigned to the first column of each row. The second column contains the element values of the “National Language” node, the third column the element values of the “Mathematics” node, the fourth column the element values of the “Science” node, and the fifth column “Society”. Associate node element values with each other. As a result, the XML document shown in Fig. 2 can be displayed in the HTML table format. These attribute values and element values are specified to be editable, and the user can edit these values by the editing function of the HTML unit 50 on the display screen of the HTML. The sixth column specifies the formula for calculating the weighted average of national language, mathematics, science, and society, and displays the average score of the students' grades. In this way, by making it possible to specify an arithmetic expression in the definition file, more flexible display is possible and user convenience during editing can be improved. The sixth column specifies that editing is not possible, so that only the average score cannot be edited individually. In this way, by making it possible to specify whether editing is possible in the mapping definition, it is possible to prevent user misoperation.

[0029] FIGS. 4 (a) and 4 (b) show examples of definition files for mapping the XML document shown in FIG. 2 to the table shown in FIG. This definition file is described in the script language defined for the definition file. The definition file contains command definitions and display templates. In the example shown in Fig. 4 (a) and (b), "add student" and "delete student" are defined as commands. Each of them is associated with an operation for inserting the node “student” in the source tree and an operation for deleting the node “student” from the source tree. As a template, it is described that headings such as “name” and “national language” are displayed in the first row of the table, and the contents of the node “student” are displayed in the second and subsequent rows. In the template that displays the contents of node “Student”, the term “text-of” means “editable” and the term “va l ue-of” means “edit” It means “impossible”. In the sixth column of the row displaying the contents of the node “Student”, the calculation formula “(src: Japanese + src: Mathematics + src: Science + src: Society) div 4” is described in the sixth column. Mean that the student's average performance is displayed.

FIG. 5 shows an example of a screen displayed by mapping the XML document described in the grade management platform shown in FIG. 2 to the HTML according to the correspondence shown in FIG. Each row in Table 90 shows, from the left, each student's name, national language grade, mathematics grade, science grade, social grade, and average score. The user can edit the XML document on this screen. For example, if you change the value in the second row and third column to “7 0”, the element value in the source tree corresponding to this node, that is, the math grade for student “B” changes to “7 0” Is done. At this time, VC unit 80 should make the destination tree follow the source tree, change the corresponding part of the destination tree, and HTML unit 50 will update the display based on the changed destination tree. To do. Therefore, in the table on the screen, the mathematics score of student “B” is changed to “7 0”, and the average score is changed to “5 5”.

[0031] In the screen shown in Fig. 5, the commands "Add Student" and "Delete Student" appear in the menu as defined in the definition file shown in Fig. 4 (a) (b). Indicated. When the user selects these commands, the node “Student” is added or deleted in the source tree. As described above, the document processing apparatus 20 of the base technology can not only edit the element value of the component at the end of the hierarchical structure but also edit the hierarchical structure. An editor with a tree structure like this Capabilities may be provided to the user in the form of commands. For example, a command for adding or deleting a table row may be associated with an operation for adding or deleting a node “student”. In addition, a command for embedding other libraries may be provided to the user. Using this table as an input template, you can also add new student grade data in the form of blanks. As described above, the VC function makes it possible to edit a document described in the grade management library while using the display / editing function of the HTML unit 50.

FIG. 6 shows an example of a graphical user interface that the definition file generator 86 provides to the user in order for the user to generate a definition file. In the area 9 1 on the left side of the screen, the mapping source XML document is displayed as a tree. In the area 92 on the right side of the screen, the screen layout of the XML document to be mapped is shown. This screen layout can be edited by the HTML unit 50, and the user creates a screen layout for displaying the document in the area 92 on the right side of the screen. Then, for example, by using a pointing device such as a mouse, the node of the mapping source XML document displayed in the area 91 on the left side of the screen is displayed in the screen layout using HTML displayed in the area 92 on the right side of the screen. By dragging and dropping, the connection between the mapping source node and the mapping destination node is specified. For example, if you drop “Mathematics”, a child element of the element “Student”, into the first row and third column of Table 90 on the HTML screen, between the “Mathematics” node and the “TD” node in the third column. A connection is stretched over. Each node can be specified for editing. An arithmetic expression can be embedded in the display screen. When the editing of the screen is completed, the definition file generator 86 generates a definition file describing the screen layout and the connection between the nodes.

[0033] View editors that support major libraries such as XHTML, Math ML, and SVG have already been developed, but they correspond to documents written in original pages such as the document shown in Figure 2. Developing a view editor is not practical. However, as mentioned above, If you create a definition file for the webbing, you can use the VC function to display and edit documents written in the original library without developing a view editor.

FIG. 7 shows another example of the screen layout generated by the definition file generation unit 86. In the example shown in FIG. 7, Table 90 and a pie chart 93 are created on the screen for displaying the XML document described in the grade management policy. This pie chart 93 is described by S V G. As will be described later, the document processing apparatus 20 of the base technology can process a composite document including a plurality of libraries in one XML document, so that it is described in HTML as in this example. Table 90 and the pie chart 93 described in SVG can be displayed on one screen.

FIG. 8 shows an example of an XML document editing screen by the document processing apparatus 20. In the example of FIG. 8, one screen is divided into a plurality of areas, and the XML document to be processed is displayed in a plurality of different display formats in each area. In area 94, the source of the document is displayed. In area 95, the document structure is displayed. In area 96, the table described in HTML shown in Fig. 5 is displayed. Is displayed. Documents can be edited on any of these screens. When a user edits on any of these screens, the source code is changed, and the plug-in responsible for displaying each screen Update the screen to reflect the tree changes. Specifically, as a listener of the mutation event that notifies the change of the source tree, the display unit of the plug-in responsible for displaying each editing screen is registered, and either of the plug-in or VC unit 8 0 is used. When the source tree is changed, all the display units displaying the edit screen receive the issued mutation event and update the screen. At this time, if the plug-in is displaying with the VC function, the VC unit 80 changes the destination tree following the change of the source tree, and then refers to the changed destination tree. The display unit updates the screen. [0036] For example, when the source display and the tree display are realized by a dedicated plug-in, the source display plug-in and the tree display plug-in do not use the destination tree, but directly use the source tree. Browse and display. In this case, when editing is performed on any of the screens, the source display plug-in and the single display plug-in update the screen with reference to the changed source tree, and take charge of the screen in area 96. The following HTML unit 50 updates the screen by referring to the changed destination tree following the change of the source tree.

[0037] The source display and the tree display can also be realized by using the VC function. In other words, the source and tree structure may be laid out using HTML, XML documents may be mapped onto the HTML, and displayed using the HTML unit 50. In this case, three destination destinations are generated: source format, tree format, and tabular format. When editing is performed on any of the screens, VC Unit 8 0 changes the source tree, then changes each of the three destination trees: source format, solid format, and table format. Browse the destination tree and update the three screens.

[0038] Thus, by displaying a document in a plurality of display formats on one screen, it is possible to improve user convenience. For example, the user can display and edit a document in a visually easy-to-understand format using Table 90 or the like while grasping the hierarchical structure of the document by displaying the source or the tree. In the above example, one screen can be divided and screens in multiple display formats can be displayed at the same time. One screen can be displayed in one display format, and the display format can be switched according to user instructions. In this case, the main control unit 2 2 power receives a display format switching request from the user, and instructs each plug-in to switch the display.

FIG. 9 shows another example of an XML document edited by the document processing apparatus 20.

In the XML document shown in Figure 9, the X inside the “fore i gnObject” tag of the SVG document An HTML document is embedded, and a mathematical expression written in Math ML is included in the XHTML document. In such a case, the editing unit 24 refers to the name space and distributes the drawing work to an appropriate display system. In the example of FIG. 9, the editing unit 24 first causes the SVG unit 60 to draw a rectangle, and then causes the HTML unit 50 to draw an XHTML document. In addition, let the Math ML unit (not shown) draw mathematical formulas. In this way, a compound document including a plurality of pages is properly displayed. The display results are shown in Fig. 10.

[0040] During document editing, the displayed menu may be switched according to the position of the cursor (carriage). That is, when the cursor exists in the area where the SVG document is displayed, the menu defined by the SVG unit 60 or the command defined in the definition file for mapping the SVG document is displayed. When the XHTML document exists in the displayed area, the menu defined by the HTML unit 50 or the command defined in the definition file for mapping the XHTML document is displayed. As a result, an appropriate user interface can be provided according to the editing position.

[0041] In a compound document, when there is no appropriate plug-in or mapping definition file corresponding to a certain library, the part described by the library may be displayed in a source or tree. Previously, when opening a compound document in which another document was embedded in one document, the contents could not be displayed unless an application that displayed the embedded document was installed. Then, even if there is no display application, the content can be grasped by displaying the XML document composed of text data in the source display or the tree display. This is a unique feature of text-based documents such as XML.

[0042] Another advantage of the data being described in the text base is that, for example, in a part described by a certain library in a compound document, the data of a part described in another part of the same document is changed. You may refer to it. Also, sentence When performing a search within a document, text strings embedded in diagrams such as SVG can also be searched.

[0043] A tag written in another poker library may use a tag of another poker library. This XML document is not valid, but can be processed as a valid XML document if it is well-formed. In this case, the tag of the other vocabulary inserted may be mapped by the definition file. For example, you can use tags such as “Important” and “Most important” in an XHTML document and highlight the parts enclosed by these tags, or sort them in order of importance. May be.

[0044] In the editing screen shown in FIG. 10, when a user edits a document, the plug-in or VC unit 80 responsible for the edited part changes the source tree. In the source tree, listeners for mutation events can be registered for each node. Normally, the plug-in display section or VC unit 80 corresponding to the portal to which each node belongs is registered as a listener. The When the source tree is changed, the DOM provider 32 traces from the changed node to a higher hierarchy, and if there is a registered listener, issues a mutation event to that listener. For example, in the document shown in Fig. 9, when the node below the <htm I> node is changed, the mutation event is notified to the HTM Lunit 50 registered as a listener in the <htm I> node. At the same time, the mutation event is also notified to the SVG unit 60 registered as a listener in the upper <s V g> node. At this time, the HTML unit 50 refers to the changed source tree and updates the display. The SVG unit 60 may ignore the mutation event because the node belonging to its own Pocabulary has not changed.

[0045] Depending on the contents of editing, the overall layout may change as the display is updated by the HTML unit 50. In this case, use a configuration that manages the layout of the screen, for example, a plug-in that is responsible for displaying the top-level node. The layout of the display area for each plug-in is updated. For example, when the display area by the HTML unit 50 becomes larger than before, the HTML unit 50 first draws a part that it is in charge of and determines the size of the display area. Then, notify the configuration that manages the layout of the screen of the size of the display area after the change, and request a layout update. The configuration that manages the screen layout receives the notification and re-lays out the display area for each plug-in. In this way, the display of the edited part is updated appropriately and the layout of the entire screen is updated.

[0046] Next, a functional configuration for realizing the document processing apparatus 20 of the base technology will be described in more detail. In the following explanation, when describing the class name, etc., the alphabetic characters will be used as they are.

[0047] A. Overview

With the advent of the Internet, the number of documents processed and managed by users has increased almost exponentially. The web (World wide Web), which forms the core of the Internet, has become a big receptacle for such document data. In addition to documents, the Web provides information retrieval systems for such documents. These documents are usually written in a markup language. One simple and popular example of a markup language is HTML (HyperText Markup Language). Such documents further include links to other documents stored elsewhere on the web. XML (extensible Markup Language) is a more advanced and popular markup language. Simple browsers for accessing and browsing web documents have been developed in object-oriented programming languages such as Java (registered trademark).

[0048] Documents described in a markup language are usually represented in the form of a tree data structure in browsers and other applications. This structure corresponds to the tree of the result of parsing the document. The DOM (Document Object Model) is a well-known tree-based data structure model used to represent and manipulate documents. DOM includes HTML and XML documents Provides a standard set of objects for representing documents. The DOM has two basic components: a standard model of how objects that represent components in a document are connected, and a standard interface for accessing and manipulating those objects. Nent included.

[0049] Application developers can support DOM as an interface to their own data structures and API (Application Program Interface). On the other hand, application developers who create documents can use the standard interface of DOM rather than their own API interface. Thus, due to its ability to provide standards, the DOM is effective in facilitating the mutual use of documents in various environments, especially the web. Several versions of the DOM have been defined and are used by different programming environments and applications.

[0050] A DOM tree is a hierarchical representation of a document based on the contents of the corresponding DOM. The DOM tree contains a “root” and one or more “nodes” that originate from the root. In some cases, the root represents the entire document. Intermediate nodes can represent elements such as a table and the rows and columns in the table, for example. A “leaf” in a DOM tree usually represents text or image-like data that cannot be further decomposed. Each node in the DOM tree may be associated with attributes that describe the parameters of the element represented by the node, such as font, size, color, and indentation.

[0051] HTML is a language generally used to create a document, but is a language for format and layout, not a data description language. Nodes in the DOM tree that represent HTML documents are elements that are predefined as HTML formatting tags, and HTML is usually used for data description and tagging / labeling of data. It is often difficult to formulate queries for data in HTML documents. [0052] The goal of network designers is to enable documents on the web to be queried and processed by software applications. Regardless of how they are displayed, a hierarchically structured language can be queried and processed that way. Markup languages such as XML (extensible Markup Language) can provide these features.

[0053] Contrary to HTML, a well-known advantage of XML is that data elements can be labeled using "tags" that can be freely defined by the document designer. is there. Such data elements can be structured hierarchically. In addition, XML documents can contain document type definitions that describe the tags used in the document and the “grammar” of their interrelationships. CSS (Cascading Style Sheet) or XS L (XML Style Language) is used to define how to display a structured XML document. Additional information on DOM, HTML, XML, CSS, XS L and related language features can also be obtained from the web. (Eg http: 〃 www. W3. Org / TR /)

[0054] X path provides common syntax and semantics for specifying the location of parts of an XML document. An example of functionality is traversing the DOM tree corresponding to an XML document. It provides basic functions for manipulating strings, numbers, and Boolean characters associated with various representations of XML documents. X path is the syntax of the appearance of an XML document, for example, the grammar and the abstract syntax such as the DOM tree, not the grammar of what line or number of characters when viewed as a text string. It works in any structure. By using X path, the location can be specified through a hierarchical structure in the DOM tree of the XML document, for example. In addition to its use for addressing, X path is also designed to be used to test whether a node in the DOM tree matches the pattern. More details about XP ath can be found at http: // www. W3. Org / TR / xpath [0055] The known advantages and features of XML can handle documents written in a markup language (eg XML) and provide a user-friendly interface for creating and modifying documents. An effective document processing system is needed.

[0056] Some of the system configurations described here are described using the well-known GU I (Graphical User Interface) paradigm called Model-View-Control ler (MVC). The The MVC paradigm divides an application or part of an application interface into three parts: a model, a view, and a controller. MVC was originally developed to assign traditional input, processing, and output roles to the GU I world.

[Input] → [Process] → [Output]

[Controller] → [Model] → [View]

[0057] According to the MVC paradigm, external modeling, visual feedback to the user, and user input are handled by model (M), view (V), and controller (C) objects. Treated separately. The controller interprets input such as mouse and keyboard input from the user and maps these user actions to commands sent to the model and / or view to bring about appropriate changes. Works. The model acts to manage one or more data elements, responds to queries about that state, and responds to instructions that change the state. The view acts to manage the rectangular area of the display and has the function of presenting data to the user through a combination of graphics and text.

[0058] B. Overall Configuration of Document Processing System

An example of a document processing system will be clarified with reference to FIG.

[0059] Fig. 11 (a) shows a conventional configuration example of elements that function as the basis of a document processing system of the type described later. Configuration 10 includes a processor of the type such as a CPU or microprocessor 11 connected to memory 12 by communication path 13. Memory 1 2 can be any ROM and / or R available now or in the future It may be in AM format. The communication path 13 is typically provided as a bus. An input / output interface 1 6 to user input devices 14 and display devices 15 (or other user interfaces) such as a mouse, keyboard, voice recognition system, etc. is also provided for communication between the processor 1 1 and the memory 1 2. Connected to the bus. This configuration may be a stand-alone, a networked form in which a plurality of terminals and one or more servers are connected, or may be configured by any known method. The present invention is not limited by the arrangement of these components, the centralized or distributed architecture, or the communication methods of the various components.

[0060] Further, the present system and the embodiments discussed herein are discussed as including several components and sub-components that provide various functionalities. These components and sub-components can be realized not only by a combination of hardware and software, but also by hardware alone or software alone to provide the noted functionality. Furthermore, the hardware, software, and combinations thereof can be realized by general-purpose computing devices, dedicated hardware, or combinations thereof. Thus, the configuration of a component or subcomponent includes a general purpose / dedicated computing device that executes specific software to provide the functionality of the component or subcomponent.

[0061] FIG. 11 (b) shows an overall block diagram of an example of a document processing system. A document is generated and edited in such a document processing system. These documents may be written in any language that has the characteristics of a markup language, such as XML. For convenience, the terminology and titles of specific components and subcomponents were created. However, these should not be construed to limit the scope of the general teachings of this disclosure.

[0062] The document processing system can be regarded as having two basic configurations. The first configuration is an “execution environment” 1 0 1 which is an environment in which the document processing system operates. For example, the execution environment can be a user during document processing and management. Provides basic utilities and functions that support not only the system. The second configuration is an “application” 1 0 2 composed of applications running in the execution environment. These applications include the document itself and various representations of the document.

[0063] 1. Execution environment

The key component of the execution environment 10 1 is Program lvoker (program launcher: program starter) 1 0 3. Program lvoker 1 0 3 is a basic program accessed to start the document processing system. For example, when a user logs on to a document processing system and starts, Program l nvoker 1 0 3 force is executed. Program l nvoker 1 0 3 can, for example, read and execute functions added as plug-ins to the document processing system, start and execute applications, and read properties related to documents . The functions of Program l nvoker 1 0 3 are not limited to these. When a user wants to launch an application that is intended to run in the execution environment, Program lvoker 1 0 3 finds the application, launches it, and executes the application.

[0064] Several components such as a plug-in subsystem 1 0 4, a command subsystem 1 0 5, and a resource module 10 9 are attached to Program lvoker 10 3. These configurations are described in detail below.

[0065] a) Plug-in subsystem

The plug-in subsystem 1 0 4 is used as a highly flexible and efficient configuration for adding functionality to a document processing system. The plug-in subsystem 10 4 can also be used to modify or delete functions that exist in the document processing system. In addition, a wide variety of functions can be added or modified using the plug-in subsystem. For example, it is possible to add an Ed itl et (editlet) function that helps to draw a document on the screen. Ed itl et plug-in is added to the system It also supports editing of lari.

[0066] The plug-in subsystem 104 includes a Service Broker (service broker) 1041. ServiceBroker 1 041 mediates services added to the document processing system by managing plug-ins added to the document processing system.

[0067] Individual functions that achieve the desired functionality are added to the system in the form of Service 1042. Available types of Service 1042 are: Application service, ZoneFactory (zone factory: zone generator) Service, Editlet (editlet: editor) Service, Comma dFactory (command factory) : Command generation part) Service, ConnectXPath (Connect XP ath: XP ath management part) Service, CSS Computation (CSS calculation part: CSS calculation part) Service, etc., but not limited to these. These services and other configurations of the system and their relationship are detailed below for a better understanding of the document processing system.

[0068] The relationship between the plug-in and the service is as follows. A plug-in is a unit that can contain one or more ServiceProviders. Each ServiceProvider has one or more classes of Service associated with it. For example, by using a single plug-in with the appropriate software application, one or more services can be added to the system, thereby adding the corresponding functionality to the system.

[0069] b) Command subsystem

Command subsystem 105 is used to execute commands in the form of commands related to document processing. A user can execute an operation on a document by executing a series of instructions. For example, a user edits an XML DOM tree corresponding to an XML document in a document processing system by issuing an instruction in the form of a command, and processes an XML document. These commands can be used for keystrokes, mouse clicks, or other valid user designs. It may be entered using a interface action. One command may execute more than one instruction. In this case, these instructions are wrapped (contained) in one command and executed in succession. For example, a user wants to replace a wrong word with a correct word. In this case, the first instruction is to find the wrong word in the document, the second instruction is to delete the wrong word, and the third instruction is to insert the correct word It may be. These three instructions may be wrapped in one command.

[0070] The command may have an associated function, for example, an “undo” function, described in detail below. These functions may also be assigned to any base class that is used to create objects.

[0071] The key component of the command subsystem 1 05 is Gommandlnvoker (command launcher: command starter) 1 05 1 which selectively gives commands and acts to execute them. Although only one Gommandln voker is shown in Fig. 11 (b), one or more Go countries and lnvoker may be used, and one or more commands may be executed simultaneously. Gommandlnvoker 1 05 1 retains the functions and classes necessary to execute commands. In operation, the Command 1 052 to be executed is loaded into the Queue 1 053. Gommandlnvoker generates a command thread that runs continuously. If there is no Command already running in Commandlnvoker, Go Country and 1 052 intended to be executed by Comma nlnvoker 1 05 1 are executed. If Gommandlnvoker is already executing a command, a new Command will be stacked at the end of Queue 1 053. In each command invoker 1 05 1, only one command is executed at a time. If execution of the specified Gomm and fails, Go country andlnvoker 1 05 1 executes exception handling.

[0072] Command types executed by Commandlnvoker 1 05 1 include Undoab I eCommand (cancellation command) 1 054, AsynchronousCommand (asynchronous command) 1 055, and VGGo country and (VC command) 1 056, It is not limited to these. Undoab I eCommand 1 054 is the result of the command if the user wants it. It is a Go country and can cancel the fruit. Examples of UndoableGo country and include cutting, copying, and inserting text. In operation, when a user selects a portion of a document and applies a cut command to that portion, the cut portion is “not cut” if necessary, using UndoableG 0 country and. Can be.

[0073] The VGGo country andl 056 is stored in a Vocabulary Connection Descriptor (VCD) script file. These are user-specified commands that can be defined by the programmer. The Command may be a more abstract Go country and combination, for example, to add an XML fragment, delete an XML fragment, or set an attribute. These Go countries and are particularly focused on document editing.

[0074] AsynchronousCommand 1 055 is a command from the system, such as saving a document, and is executed asynchronously separately from UndoableGommand and VGGommand. AsynchronousCommand cannot be undone because it is not possible with UndoableGommand.

[0075] c) Resources

Resource 109 is an object that provides several functions to various classes. For example, string resources, icons, and default key bindings are examples of resources used in the system.

[0076] 2. Application components

The application component 102, which is the second main feature of the document processing system, is executed in the execution environment 101. Application component 1102 includes the actual document and various logical and physical representations of the document in the system. In addition, application component 102 includes the configuration of the system used to manage documents. The application component 102 further includes a user application (user application) 106, an application core 108, a user interface 107, and a GoreGomponent (core component) 110. [0077] a) User application

UserApplication 10 06 is entered on the system together with Program nvoker 1 03. UserApplication 106 is an adhesive that connects a document, various representations of the document, and the user interface required to interact with the document. For example, suppose a user wants to generate a set of documents that are part of a project. When these documents are loaded, an appropriate representation of the document is generated. User interface functions are added as part of UserApplication 106. In other words, UserApplication 106 holds both the representation of the document that allows the user to interact with the document that forms part of the project, and various aspects of the document. Once UserApplication 1 06 is generated, whenever a user wants to interact with a document that forms part of Project 卜, the user can easily sneak UserApplication 1 06 into the execution environment. it can.

[0078] b) Core components

CoreComponent 1 1 0 provides a way to share documents between multiple panes. As detailed later, Pane displays the DOM tree and handles the physical layout of the screen. For example, a physical screen consists of multiple panes in the screen that depict individual pieces of information. The document that the user sees on the screen is

Can appear in one or more panes. Also, two different documents may appear in two different panes on the screen.

[0079] As shown in Figure 11 (c), the physical layout of the screen is also in the form of a tree. Pane can be RootPane 1 084 or SubPane 1 085. RootPane 1 084 is a Pane that hits the root of the pane tree, and SubPane 1 085 is an arbitrary Pane other than RootPane 1 084.

[0080] CoreComponent 1 1 0 also provides fonts and serves as a source of multiple functional operations for documents, such as toolkits. One example of a task performed by CoreComponent 1 1 0 is the movement of a mouse force between multiple panes. Another example of a task to be performed is one of the documents in a Pane Mark a part and copy it onto another Pane containing a different document.

[0081] c) Application Core

As described above, the application component 1 0 2 is composed of documents that are processed and managed by the system. This includes various logical and physical representations of documents within the system. The application core 1 0 8 is a configuration of the application component 1 0 2. Its function is to keep the actual document with all the data it contains. The application core 1 0 8 includes DocumentManager (document manager: document management unit) 1 0 8 1 and Document (document: document) 1 0 8 2 itself.

[0082] Various aspects of DocumentManager 1 0 8 1 are described in detail below. DocumentManager 1 0 8 1 manages Document 1 0 8 2. DocumentManager 1 0 8 1 is RootPane 1 0 8 4, SubPane 1 0 8 5, CI ipBoard (Clip Port) Utility 1 0 8 7, and Snapshot (Snapshot) Utility 1 0 8 8 Also connected to. The G i pBoard utility 1 0 8 7 provides a way to preserve the portion of the document that the user has decided to add to the clip pod. For example, suppose a user wants to cut a part of a document and save it in a new document for later review. In such a case, the clipped part is added to the G i pBoard.

[0083] Next, the Snapshot utility 1 0 8 8 will also be described. The SnapShort utility 1 0 8 8 makes it possible to remember the current state of an application as it transitions from one state to another.

[0084] d) User interface

Another configuration of application components 1 0 2 is a user interface 1 0 7 that provides a means for users to physically interact with the system. For example, the user interface is used by users to upload, delete, edit, and manage documents. User interface The chair includes Frame 1 07 1, MenuBar 1 072, StatusBar 1 073, and URLBar 1 074.

[0085] Frame 1 07 1 is considered to be an active area of the physical screen, as is generally known. MenuBar 1 072 is a screen area that contains menus that provide selection to the user. StatusBarl 073 is a screen area that displays the execution status of the application. URLBarl 074 provides an area for entering U R L address to navigate the Internet.

[0086] C. Document management and related data structures

FIG. 12 shows the details of DocumentManager 1 081. This includes the data structures and structures used to represent the document within the document processing system. For clarity, the configuration described in this subsection is described using the MVC paradigm.

[0087] DocumentManager 1 081 includes a DocumentGontainer (document container: document container) 203 that holds and hosts all the documents in the document processing system. A tool kit 201 that is matched to DocumentManager 1 081 provides various tools used by DocumentManager 1 081. For example, DomService (DOM service) is a tool provided by toolkit 201 to provide all the functionality needed to create, maintain and manage DOMs corresponding to documents. . Another tool provided by tool kit 201, lOManager (input / output manager) manages input to and output from the system. Similarly, StreamHandler (stream handler) is a tool that handles uploading documents by bitstream. These tools are not specifically shown in the figure and are not assigned a reference number, but form a component of the tool kit 201.

[0088] According to the representation of the MVC paradigm, model (M) includes a DOM tree model 202 of the document. As mentioned above, all documents are represented as DOM trees in the document processing system. The document is also DocumentGontainer 2 Form part of 03.

[0089] 1. DOM model and zones

A DOM tree representing a document is a tree having Node 2021. Zone 209, which is a subset of the DOM tree, contains the associated area of one or more nodes in the DOM tree. For example, only a part of the document can be displayed on the screen, but this part of the visualized document is displayed using Zone 209. A Zone is created, handled, and processed using a plug-in called ZoneFactory (zone factory: zone creation unit) 205. Zone represents a part of DOM, but one or more “namespaces” may be used. As is well known, a namespace is a collection of names that are unique within a namespace. In other words, the same name does not exist in the namespace.

[0090] 2. Relationship between Facet and Facet and Zone

Facet 2022 is another configuration within the model (M) part of the MVC paradigm. Facet is used to edit Nodes in the Zone. Facet2022 organizes access to the DOM using procedures that can be executed without affecting the contents of the Zone itself. As explained below, these procedures perform important and useful operations related to Node.

[0091] Each Node has a corresponding Facet. Instead of directly manipulating Nodes in D O M, DOM integrity is protected by using Facet to perform operations. If the operation is performed directly on Node, several plugins can modify the DOM at the same time, resulting in inconsistencies.

[0092] The DOM standard established by the W3 C defines a standard interface for operating Nodes, but in fact, there are operations specific to each POD library or Node. It is convenient to prepare this operation as API. In the document processing system, APIs specific to each node are prepared as Facet and attached to each node. This makes it possible to add useful APIs while complying with the DOM standard. In addition, every pokébra Rather than implementing a specific DOM, by adding a specific API to the standard DOM implementation later, it is possible to handle various poker libraries in a unified manner. Documents with mixed vocabulary in any combination can be processed appropriately.

[0093] A Poch Library is a set of tags (for example, XML tags) belonging to a namespace. As mentioned above, a namespace has a set of unique names (here tags). A poch library appears as a subtree of the DOM tree that represents an XML document. This subtree contains Zones. In a specific example, the tag set boundary is defined by the Zone. Zone 209 is generated using a service called ZoneFactory 205. As mentioned above, Zone 209 is an internal representation of part of the DOM tree that represents the document. A logical representation is required to provide access to some of these documents. This logical representation informs the computer how the document is logically represented on the screen. Canvas 210 is a service that acts to provide a logical layout corresponding to the Zone.

On the other hand, the Pane 21 1 is a physical screen layout corresponding to the logical layout provided by the Canvas 210. In fact, the user sees only the rendering of the document with text and images on the display screen. Therefore, the document must be rendered on the screen by the process of drawing characters and images on the screen. The document is drawn on the screen by Canvas 210 based on the physical layout provided by Pane 21 1.

[0095] Ganvas 210 corresponding to Zone 209 is generated using Editlet 206. The DOM of the document is edited using Editlet 206 and Ganvas 210. In order to maintain the integrity of the original document, Editlet 206 and Ganvas 210 use Facet corresponding to one or more Nodes in Zone 209. These services do not directly operate the nodes in the Zone and DOM. Facet is operated using Gommand207.

[0096] The user generally moves the cursor on the screen or types a command To interact with the screen. Canvas 2 10 which provides a logical layout on the screen accepts this powerful operation. Canvas 2 1 0 allows Facet to execute the corresponding action. Due to this relationship, the Kichiichi Sol Subsystem 20 4 functions as a controller (C) of the MVC paradigm for DocumentManager 1 0 8 1. Ganvas 2 1 0 also has a task to handle events. For example, Canvas 2 1 0 handles events such as mouse clicks, focus movements, and similar actions triggered by the user.

[0097] 3. Overview of the relationship between Zone, Facet, Canvas and Pane

Documents in a document processing system can be viewed from at least four perspectives. 1) the data structure used to maintain the content and structure of the document in the document processing system, 2) a means for editing the content of the document without affecting the integrity of the document, 3) on the screen of the document 4) The physical layout of the document on the screen. Zone, Facet, Canvas, and Pane represent the components of the document processing system that correspond to the above four viewpoints.

[0098] 4. Undo subsystem

As mentioned above, it is desirable to be able to undo any changes to the document (eg editing). For example, assume that the user performs an edit operation and then decides to cancel the change. In connection with Figure 12 the undo subsystem 2 1 2 implements a revocable component of the document management department. UndoManager (Undo Manager) 2 1 2 1 holds operations on all documents that may be canceled by the user.

[0099] For example, it is assumed that a user executes a command for replacing a word in a document with another word. The user then thinks again and decides to change back to the original word. The undo subsystem 2 1 2 supports such operations. UndoManager 2 1 2 1 holds the operation of UndoableEdit (Undoable Edit: Undoable Edit) 2 1 2 2. [0100] 5. Rikiichi Sol Subsystem

As described above, the controller portion of the MVC may include a force-sol subsystem 204. The Rikiichi Sol Subsystem 204 accepts input from the user. These inputs generally have the character of commands and / or editing operations. Therefore, the Rikiichi Sol Subsystem 204 can be considered as the controller (C) part of the MVC paradigm related to DocumentManager 1 081.

[0101] 6. View

As described above, Canvas 210 represents the logical layout of the document to be presented on the screen. In the example of an XHTML document, Ganvas 210 may include a box tree 208 that logically represents how the document looks on the screen. This box tree 208 will be included in the view (V) portion of the MVC paradigm associated with DocumentManager 1 081.

[0102] D. Pockabra Connection

An important feature of the document processing system is that XML documents can be handled by mapping them to other representations, and if the mapped destination representation is edited, the editing is consistent with the original XML document. To provide an environment that is reflected while maintaining

[0103] A document described in a markup language, for example, an XML document, is created based on a library defined by a document type definition. A Pokéebra is a set of tags. Since a pocabulary may be arbitrarily defined, there can be an infinite number of pocabularies. However, it is impractical to provide a dedicated processing / management environment for each of the many possible libraries. Pocabulary Connection provides a way to solve this problem

[0104] For example, a document may be described in two or more markup languages. Documents include, for example, XHTML (extensible HyperText Markup Language), SVG (Scalable Vector Graphics), Math ML (Mathematical Markup Lan guage) and other markup languages. In other words, the markup language may be found in the same way as a tag library in XML.

[0105] The Pokélibry is processed using a Pokéebra rib lagquin. Documents described in a vocabulary where plug-ins are not available in the document processing system are displayed by mapping to documents in another vocabulary where plug-ins are available. This feature enables proper display of vocabulary documents without plug-ins.

[0106] The poker library connection includes the ability to obtain a definition file and map between two different vocabularies based on the obtained definition file. A document written in one Poch library can be mapped to another Poch library. In this way, the PB library connection allows a document to be displayed and edited by a display / edit plug-in corresponding to the Pb library to which the document is mapped.

As described above, each document is generally described in the document processing system as a DOM tree having a plurality of nodes. The “definition file” describes the correspondence between each node and other nodes. It is specified whether the element value and attribute value of each node can be edited. An arithmetic expression using the element value or attribute value of the node may be described.

[0108] Using the feature of mapping, a destination DOM tree to which the definition file is applied is generated. In this way, the relationship between the source DOM tree and the destination DOM tree is established and maintained. The Pocabular connection monitors the correspondence between the source DOM tree and the destination DOM tree. Upon receiving an editing instruction from the user, the Pb library connection changes the associated node in the source D O M tree. A “mutation event” is issued to indicate that the source D O M tree has changed, and the destination D O M tree is changed accordingly.

[0109] Known only to a small number of users due to the use of the Pocabulary Connection A relatively minor vocabulary can be converted to another major vocabulary. Therefore, even a minor library used by a small number of users can properly display a document and provide a desirable editing environment.

[0110] As described above, the Pocabulary Connection Subsystem, which is a part of the document processing system, provides a function that enables multiple expressions of a document.

[0111] Figure 13 shows a Vocabulary Connection (V C) subsystem 300. The VC subsystem 300 provides a way to maintain the consistency of two alternative representations of the same document. For example, the two representations may be representations of the same document in two different pockets. As mentioned above, one may be the source DOM tree and the other may be the destination DOM tree.

[0112] 1. Pocka Library Connection Subsystem

The functions of the POB library connection subsystem 300 are realized in a document processing system using a plug-in called Vocabulary Connection 301. For each Vocabulary 305 in which the document is represented, a corresponding plug-in is required. For example, if a part of a document is described in HTML and the rest is described in SVG, a plug-in plug-in corresponding to HTML and SVG is required.

[0113] The VocabularyGonnection plug-in 301 generates an appropriate VGGanvas (Pocket library connection canvas) 310 for Zone 209 or Pane 211 corresponding to the appropriate Vocabulary 305 document. Using VocabularyGonnection 301, changes to Zone 209 in the source DOM tree are propagated to the corresponding Zone in another DOM tree 306 by the transformation rule. A conversion zole is described in the form of a Vocabulary Connection Descriptor (VCD). For each VC D file that supports conversion between such a source DOM and destination DOM, a corresponding VGManager (Pobible Connection Manager) 302 is generated. It is.

[0114] 2. Connector

Connector 304 connects the source node of the source D OM tree and the destination node of the destination DOM tree. Gonnector3 04 acts to see modifications (changes) to the source node in the source DOM tree and the source document corresponding to the source node. Then modify the node of the corresponding destination DOM tree. Gonnector304 is the only object that can modify the destination DOM tree. For example, the user can make modifications only to the source document and the corresponding source DOM library. Connector 304 then makes the corresponding modifications to the destination DOM tree.

[0115] Connector 304 is logically linked to form a tree structure. The tree formed by Connector 304 is called GonnectorTree. The Connector 304 is generated using a service called GonnectorFactory (connector factory: connector generation unit) 303. GonnectorFactory 303 creates Connector 304 from the source document and links them to form GonnectorTree. The VocabularyGonnectionManager 302 holds a GonnectorFactory 303.

[0116] As described above, a Poch Library is a set of tags in a namespace.

As shown, Vocabulary 305 is generated for a document by Vocabu IaryConnection 301. This is done by parsing the document file and generating an appropriate Vocabulary Connection Manager 302 for mapping between the source DOM and the destination D OM. Further, an appropriate relationship is created between the GonnectorFactory 303 that generates the Connector, the ZoneFactory 205 that generates the Zone 209, and the Editlet 206 that generates the Canvas corresponding to the node in the Zone. When a user disposes of or deletes a document from the system, the corresponding VocabularyGonnectionManager 302 is deleted.

[0117] Vocabulary 305 generates VGGanvas 310. In addition, Connector 30 4 and the destination DOM tree 306 are generated correspondingly.

[0118] Sources DO M and Canvas correspond to model (M) and view (V), respectively. However, such an expression is only meaningful if the target Pocabulary can be drawn on the screen. The depiction is done with Pokayabra Rib Lagoin. Pocabulary plug-ins are provided for major podocalyps such as XHTML, SVG, and MathML. Pokaya brarib lagins are used in conjunction with the target pokary library. They provide a way to map between podapuraries using vocabulary connection descriptors.

[0119] Such mapping is only meaningful if the target Pocabula mapping is possible and the method depicted on the screen is predefined. Such a rendering method is a standard defined by organizations such as W 3 C, such as X H TM L.

[0120] VGGanvas is used when a poker library connection is required. In this case, the source Ganva s is not generated because the source view cannot be generated directly. In this case, VGGanvas is created using GonnectorTree. This VGGanvas only handles event conversion and does not assist in rendering the document on the screen.

[0121] 3. DestinationZone, Pane, and Canvas

As mentioned above, the purpose of the Pocabulary Connection Subsystem is to generate and maintain two representations of the same document simultaneously. The second representation is also in the form of a DOM tree, which has already been described as a destination DOM tree. To see the document in the second representation, we need DestinationZone, Canv as and Pane.

[0122] When a VGGanvas is created, a corresponding DestinationPane307 is created.

In addition, an associated 0651 ^ 1131 ^ 011031 ^ 35308 and a corresponding BoxTree309 are generated. Similarly, VGGanvas 3 1 0 is also associated with Pane 2 1 1 and Z one209 for the source document. [0123] DestinationGanvas308 provides a logical layout of the document in the second representation. In particular, DestinationGanvas308 provides user interface features such as cursors and selections to depict documents in the destination representation. Events that occur in DestinationGanvas308 are fed to Gonnector. DestinationGanvas 308 notifies Connector 304 of events specific to the mouse event, key event, drag and drop event, and document destination (second) representation of the library.

[0124] 4. Pokablary Connection Command Subsystem

As a component of the POB library connection (VC) subsystem 300, there is a POB library connection (VC) command subsystem 31 3. The library connection command subsystem 313 generates a VGGo country and (pocket connection command) 315 used for execution of instructions related to the protocol connection subsystem 300. VGGo country and can be generated by using the built-in Go country andTemplate (command template) 31 8 and / or by generating commands from scratch in the script subsystem 31 4 using script language can do.

[0125] Examples of command templates include "lf" command template, "When" command template, and "Insert" command template. These templates are used to create VGGommand.

[0126] 5. XP at h subsystem

The X P at h subsystem 31 6 is an important component of the document processing system, and supports the implementation of the poker library connection. Connector 304 generally contains xpath information. As mentioned above, one of the tasks of a poker library connection is to reflect changes in the source DOM tree in the destination DOM tree. The xpath information contains one or more xpath expressions that are used to determine the subset of the source DOM tree that should be monitored for changes / modifications.

[0127] 6. Source DOM tree, destination DOM tree, and Connect Overview of orTree

The source DOM tree is a DOM tree or Zone that represents a document in a vocabulary before being converted to another vocabulary. The node of the source DOM tree is called the source node.

[0128] In contrast, the destination DOM tree is a DOM tree that represents the same document with a different vocabulary after being transformed by mapping, as described above in connection with the Pocabulary connection. Zone. Destination D O M Tree nodes are called destination nodes.

[0129] GonnectorTree is a hierarchical expression based on a Connector that represents a correspondence between a source node and a destination node. The Connector monitors the source node and modifications made to the source document and modifies the destination DOM tree. The Connector is the only object that is allowed to modify the destination DOM tree.

[0130] E. Event flow in document processing system

For practical use, the program must respond to user commands. An event is a way to describe and execute a user action executed on a program. Many high-level languages, such as J a V a, rely on events that describe user actions. Traditionally, programs had to actively gather information to understand user actions and execute them themselves. For example, after a program initializes itself, it enters a loop that repeatedly checks the user's actions to take appropriate action when the user takes action on the screen, keyboard, mouse, etc. Means. However, this process is cumbersome. In addition, it requires a program that consumes CPU cycles and loops while waiting for the user to do something.

[0131] Many languages solve these problems by adopting different paradigms. One of them is the foundation of all modern window systems This is event-driven programming. In this paradigm, all user actions belong to a collection of abstract events called “events”. Events describe specific user actions in sufficient detail. Rather than actively collecting user-generated events, the system notifies the program when an event to be monitored occurs. Programs that handle user interaction in this way are said to be "event driven".

[0132] This is often handled using the “Event” class, which captures the basic properties of events generated by all users.

[0133] The document processing system defines and uses its own events and how to handle these events. Several types of events are used. For example, a mouse event is an event that occurs from a user mouse action. User actions including the mouse are passed to the mouse event by Canvas 2 10. In this way, Canvas can be said to be at the forefront of interaction by users of the system. If necessary, the canvas at the front passes the content related to the event to the child.

[0134] On the other hand, a keest mouth event starts from Canvas 2 1 0. Key — Stroke events have immediate focus. That is, it is related to work at any moment. Keystroke events entered on Ganvas 2 1 0 are passed to their parents. Keystrokes are handled by different events that can handle string insertion. Events that handle string insertion occur when a character is inserted using the keyboard. Other “events” include, for example, other events that are treated like drag events, drop events, and mouse events.

[0135] 1. Handling of events outside the Pokémon connection

Events are passed using the event thread. When Ganvas 2 1 0 receives an event, it changes its state. Go country and l 0 5 2 are posted to GommandQueue 1 0 5 3 by Canvas 2 1 0 if necessary. [0136] 2. Handling of events in a Pokémon connection

Using 301, Dest i nat i onCanvas (7—the example XHTMLGanvasl 106 is specific to events that occurred, eg mouse events, keypoint events, dragand drop events, and poker libraries. Receive events, etc. These events are notified to the connector 30. More specifically, as shown in Figure 21 (b), the event flow in the VocabularyGonnection plug-in 301 is SourcePane 1 1 03 , VCCanvas 1 10 04, Destination Pane 1 1 05, DestinationGanvas 1 10 06, which is an example of DestinationGanvas, Destination DOM tree and Goni- ector ree¾r.

[0137] F. Programlnvoker and the relationship between Programlnvoker and other components

The relationship between Programlnvoker 1 03 and other components is shown in more detail in Figure 14 (a). Programlnvoker 1 03 is a basic program in the execution environment that is executed to start the document processing system. As shown in Figure 11 (b) and Figure 11 (c), UserApplication 10 06, ServiceBroke r 1041, Command I nvoker 1 051, and Resource 1 09 are all in Program I nvoker 1 03. Connected. As described above, the application 102 is a component that is executed in the execution environment. Similarly, ServiceBroker 1 0 41 manages plug-ins that add various functions to the system. On the other hand, Go country ndlnvoker 1 051 executes the instructions provided by the user and holds the classes and functions used to execute the commands.

[0138] 1. Plug-ins and services

ServiceBroker 1 041 will be described in more detail with reference to FIG. 14 (b). As mentioned above, ServiceBroker 1 041 manages plug-ins (and related services) that add various functions to the system. Service 1 042 is the lowest layer that can add or change features to the document processing system. “Service” consists of two components of ServiceGategory401 and ServiceProvider 402. As shown in Figure 14 (c), one 361 ^ 6031: 680 ^ 40 1 Can have multiple related ServiceProviders 402. Each ServicePro V i der acts to run part or all of a particular Service Gategory. On the other hand, ServiceGatego401 defines the type of Service.

[0139] Service is 1) "spot color service" that provides specific spot colors to the document processing system, 2) "ablation service" that is an application executed by the document processing system, and 3) the entire document processing system. It can be classified into three types: “environmental services”, which provide the necessary characteristics over a wide range.

[0140] An example of Service is shown in Figure 14 (d). In Gat egory of application Service, it is a row of system utility card << corresponding ServiceProvider. Similarly, Editlet 206 is a Category, and HTMLEditlet and SVGEdit let are corresponding ServiceProviders. ZoneFactory 205 is another Category of Service, and has a corresponding ServiceProvider (not shown).

[0141] Although plug-ins have already been described as adding functionality to a document processing system, they may be considered a unit consisting of several ServiceProviders 402 and their associated classes. Each plug-in has dependencies and ServiceGategory 401 described in the declaration file.

[0142] 2. Relationship between Program Invoker and applications

Figure 14 (e) shows further details about the relationship between Programlnvoker 1 03 and UserApplication 1 06. Necessary documents and data are loaded from storage. All necessary plug-ins are loaded on ServiceBroker 1 04 1. ServiceBroker 1 04 1 holds and manages all plug-ins. Plug-ins can be physically added to the system and their functions can be loaded from storage. When the plug-in content is loaded, ServiceBroker 1 04 1 defines the corresponding plug-in. Next, the corresponding UserApplication 1 06 is generated, loaded into the execution environment 1 0 1, and attached to the Programlnvoker 1 03.

[0143] G. Relationship between application service and environment

Figure 15 (a) shows an application loaded on Programlnvoker 1 03 Provides further details about the configuration of the service. Command Invoker 1 051, which is a component of command subsystem 1 05, starts or executes Command 1 052 in Program Invoker 1 03. Command 1 052 is a command used to process a document such as XML and edit the corresponding XML DOM tree in the document processing system. Command Invoker 1 051 holds classes and functions necessary for executing Comma nd1 052.

[0144] ServiceBroker 1 041 is also executed in Program nvoker 1 03. UserApipication 1 06 is connected to the user interface 1 07 and GoreGomponent 1 1 0. GoreGomponent 1 1 0 provides a way to share documents between all panes. GoreGomponent 1 1 0 provides additional fonts and acts as a toolkit for Pane.

FIG. 15 (b) shows the relationship between Frame 1 07 1, MenuBar 1 072, and StatusBar 1 07 3.

[0146] H. Application Core

Figure 16 (a) provides further explanation of the application core 108 that holds all documents, and parts of documents and data belonging to the documents. Gor eComponent 1 1 0 is attached to DocumentManager 1 081 that manages document 1 082. DocumentManager 1 081 is the owner of all documents 1 082 stored in the memory associated with the document processing system.

[0147] DocumentManager 1 081 is also connected to Root Pane 1 084 to facilitate the display of the document on the screen. The functions of GI ipBoard 1 087, SnapShot 1 088, Drag & Drop 601 and Over Iay 602 are also attached to GoreGomponent 1 1 0.

[0148] SnapShot 1 088 is used to restore the application state. When the user starts SnapShot 1 088, the current state of the application is detected and stored. Then, when the application state changes to another state, the stored state contents are preserved. SnapShotl 088 is illustrated in Figure 16 (b). In operation, from the URL where the application is In order to make it possible to seamlessly execute the operation of going back and the operation of moving forward when moving to Snapshot, Snapshot 1088 stores the previous state.

[0149] I. Document structure in DocumentManager

Figure 17 (a) shows further explanation of DocumentManager 1 08 1 and how documents are organized and maintained in DocumentManager. As shown in FIG. 1 1 (b), DocumentManager 1 08 1 manages document 1 082. In the example shown in Fig. 17 (a), one of the documents is RootDocument 701, and the remaining document is SubDocument 702. Do cumentManager 1 08 1 is connected to RootDocument 70 1 and RootDocument 7 0 1 is connected to all SubDocuments 702.

[0150] As shown in Figure 1 2 and Figure 17 (a), DocumentManager 1 08 1 is an object that manages all documents 1 082 00 (51 ^ 6111: 00111: 3 ^ 6 "203 Tools that form part of the toolkit 20 1 (eg XM L toolkit) including D0MService703 and lOManager 704 are also supplied to DocumentManager 1 08 1. See Figure 17 (a) again. Then, D0MService703 generates a DOM tree based on the document managed by DocumentManager 1 08 1. Each Document 705 is created by the corresponding DocumentGontainer 203, whether it is RootDocument 701 or SubDo cument702. Managed.

[0151] Figure 17 (b) shows how documents A_E are arranged hierarchically. Document A is a RootDocument. Document B—D is a SubDocument of Document A. Document E is a SubDocument of Document D. The left side of Fig. 17 (b) shows an example of the same document hierarchy displayed on the screen. Document A, the RootDocument, is displayed as a basic frame. Document B_D, which is a SubDocument of Document A, is displayed as a subframe in Basic Frame A. Document E, which is a SubDocument of Document D, is displayed on the screen as a subframe of Subframe D.

[0152] Referring again to Figure 17 (a), UndoManager (Undo Manager: Undo Manager) 706 and UndoWrapper 707 are respectively Generated for DocumentGontainer 203. UndoManager 706 and UndoWrapper 707 are used to execute undoable commands. By using this feature, you can undo changes made to a document using an editing operation. SubDocument changes are also closely related to RootDocument. The undo operation takes into account changes that affect other documents in the hierarchy and maintains consistency among all documents in a chained hierarchy, for example, as shown in Figure 17 (b). Guarantee that.

[0153] UndoWrapper 707 wraps the undo objects related to SubDocument in DocumentGontainer 203 and binds them to the undo object related to RootDocument. UndoWrapper 707 executes collection of undoable objects that can be used in UndoableEditAcceptor (undoable edit acceptor).

[0154] The UndoManager 706 and the UndoWrapper 707 are connected to the Undoab IE Edit Acceptor 709 and the UndoableEditSource (Undoable Edit Source) 708. As will be appreciated by those skilled in the art, Document 705 may be UndoableEditSource 708 or the source of an editable edit object.

[0155] J. Undo command and undo framework

Figures 18 (a) and 18 (b) provide further details about the undo framework and undo commands. As shown in Fig. 18 (a), UndoCommand 80 1, RedoCommand 802, and UndoableEditGommand803 are commands that can be loaded on Gommandlnvoker 1 05 1 as shown in Fig. 11 (b) and executed in order. Is done. UndoableEditGommand803 is further attacked by Undoable EditSource 708 and Undoab IeIdAcceptor 709.

“Foo” EditGommand804 and “bar” EditGommand 805 are examples of Undoab IeEditC ommand.

[0156] 1. Executing UndoableEditGommand

Figure 18 (b) shows the execution of UndoableEditGommand. First, the user edits Suppose you edit a Document 705 using a command. In the first step S 1, UndoableEditAcceptor 709 is attacked in Document 705 DOM tree 11 | ^ 0813 | 6 already 1: 30111 ^ 6708. In the second step S2, Document705 is edited using the DOM API based on the command issued by the user. In the third step S3, the mutation event listener is notified that a change has been made. That is, in this step, the listener that monitors all changes in the DOM tree detects the editing operation. In the fourth step S 4, UndoableEdit is stored as an object of UndoManager 706. In 5th step S5, it is defeated from UndoableEditAcceptor 709 ^ UndoableEditSource708. The UndoableEditSource 708 may be the Document 705 itself.

[0157] K. Procedure for loading documents into the system

In the subsection above, the various components and subcomponents of the system were described. The following describes the methodology for using these components. Figure 19 (a) shows an overview of how a document is loaded into the document processing system. Each step is detailed in relation to a specific example in Figures 24-28.

[0158] Briefly, a document processing system generates a DOM from a binary data stream consisting of data contained in a document. ApexNode (apex node) Force Generated for the part of the document that is the focus and belongs to the Zone. Subsequently, the corresponding Pane is identified. The identified Pane generates Zone and Canvas from ApexNode and physical screen surface. The Zone then creates Facets for each node and provides the information needed for them. Canvas generates a data structure for rendering nodes from the DOM tree.

[0159] More specifically, the document is loaded from storage 901. A DOM tree 902 of the document is generated. A corresponding DocumentGontainer 903 is created to hold the document. DocumentGonta iner 903 is compatible with DocumentManager 9 Attach to 04. A DOM tree contains a root node and sometimes multiple secondary nodes.

[0160] In general, such documents include both text and graphics. Thus, a DOM tree may have, for example, an SV G subtree as well as an X H TM L subtree. The XH ™ L subtree has an XH ™ L ApexNode 905. Similarly, the SVG subtree has S V G ApexNode 906.

[0161] In step 1, ApexNode 906 force is attached to Pane907, which is the logical layout of the screen. In step 2, Pane907 asks GoreGomponent, who is PaneOwner 908, a ZoneFactory for ApexNode 906. In step 3, PaneOwner 908 returns a ZoneFactory and an Edi tl et which is a GanvasFactory for ApexNode 906.

[0162] In step 4, Pane907 force << Zone909 is generated. Zone909 is attached to Pane 907. In step 5, Zone909 generates a facet for each node and attaches to the corresponding node. In Step 6, Pane 907 force << Ganvas9 1 0 is generated. Canvas 9 1 0 is attacked by Pane 907. Ganvas9 1 0 includes various commands. In step 7, Ganvas9 10 builds a data structure for rendering the document on the screen. For XH TM L, this includes a box tree structure.

[0163] 1. Zone MV C

Figure 19 (b) shows an overview of the Zone configuration using the MVC paradigm. In this case, since Zone and Facet are inputs related to the document, Model (M) includes Zone and Facet. Since the canvas and the data structure for rendering the document on the screen are the output that the user sees on the screen, the view (V) corresponds to the canvas and the data structure. Since Command executes control operations on the document and its various relationships, Control (C) includes Go Country and included in Canvas. [0164] L. Document Representation

An example of a document and its various expressions will be described below using FIG. The document used in this example contains both text and images. Text is represented using X HTML, and images are represented using SVG. Figure 20 details the MVC representation of the relationship between the document components and the corresponding objects. In this example, Document 1 001 is attached to DocumentContainer 1 002 that holds Document 1 001. The document is represented by a DO M tree 1 003. The DOM tree contains ApexNode 1 004.

[0165] ApexNode is represented by a black circle. Nodes that are not vertices are represented by white circles. The Facet used to edit a node is represented by a triangle and is attached to the corresponding node. Since the document has text and images, the DOM tree of this document contains an XHTML portion and an SVG portion. ApexNode 1 004 is the top node of the XH ™ L subtree. This is attacked by XHTMLPane 1 005, the top pane for the physical representation of the XHTML part of the document. ApexNode 1 004 is also attacked by XHTMLZone 1 006, which is part of the document's DOM tree.

[0166] Facet corresponding to Node 1 004 is also attached to XHTMLZone 1 006. X HTMLZone 1 006 is attached to XHTMLPane 1 005. XHTMLEditlet generates XHTMLGanvas 1007, which is a logical representation of the document. XHTMLGanvas 1 007 is attacked by XHTMLPane 1 005. XHTMLGanvas 1 007 generates BoxTree 1 009 for the XHTML component of Document 1 001. Various Go countries and 1 008 required to hold and render the X H TM L portion of the document are also added to XHTMLGanvas 1 007.

[0167] Similarly, ApexNode 1 0100 in the SVG subtree of the document is attached to SVGZone 1 01 1 that is part of the DOM tree of Document 1 001 that represents the SVG component of the document. ApexNode 1 01 0 is attached to SVGPane 1 01 3 which is the highest Pane in the physical representation of the SVG part of the document. SVGGanvas 1 01 2, which represents the logical representation of the S VG part of the document, is generated by SVGEditlet And attached to SVGPanel 01 3. The data structure and commands for rendering the SVG part of the document on the screen are attacked by SVGGanvas. For example, this data structure may include circles, lines, rectangles, etc. as shown.

[0168] A part of the representation of the document example described in relation to FIG. 20 will be further described using the MVC paradigm described above in relation to FIG. 21 (a). Figure 21 (a) shows a simplified MV relationship in the XH TM L component of Document 1001. The model is XHTMLZonel 1 01 for the X H TM L component of Document 1 001. The XHTMLZone tree contains several Nodes and their corresponding Facets. The corresponding XHTMLZone and Pane are part of the model (M) part of the MV C paradigm. The View (V) portion of the MVC paradigm is the corresponding X HTML Canvas 1 1002 and BoxTree of the X H TM L component of Document 1 001. The XHTML part of the document is rendered on the screen using Canvas and Go country and included. Events such as keyboard and mouse input go in the opposite direction, as shown.

[0169] The SourcePane has an additional function: the role as a holder of DOM. Figure 21 (b) provides a library connection for the Document "! 001 component shown in Figure 21 (a). SourcePane 1 1 03, acting as a DOM holder, is the source D OM tree of the document. Gonne ctorTree is created by GonnectorFactory and creates DestinationPane 1 1 05 which also functions as the destination DOM holder Destinatio nPane 1 1 05 is a layout of the XHTMLDestinationGanvas 1 1 06 in the form of a box tree. Is done.

[0170] Relationship between M. plug-in subsystem, Pb library connection, and connector

Figures 22 (a)-(c) show further details related to the plug-in subsystem, the poker library connection, and the connector, respectively. Plug-in subsystems are used to add or replace functionality in a document processing system. It is. The plug-in subsystem includes ServiceBroker 1 041. ZoneFactoryService 1 201 that is attacked by Service Broker 1 041 generates a Zone for a part of the document. EditletService 1 202 is also attached to ServiceBroker 1 04 1. EditletService 1 202 generates a Ganvas corresponding to the Node in the Zone.

[0171] Examples of ZoneFactory are XHTMLZoneF actory 1 21 1 and SVGZoneFactory 1 21 2 that generate XHTMLZone and SVGZone, respectively. As described above in connection with the example document, the text component of the document may be represented by generating XHTMLZone, and the image may be represented using SVGZone. Examples of EditletService include XHTMLEditlet 1 221 and SVGEditlet 1 222.

[0172] Figure 22 (b) shows further details related to the Pocabulary connection. As described above, the POB library connection is an important feature of a document processing system, and enables consistent expression and display of documents in two different ways. The VGManager 302 that holds the GonnectorFactory 303 is a part of the poker library connection subsystem. GonnectorFactory 303 generates a connector 304 for the document. As mentioned above, the Connector monitors the nodes in the source D OM and modifies the nodes in the destination DOM to maintain consistency between the two representations.

[0173] Temp late 31 7 represents a conversion rule of several nodes. A poker library connection descriptor (VCD) file is a list of Templates that represent a number of rules that transform an element or set of elements that satisfy a particular path or rule into another element. Temp late 31 7 and GommandTemplate 31 8 are all attached to VGMana ger302. VGManager is an object that manages all sections in a V CD file. One VGManager object is generated for one VCD file.

[0174] Figure 22 (c) provides further details related to the Connector. GonnectorF actory 303 (Connect ¾: Generate from i source document. ConnectorFactory 3 03 is attached to Vocabulary, Template, and ElementTemplate Each creates a Vocabu IaryConnector TemplateConnector ElementGonnector.

[0175] The VGManager 302 holds a GonnectorFactory 303. The corresponding VCD file is read to generate the Vocabulary. In this way, Connect orFactory 303 force << is generated. This GonnectorFactory 303 is related to a ZoneFactory that generates a Zone and an Editlet that generates a Canvas.

[0176] Next, the EditletService of the target platform generates a VGGanvas. VGGanvas also creates an ApexNode Connect or in the source DOM tree or Zone. Child connectors are recursively generated as needed. Gonnec torTree is created by the set of templates in the V CD file.

[0177] A template is a set of rules for converting markup language elements into other elements. For example, each template is matched to the source DOM tree or Zone. If it matches properly, a vertex connector is created. For example, the template “A / * / D” matches all branches that start at node A and end at node D, regardless of what nodes are in between. Similarly, “〃B” matches all “B” nodes from the root.

[0178] Example of VCD file related to N. GonnectorTree

Continuing with the example describing the processing associated with a particular document. A document with the title “MySampleXML” with a document title is loaded into the document processing system. Figure 23 shows an example VCD script using VGManager and Connect orFactoryTree for the “MySampleXML” file. Shows the section, template section and corresponding components in VGManager in the script file. In the tag “vcd: vocabularyj”, the attribute “match” is “sample: rootj”, “label” is “MySampl eXMLj”, “cal temp latej is“ sample templatej ”.

[0179] In this example, Vocabulary includes a vertex element as “sampl e: root j in the VGManager of“ MySampl eXML ”. The corresponding UI label is“ MySampl eXMLj. In the template section, the tag is “vcd: templatej, ¾ Hij (i “sample: tempi ate”.

[0180] O. Detailed example of how files are loaded into the system

Figure 24-28 shows a detailed description of loading the document “MySampleXML”. In step 1 shown in Figure 24 (a), the document is loaded from storage 1 405 forces. The DOMService generates a DocumentGontaineM 401 that matches the D OM tree and DocumentManager 1 406. DocumentGontaineM 4 01 is attached to DocumentManager 1 406. The document contains XHTML and MySampleXML subtrees. ApexNode 1 403 of XH T M L is the top node of X H T M L to which the tag rxhtml: htmlj is attached. ApexNode 1 404 of “MySampleXML” is the top node of “MySampl eXMLj” with the tag “sample: rootj”.

[0181] In step 2 shown in Fig. 24 (b), RootPane generates XHTMLZone, Facet, and Canvas of the document. Panel 407, XHTMLZone 1 408, XHTMLCanvas 1 409, and BoxTree 1 410 are generated corresponding to ApexNode 1 403.

[0182] In step 3 shown in Fig. 24 (c), a tag "samp le: root" that XHTMLZone does not know is found and a SubPane is generated from the XHTMLGanvas area.

[0183] In Step 4 shown in Fig. 25, SubPane can handle "sample: rootj and obtain a ZoneFactory that can generate an appropriate Zone. This ZoneFactory is in a Vocabulary where ZoneFactory can be executed. It contains the contents of the Vo Ibu IarySection on “MySampl eXML”.

In step 5 shown in FIG. 26, a Vocabulary force << DefaiHtZone 1 601 corresponding to “MySampleXML” is generated. A corresponding Editlet is created and SubPane 1 501 is provided to create a corresponding Ganvas. Editlet is generated as VGGanvas ¾ :. And that's TemplateSection¾rP 乎. GonnectorFactoryTree Ru was also included ^λ. GonnectorFactoryTree creates all Gonn ector¾r that will become GonnectorTree.

[0185] In step 6 shown in Figure 27, each connector is a destination DO Generate an M object. Some of the connectors contain xpath information. The xpath information contains one or more xpath expressions that are used to determine the subset of the source DOM tree that needs to be monitored for changes / modifications.

[0186] In step 7 shown in FIG. 28, the Pocabulary creates a Destination DOM i onPane from the source DOM pane. This is done based on the SourcePane. The ApexNode in the destination tree is attached to the DestinationPane and the corresponding Zone. The DestinationPane is provided with its own Editlet that creates a DestinationGanvas and builds data structures and commands to render the document in the destination format.

[0187] Figure 29 (a) shows the flow when an event occurs on a node that does not have a corresponding source node and exists only in the destination tree. Events acquired by Canvas, such as mouse events and keyboard events, are passed to the destination interface and transmitted to the EI ementTemp IateConnector. Since ElementTemplateGonnector does not have a corresponding source node, the transmitted event is not an edit operation on the source node. ElementTemplateGonnector executes the corresponding Action if it is communicated and the new event matches the command described in GommandTemplate. If there is no matching command, El ementTemp IateConnector ignores the transmitted event.

[0188] Figure 29 (b) shows the flow when an event occurs on the node of the destination tree associated with the source node by TextOfGonnector. The TextOf Connector gets the text node from the node specified by XP ath in the source D OM tree and maps it to the node in the destination DOM tree. Events acquired by Ganva s, such as mouse events and keyword events, pass through the destination tree and are transmitted to TextOfGonn ector. TextOf Connector maps the transmitted event to the corresponding edit command of the source node, and loads it in Queuel 053. An edit command is a set of DOM API calls that are executed via Facet. Ki When a command loaded on the user is executed, the source node is edited. When the source node is edited, a mutation event is issued, and the change of the source node is notified to the TextOfGonnector registered as a listener. Text OfGonnector reconstructs the destination tree so that changes in the source node are reflected in the corresponding destination node. At this time, if a control statement such as “for eachj or“ for l oopj ”is included in the template that includes T extOf Connector, GonnectorFactory re-evaluates this control statement and reconstructs Tex tOfGonnector. The tree is rebuilt.

[0189] (First embodiment)

In the first embodiment, a new XML utilization technology is proposed. In addition, a new programming / radame is proposed.

[01 90] As described above, the creator of a web page is able to create a web page having various functions by using the V B script to control the Active X control. The Active X controls themselves are black-boxed inside, so you can freely customize the functions of the Activ X controls and connect multiple Activ X controls to each other. It cannot be operated directly in cooperation.

[0191] The present inventor has realized that the XML processing technology described in the base technology is a technology suitable for solving such a problem. Conventional general archiving stores data necessary for its own operation in its own binary format, so unless an API that allows external reference is prepared, It was not possible to refer to the internal data from outside. By holding the data used by the application in XML format, it is possible to easily reference data from other publications using the technology described in the base technology. . In other words, the document processing apparatus 20 of the base technology holds the XML document in the DOM format, so that data can be freely accessed from the outside using the API provided by the DOM as a standard. Using this technology that should be called a “white box”, Build a highly flexible programming paradigm. The present inventor has further advanced the XML processing technology described in the prerequisite technology, and has come up with a new XML usage technology as described later.

[0192] Here, the relationship between the data structure of an XML document and the processing technology of the XML document will be described. Figures 30 (a), (b), and (c) show examples of the data structure of the XML document to be processed. The simplest example is an XML document written in a single Pocabulary, as shown in Figure 30 (a). The processing system of this XML document only needs to be able to process an XML document described in a specific vocabulary, such as a browser that displays a web page described in XHTML.

[0193] On the other hand, as described in the base technology, the applicant of the present invention, as shown in Fig. 30 (b), has a certain component of a library (indicated by white circles) and another one. We have developed a document processing device that can properly process XML documents that contain the following components (indicated by black circles). In the base technology document processing device 20, an appropriate processing system is called for each fragment by the main control unit 22, which is an example of the activation unit, for an XML compound document that combines various XML vocabularies. You can build a view and edit the XML compound document according to the user's editing operation. These processing systems may be hard-coded plug-ins (for example, HTM L unit 50 and S VG unit 60) developed by Java (registered trademark), etc., or written in the definition file according to VC unit 80. Sometimes it is script-based. If it is a media vocabulary such as XHTML, a one-word plug-in is provided, and if it is a user's private library, it will be described in a definition file. With this technology, for example, in the example shown in Fig. 30 (b), a document described in XHTML (components with white circles) is replaced with a partial document described with a library for displaying graphs (components with black dots). It is possible to insert and place a graph on the screen of an XH TM L document.

[0194] Let us focus on the relationship between the XML fragment and the processing system. Processing system is X Called by the ML fragment, and builds a view based on the contents of XML. Then, get UI events from the user and edit the XML. From a different point of view, it can be understood that the processing system responsible for displaying and editing a specific library is called with the XML fragment of that library as an argument.

[0195] The present inventor has realized that a more free and flexible processing system execution environment can be provided by using such a framework. In other words, the processing system is not limited to displaying and editing a certain XML, but may perform various processes more freely. For example, the server may be accessed through the Web Service API based on the data in the XML fragment, or natural language processing such as summarization and translation may be performed. The XML fragment is also an argument when starting the processing system, but at the same time, it plays the role of heap memory used during operation. Considering this, the document processing device 20 of the base technology places a “tag” to start the procedure (processing system) in the XML document, and designates the argument as an attribute (attribute). It can be seen that this is a unique program execution environment where the procedure is executed with the enclosed text part as the operation target.

[0196] In the present embodiment, a data structure as shown in Fig. 30 (c) is proposed as a data structure of a new XML document. In FIG. 30 (c), the component 25 indicated by hatching has pointer information to other data 26 in the document. The processing system in charge of the library to which this component 25 belongs operates by referring to the data 26 indicated by the pointer information. For example, as described above, when a graph is inserted into an XHTML document, the entity of the graph data is not described in the graph display platform as shown in Fig. 30 (b), but in the XHTML document. A graph is generated with reference to other data described in (1). By adopting such a data structure, it is possible to construct an application that operates by referring to other data in the document or data of another document.

[0197] The document processing device refers to the namespace of the component included in the document and Start the processing system. Therefore, in the example of FIG. 30 (c), the component 25 shown with diagonal lines has a function of starting a processing system for displaying graphs. Then, the activated processing system does not process the component existing under the component 25, but refers to the data 26 pointed to by the pointer information of the component 25. Operate. This component 25 also has an “anchor” function that indicates the position of the graph in the document. The pointer information included in the component 25 may be specified as an attribute of the component 25, or may be specified as an element value of the component 25 itself or a subordinate component. Parameter information necessary for the operation of the processing system may be described in the XML fragment containing the component 25.

[0198] With this technology, the processing system can use the data outside the fragment that it is responsible for as an argument that adjusts its own behavior or as a heap area. In other words, the model is such that only the reference position is entered in the fragment part using the Xpaht equation, and the actual value is beyond the Xpaht equation. This is equivalent to saying that a pointer is passed as a function argument.

[0199] Considering the above-described technique from the viewpoint of a programming paradigm, an application runtime environment that can operate by referring to data at any location in a document is provided. Furthermore, as described above, data in a document can be referenced from any application using the DOM API. Therefore, there is a new programming environment that can use data in a document held as a DOM as a shared memory. Provided. In the document, the component 25 for starting the application is described, and the application started with the component 25 refers to the pointer information of the component 25. The other data 26 of the document is used as a shared memory. In this way, a new programming paradigm is realized in which documents and applications work together seamlessly.

[0200] The document processing device 20 can detect the mutation when the DOM is changed. The data is referred to by the graph display processing system 2 6 force even if it is changed by another processing system, the change is notified to the graph display processing system. By doing so, changes can be appropriately reflected. In this way, even when multiple applications are operating with reference to the same data, the data can be linked appropriately, so that multiple applications can be easily linked to operate. The fact that multiple processing systems operate with reference to the same pointer is, in other words, the cooperation of processing systems that use XML documents as shared memory.

[0201] In a conventional spreadsheet application, a calculation procedure could be started by entering a calculation formula in a cell. When embedding a graph, it is common to specify a range of cells to be referenced and generate a graph using the data in that cell. It can be said that the technology of this embodiment brings this model into the XML compound document and incorporates the features unique to XML.

[0202] Using a spreadsheet application, if you create a "functional" document with a tabulation function and a graph display function, the user can enter data and recalculate using this document. Or you can manipulate the results while simulating the results. Similarly, the document processing apparatus of the present embodiment uses the above-described technology to link various procedures (processing systems) to create “functional” XML compound documents specialized for various purposes. Can do. What's more, unlike spreadsheet applications, it is possible to implement a platform based on open, XML technology that is transparent and scalable. Users can use these functional XML documents to perform various operations.

[0203] Figures 3 1 (a) and (b) show examples of pointer information. Figure 31 (a) shows an example when the pointer information is described by an X path expression. In this example, pointer information indicating the position of data 26 to be referred to by the processor is described by an X path expression. The processor uses this X path expression to specify the data that it should reference. 2 6 can know the position.

[0204] Figure 3 (b) shows an example where pointer information is given as conceptual information.

Component 25 contains clearly standardized conceptual information that conceptually indicates the location of data 26 to be referenced by the processor as element or attribute values. The “clearly defined conceptual information” may be, for example, conceptual information based on ontology technology. In this case, a concept solution engine 27 is provided to interpret the concept information and identify the actual data. The concept solution engine 27 acquires the concept information and converts the concept information into, for example, a tag name. When “important data” is specified as concept information, the concept resolution engine 27 returns tag names such as <important>, <i mportant>, and <confidential>, for example. This indicates that the processor should refer to the data with tags such as <Important> in the document. You may specify what information is required when you submit a solution to the concept resolution engine 27. For example, when the concept of “important data” is specified, if you request conversion to an English tag name, the concept resolution engine 2 7 will return tag names such as <i mportant> and <secret>. May be.

[0205] When the parameter information required for the operation of the processing system is described in the XML fragment including component 2 5, as one of the parameter information, the destination data indicated by the pointer information It may describe semantic type information that is clearly specified. “Separately defined semantic type information” may be, for example, semantic type information based on ontology technology. For example, when the concept of “important” is designated as the pointer information, information such as “management” and “business” may be designated as the semantic type information. In addition, when the concept of “amount” is specified as the pointer information, information such as “sales money”, “recommended retail price”, and “borrowing money” may be specified as semantic type information. This allows the processor to check semantic type consistency.

[0206] In traditional programming languages, types cannot have semantic meaning. For example, in the case of "int" type that is numeric type, the numeric value to be assigned Although it is possible to check the consistency of whether or not is an integer, it is not possible to check the semantic consistency of the number to be assigned. For this reason, for example, in the process of calculating the person-month, even if the person and the month are mistakenly added or the person and the person are multiplied, the programming language cannot recognize a semantic error. . On the other hand, according to the technology of the present embodiment, whether it is “sales” or “borrowing”, “1 yen unit” or “thousand dollar unit”, Semantic consistency such as “number of people” or “year” can be confirmed. When the processor confirms the semantic type consistency, for example, using the concept resolution engine 27, is the tag name of the data to be referenced consistent with the specified semantic type information? You may check whether or not.

[0207] Technology that gives semantic type information to data using ontology technology can be used universally as a new programming technology. In this way, programming techniques that include a semantic technical concept are called “semantic programming” in contrast to conventional programming techniques.

[0208] Here, as an example of the semantic programming technique, an explanation will be given of the expansion of the mutation event by the D O unit 30 described in the base technology. When a DOM is changed, if the DOM contains “standardized meaningful type information”, a mutation event is issued to the processing system that references the type information. The In other words, the processor can not only directly specify the DOM that it wants to monitor for changes, but can also indirectly specify “significantly standardized semantic type information”.

[0209] Figures 3 2 (a) and (b) are diagrams for explaining the mechanism for notifying DOM changes. Figure 3 2 (a) shows the mechanism of the mutation event in the document processing device 20 of the base technology. Processing system 29 specifies the node that should be monitored for changes using the X path expression and registers it as a listener for the mutation event. The DOM unit 30 issues a mutation event to the registered listener when the DOM changes. [0210] Figure 3 2 (b) shows the mechanism of the mutation event newly proposed in this embodiment. The document processing device 20 is newly provided with a notification unit 28 that mediates notification of mutation events. The notification unit 28 receives the designation of the node to be monitored from the processing system 29. When the DOM is changed, the DOM unit 30 notifies the notification unit 28 of that fact. When notified of the DOM change from the DOM unit 30, the notifying unit 28 issues a mutation event to the processing system 29 monitoring the changed node.

[021 1] The notification unit 2 8 may accept the node to be monitored by the processing system 29 using the X path expression, but it is clearly standardized to provide a more flexible and versatile programming environment. The designation based on the converted concept information may be accepted. In this case, when notified of the DOM change from the DOM unit 30, the notification unit 28 sends the tag name of the node to the concept resolution engine 27, and the concept resolution engine 27 sends the tag name to the tag name. Get the corresponding conceptual information. The notification unit 28 issues a mutation event to the processing system 29 in which the acquired conceptual information is registered. Thereby, the processing system 29 can request the notification unit 28 to notify, for example, when “important information” is changed. When the notification unit 28 receives a mutation event from the DOM unit 30, the notification unit 28 determines whether the changed node corresponds to “important information” by using the concept solution engine 27. If applicable, notify the processor 29 of the DOM change.

[0212] With such semantic programming technology, more flexible and versatile programs can be easily developed.

[0213] Next, a technique for editing a document having various functions using the data structure shown in Fig. 30 (c) will be described.

[0214] The processing system of the namespace library to which the component 25 belongs, that is, the processing system activated by the component 25 may be provided as a part of a customizable application. In the following, this processing system is called a “view template” in the sense of the parts that make up the document view. A view template may be provided as a script-based definition file or It may be provided as a druppin. To use the functions of the view template 構成, describe the component 2 5 that is the anchor of the view template 中 in the document, and indicate the data that the processor should refer to the component 2 5 In addition to describing the pointer information, other information required by the processing system may be described. In order to make the view template available for general use, it is preferable to provide an environment in which the pointer information can be specified as clearly standardized conceptual information. The data to be referred to may be specified using a conditional expression that combines arithmetic operations, logical operations, natural language processing, and other arbitrary operations.

FIG. 33 shows the configuration of the document processing apparatus according to the embodiment. The document processing apparatus 100 according to the present embodiment includes a view template control unit 70, an acquisition unit 71, and a view template 7 8 in addition to the configuration of the document processing apparatus 20 of the base technology shown in FIG. Is provided. The view template control unit 70 includes a presentation unit 72, a reception unit 74, and an editing unit 76.

[0216] The acquisition unit 7 1 acquires a document to be processed. As described above, the view template 78 is a processing system that expresses a predetermined function using data contained in a document, and is a component part of a document editing screen.

[0217] The presentation unit 7 2 presents the user with a view template 78 that can be used in the document processing apparatus 100. The presentation unit 72 may present a list of view templates 78 installed in the document processing apparatus 100 on the display screen, and the available view according to the contents of the document being edited. Template 7 8 may be selected and presented. For example, when an SVG document is being edited, a view template 78 that can be inserted into the SVG document may be selected and presented.

[0218] The accepting unit 74 accepts an instruction from the user to add the view template 78 to the document. When the user drags and drops the icon of the view template 7 8 displayed on the list screen of the view template 7 8 presented by the presentation unit 7 2 onto the display screen of the document being edited, the reception unit 7 4 An instruction to insert a view template 78 at the position may be accepted. [0219] The editing unit 7 6 is configured to activate the view template 7 8 at the position instructed to be inserted in the document when the reception unit 7 4 receives the insertion instruction of the view template 7 8. Insert an element (tag). At this time, the editing unit 76 may present a screen for accepting the range of data used by the view template 78 for operation, and accept the designation of data from the user. The editing unit 76 may automatically determine the range of data used by the view template 78 for operation. The editing section 76 describes the pointer information of the data used by the view template 78 for operation in the document. Further, the editing unit 76 may accept parameters necessary for the operation of the view template 78 from the user or automatically determine and describe them in the document.

[0220] When the editing unit 7 6 adds a component for starting the view template 7 8 to the document, the main control unit 22 starts the processing system for processing the component, that is, the view template 7 8. The view provided by the view template 7 8 is displayed on the document editing screen. After that, the functions provided by View Template 78 can be used on the document editing screen.

[0221] Figure 34 shows an example of a document editing screen. On the document editing screen 9 7, a view template palette 9 8 is displayed by the presentation unit 72. The document being edited contains information such as the personal schedule, To Do, and e-mail, but the edit screen shown in Figure 34 shows a view on the information. It is not displayed because it is not.

[0222] Here, when the user selects a view template 7 8 for displaying a schedule from the view template palette 9 8 and drags and drops it on the edit screen, the reception unit 7 4 This request is accepted, and the editing unit 76 inserts a component for starting the view template 78 for schedule display at a predetermined position of the document. At this time, the editing unit 76 describes the pointer information of the part storing the schedule information in the document as the attribute value of this component.

[0223] Figure 3 5 shows the view template for schedule 7 8 activated The edit screen is shown. When a component for starting up a view template 7 8 for scheduling is inserted into a document by the editing unit 7 6, a view template 7 that processes the component by the main control unit 2 2, which is an example of the startup unit, 7 8, that is, the schedule view template 7 8 is activated, and the schedule information 9 9 described in the part indicated by the pointer information is displayed in a table format.

[0224] As described above, according to the technique of this embodiment, view templates 78 having various functions prepared for general purposes can be added to a document, and a functional document can be easily constructed. can do.

[0225] (Second embodiment)

The technique for providing a general-purpose document processing function described in the first embodiment will be further described. The function called “view template” in the first embodiment is a processing system (component) that provides a general-purpose VC function in this embodiment. AVC (Adaptive Vocabu) l ary C omponent).

FIG. 36 shows the configuration of the document processing apparatus according to the present embodiment. The document processing apparatus 100 according to the present embodiment replaces the view template control unit 70 and the view template 78 of the document processing apparatus 100 according to the first embodiment shown in FIG. Units 3 0 0 0 are provided. AVC control unit 3 00 0 is a processing system that provides AVC functions. AVC component for table display 3 0 1 0, AVC component for chart display 3 0 2 0, UI display AVC component 3 0 3 0, AVC component 3 0 4 0 for tree display, and AVC property setting part 3 0 0 2 for setting property information necessary for the operation of these AVC components including.

[0227] Figure 37 shows an example of an XML document populated with AVC component properties. This XML document is described as a “doc”, a library for describing data in the word book. An element “page” that is a child element of the root element “doc” indicates a page of the word book, and a plurality of elements are provided according to the number of pages. So Each element “page” includes an element “english” for storing English notation and an element “japanese” for storing Japanese notation.

In the example of FIG. 37, in order to display this word book in a table format, an AVC property 3012 describing property information necessary for the operation of the AVC component 3010 for table display is inserted. The AVC property 3012 is described by a table display “tbl” that can be processed by the table display AVC component 3010. In the A VC property 3012, the correspondence between the “tbl” and the “doc” library is described using the “avc” library for describing the AVC property. The following is a description of the original XML document, where “doc” is referred to as “host library” and the inserted AVC property is described as “pbl”, where “tbl” is referred to as “guest Poch library”. Or “AVC Pocapri”.

[0229] In the example of Fig. 37, the element "column" that stores the data of each column of the table has two "property" elements as child elements. In the first element “property”, the property information that the parameter “labe 卜 transfer 1” refers to the element “engl ish” of the host platform is recorded. The second element “pr opertyj” records property information that the parameter “labe 卜 transfer2” refers to the element “japanese” of the host library. The AVC component for table display 301 0 refers to this property information and displays the values by substituting the values of “english” and “japa nesej” of the host platform in each column of the table. Any document data can be passed to a processing system having general-purpose functions such as the AVC component 3010 for table display and processed.

FIG. 38 shows the procedure of the document processing method according to the present embodiment. When the user instructs the insertion of the view provided by the A VC component (S 1 0), the host platform implementation is instructed by the source DOM to specify the AVC property template of the AVC component that is instructed to insert. In the position (S 1 2). This function may be handled by the main control unit 22 of the document processing apparatus 20 or the AVC control unit 3000. An instruction to insert an AVC component may be accepted when a menu or command is selected, or an AVC component may be accepted when an icon indicating the AVC component is dropped at the insertion position on the document display screen. You may accept a component insertion instruction. By referring to the schema of the host platform, it is determined whether or not the AVC property can be inserted at the indicated position. If the AVC property is against the schema, the insertion may not be accepted.

[0231] When the source DOM is changed, a mutation event is issued by the DOM unit 30 (S 14), and the processing system of the host library that receives the mutation event redisplays the document (S 1 6). At this time, since the inserted AVC property is described in a platform that cannot be processed by the processing system of the host platform, the processing system of the host platform requests the main control unit 22 to delegate the processing. The main control unit 22 selects an AVC component as a processing system capable of processing the AVC property and instructs the processing (S 18). In the example shown in FIG. 37, since the A VC property 3012 is described by the A VC library “tbl”, the A VC component 3010 for table display is selected. The delegated A VC component processes and displays the A VC property, but here the template is inserted and the property value entity is not set, so the AVC component In order to set the A VC property, the A VC property setting section 3002 is called (S20).

[0232] The AVC property setting unit 3002 requests the AVC component to present a dialog screen for accepting the setting of the AVC property (S22). This dialog screen is prepared as a library where A VC components can be used in common, and the A VC component generates a dialog screen that displays the property information that needs to be set and presents it to the user (S twenty four) . In this dialog screen, for example, property information to be set List, screen preview displayed, and data that can be referenced by the AVC component, that is, a list of elements and attributes included in the document may be presented. The user can select the element to be set in the table column, row, label, etc. from the list of elements included in the document, and drag and drop it on the property information list screen so that the correspondence can be set. It may be.

[0233] When the user sets the property information using the dialog screen (S 26), the AVC component accepts the property setting information, and the node corresponding to the AVC property inserted in the source D OM Write the set property value (S28). When the source DOM is changed, a mutation event is issued by the DOM unit 30 (S 30), and the AVC component itself, which is the AVC property processing system, receives the mutation event and processes the AVC property ( S 32). In this way, using the information set in the AVC property, the function of the AVC component is expressed and the display desired by the user is made (S34). Figure 39 shows an example of the displayed screen.

[0234] When the XML document with the A VC property inserted is opened, the screen shown in Fig. 39 is displayed in the same way as described below. First, the main control unit 22 dispatches the processing system to the root element, and processes the host library. Since the processing system of the host pouch library cannot process the inserted AV C vocabulary, a pane is assigned to the part described in the AV C vocabulary, and the processing is transferred to another processing system. The main control unit 22 selects the A VC component as the processing system of the A VC library, and the selected AVC component generates a view with reference to the AVC property. In this way, the display screen shown in FIG. 39 is obtained.

[0235] (Third embodiment)

In the second embodiment, the AVC property is inserted into the XML document, and the AVC component is activated as the AVC property processing system to express the AVC function. In this embodiment, the A VC property is inserted into the XML document. Without explaining the technology to develop A VC function.

FIG. 40 shows the configuration of the document processing apparatus according to the present embodiment. In addition to the configuration of the document processing apparatus 100 of the second embodiment shown in FIG. 36, the document processing apparatus 100 of the present embodiment includes an AVC property setting unit 3002 and an AVC property generation unit 3004 and a definition file. A generation unit 3006 is further included. Other configurations and operations are the same as those of the second embodiment.

[0237] When the A VC property setting unit 3002 receives the property information setting necessary for the operation of the A VC component from the user, the AVC property generation unit 3004 displays the AVC property in the source document as shown in Fig. 37. Instead of importing 3012, an AVC property file containing AVC properties 3012 is generated as a separate file from the source document. The definition file generation unit 3006 generates a module for reading the A VC property file. Here, a script-based definition file using the VC function is generated.

FIG. 41 shows the procedure of the document processing method according to the present embodiment. The user switches the processing system of the entire document or a zone from the first processing system that processes the tag set to which the zone component belongs to the A VC component that is an example of the second processing system. When instructed (S 50), the AVC property setting unit 3 002 obtains a list of A VC components that are registered and available in the document processing apparatus 100 and presents them to the user. Accepts selection of VC components (S 52). A VC property setting unit 30 02 When receiving the selection of the A VC component to be used (S54), the A VC property generation unit 3004 selects the necessary parameter / parameter settings for the operation of the AVC component. Instantiate the AVC property of the selected AVC component 卜 (S 56), and request the AVC component to present the setting dialog screen (S 58). The requested A VC component generates a setting dialog using the common library and presents it to the user (S 60). [0239] When the user sets property information using the dialog screen (S62), the A VC property generation unit 3004 generates an A VC property file. Here, the A VC component requests the definition file generation unit 3006 to present the definition file registration dialog screen (S 64). The definition file generation unit 3006 queries the user for the registration name of the definition file (S 66) and receives the definition file name from the user (S 68). A definition file to be called as a processing system is generated and registered so that the document processing apparatus 100 can be used (S 70). This definition file includes an instruction for reading an A VC property file and an instruction for delegating the processing of the read A VC property to another appropriate processing system, that is, an A VC component.

[0240] When the creation of the AVC property file and the definition file are completed, the AVC property setting unit 3002 switches the processing system to the created definition file (S72). With this definition file, the AVC property file is read and the process is delegated to the AVC component. The AVC component to which the process has been delegated refers to the AVC property file that stores information for identifying the data to be used, and identifies the data to be used by the AVC component from the data contained in the document. The specified data is expressed using the identified data, and a view is generated and displayed (S74). In this way, using the information set in the AV property, the function of the AV component is developed, and the display desired by the user is made.

[0241] With this technology, the AVC function can be realized without inserting property information into the source document. Therefore, it is possible to add a new view using the AVC function while maintaining the validation of the source document, regardless of the platform describing the source document. Also, by saving the generated definition file and applying it to another document, you can reuse the definition file and use the AV function for multiple documents.

[0242] In the source document, describe the instruction to specify the processing system to be applied as PI. You may do it. This allows you to specify a processing system without affecting the validation of the document. A PI that specifies the processing system may be described for each zone where the processing system switches. When assigning a processing system to an Apex element, the main control unit 22 assigns the processing system preferentially if a PI that specifies the processing system is described. If this function is used, the AVC component can be assigned preferentially and the AVC function can be expressed by specifying the definition file generated to call the AVC function as PI.

[0243] (Fourth embodiment)

FIG. 42 shows a configuration of the document processing apparatus according to the present embodiment. The document processing apparatus 100 according to the present embodiment further includes an AVC component switching unit 3050 in addition to the configuration of the document processing apparatus 100 according to the second embodiment shown in FIG. The A VC component switching unit 3050 accepts from the user whether the A VC component applied to the document is to be switched to a plurality of A VC components 301 0 to 3040, and selects the selected AVC component. Apply the nent to the document. As a result, the user can switch and apply a plurality of AVC components to the same document, and can process the document in a multifaceted manner using AVC components having various functions. Other configurations and operations are the same as those of the second embodiment.

FIG. 43 shows an example of a document in which the AVC property of the AVC component 3010 for table display is inserted. This XML document is an anchor for starting up the AVC component 301 0 for table display and the data described in the “ns1” poker library for describing computer specifications under the “b odyj” element of the XHTML document. And an AVC property 3012 including parameters necessary for processing the data described in the “ns1” in the AVC component 3010 for table display. The child element “pc” of the root element “root” of the library “ns1” is provided multiple times, and each sets the clock frequency of the CPU installed in the computer. It contains an element “cpu” for storing, an element “memory” for storing the memory capacity, an element “hdd” for storing the capacity of the hard disk drive (HDD), and an element “price” for storing the price. The element 3025 is described in “avc-datagrid”, which is a library in which the table display AVC component 3 100 is responsible for starting up the table display AVC component 3010. The root element “datagrid” of this Pocabulary has as its attributes information indicating the name of the AVC component, the version number, and whether to open the dialog at startup. The AVC property 3012 is omitted in FIG. 43, and details are shown in FIG. 44 and FIG.

FIG. 44 shows the contents of the AV property 3012 described in the document shown in FIG. The AVC property 301 2 includes the property information referenced by the AVC component for table display, that the repeated element is “/ html / body / p / root / pcj”, the display / non-display of the header line, and the line number column. Display / hide, display area width, display area height, summary row display / hide, summary row display format, summary row digit separator, summary row decimal display digits, summary column display Describes / display, summary column display format, column separator for summary column, number of decimal places displayed for summary column, and summary column width.

FIG. 45 shows the contents of the AV property 3012 described in the document shown in FIG. The element “column” in the “avc_datagr id” of the poch library “cpu” is a subordinate element of “/ html / body / p / root / pc” in which the column node is specified as a repeated element as property information about the table column. Text node, column heading, data type, maximum number of characters when the data type is "string", display format when the data type is "numeric", thousands separator, decimal number of digits, Contains elements that describe the date / time format, column width, and type mismatch display / non-display when the data type is “date / time”. Property information is described in the same way for the other columns.

FIG. 46 shows an example of a screen on which the document shown in FIG. 43 is displayed. Tape started as a processing module for element 3025 described in the document shown in Figure 43 The AVC component 3010 for displaying the data refers to the AVC property 3012, and displays the data related to the computer specifications described in the document in a table. In FIG. 45, the property information for storing the column headings is described as <avc: property name = "ti 11 e type =" ti 11 e checked = false inher itab le = "true"/> The heading is not set and it is an empty element. At this time, the AVC component for table display 3010 displays the element name of the element designated as data in this column as a heading. Therefore, in Figure 46, the element name “cpu” of the element specified as the data of that column is displayed as the heading of the second column of the table.

[0248] Figure 47 shows the menu that appears when the mouse is right-clicked in the region of the view generated by the A VC component. Here, when the user selects “setting”, a dialog screen for setting the A VC property 3012 to which the A VC property setting section 3002 force table display A VC component 3010 refers is displayed. When “Switch” is selected, the AVC component switching section displays a dialog screen for switching 3050 AVC components.

FIG. 48 shows an example of a dialog screen displayed by the A VC component switching unit 3050. The AVC component switching unit 3050 acquires and displays a list of AVC components that can be used by the document processing apparatus 100, and accepts selection of the switching destination AVC component from the user. When AVC components are newly installed in the document processing device 100, the number of AVC components to be switched to can be increased. Here, it is assumed that the chart display A VC component 3020 to be displayed in the form of a scatter diagram is selected.

[0250] When the AVC component switching unit 3050 receives the AVC component of the switching destination, as will be described later, the element 3025 serving as an anchor for starting the AVC component in the source DOM is replaced with the original AVC component. The vocabulary element that can be processed by the element is rewritten to the vocabulary element that can be processed by the AVC component at the switching destination. Rewriting the source DOM The change is notified to the processing system by the mutation event. At this time, as the processing system of the newly rewritten element 30 25, the AVC component of the switching destination, here for the chart display AVC component 3 0 2 0 is activated. The activated chart display AVC component 3 0 2 0 calls the AVC property setting unit 3 0 0 2 in order to accept the setting of the AVC property.

[0251] Fig. 49 shows an example of the A V C property setting screen displayed by the A V C property setting section 3 0 0 2. Figure 49 shows the screen for setting scatter plot data. In the scatter chart, in addition to the X and Y axes, series and element labels can be specified. Here, it is not meaningful to display only one point on the scatter plot. Therefore, it is possible to specify a repeated element and specify the data contained in that element as the X-axis, Y-axis, series, and element label.

[0252] At this time, the repetition element was specified as "/ htm l / body / p / root / pcj" in the AVC component for table display 3 0 10 which is the AVC component before switching. Inheriting this setting, the same element is automatically set as a repeated element.In the AVC component for table display 3 0 1 0, "cpu", "memoryj," specified as column data By default, the text nodes of “hdd” and “pr i ce” are automatically set as X axis, γ axis, series, and element label data. As a result, even if the AV component is switched, the same property information is automatically inherited, thereby reducing the user's setting effort. To change the data specification, simply select the data from the document elements on the left-hand side, and click “Settings” or drag and drop. A preview of the display screen is displayed in the lower right.

FIG. 50 shows an example of the AVC property setting screen displayed by the AVC property setting unit 300. Figure 50 shows the screen for setting the option of the data specified as the X-axis. The data specified as the X-axis is found, and the data type, display item, and data type are “string”. The maximum number of characters, if any The display / hide of invalid data can be set. The same applies to the Y axis. “String” is selected by default as the data type, but “numeric” and “date / time” can be specified if the data is numeric. When the data type is “character string”, the same character string is grouped and an icon is displayed on the scatter plot. If the data type is “number” or “date and time”, the scatter plot is displayed with the axis as a number line. Here, the element “cpu” is specified as a character string on the X axis and the element “memory” is specified as a character string on the Y axis, so the text node of the element “cpu” is “2.2 ghz on the X axis. ”,“ 2.8 ghz ”,“ 3.0 ghz ”, and the Y-axis displays the icons with the text node of the element“ memory ”classified into“ 512 mbj ”and“ 1 gbj ”. .

FIG. 5 1 shows an example of an AVC property setting screen displayed by the AV property setting section 3 0 0 2. Figure 5 1 shows the screen for setting the option of data specified as a series. The maximum data when the data type, display item, and data type of the data specified as a series is "string" The number of characters and legend display / non-display can be set. On the scatter chart, different icons are displayed for the same character string, numerical value, or date / time. Here, since the element “hdd” is specified as a character string in the series, three types of icons are displayed for each character string of the text node of the element “hdd”.

FIG. 5 2 shows an example of the A V C property setting screen displayed by the A V C property setting unit 3 0 0 2. Figure 52 shows the screen for setting the options for the data specified as the element label, and the maximum number of characters for the data specified as the element label can be set. On the scatter diagram, the specified data is displayed as a label near the icon. Here, since the text node of the element “pr i ce” is specified as the element label, the element “pr i cej” included in the element “pc” is located near each icon corresponding to the element “pc”. The text node string is displayed as a label.

FIG. 53 shows an example of an AVC property setting screen displayed by the AVC property setting unit 3 0 2. Figure 5 3 shows the property information in the scatter plot display area. The screen for setting the information is shown, and the width and height of the display area can be set.

FIG. 54 shows an example of the display screen when switching to the AVC component 3020 for chart display. In FIG. 46, the table display A VC component 3010 was applied and the data in the document was displayed in a table. However, the same data can be obtained by switching to the chart display A VC component 3020. Displayed as a scatter plot. In this way, multiple AVC components can be switched and applied to the same document, so that various general-purpose functions can be used to process the document in multiple ways. You can.

FIG. 55 shows how the document shown in FIG. 43 is changed by switching the AV component. As described above, when the AVC component switching unit 3050 switches AVC components, the table display AVC component 301 0 processes the element 3025 that is an anchor to activate the AVC components. The element of “avc_datagr i dj”, which is a possible vocabulary, is rewritten to the element of “avc-xychart”, which is a library that can be processed by the AVC component for chart display 3020.

FIG. 56 shows the contents of the AVC property 3012 described in the document shown in FIG. The AVC property 301 2 includes the property information referenced by the chart display AVC component 3020. The repeated element is “/ html / body / p / root / pcj”, the width of the display area, and the display area width. This property information is the same as that described in the AVC property 301 2 of the AVC component for table display shown in Fig. 44-component 301 0, and describes the A VC property. In this way, by describing the AVC property 3 01 2 using a common schema, one AVC component can be written once for a document. If the AVC property 301 2 is set by applying the Nent, the setting is inherited between the AVC components when the AVC component is switched. It is possible to reduce the trouble of user setting. It is also possible to generate a view with AVC components applied semi-automatically. When developing a new AVC component, make it operate by referring to the AVC property 3 0 1 2 using a common schema so that settings common to other AVC components can be inherited. It is desirable.

FIG. 5 7 shows the contents of the AV property 3 0 1 2 described in the document shown in FIG. The element “ax is” of the Poch Library “avc-xychart” is the property information related to the X-axis, and the axis data is specified as a repeated element. “Chtm” The subordinate element “cpu” ”Text node, axis heading, data type, minimum value when data type is“ number ”, maximum value, major tick width, minor tick width, minimum when data type is“ datetime ” Value, maximum value, major scale width, minor scale width, how to handle date-only data, display items when data type is `` character string '', maximum number of characters, display / hide of invalid data are described Includes elements. Property information is also described for the Y axis.

[0261] FIG. 5 8 shows the contents of the AV property 3 0 1 2 described in the document shown in FIG. The element “ser i es” of the pav library “avc-xychart” is subordinate to “/ htm l / body / p / root / pc”, where the data of the series is specified as a repeated element as property information about the series. It is a text node of element “hdd”, data type, minimum value, maximum value, scale width when data type is “numeric”, minimum value, maximum value, scale when data type is “datetime” Includes elements that describe the width, how to handle date-only data, display items when the data type is "string", the maximum number of characters, and display / non-display of the legend.

[0262] Figure 59 shows the contents of the AV property 3 0 1 2 described in the document shown in Figure 55. The element “object l abe l” of the pavobbler “avc_xychart” is a subordinate element of “/ htm l / body / p / root / pc” in which the element label data is specified as a repeated element as property information about the element label. It is a text node of “pr i ce” and includes an element describing the maximum number of characters.

[0263] Figure 60 is a screen for setting the scatter plot data shown in Figure 49. The screen when the Y-axis data is changed is shown. When the text node of element “pr i ce” is dragged and dropped onto the Y-axis data area, the text node of element “pr i ce” is newly designated as the Y-axis data. In the lower right corner of the screen, a preview of the scatter plot with the Y axis changed to “pri cej” is displayed. In this way, the AVC component for chart display 3 0 2 0 is an arbitrary element that exists repeatedly in the document. Scatter plots can be created by setting element data as axes.

[0264] Figure 61 shows the screen when the data type of the Y-axis data is changed. The text node of the element “p r i cej” stores the price of the computer as a numeric value, so a data type of “numeric value” is allowed in addition to “string”. So, if you change the data type of the Y-axis to “Numeric” and set the minimum value to “0”, the Y-axis will change to a number line starting from 0 as shown in the lower right of the screen. The price of each computer is plotted on a straight line.

[0265] In this way, different views can be given to the same document by allowing the user to specify the data type. For example, in both the table display AVC component 3 0 1 0 and the chart display AVC component 3 0 2 0, sorting depends on whether the data is handled as a character string or a numeric value. And mapping results change. By enabling the user to specify the data type, flexible and highly versatile functions can be provided. In addition, users can give their own data types for data written in a pokary that is not a pakary that they have created. Even if there is a schema such as DTD or XMLSShema in the poker library, different data types can be given on the AVC component, and the data can be processed flexibly.

[0266] The present invention has been described based on the embodiments. This embodiment is an exemplification, and it is understood by those skilled in the art that various modifications can be made to combinations of the respective constituent elements and processing processes, and such modifications are also within the scope of the present invention. It is where

[0267] In the embodiment, an example of processing an XML document has been described. The document processing apparatus 10 0 in the form can similarly process documents described in other markup languages such as SGML and HTML.

Industrial applicability

The present invention can be used for a document processing apparatus that processes data structured in a markup language.

Claims

The scope of the claims

[1] Multiple processing modules that can be used as general-purpose parts for processing the data in a document and expressing a predetermined function;

A switching unit capable of switching and applying a plurality of different processing modules to the same data;

A document processing apparatus comprising:

[2] The document is described in a markup language and includes a tag set component that can be processed by the processing module.

2. The document processing apparatus according to claim 1, wherein in order to process the component, the processing module capable of processing a tag set to which the component belongs is activated.

[3] The switching unit, when switching the processing module, the configuration of the tag set that can be processed by the switching destination processing module from the component of the tag set that can be processed by the processing module of the switching source 3. The document processing device according to claim 2, wherein the document processing device is rewritten as an element.

[4] A property setting unit for receiving parameter settings necessary for the operation of the processing module is further provided.

The document processing apparatus according to claim 2 or 3, wherein the property setting unit describes the received parameter in the document as an element value or an attribute value of the component or a descendant component. .

[5] When the property setting unit switches the processing module, the property setting unit switches the setting of the parameter used in common between the switching source processing module and the switching destination processing module from the switching source processing module. 5. The document processing apparatus according to claim 4, wherein the document processing apparatus is automatically set by being inherited by a previous processing module.

6. The document processing apparatus according to claim 4 or 5, wherein the property setting unit receives a setting of a data type in the document processed by the processing module.

[7] The property setting unit receives a setting of text data to be displayed as a label of the data when the processing module displays the data in the document on the screen, and the text to be displayed as the label of the data. 7. The document processing device according to claim 4, wherein when data is not set by a user, an element name of the data is set as a label.

[8] applying any one of a plurality of processing modules that can be used as general-purpose components for processing the data in the document to express a predetermined function to the data in the document;

Switching and applying another processing module to data in the same document;

A document processing method comprising:

[9] A plurality of processing modules that can be used as general-purpose parts for processing the data in a document and expressing a predetermined function;

A function of switching and applying a plurality of different processing modules to the same data;

A program that causes a computer to execute.