WO2005098660A9 - 文書処理装置及び文書処理方法 - Google Patents
文書処理装置及び文書処理方法Info
- Publication number
- WO2005098660A9 WO2005098660A9 PCT/JP2005/006798 JP2005006798W WO2005098660A9 WO 2005098660 A9 WO2005098660 A9 WO 2005098660A9 JP 2005006798 W JP2005006798 W JP 2005006798W WO 2005098660 A9 WO2005098660 A9 WO 2005098660A9
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- document
- data
- unit
- calculation
- calculation formula
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/103—Formatting, i.e. changing of presentation of documents
- G06F40/106—Display of layout of documents; Previewing
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/14—Tree-structured documents
- G06F40/143—Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
Definitions
- the present invention relates to a document processing technique, and more particularly to a document processing apparatus and a document processing method for processing a document described in a markup language.
- XML is attracting attention as a format suitable for sharing data with others via a network, and applications for creating, displaying, and editing XML documents have been developed (for example, (See Patent Document 1).
- An XML document is created based on a vocabulary (tag set) defined by a document type definition or the like.
- Patent Document 1 Japanese Patent Laid-Open No. 2001-290804
- the present invention has been made in view of these circumstances, and an object thereof is to provide a technique for effectively using data included in a document described in a markup language.
- One embodiment of the present invention relates to a document processing apparatus.
- This document processing apparatus displays a document described in a markup language, and a processing system for accepting editing of the document by a user, and an element value or attribute value of a component included in the document includes other values.
- a calculation unit that, when described by a calculation formula that refers to data, obtains reference data, executes the calculation formula, and assigns the calculation result to the element value or the attribute value. It is characterized by.
- the markup language may be XML-opened, for example, XML, SVG, MathML, or the like, SGML, HTML, or the like.
- the reference destination data may be described in a markup language different from that of the reference source component.
- the calculation formula may be described in a markup language for describing the calculation formula.
- the calculation unit may be provided as a plug-in that interprets and processes a dedicated markup language for describing the calculation formula.
- the calculation formula may be described in a definition file that is externally referenced from the document.
- the calculation unit may re-execute the calculation formula and assign the calculation result to the element value or the attribute value.
- the processing system may update the display after a new calculation result is assigned. As a result, the data of the reference source can be appropriately updated and reflected in the display in real time.
- the document processing apparatus further includes a generation unit that generates data in a format that conforms to a document object model defined to provide an access method for handling a document as data from the document,
- the unit may generate document object model data corresponding to the document, and the processing system may display the document by referring to the document object model data.
- the calculation unit may specify and acquire the reference destination data from the document object model data. Even documents written in multiple different markup languages can be accessed using the same access method by converting them to document object model data, so the calculation unit can easily identify the reference data. Can be obtained.
- Another aspect of the present invention relates to a document processing method.
- this document processing method when a document described in a markup language is displayed on a display device, the element value or attribute value of a component included in the document is described by a calculation formula that refers to other data. Determining whether or not, and when the element value or the attribute value is described by the calculation formula, obtain the reference destination data, execute the calculation formula, and calculate the calculation result And substituting in the element value or the attribute value.
- FIG. 1 is a diagram showing a configuration of a document processing apparatus according to a first embodiment of the present invention.
- FIG. 2 is a diagram illustrating an example of an XML document processed by the document processing apparatus according to the first embodiment.
- 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 is a diagram showing an example of a VC 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 HTML according 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 VC definition file generation unit.
- FIG. 7 is a diagram showing another example of the screen layout generated by the VC 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 processed by the document processing apparatus according to the first embodiment.
- FIG. 10 is a diagram showing an example of a screen displaying the document shown in FIG.
- FIG. 11 is a diagram showing a configuration of a document processing apparatus according to a second embodiment of the present invention.
- FIG. 12 is a diagram showing an example of a document processed by the document processing apparatus shown in FIG.
- FIG. 13 is a diagram showing an example of a VC definition file for displaying the XML document shown in FIG. 12 by the VC function.
- FIG. 14 is a diagram showing an example of a display template described in the VC definition file shown in FIG. 13.
- FIG. 15 A diagram showing an example of a template for displaying a component storing details of a travel expense route among the display templates described in the VC definition file shown in FIG. is there.
- FIG. 16 is a diagram showing an example of a calculation definition file applied to the XML document shown in FIG.
- FIG. 17 is a diagram showing an example of a screen in which the document shown in FIG. 12 is displayed according to the VC definition file shown in FIGS. 13 to 15.
- FIG. 18 A diagram showing an example of the screen when the employee number is changed in the editing screen shown in FIG.
- FIG. 19 is a diagram showing an example of the screen when a detailed business trip item is added and the amount of travel expenses is changed on the editing screen shown in FIG.
- FIG. 20 is a diagram showing another example of a document processed by the document processing apparatus according to the second embodiment.
- FIG. 21 is a diagram showing an example of a VC definition file for displaying the XML document shown in FIG. 20 using the VC function.
- FIG. 22 is a diagram showing an example of a screen in which the document shown in FIG. 20 is displayed according to the VC definition file shown in FIG.
- FIG. 23 is a diagram showing an example of a screen when a sample value is changed in the editing screen shown in FIG.
- 100 document processing device 110 main control unit, 120 editing unit, 130 DOM unit, 132 DOM providing unit, 134 DOM generation unit, 136 output unit, 140 CSS unit, 150 HTML unit, 160 SVG unit, 180 VC unit, 182 Mapping ⁇ ⁇ 184 VC definition file acquisition unit, 186 VC definition file generation unit, 190 calculation unit, 192 calculation definition file acquisition unit, 194 execution unit.
- FIG. 1 shows a configuration of a document processing apparatus 100 according to the first embodiment of the present invention.
- the document processing apparatus 100 processes a structure document in which data in the document is classified into a plurality of components having a hierarchical structure.
- an example of processing an XML document as an example of a structure document is described. Will be described.
- the document processing apparatus 100 includes a main control unit 110, an editing unit 120, a DOM unit 130, a CSS unit 140, an HTML unit 150, an SVG mute 160, and a VC unit 180 which is an example of a conversion unit.
- these configurations are the power that can be realized by the CPU, memory, and programs loaded in the memory of any computer.
- functional blocks that are realized by their cooperation are depicted. Therefore, those skilled in the art will understand that these functional blocks can be realized in various forms by hardware only, software only, or combinations thereof.
- the main control unit 110 provides a framework for loading plug-ins and executing commands.
- the editing unit 120 provides a framework for editing XML documents.
- the document display and editing functions in the document processing apparatus 100 are realized by plug-ins, and necessary plug-ins are loaded by the main control unit 110 or the editing unit 120 according to the type of document.
- the main control unit 110 or the editing unit 120 refers to the namespace of the XML document to be processed, determines which vocabulary the XML document is described in, and displays or displays corresponding to the vocabulary. Load the editing plug-in to display and edit.
- the document processing apparatus 100 has a display system and editing system plug-in for each vocabulary (tag set) such as an HTML unit 150 that displays and edits HTML documents and an SVG unit 160 that displays and edits SVG documents.
- the HTML unit 150 is loaded when editing an HTML document
- the SVG unit 160 is loaded when editing an SVG document.
- both the HTML unit 150 and the SVG unit 160 are loaded.
- the user can select and install only the necessary functions and add or delete functions as needed later, so that the recording medium such as a hard disk for storing the program can be used.
- Storage area can be used effectively and program execution Sometimes, memory waste can be prevented.
- it has excellent function expandability, and as a development entity, it is possible to cope with a new vocabulary in the form of a plug-in, making development easier, and as a user, it is easy and low by adding plug-ins. Additional functions can be added at cost.
- the editing unit 120 receives an event of an editing instruction through the user interface, notifies the event to an appropriate plug-in, etc., and re-executes the event (redo) or cancels the execution (undo). ) Etc. are controlled.
- the DOM unit 130 includes a DOM providing unit 132, a DOM generation unit 134, and an output unit 136.
- a document object model (Document Object Model) defined to provide an access method when handling an XML document as data. : Realize functions that conform to DOM).
- the DOM provider 132 is an DOM implementation that satisfies the interface defined in the editing unit 120.
- the DOM generation unit 134 generates a DOM tree from the XML document. As will be described later, when mapping to another vocabulary by the XML document power VC unit 180 to be processed, the source tree corresponding to the mapping source XML document and the destination corresponding to the mapping destination XML document A tree is generated.
- the output unit 136 outputs the DOM tree as an XML document at the end of editing, for example.
- the CSS unit 140 includes a CSS analysis unit 142, a CSS providing unit 144, and a rendering unit 146, and provides a display function compliant with CSS.
- the CSS analysis unit 142 has a function of a parser that analyzes CSS syntax.
- the CSS provider 144 is an implementation of CSS objects, and performs CSS cascade processing on the DOM tree.
- the rendering unit 146 is a CSS rendering engine, and is used to display a document described in a vocabulary such as HTML that is laid out using CSS.
- the HTML unit 150 displays or edits a document described in HTML.
- the SVG unit 160 displays or edits documents described in SVG. These display Z editing systems are realized in the form of plug-ins.
- the display unit (Canvas) 156 and 166 for displaying a document, and the control unit (Editlet) 152 and 16 for transmitting and receiving events including editing instructions, respectively. 2. Equipped with editing units (Zone) 154 and 164 that receive editing commands and edit the DOM.
- the unit 154 or 164 changes the DOM tree, and the display unit 156 or 166 updates the display.
- the document processing apparatus 100 enables editing in accordance with each vocabulary just by editing an XML document in a tree display format.
- HTML unit 150 provides a user interface for editing HTML documents in a manner similar to a word processor
- SVG unit 160 provides a user interface for editing SVG documents in a manner similar to an image drawing tool. Provide an interface.
- the VC unit 180 includes a mapping unit 182, a VC definition file acquisition unit 184, and a VC definition file generation unit 186.
- a mapping destination A framework for displaying or editing a document with a plug-in for display editing corresponding to the above-mentioned vocabulary is provided.
- this function is called Vocabulary Connection (VC).
- the VC definition file acquisition unit 184 acquires a script file describing the mapping definition.
- This VC definition file describes the correspondence (connection) between nodes for each node. At this time, whether or not the element value and attribute value of each node can be edited may be designated. You can also write arithmetic expressions using node element values and attribute values.
- the mapping unit 182 refers to the VC definition file acquired by the VC definition file acquisition unit 184, causes the DOM generation unit 134 to generate a destination tree, and manages the correspondence between the source tree and the destination tree.
- the VC definition file generation unit 186 provides a graphical user interface for the user to generate a VC definition file.
- the VC unit 180 monitors the connection between the source tree and the destination tree.
- the VC unit 180 receives an editing instruction from the user via the user interface provided by the plug-in responsible for display, the VC unit 180 starts with the source tree. Change the corresponding node. DO M unit 130 force
- the VC unit 180 receives the mutation event and changes the source tree. Change the node in the destination tree that corresponds to the changed node that synchronizes the destination tree. Displaying the destination tree z
- the plug-in to be edited such as the HTML unit 150, receives a mutation event indicating that the destination tree has been changed, and updates the display with reference to the changed destination tree. With such a configuration, even a document described in a local vocabulary used by a small number of users can be displayed by converting it to another major vocabulary, and the editing environment can be reduced. Provided.
- the DOM generation unit 134 When the document processing apparatus 100 reads a document to be processed, the DOM generation unit 134 generates a DOM tree from the XML document. In addition, the main control unit 110 or the editing unit 120 determines a vocabulary describing a document with reference to the name space. If a plug-in corresponding to the vocabulary is installed in the document processing apparatus 100, the plug-in is loaded and the document is displayed and edited. If the plug-in linker S is not installed, check whether the VC definition file for mapping exists.
- the VC definition file acquisition unit 184 acquires the VC definition file, generates the destination tree according to the definition, and displays the document with the plug-in corresponding to the mapping destination library. Edited. In the case of a compound document containing a plurality of vocabularies, as will be described later, corresponding portions of the document are displayed and edited by plug-ins corresponding to the respective vocabularies. If the VC definition file does not exist, the document source or tree structure 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 grade data.
- the component “score” that is the top node of the XML document has a plurality of component “students” provided for each student under the subordinate.
- 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.
- the constituent elements “National language”, “Mathematics”, “Science” and “Society” store the results of national language, mathematics, science and society, respectively.
- a student with the name “A” has a national language grade of “90”, a mathematics grade of “50”, a science grade of “75”, and a social grade of “60”. is there.
- the vocabulary (tag set) used in this document will be referred to as the “score management vocabulary”.
- the document processing apparatus 100 does not have a plug-in corresponding to the display management Z editing of the grade management vocabulary, in order to display this document by a method other than the source display and the tree display,
- the VC function described above is used.
- the user interface for creating the user's own power definition file will be described later.
- the VC definition file has already been prepared and will be described.
- FIG. 3 shows an example of mapping the XML document shown in FIG. 2 to a table described in HTML.
- the “Student” node of the Grade Management Library is associated with the row (“TR” node) of the 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 contains the element values of the “Mathematics” node
- the fourth column contains the element values of the “Science” node
- the fifth column “Society” Associate the element values of the node.
- the XML document shown in Fig. 2 can be displayed in an HTML table format.
- the sixth column specifies a formula that calculates the weighted average of national language, mathematics, science, and social performance, and displays the student's average score. In this way, by making it possible to specify an arithmetic expression in the VC definition file, more flexible display is possible, and user convenience during editing can be improved. Note that the sixth column specifies that editing is not possible, and that only the average score cannot be edited individually. In this way, by making it possible to specify whether or not editing can be performed in the mapping definition, it is possible to prevent an erroneous operation of the user.
- FIG. 4 shows an example of a VC definition file for mapping the XML document shown in FIG. 2 to the table shown in FIG.
- This VC definition file is described in the scribble language defined for the VC definition file.
- the VC definition file contains command definitions and display templates. In the example shown in Figure 4, the commands are “Add Student” and “Delete Student”. Each of these 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. Also as a template
- FIG. 5 shows an example of a screen displayed by mapping the XML document described in the grade management vocabulary shown in FIG. 2 to HTML according to the correspondence shown in FIG. From the left, each row in Table 200 displays the name of each student, national language grade, mathematics grade, science grade, social grade, and average score.
- the user can edit the XML document on this screen. For example, changing the value in the second row and third column to “70” changes the element value of the source tree corresponding to this node, that is, the math grade of student “B” to “70”.
- the VC unit 180 changes the corresponding part of the destination tree that makes the destination tree follow the source tree, and updates the display based on the changed destination tree of the HTML unit 150. Therefore, in the table on the screen, the math grade of student “B” is changed to “70”, and the average score is changed to “55”.
- the screen shown in FIG. 5 is displayed in the command power S menu of “add student” and “delete student”. User power S When these commands are selected, the node “Student” is added or deleted in the source tree.
- a single-structure editing function may be provided to the user in the form of a command.
- a command for adding or deleting a table row may be associated with an operation for adding or deleting the node “student”.
- a command for embedding other vocabulary may be provided to the user.
- this table as an input template, new student grade data can be added in the form of hole filling.
- VC unit 150 displays HTML unit 150 While using the editing function, it is possible to edit a document described in the Grade Management Box Library.
- FIG. 6 shows an example of a graphical user interface that the VC definition file generation unit 186 presents to the user in order for the user to generate a VC definition file.
- the mapping source XML document is displayed in a tree form.
- the area 204 on the right side of the screen shows the screen layout of the XML document to be mapped.
- This screen layout can be edited by the HTML unit 150, and the user creates a screen layout for displaying a document in an area 204 on the right side of the screen.
- mapping source XML document displayed in the area 202 on the left side of the screen into the HTML screen layout displayed in the area 204 on the right side of the screen.
- the connection between the mapping source node and the mapping destination node is specified. For example, if you drop “math”, which is a child element of the element “student”, into the first row and third column of table 200 on the HTML screen, it will be between the “math” node and the “TD” node in the third column A connection is established.
- Each node can be specified for editing.
- An arithmetic expression can also be embedded in the display screen.
- the VC definition file generation unit 186 generates a VC definition file describing the screen layout and the connections between nodes.
- FIG. 7 shows another example of the screen layout generated by the VC definition file generation unit 186.
- a table 200 and a pie chart 206 are created on the screen for displaying an XML document described in the grade management vocabulary.
- This pie chart 206 is described in SVG.
- the document processing apparatus 100 can process a compound document including a plurality of libraries in one XML document.
- the table 200 described in HTML and the pie chart 206 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 100.
- one screen is divided into multiple parts, and the XML document to be processed is displayed in different display formats in each area.
- the document source is displayed in area 210
- the tree structure of the document is displayed in area 212
- the table described in HTML shown in FIG. 5 is displayed in area 214.
- Documents can be edited on any of these screens.
- the source tree is changed, and the plug-in responsible for displaying each screen is changed to the source tree. Update the screen to reflect your changes.
- any plug-in or VC unit As a listener for the mutation event that notifies the source tree change, register the display section of the plug-in responsible for displaying each edit screen, and select V, any plug-in or VC unit.
- the source tree is changed by 180, all display sections displaying the edit screen receive the issued mutation event and update the screen.
- the VC unit 180 changes the destination tree following the change in the source tree, and then plugs the plug-in by referring to the changed destination tree. The in display updates the screen.
- the source display plug-in and the tree display plug-in directly refer to the source tree without using the destination tree. And display.
- the source display plug-in and the tree display plug-in update the screen with reference to the changed source tree and are in charge of the screen in the area 214.
- the HTML queue 150 updates the screen with reference to the changed destination tree following the change of the source tree.
- the source display and the tree display can also be realized by using the VC function. That is, the source and tree structure may be laid out in HTML, an XML document may be mapped to the HTML, and displayed by the HTML unit 150. In this case, three destination trees are generated: source format, tree format, and tabular format. Any screen When editing is done in VC unit 180, after changing the source tree, VC unit 180 changes each of the three destination trees: source format, tree format, and tabular format, and HTML unit 150 changes the destination tree. Browse and update the three screens
- the user can display and edit a document in a format that can be easily visually divided using the table 200 or the like while grasping the hierarchical structure of the document by the source display or the tree display.
- the ability to divide a screen and display a screen in multiple display formats at the same time may display a screen in one display format on a single screen, and the display format can be switched by a user instruction.
- the main control unit 110 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 100.
- the XHTML document is embedded in the “foreignObject” tag of the SVG document, and moreover, the mathematical expression described in MathML is included in the XHTML document.
- the editing unit 120 refers to the name space and distributes the drawing work to an appropriate display system.
- the editing unit 120 first causes the SVG unit 160 to draw a rectangle, and then causes the HTML unit 150 to draw an XHTML document.
- the MathML unit (not shown) is made to draw mathematical expressions.
- Figure 10 shows the display results.
- the plug-in or VC unit 180 responsible for the edited part changes the source tree. Mutation event listeners can be registered for each node in the source tree. Normally, the plug-in display or VC cut 180 corresponding to the vocabulary to which each node belongs is registered as a listener. Is done. When the source tree is changed, the DOM provider 132 traces from the changed node to a higher hierarchy, and if there is a registered listener, issues a mutation event to the listener.
- the HTML unit 150 updates the display with reference to the changed source tree.
- the SVG unit 160 may ignore the mutation event because the node belonging to its own vocabulary has changed.
- the layout may change as the display is updated by the HTML unit 150.
- the layout of the display area for each plug-in is updated by the configuration that manages the layout of the screen, for example, the plug-in responsible for displaying the top node.
- the HTML unit 150 first draws a part that it is in charge of and determines the size of the display area. Then, the configuration managing the screen layout is notified of the size of the display area after the change, and the layout is requested to be updated.
- 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.
- the displayed menu may be switched according to the position of the cursor (carriage). That is, when the cursor is in the area where the SVG document is displayed, the menu defined by the SVG unit 160 or the command defined in the VC 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 150 or the command defined in the VC definition file for mapping the XHTML document is displayed. Thereby, an appropriate user interface can be provided according to the editing position.
- a compound document has a VC definition file for an appropriate plug-in or mapping that corresponds to a certain library, the part described by that library is displayed in the source display or tree display. May be.
- the contents cannot be displayed unless the application that displays the embedded document is installed. Even if there is no display application, the contents can be grasped by displaying the XML document composed of text data as a source or tree. This is a text This is a unique feature of XML and other documents.
- a tag of another vocabulary may be used in a document described by a certain vocabulary. This XML document is not valid, but if it is well-formed (welH rmed), it can be processed as a valid XML document.
- the tag of another inserted library may be mapped by the VC definition file and processed by the VC unit 180. 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. Moyo.
- FIG. 11 shows the overall configuration of the document processing apparatus 100 according to the second embodiment of the present invention.
- the document processing apparatus 100 of the present embodiment is a calculation unit that is a plug-in that executes calculation processing with reference to other data in addition to the configuration of the document processing apparatus 100 of the first embodiment shown in FIG. 190 is further provided.
- the calculation unit 190 is a vocabulary for describing calculation formulas, etc. & 1 ( ⁇ 1 ⁇ processes documents described in the vocabulary.
- the calculation unit 190 is a component element included in a document to be processed. Value or attribute value, etc. When it is described by the calculation formula that refers to the data of, the data of the reference destination is acquired, the calculation formula is executed, and the calculation result is assigned to the element value or attribute value.
- the reference destination data may be described in the same library as that of the reference source, or may be described in a different library. Further, data described in another document may be referred to. When referring to data of another document, the document processing apparatus 100 may read the document in which the reference destination data is described and acquire the reference destination data. Other configurations and operations are the same as those in the first embodiment, and the same reference numerals are given to the same configurations.
- the calculation unit 190 includes a calculation definition file acquisition unit 192 that acquires a calculation definition file described in a calculation library, and an execution unit 194 that executes a calculation formula described in the calculation definition file. Including. When a document is read and it is described in the document that the calculation definition file should be externally referenced, the calculation definition file acquisition unit 192 acquires the calculation definition file and the execution unit 194 describes it. The calculated formula is executed and the calculation result is substituted. When the data referenced by the calculation formula is updated, the execution unit 194 receives a mutation event indicating that the node storing the reference destination data has been updated, and re-executes the calculation formula. Assign to the data of the reference source. When the data of the reference source is updated, the plug-in responsible for displaying the node updates the display, and the calculation result is reflected in the display.
- FIG. 12 shows an example of a document processed by the document processing apparatus 100 according to the present embodiment.
- This XML document is used to apply for travel expenses.
- This XML document is described by “ryohi”, which is a travel expenses settlement library, and “office”, which is a staff data management archive.
- ryohi which is a travel expenses settlement library
- office which is a staff data management archive.
- this document should be displayed by the VC function with reference to the VC definition file “ryohiseisan.vcdj” and that the calculation should be performed with reference to the calculation definition file “ryohiseisan.calcj”.
- the component “ryohiseisan”, which is the top node, is a component of the “ryohi” vocabulary. It has the components “period”, “place”, “business”, “items”, and “tota price”.
- the component “person” stores the applicant's data for travel expenses and stores “department-code”, which stores the department code to which the applicant belongs.
- “Department-namej”, which stores the department name of the applicant, “rank” which stores the rank of the applicant, “number” which stores the employee number of the applicant, “name” which stores the name of the applicant, and the applicant “Tel” for storing the telephone number of Component “persondb” is to store the data of the employees, as the attribute values of a plurality of components provided under the control of its "re C ord", employee number “number”, the name "name”, the telephone number "”tel” is stored.
- the component “period” stores the business trip period, and the start date force attribute value “end” stores the end date in the attribute value “start”.
- the component “place” stores a business trip destination.
- the component “business” stores the business trip requirements.
- the component “items” stores the details of the travel expenses, and the date “datetime” is used as the attribute value of multiple component “item” subordinates. “, Departure place“ route-stai: ”, arrival place“ route-end ”, type“ type ”, and amount“ price ”are stored.
- the component “tota ⁇ price” stores the total amount of business trip expenses. The total amount of travel expenses is calculated according to the formula described in the definition file for calculation, as will be described later.
- FIG. 13 shows an example of a VC definition file for displaying the XML document shown in FIG. 12 by the VC function.
- the VC definition file “ryohisaisan.vcd” contains command definitions and display templates.
- “add route” and “delete route” are defined as commands.
- the operation to insert the node “ryohi: item” into the source tree and the source tree power are also “node”
- the operation to delete “ryohi: item” is associated.
- the display template is actually described in the “conversion template” portion of the VC definition file shown in FIG. 13, but here it is divided into FIG. 14 and FIG.
- FIG. 14 shows an example of a display template described in the VC definition file shown in FIG.
- the XML document shown in FIG. 12 is converted into an HTML document and displayed according to the template shown in FIG. In the template, the part describing the display style is omitted.
- office: person / office: number that stores the employee number
- text-of indicating that editing is possible
- office: person / office: name that stores the employee's name is stored.
- the calculation unit 190 automatically changes the name and extension when the user changes the employee number, the name and extension cannot be edited.
- FIG. 15 is a template for displaying the component “ryohi: item” that stores the details of the travel expenses route among the display templates described in the VC definition file shown in FIG.
- An example of In the table displaying the details of the travel expenses an “add” button for adding a route and a “delete” button for deleting a route are displayed in each row displaying the route details.
- the “Add” button is associated with the command “Add route” in the VC definition file shown in FIG. 13, and the “Delete” button is associated with “Delete route”. The user clicks the button. As a result, the corresponding command is executed.
- FIG. 16 shows an example of a calculation definition file applied to the XML document shown in FIG.
- This calculation definition file is described in a vocabulary for describing calculation formulas.
- the first keynote ⁇ To “calc: Dind”, “ ⁇ ” “ryohi: ryohiseisan / office: person / office: name”, “ ⁇ de“ office: persondb ”'s younger brother“ office: number-th "Roh ⁇ ⁇ door ⁇ office: record ⁇ of values of" "that the na me" is substituted are described. That is, when the applicant's employee number is changed, the employee's name described in the employee list is assigned to the applicant's name.
- the second element “calc: bind” describes that when the applicant's employee number is changed, the employee's extension number is assigned to the applicant's extension number. ing.
- the third element “calc: bind” contains the node “
- ryohi ryohiseisan / ryohi: tota ⁇ pricej is assigned a sufficient value of “ ⁇ ” of “ryohi: item”. In other words, the total value of each detailed amount of business trip expenses is substituted into the total amount of business trip expenses.
- FIG. 17 shows an example of a screen that displays the document shown in FIG. 12 according to the VC definition file shown in FIGS. 13 to 15.
- the attribute values “route-start”, “route-end”, and “type” have no value, but according to the definition described in the VC definition file shown in Fig. 15, there is no substitute.
- the text is displayed.
- FIG. 18 shows an example of the screen when the employee number is changed in the editing screen shown in FIG.
- the user rewrites the applicant's employee number field from “1821” to “1318”
- the corresponding node in the source tree is first changed to “1318”.
- this node A mutation event indicating that the change has been made is issued to the calculation unit 190.
- the execution unit 194 of the calculation unit 190 changes the source tree according to the rules described in the calculation definition file.
- the applicant's name and extension are changed.
- a mutation event to that effect is issued to the VC unit 180, and the VC unit 180 changes the destination tree.
- a mutation event indicating that the destination tree has been changed is issued to the HTML unit 150, and the display is updated by the HTML unit 150.
- FIG. 19 shows an example of the screen when the detailed item of the business trip is added and the amount of the transportation expense is changed on the editing screen shown in FIG.
- the node “ryohi: item” is added to the source tree according to the definition of the command described in the VC definition file, and a detailed item line for the trip is added.
- the execution unit 194 of the calculation unit 190 updates the total amount of the travel expenses in accordance with the definition described in the calculation definition file. Then, the display is updated in the same manner as described above.
- FIG. 20 shows another example of a document processed by the document processing apparatus 100 of the present embodiment.
- This XML document is described by a vocabulary “sample” and a calculation vocabulary “calculation”.
- this document should be displayed by the VC function with reference to the VC definition file “embed.vcd” and that the calculation unit 190 should perform the calculation.
- the component “sample”, which is the top node, is a component of the “sample” vocabulary, and includes the component “value”, the component “value-tota ⁇ abs”, and the component “value” as child elements. -tota ⁇ ref ".
- the component “value” stores a value referred to in the calculation formula.
- the component rvalue-total-absj and the component “value—total—ref” store the total of the element values of the component “value”.
- the component “value-tota ⁇ abs” and “value-tota ⁇ ref” each contain the genus property value “cal expression.
- the calculation formula is calculated to calculate the total value, and the calculation result is stored as an element value.
- the attribute value “calc: expression” of the component “value-tota ⁇ abs” is the reference destination The node is described with an absolute path, and the attribute value “calc: expressionJ” of the component “value-tota ⁇ ref” is the force with which the referenced node is described with a relative path. : value ”is referred to, so the same total value is calculated.
- the attribute “calc: expression” is specified as a global attribute with a namespace prefix.
- a global attribute can be specified as an attribute that has the same meaning for any component of a library. That is, it functions as an attribute “expression” that expresses a calculation formula in the “b” library “calculation” for any component of the library.
- the value of the calculation formula described as the attribute value is calculated by the calculation unit 190 and substituted into the element value of the constituent element.
- FIG. 21 shows an example of a VC definition file for displaying the XML document shown in FIG. 20 using the VC function.
- the VC definition file “embed.vcd”, command definitions and display templates are described.
- “Delete node” and “Expression attribute deletion script” are defined as commands, and the source tree power is also set to node “
- sample sample / sample: value— The operation to delete “tota ⁇ abs” and the node “
- sample sample / sample: value— tota to absj x ⁇
- FIG. 22 shows an example of a screen in which the document shown in FIG. 20 is displayed according to the VC definition file shown in FIG. Calculated by the plug-in for calculation, the first component “sample: valuej element value“ 100 ”, the second component“ sample: value ”element value“ 200 ”, and the third component“ sample: The total value force of the element value “300” of “value” is calculated by the execution unit 194 of the calculation unit 190, and the components “sample: value-tota ⁇ abs” and “
- FIG. 23 shows an example of a screen when sample value 1 is changed in the editing screen shown in FIG.
- the user rewrites the column of sample value 1 from “100” to “500”
- the element value of the corresponding node “sample: sample / sample: value” in the source tree is changed to “500”.
- a mutation event indicating that this node has been changed is issued to the computation queue 190.
- the execution unit 194 of the calculation unit 190 receives the component “sample: sample / sample: value—tota ⁇ abs” and the component “ sample: sample / sample: value—
- the source tree is changed with the power expressed in the decant expression described in the attribute value of totaHrefJ.
- the total value of the sample values is changed.
- a mutation event to that effect is issued to the VC unit 180, and the VC unit 180 changes the destination tree.
- a mutation event indicating that the destination tree has been changed is issued to the HTML unit 150, and the display is updated by the HTML unit 150.
- the other Arbitrary data can be referenced.
- the calculation formula may be in an arbitrary format. For example, in order to synchronize data among a plurality of components, the calculation formula may substitute the same data, or may be an arithmetic formula or a character string. It may be an operation or the like.
- the document processing apparatus 100 is a document described in another markup language such as SGML or HTML. Can be processed similarly.
- the present invention can be used in a document processing apparatus that processes a document described in a markup language.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Document Processing Apparatus (AREA)
Abstract
Description
Claims
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP05728739A EP1744255A1 (en) | 2004-04-08 | 2005-04-06 | Document processing device and document processing method |
| JP2006512109A JPWO2005098660A1 (ja) | 2004-04-08 | 2005-04-06 | 文書処理装置及び文書処理方法 |
| US11/578,133 US20070198915A1 (en) | 2004-04-08 | 2005-04-06 | Document Processing Device And Document Processing Method |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| JP2004-114707 | 2004-04-08 | ||
| JP2004114707 | 2004-04-08 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| WO2005098660A1 WO2005098660A1 (ja) | 2005-10-20 |
| WO2005098660A9 true WO2005098660A9 (ja) | 2007-02-08 |
Family
ID=35125269
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/JP2005/006798 Ceased WO2005098660A1 (ja) | 2004-04-08 | 2005-04-06 | 文書処理装置及び文書処理方法 |
Country Status (5)
| Country | Link |
|---|---|
| US (1) | US20070198915A1 (ja) |
| EP (1) | EP1744255A1 (ja) |
| JP (1) | JPWO2005098660A1 (ja) |
| CN (1) | CN1977259A (ja) |
| WO (1) | WO2005098660A1 (ja) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPWO2005098658A1 (ja) * | 2004-04-08 | 2008-02-28 | 株式会社ジャストシステム | 文書処理装置及び文書処理方法 |
| JP2007293548A (ja) * | 2006-04-24 | 2007-11-08 | Canon Inc | 情報処理装置および情報処理方法 |
| US7865820B2 (en) * | 2006-08-29 | 2011-01-04 | Sap Ag | Generating a business document model |
| JP2008234370A (ja) * | 2007-03-21 | 2008-10-02 | Just Syst Corp | 文書処理装置及び文書処理方法 |
| US9396167B2 (en) | 2011-07-21 | 2016-07-19 | Flipboard, Inc. | Template-based page layout for hosted social magazines |
| US9529790B2 (en) | 2013-07-09 | 2016-12-27 | Flipboard, Inc. | Hierarchical page templates for content presentation in a digital magazine |
| CN105302445B (zh) * | 2015-11-12 | 2019-07-23 | 小米科技有限责任公司 | 图形用户界面绘制方法及装置 |
| US10452747B2 (en) | 2016-04-11 | 2019-10-22 | Microsoft Technology Licensing, Llc | Dynamically formatting scalable vector graphics |
Family Cites Families (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH10171785A (ja) * | 1996-12-09 | 1998-06-26 | Fuji Xerox Co Ltd | 文書作成装置 |
| JP3715777B2 (ja) * | 1998-03-02 | 2005-11-16 | 三菱電機株式会社 | 構造化文書編集方法及び構造化文書編集装置並びに構造化文書編集プログラムを記録した記録媒体 |
| WO2001095088A1 (en) * | 2000-06-05 | 2001-12-13 | Altoweb Systems, Inc. | Converting, and presenting the source document in a target format |
| JP2002215609A (ja) * | 2001-01-24 | 2002-08-02 | Toppan Printing Co Ltd | Bml文書自動作成プログラム、bml文書自動作成プログラムを記録した記録媒体、bml文書自動作成方法及びbml文書自動作成システム |
| GB0107784D0 (en) * | 2001-03-28 | 2001-05-16 | Hewlett Packard Co | Improvement relating to developing documents |
| JP3692054B2 (ja) * | 2001-05-21 | 2005-09-07 | 株式会社東芝 | 文書構造変換方法および文書構造変換装置およびプログラム |
| US20030018661A1 (en) * | 2001-07-19 | 2003-01-23 | Darugar Parand Tony | XML smart mapping system and method |
| JP2003067185A (ja) * | 2001-08-14 | 2003-03-07 | Internatl Business Mach Corp <Ibm> | アプリケーション編集装置、データ処理方法及びプログラム |
| US7171615B2 (en) * | 2002-03-26 | 2007-01-30 | Aatrix Software, Inc. | Method and apparatus for creating and filing forms |
| JP3857663B2 (ja) * | 2002-04-30 | 2006-12-13 | 株式会社東芝 | 構造化文書編集装置、構造化文書編集方法及びプログラム |
| US7228496B2 (en) * | 2002-07-09 | 2007-06-05 | Kabushiki Kaisha Toshiba | Document editing method, document editing system, server apparatus, and document editing program |
| US7069504B2 (en) * | 2002-09-19 | 2006-06-27 | International Business Machines Corporation | Conversion processing for XML to XML document transformation |
| US20040237040A1 (en) * | 2003-05-19 | 2004-11-25 | Malkin Wayne Allan | System and method of processing an electronic form using layered aspects |
| US7168035B1 (en) * | 2003-06-11 | 2007-01-23 | Microsoft Corporation | Building a view on markup language data through a set of components |
| US20040268229A1 (en) * | 2003-06-27 | 2004-12-30 | Microsoft Corporation | Markup language editing with an electronic form |
| JPWO2005098658A1 (ja) * | 2004-04-08 | 2008-02-28 | 株式会社ジャストシステム | 文書処理装置及び文書処理方法 |
-
2005
- 2005-04-06 US US11/578,133 patent/US20070198915A1/en not_active Abandoned
- 2005-04-06 EP EP05728739A patent/EP1744255A1/en not_active Withdrawn
- 2005-04-06 WO PCT/JP2005/006798 patent/WO2005098660A1/ja not_active Ceased
- 2005-04-06 JP JP2006512109A patent/JPWO2005098660A1/ja active Pending
- 2005-04-06 CN CNA2005800119359A patent/CN1977259A/zh not_active Withdrawn
Also Published As
| Publication number | Publication date |
|---|---|
| CN1977259A (zh) | 2007-06-06 |
| JPWO2005098660A1 (ja) | 2008-02-28 |
| WO2005098660A1 (ja) | 2005-10-20 |
| EP1744255A1 (en) | 2007-01-17 |
| US20070198915A1 (en) | 2007-08-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20100199167A1 (en) | Document processing apparatus | |
| US20100107048A1 (en) | Document processor and document processing method | |
| WO2006051715A1 (ja) | 文書処理装置及び文書処理方法 | |
| US20100100807A1 (en) | Data processing device, and data processing method | |
| WO2007081017A1 (ja) | 文書処理装置 | |
| WO2005098660A9 (ja) | 文書処理装置及び文書処理方法 | |
| WO2005098658A1 (ja) | 文書処理装置及び文書処理方法 | |
| US20080282143A1 (en) | Document Processing Device and Document Processing Method | |
| WO2006137563A1 (ja) | データ処理装置及びデータ処理方法 | |
| WO2006137562A1 (ja) | 文書処理装置及び文書処理方法 | |
| WO2006051869A1 (ja) | 文書処理装置及び文書処理方法 | |
| WO2005098662A1 (ja) | 文書処理装置及び文書処理方法 | |
| WO2006051974A1 (ja) | 文書処理装置および文書処理方法 | |
| WO2007052680A1 (ja) | 文書処理装置及び文書処理方法 | |
| WO2006001393A1 (ja) | 文書処理方法および装置 | |
| WO2006001392A1 (ja) | 文書処理方法および装置 | |
| JP4719743B2 (ja) | グラフ処理装置 | |
| WO2006001391A1 (ja) | 文書処理装置および文書処理方法 | |
| JP2008257277A (ja) | 文書処理装置、方法、及びプログラム | |
| WO2005098659A1 (ja) | 文書処理装置及び文書処理方法 | |
| JP2007183849A (ja) | 文書処理装置 | |
| WO2006118287A1 (ja) | 文書処理装置及び文書処理方法 | |
| JP2009110338A (ja) | 文書処理装置及び文書処理方法 | |
| JP2008225931A (ja) | 文書処理装置及び文書処理方法 | |
| JP2007004627A (ja) | 文書処理装置 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
| AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
| WWE | Wipo information: entry into national phase |
Ref document number: 2006512109 Country of ref document: JP |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 200580011935.9 Country of ref document: CN |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 11578133 Country of ref document: US Ref document number: 2007198915 Country of ref document: US |
|
| WWW | Wipo information: withdrawn in national office |
Ref document number: DE |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2005728739 Country of ref document: EP |
|
| WWP | Wipo information: published in national office |
Ref document number: 2005728739 Country of ref document: EP |
|
| WWP | Wipo information: published in national office |
Ref document number: 11578133 Country of ref document: US |