JP2009110338A - Document processing device and document processing method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a technology for appropriately processing a diagram. <P>SOLUTION: A diagram component 70 in a document processing device 100 comprises a processing part 72 providing a function of processing the diagram according to a notation of a diagram of specific classification, a core part 76 providing a function used in common irrespective of the classification of the diagram when processing the diagram, and a rule management part 74 determining the propriety of editing by the processing part 72 according to the notation of the diagram of specific classification. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a document processing technique, and more particularly to a document processing apparatus and method for processing a diagram.

XML is attracting attention as a format suitable for sharing data with others via a network or the like, and an application for creating, displaying, and editing an XML document has been developed (see, for example, Patent Document 1). ). The XML document is created based on a vocabulary (tag set) defined by a document type definition or the like.
JP 2001-290804 A

  The vocabulary is allowed to be arbitrarily defined, and in theory, there can be an unlimited number of vocabularies. The present applicant has developed a technique capable of appropriately processing an XML document that allows such a flexible design. Then, they came up with a highly convenient data processing technology that takes full advantage of XML.

  The present invention has been made in view of these circumstances, and an object thereof is to provide a technique for appropriately processing a document structured in a markup language.

  One embodiment of the present invention relates to a document processing apparatus. This document processing apparatus includes a processing unit that provides a function of processing the diagram according to a notation of a specific type of diagram, and a function that is commonly used regardless of the type of diagram when processing the diagram. A core unit to be provided, and a rule management unit that determines whether or not editing by the processing unit is permitted according to the notation method of the specific type of diagram.

  The processing unit, the core unit, and the rule management unit may be provided as independent modules, respectively, and the processing unit communicates with each of the core unit and the rule management unit. You may have.

  The processing unit may convert the diagram into data using a markup language for describing the diagram. A document processing apparatus reads a document describing a diagram, maps the document to data described in the markup language that can be processed by the processing unit, and manages a correspondence between mapping source data and mapping destination data May be further provided. If the coordinates of the figure included in the diagram are not described in the read document, the conversion unit reads the file describing the coordinates associated with the document, or sets the coordinates to a predetermined rule. Therefore, the coordinates may be acquired and mapped by automatically calculating.

  The processing unit may provide a grouping function for grouping a plurality of figures to be edited, and the grouping function is a grouping of figures indicating a connection relation between one figure and another figure. Even if it is selected, the figure may be excluded from the editing target.

  The processing unit may provide a function of selecting a graphic belonging to the frame as an editing target when the graphic that becomes the frame of the diagram is selected as the editing target.

  Another aspect of the present invention relates to a document processing method. This document processing method includes a processing unit that provides a function of processing the diagram according to a notation of a specific type of diagram, and a function that is commonly used regardless of the type of diagram when processing the diagram. The providing core unit causes the computer to execute a step of editing the diagram and a step of determining whether the processing unit is allowed to edit according to a notation of the specific type of diagram.

  It should be noted that any combination of the above-described constituent elements and a representation of the present invention converted between a method, an apparatus, a system, etc. are also effective as an aspect of the present invention.

  According to the present invention, it is possible to provide a technique for appropriately processing a diagram.

(Prerequisite technology)
FIG. 1 shows a configuration of a document processing apparatus 20 according to the base technology. The document processing apparatus 20 processes a structured document in which data in the document is classified into a plurality of components having a hierarchical structure. In the base technology, an example of processing an XML document as an example of a structured document will be described. . 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 which is an example of a conversion unit. In terms of hardware components, these configurations are realized by a CPU of a computer, a memory, a program loaded in the memory, and the like, but here, functional blocks realized by their cooperation are illustrated. Accordingly, 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.

  The main control unit 22 provides a framework for loading plug-ins and executing commands. The editing unit 24 provides a framework for editing the XML document. The document display and editing functions in the document processing apparatus 20 are realized by plug-ins, and necessary plug-ins are loaded by the main control unit 22 or the editing unit 24 according to the type of the document. The main control unit 22 or the editing unit 24 refers to the name space of the XML document to be processed, determines which vocabulary the XML document is described in, and a display or editing plug corresponding to the vocabulary Load the in to display and edit. For example, the document processing apparatus 20 has a display system and an editing system as plug-ins for each vocabulary (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. The HTML unit 50 is loaded when editing an HTML document, and the SVG unit 60 is loaded when editing an SVG document. As will be described later, when a compound document including both HTML and SVG components is to be processed, both the HTML unit 50 and the SVG unit 60 are loaded.

  According to such a configuration, the user can select and install only necessary functions, and can add or delete functions as appropriate later, so that the storage area of a recording medium such as a hard disk for storing the program is effective. In addition, it is possible to prevent the memory from being wasted when executing the program. In addition, it has excellent function extensibility, and as a development entity, it is possible to handle new vocabularies in the form of plug-ins, making development easier, and as a user, adding plug-ins makes it easy and low-cost. Functions can be added.

  The editing unit 24 receives an editing instruction event from the user via the user interface, notifies the event to an appropriate plug-in, and performs processing such as event re-execution (redo) or execution cancellation (undo). Control.

  The DOM unit 30 includes a DOM providing unit 32, a DOM generation unit 34, and an output unit 36, and is a document object model (DOM) defined for providing an access method when handling an XML document as data. Realize functions that comply with. The DOM providing unit 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, when the XML document to be processed is mapped to another vocabulary by the VC unit 80, the source tree corresponding to the mapping source XML document and the destination tree corresponding to the mapping destination XML document Is generated. The output unit 36 outputs the DOM tree as an XML document at the end of editing, for example.

  The CSS unit 40 includes a CSS 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 parser function of analyzing the CSS syntax. The CSS providing unit 44 is an implementation of a CSS object, and performs a CSS cascade process 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.

  The HTML unit 50 displays or edits a document described in HTML. The SVG unit 60 displays or edits a document described in SVG. These display / editing systems are realized in the form of plug-ins, and display units (Canvas) 56 and 66 for displaying documents, and control units (Editlet) 52 and 62 for transmitting and receiving events including editing instructions, respectively. Editing units (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 configuration similar to a framework called MVC (Model-View-Controller). In general, the display units 56 and 66 are “View”, the control units 52 and 62 are “Controller”, and the editing unit. The entities 54 and 64 and DOM correspond to “Model”, respectively. The document processing apparatus 20 of the base technology enables not only editing the XML document in a tree 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. To do.

  The VC unit 80 includes a mapping unit 82, a definition file acquisition unit 84, and a definition file generation unit 86. By mapping a document described in a certain vocabulary to another vocabulary, a display corresponding to the mapping destination vocabulary Provides a framework for displaying or editing a document with an editing plug-in. In the base technology, this function is called vocabulary connection (VC). The definition file acquisition unit 84 acquires a script file describing a mapping definition. This 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. 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 script 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.

  When 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, the VC unit 80 first selects the corresponding node of the source tree. change. When the DOM unit 30 issues a mutation event to the effect that the source tree has been changed, the VC unit 80 receives the mutation event, and the node changed to synchronize the destination tree with the change of the source tree. Change the destination tree node corresponding to. A plug-in for displaying / editing the destination tree, for example, the HTML unit 50, 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 an editing environment is provided. Is done.

  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 22 or the editing unit 24 determines the vocabulary describing the document with reference to the name space. If a plug-in corresponding to the vocabulary is installed in the document processing apparatus 20, the plug-in is loaded to display / edit the document. If the plug-in is not installed, check whether the mapping definition file exists. When 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 vocabulary. In the case of a compound document including a plurality of vocabularies, corresponding portions of the document are displayed / edited by plug-ins corresponding to the respective vocabularies, as will be described later. If the 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 performance data. The component “score” which 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 “Japanese language”, “Mathematics”, “Science”, and “Society” store the results of Japanese language, mathematics, science, and society, respectively. For example, a student whose name is “A” has a national language grade of “90”, a mathematics grade of “50”, a science grade of “75”, and a social grade of “60”. Hereinafter, the vocabulary (tag set) used in this document is referred to as a “results management vocabulary”.

  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, in order to display this document by a method other than source display and tree display, the VC function described above is used. Used. That is, it is necessary to prepare a definition file for mapping the grade management vocabulary to another vocabulary provided with a plug-in, such as HTML or SVG. A user interface for the user himself to create a definition file will be described later, and here, the description 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 of FIG. 3, the “student” node of the grade management vocabulary is associated with a row (“TR” node) of a table (“TABLE” node) in HTML, and an 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”. The node element values are associated with each other. Thereby, the XML document shown in FIG. 2 can be displayed in an HTML table format. These attribute values and element values are specified to be editable, and the user can edit these values using the editing function of the HTML unit 50 on the HTML display screen. In the sixth column, an arithmetic expression for calculating a weighted average of national language, mathematics, science and social results is designated, and the average score of the students' results is displayed. 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. Note that the sixth column specifies that editing is not possible, and only the average score cannot be edited individually. As described above, 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 by the user.

  4A and 4B 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 a script language defined for the definition file. In the definition file, command definitions and display templates are described. In the example of FIGS. 4A and 4B, “add student” and “delete student” are defined as commands, respectively, an operation of inserting a node “student” into the source tree, An operation for deleting the node “student” is associated. As a template, it is described that headings such as “name” and “national language” are displayed on the first line of the table, and the contents of the node “student” are displayed on and after the second line. In the template that displays the contents of the node "Student", the term described as "text-of" means "editable" and the term described as "value-of" is "not editable" It means that. In the sixth column of the row displaying the contents of the node “Student”, the formula “(src: Japanese + src: Mathematics + src: Science + src: Society) div 4” is described. , Which means that the average of the student's grades is displayed.

  FIG. 5 shows an example of a screen in which the XML document described in the grade management vocabulary shown in FIG. 2 is mapped and displayed in HTML according to the correspondence shown in FIG. In each row of Table 90, from the left, the name of each student, national language grade, mathematics grade, science grade, social grade, and average score are displayed. The user can edit the XML document on this screen. For example, when the value of the second row and third column is changed to “70”, the element value of the source tree corresponding to this node, that is, the math grade of the student “B” is changed to “70”. At this time, the VC unit 80 changes the corresponding part of the destination tree so that the destination tree follows the source tree, and the HTML unit 50 updates the display based on the changed destination tree. Therefore, also in the table on the screen, the mathematics score of the student “B” is changed to “70”, and the average score is changed to “55”.

  On the screen shown in FIG. 5, commands “add student” and “delete student” are displayed in the menu as defined in the definition file shown in FIGS. 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 edit not only the element value of the component at the end of the hierarchical structure but also the hierarchical structure. Such a tree structure editing function may be provided to the user in the form of a command. Further, for example, a command for adding or deleting a table row may be associated with an operation for adding or deleting the node “student”. In addition, a command for embedding another vocabulary may be provided to the user. Using this table as an input template, new student grade data can be added in the form of hole filling. As described above, the VC function makes it possible to edit a document described in the grade management vocabulary 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 presents to the user in order for the user to generate a definition file. In the area 91 on the left side of the screen, the XML document that is the mapping source is displayed as a tree. An area 92 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 50, and the user creates a screen layout for displaying a document in the area 92 on the right side of the screen. Then, for example, by using a pointing device such as a mouse, a node of the mapping source XML document displayed in the area 91 on the left side of the screen is dragged and dropped into the screen layout by HTML displayed in the area 92 on the right side of the screen. Thus, the connection between the mapping source node and the mapping destination node is designated. For example, when “mathematics” which is a child element of the element “student” is dropped on the first row and the third column of the table 90 of the HTML screen, the connection is made between the “math” node and the “TD” node in the third column. Is stretched. Each node can be designated for editing. An arithmetic expression can also be embedded in the display screen. When the editing of the screen is finished, the definition file generator 86 generates a definition file describing the screen layout and the connection between the nodes.

  Viewers and editors corresponding to major vocabularies such as XHTML, MathML, and SVG have already been developed, but viewers and editors corresponding to documents described in original vocabulary such as the document shown in FIG. 2 are developed. Is not realistic. However, if a definition file for mapping to other vocabularies is created as described above, the document described in the original vocabulary can be displayed using the VC function without developing a viewer or editor. Can be edited.

  FIG. 7 shows another example of the screen layout generated by the definition file generator 86. In the example of FIG. 7, a table 90 and a pie chart 93 are created on a screen for displaying an XML document described in the grade management vocabulary. This pie chart 93 is described in SVG. As will be described later, since the document processing apparatus 20 of the base technology can process a compound document including a plurality of vocabularies in one XML document, a table 90 described in HTML as in this example, and , A pie chart 93 written 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 parts, and XML documents to be processed are displayed in a plurality of different display formats in the respective areas. An area 94 displays the source of the document, an area 95 displays the tree structure of the document, and an area 96 displays a table described in HTML shown in FIG. . Documents can be edited on any of these screens. When the user edits 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. Specifically, as a listener for a mutation event that notifies a change in the source tree, a display unit of a plug-in responsible for displaying each editing screen is registered, and the source is generated by any plug-in or VC unit 80. When the tree is changed, all display units displaying the edit screen receive the issued mutation event and update the screen. At this time, if the plug-in is displaying by 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 to change the plug-in. The display unit updates the screen.

  For example, when the source display and 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 display the source tree. Do. In this case, when editing is performed on any of the screens, 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 of the region 96. The HTML unit 50 updates the screen by referring to the changed destination tree following the change of the source tree.

  The source display and tree display can also be realized using the VC function. In other words, the source and tree structure may be laid out in HTML, the XML document may be mapped to the HTML, and displayed by the HTML unit 50. In this case, three destination trees of a source format, a tree format, and a table format are generated. When editing is performed on any of the screens, the VC unit 80 changes the source tree, then changes each of the three destination trees in the source format, tree format, and table format, and the HTML unit 50 sets the destination tree. 3 screens are updated with reference to the nation tree.

  As described above, the convenience of the user can be improved by displaying the document in a plurality of display formats on one screen. For example, the user can display and edit the document in a visually easy-to-understand format using the table 90 or the like while grasping the hierarchical structure of the document by the source display or the tree display. In the above example, one screen is divided and screens in a plurality of display formats are simultaneously displayed. However, a screen in one display format may be displayed on one screen, and the display format may be switched according to a user instruction. . In this case, the main control unit 22 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 FIG. 9, the XHTML document is embedded in the “foreignObject” tag of the SVG document, and further, the mathematical formula described in MathML 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. Further, a mathematical expression is drawn in a MathML unit (not shown). Thus, a compound document including a plurality of vocabularies is appropriately displayed. The display result is shown in FIG.

  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 menu provided by the SVG unit 60 or the definition file for mapping the SVG document is displayed, and the cursor is displayed in the XHTML. When the document exists in the displayed area, a menu provided by the HTML unit 50 or a command defined in a definition file for mapping the XHTML document is displayed. Thereby, an appropriate user interface can be provided according to the editing position.

  If there is no appropriate plug-in or mapping definition file corresponding to a certain vocabulary in the compound document, the portion described by the vocabulary may be displayed in the source display or the tree display. 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. Even if there is no application for the purpose, the content can be grasped by displaying the XML document composed of the text data as a source or a tree. This is a characteristic unique to text-based documents such as XML.

  Another advantage of the data being described in the text base is that, for example, in a part described by a certain vocabulary in a compound document, data in a part described by another vocabulary in the same document can be referred to. Good. In addition, when a search is executed in a document, a character string embedded in a figure such as SVG can be a search target.

  A tag of another vocabulary may be used in a document described by a certain vocabulary. 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 another inserted vocabulary may be mapped by the definition file. For example, tags such as “important” and “most important” may be used in an XHTML document, and a portion surrounded by these tags may be highlighted, or may be sorted and displayed in order of importance. Good.

  When the document is edited by the user on the editing screen shown in FIG. 10, the plug-in or VC unit 80 in charge of the edited part changes the source tree. In the source tree, a listener for a mutation event can be registered for each node. Normally, a plug-in display unit or VC unit 80 corresponding to the vocabulary to which each node belongs is registered as a listener. When the source tree is changed, the DOM providing unit 32 traces from the changed node to a higher hierarchy, and if there is a registered listener, issues a mutation event to the listener. For example, in the document shown in FIG. 9, when a node below the <html> node is changed, a mutation event is notified to the HTML unit 50 registered as a listener in the <html> node, and the higher order node is also displayed. The mutation event is also notified to the SVG unit 60 registered as a listener in the <svg> node. At this time, the HTML unit 50 updates the display with reference to the changed source tree. The SVG unit 60 may ignore the mutation event because the node belonging to its own vocabulary has not been changed.

  Depending on the contents of editing, the overall layout may change as the display is updated by the HTML unit 50. In this case, the layout of the display area for each plug-in is updated by a configuration for managing the layout of the screen, for example, a plug-in responsible for displaying the top node. 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, 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. Upon receiving the notification, the configuration for managing the screen layout re-lays out the display area for each plug-in. In this way, the display of the edited part is appropriately updated, and the layout of the entire screen is updated.

(Embodiment)
FIG. 11 shows a configuration of the document processing apparatus 100 according to the embodiment. The document processing apparatus 100 includes a diagram component 70 and an acquisition unit 71 in addition to the configuration of the document processing apparatus 20 according to the base technology shown in FIG. Diagram component 70 provides the ability to display and edit diagrams. The diagram component 70 includes a processing unit 72, a rule management unit 74, and a core unit 76.

  The processing unit 72 reads and displays a document describing the diagram via the acquisition unit 71 in accordance with a standard defined for creating a diagram, and receives an editing instruction from the user and edits the diagram. . The processing unit 72 performs processing conforming to each of the specific types of notation formulated for describing flowcharts and business process models, such as JIS and BPMN. Since the specifications of the notation such as the shape of the figure and the shape of the arrow differ depending on each standard, the processing unit 72 is provided according to each specification. In the present embodiment, BPMN, which is a standard for expressing a business process model as a diagram type, will be described as an example. The processing unit 72 converts the business process model into data using a unique XML vocabulary having sufficient information to express the BPMN. Hereinafter, a document described in the XML vocabulary is also referred to as a “BPMN document”.

  The rule management unit 74 manages the editing rules in the processing unit 72. Various restrictions are defined on the diagram according to standards and the like. For example, a BPMN representing a business process model has a restriction that “a message flow is not allowed to be used between activities in each lane in the same pool”. The rule management unit 74 holds such editing restrictions, determines whether the processing unit 72 allows editing, and supports creation of a document that complies with each standard. The rule management unit 74 may be provided as a hard-coded module, or may be customizable by a parameter file or the like.

  The core unit 76 provides a function that is commonly used by a plurality of processing units 72 provided according to various diagram notations. For example, the core unit 76 provides common functions that are necessary regardless of the type of diagram, such as DOM operation and file input / output, when processing a diagram.

  As described above, the core unit 76 that provides a common function, the processing unit 72 that performs processing according to the model for creating a diagram, and the rule management unit 74 that manages editing constraints are independent modules. By providing, the processing unit 72 and the rule management unit 74 can be customized separately according to the type of diagram, and can be flexibly handled. In addition, by combining the common functions in the core unit 76, even if the types of diagrams are different, only the processing unit 72 and the rule management unit 74 need to be customized, so that the development man-hours can be reduced. The processing unit 72 has an interface for performing communication with each of the core unit 76 and the rule management unit 74, and cooperates with the core unit 76 and the rule management unit 74 via the interface.

  As a document vocabulary for describing such a business process model, BPEL has a particularly high affinity with BPMN. If a definition file for mapping a business process model in BPEL to a BPMN document is prepared, it is mapped to a BPMN document by the VC unit 80 as described in the base technology, and the processing unit 72 Can be processed. Similarly, even a document in which a diagram is described in a vocabulary other than BPEL can be processed by being mapped to the vocabulary provided by the processing unit 72 by using the technique described in the base technology. By adopting the technology as described above, it is possible to efficiently and easily construct an environment for appropriately processing a business process that is uniquely managed by each company.

  FIG. 12 shows an example of a document 4000 processed by the diagram component. This document is described by a unique XML vocabulary having sufficient information to express BPMN, and defines the types, shapes, coordinates, etc. of swimlanes, flow objects, connection objects, and deliverables. In FIG. 12, some of the style attributes of each element are omitted.

  FIG. 13 shows an example of a screen on which the document shown in FIG. 12 is displayed. Each element described in the document is displayed by the processing unit 72 implemented according to the BPMN standard. The user can add, move, or deform each graphic element on this screen. The processing unit 72 edits the document in response to an editing instruction from the user.

  The rule management unit 74 determines whether to permit editing in the processing unit 72 in accordance with the editing restrictions that are held. In the rule management unit 74, for example, as an editing rule conforming to the BPMN standard, “message flow is not allowed to be used between activities in each lane in the same pool”, “a plurality of flow objects overlap. Editing restrictions such as “Never” are managed. The processing unit 72 inquires of the rule management unit 74 whether or not the editing is permitted before editing according to an instruction from the user. The rule management unit 74 refers to the editing restrictions that are held, determines whether the editing is permitted, and replies to the processing unit 72. If the editing is permitted, the processing unit 72 executes the editing. If the editing is prohibited, the processing unit 72 presents an error message without executing the editing. Whether the editing is permitted or not may be determined by the processing unit 72 with reference to the editing constraints managed by the rule management unit 74.

  FIG. 14 shows an example of a screen for editing the document shown in FIG. In FIG. 14, the user performs editing for connecting the sequence flow from the activity 4002 to the product 4004. However, since this editing is not permitted in BPMN, the processing unit 72 presents an error message 4006 to that effect.

  The processing unit 72 may be provided with a mode for determining whether or not to permit editing each time editing is performed and a mode for allowing editing to be freely executed without determining whether or not editing is permitted. . In the latter mode, the user can freely edit without being restricted by editing restrictions. The processing unit 72 provides a function of performing a validation check in response to a request from the user or before saving a document, whether the document being edited is in violation of editing restrictions. At this time, the rule management unit 74 checks the document that is currently being edited against the editing constraints, and returns a portion that violates the editing constraints to the processing unit 72.

  FIG. 15 shows an example of a screen for editing the document shown in FIG. In the example of FIG. 15, the validation check is performed after the user edits in a mode that does not determine whether editing is permitted. In this example, since the flow object and the flow object overlap each other and the sequence flow is connected to the deliverable, the processing unit 72 presents an error message 4008 to that effect.

  FIG. 16 shows an example of a screen for editing the document shown in FIG. The processing unit 72 provides a function of grouping and editing a plurality of figures in the same way as general drawing software. In the example of FIG. 16, the user selects an activity 4010, an activity 4012, and a sequence flow 4014, and moves them by grouping them.

  In general drawing software, as shown in FIG. 17, the activity 4010, the activity 4012, and the sequence flow 4014 are moved in a group, so that the sequence flow 4014 is separated from the activity 4016 at the start position. This is not a problem when simply editing a figure, but when editing a business process diagram, the sequence flow 4014 means a process flow from the activity 4016 to the activity 4010. It is not appropriate to move away from 4016.

  Therefore, the processing unit 72 according to the present embodiment does not group the sequence flow 4014 with the activity 4010 and the activity 4012 as shown in FIG. 18, and the sequence flow 4014 is connected to the activity 4010 from the activity 4016. The activity 4010 and the activity 4012 are grouped and moved while being kept. As a result, it is possible to appropriately support editing that retains the meaning as a business process diagram rather than simple graphic editing.

  In general drawing software, the last added figure is placed on the top layer, and the added order is maintained unless the user changes the order. However, the processing unit 72 of the present embodiment Place the figure to be edited on the top layer. Accordingly, when the user again selects the same graphic as an editing target, it is easy to select the graphic, and the convenience for the user can be improved.

  When the user clicks a part other than the object in the pool or lane and selects the pool or lane, the processing unit 72 does not edit only the pool or lane frame, but selects the selected pool or lane. All the figures placed in the group are grouped for editing. At this time, since the data object, group, and annotation do not belong to the pool or lane, they are not selected by default. When editing a business process diagram, it is rare to move only the frame of the pool or lane, and the user intends to move the entire figure including the figures arranged in the pool or lane. In most cases, the convenience of the user can be improved by providing such a function. For example, the processing unit 72 selects only a frame of a pool or lane or selects an arbitrary graphic in a pool or lane by clicking a graphic while pressing an “Alt” key, a “Ctrl” key, or the like. It may be possible.

  As described in the base technology, a definition file that maps a business process model document described in a vocabulary such as BPEL to BPMN can be prepared and processed by the document processing apparatus 100 using the VC function. At this time, when mapping a document such as BPEL, which cannot define the coordinates of a figure, to BPMN, the default coordinate value of each figure is automatically set according to a predetermined rule in the definition file. It may be calculated and stored as a coordinate value in the BPMN document at the mapping destination. Further, when the edited document is saved, the coordinate values and style attributes of the respective figures are saved in the parameter file separately from the BPEL document, and the parameter file associated with the BPEL document is then edited. If there is, it may be read and merged, and stored in the mapping destination BPMN document. Such a function may be provided by a definition file, or may be provided by the processing unit 72 or the core unit 76.

  The present invention has been described based on the embodiments. This embodiment is an exemplification, and it will be 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. is there.

  Although an example of processing an XML document has been described in the embodiment, the document processing apparatus 100 according to the present embodiment can similarly process a document described in another markup language, for example, SGML, HTML, or the like. is there.

It is a figure which shows the structure of the document processing apparatus which concerns on a base technology. It is a figure which shows the example of the XML document edited by the document processing apparatus. FIG. 3 is a diagram showing an example in which the XML document shown in FIG. 2 is mapped to a table described in HTML. FIG. 4 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. 3. FIG. 4 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. 3. FIG. 4 is a diagram showing an example of a screen on which the XML document shown in FIG. 2 is mapped and displayed in HTML according to the correspondence shown in FIG. 3. It is a figure which shows the example of the graphical user interface which a definition file production | generation part presents to a user in order that a user may produce | generate a definition file. It is a figure which shows the other example of the screen layout produced | generated by the definition file production | generation part. 6 is a diagram illustrating an example of an XML document editing screen by the document processing apparatus. FIG. It is a figure which shows the other example of the XML document edited by the document processing apparatus. It is a figure which shows the example of the screen which displayed the document shown in FIG. It is a figure which shows the structure of the document processing apparatus which concerns on embodiment. FIG. 4 is a diagram illustrating an example of a document processed by a diagram component. FIG. 13 is a diagram showing an example of a screen on which the document shown in FIG. 12 is displayed. It is a figure which shows the example of the screen which is editing the document shown in FIG. It is a figure which shows the example of the screen which is editing the document shown in FIG. It is a figure which shows the example of the screen which is editing the document shown in FIG. It is a figure which shows the example of the screen which is editing the document shown in FIG. It is a figure which shows the example of the screen which is editing the document shown in FIG.

Explanation of symbols

  20 document processing apparatus, 22 main control unit, 24 editing unit, 30 DOM unit, 32 DOM providing unit, 34 DOM generating unit, 36 output unit, 40 CSS unit, 42 CSS analyzing unit, 44 CSS providing unit, 46 rendering unit, 50 HTML unit, 52, 62 control unit, 54, 64 editing unit, 56, 66 display unit, 60 SVG unit, 70 diagram component, 72 processing unit, 74 rule management unit, 76 core unit, 80 VC unit, 82 mapping unit 84 Definition file acquisition unit 86 Definition file generation unit 100 Document processing apparatus.

Claims (9)

A processing unit providing a function of processing the diagram according to a notation of a specific type of diagram;
A core unit that provides functions commonly used regardless of the type of diagram when processing the diagram;
In accordance with the notation of the specific type of diagram, a rule management unit that determines whether or not editing is permitted by the processing unit;
A document processing apparatus comprising:   The processing unit, the core unit, and the rule management unit are provided as independent modules, respectively, and the processing unit has an interface for performing communication with each of the core unit and the rule management unit. The document processing apparatus according to claim 1.   The document processing apparatus according to claim 1, wherein the processing unit converts the diagram into data using a markup language for describing the diagram.   A conversion unit that reads a document describing a diagram, maps the document to data described in the markup language that can be processed by the processing unit, and manages correspondence between mapping source data and mapping destination data; The document processing apparatus according to claim 3, wherein:   If the coordinates of the figure included in the diagram are not described in the read document, the conversion unit reads the file describing the coordinates associated with the document, or sets the coordinates to a predetermined rule. Accordingly, the document processing apparatus according to claim 4, wherein the coordinates are acquired and mapped by automatically calculating. The processing unit provides a grouping function for grouping a plurality of figures to be edited,
6. The grouping function according to claim 1, wherein, even if a graphic showing a connection relationship between a certain graphic and another graphic is selected as a grouping target, the graphic is excluded from the editing target. Document processing apparatus according to the above.   The processing unit provides a function of selecting a graphic belonging to the frame as an editing target when the graphic as a frame of the diagram is selected as the editing target. Document processing apparatus described in 1. According to the notation of a specific type of diagram, a processing unit that provides a function for processing the diagram, and a core unit that provides a function that is commonly used regardless of the type of the diagram when processing the diagram, Editing the diagram;
In accordance with the notation of the specific type of diagram, determining whether to allow editing by the processing unit;
A document processing method characterized by causing a computer to execute. Computer
A processing unit that provides a function of processing the diagram according to a notation of a specific type of diagram;
A core unit that provides a function that is commonly used regardless of the type of diagram when processing the diagram,
In accordance with the notation of the specific type of diagram, a rule management unit that determines whether the processing unit allows editing,
A document processing program characterized by functioning as