JP2002091947A - Device for dynamically preparing structured document - Google Patents

Abstract

PROBLEM TO BE SOLVED: To dynamically prepare a structured document by combining accumulated partial documents. SOLUTION: This structured document dynamically preparing device consists of a structured document registering means 103 for registering the structured document to be a management object in a structured document management database, a reference authority management database 102 in which the reference authority data of the structured document set in each user are registered and a structured document outputting means 105. The outputting means 105 acquires user's reference authority by referring to the reference authority management database, acquires a partial document over which the reference authority is held from the structured document management database on the basis of the acquired reference authority, dynamically structures the acquired partial document and outputs the structured partial document.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a structured document dynamic generation device, and more particularly to a structured document dynamic generation device that dynamically processes and outputs a registered structured document.

[0002]

2. Description of the Related Art As a technique for processing a structured document at the time of output, (1) http://www.w3.org/1999/09/ql/docs/xque
ry.html "XML-QL" and (2) JP-A-10-2142
No. 65, “Structured document processing device” is known. The technique (1) is a technique for searching a structured document for a document based on its structure, processing the content of the matched document into a specified structure, and outputting the processed structure. The technique (2) is a technique for processing an output document according to a document structure operation instruction.

[0003]

The above prior arts have the following problems. That is, the technique shown in (1) can output only a component document, and cannot output a completed document. The technique shown in (2) is a technique for generating an output document without storing an input structured document in a database. Therefore, when an output document is to be obtained, an input document is required. Further, the techniques described in the above (1) and (2) cannot restrict browsing of a part of an output document every time an output request is made. Further, it is not possible to output the contents of all the documents input for a particular structure of the document.

The present invention has been made in view of the above problems, and provides a structured document dynamic generation device that dynamically generates a structured document by combining accumulated component documents.

[0005]

The present invention employs the following means in order to solve the above-mentioned problems.

[0006] Structured document registration means for dividing a structured document to be managed into part documents and registering it in a structured document management database, and reference authority management for registering structured document reference authority data set for each user. And a structured document output unit. The structured document output unit acquires the reference authority of the user by referring to the reference authority management database, and refers to the reference authority from the structured document management database based on the acquired reference authority. A part document having a part document is acquired, and the acquired part document is dynamically structured and output.

[0007]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of the present invention will be described below with reference to FIGS. FIG. 1 is a diagram showing a structured document dynamic generation device according to an embodiment of the present invention. In the figure, 100 is an input structured document, 101 is a structured document dynamic generation device. Reference numeral 102 denotes a structured document management database which stores component documents obtained by dividing the input structured document 101. A structured document registration unit 103 inputs the structured document 100, divides the structured document into component documents based on the document structure, and registers the divided component documents in the structured document management database 102. Reference numeral 104 denotes a structure reference authority management unit that inputs an output request from the user 108 and obtains, from the structure reference authority management database, a document structure permitted to be referenced by the user 108 among the document structures included in the output request. Then, the acquired reference authority is supplied to the structured document output unit 105. Reference numeral 105 denotes a structured document output unit which acquires a part document permitted to be referenced from the structured document management database 102 based on the reference authority, stores the acquired part document in a predetermined output format, and The structured document 107 is reconstructed. 106 is an output request input by the user, 107 is an output structured document, 10
Reference numeral 9 denotes a structure reference authority management database that stores structured document reference authority for each user.

FIG. 2 is a diagram showing the operation of the structured document dynamic generation device. In the drawing, the same portions as those shown in FIG. 1 are denoted by the same reference numerals, and description thereof will be omitted. First, the structured document registration unit of the structured document dynamic generation apparatus 101 inputs an input structured document 100 such as a product information document (for example, a product specification) and converts the document into a plurality of component documents based on the document structure. 102a, 102b, 102c, 10
The document is divided into 2d parts, and the divided component documents are stored in the structured document management database 102. Each part document is "T
okkyuo "," Caution "," Zentei "
Program ”and“ Kakaku ”. The output requests 106a to 106c request acquisition of a part document specified by the document ID and output as a structured document.
The structured document output processing means of the structured document dynamic generation device 101 acquires a part document permitted to be referenced from the structured document management database 102 in response to a user output request, and The output structured document 107 such as a product information document is stored in a predetermined output format.

For example, an output request 106a from the user A
The structured document dynamic generation device 101 having received the information refers to the reference authority of the user A stored in the structure reference authority database 109. The structure reference authority database 109 does not define a structure for which the user A does not have the reference authority, and therefore, the user A has all the component documents included in the output request 106a,
"ZenteiProgram", "Tokyucy
o "and" Kakaku "are output as structured documents 107a such as product information documents.

[0010] Upon receiving the output request 106 a from the user B, the structured document dynamic generation device 101 refers to the reference authority of the user B stored in the structure reference authority database 109. Since the structure “Kakaku” to which the user B does not have the reference authority is defined in the structure reference authority database 109, the user B has a component document “Z” other than “Kakaku”.
"enteiProgram" and "Tokuyo" are output as structured documents 107a such as product information documents.

A structured document dynamic generation device 1 which has received an output request 106c (when a list document is requested) from a user C
01 refers to the reference authority of the user C stored in the structure reference authority database 109. The structure reference authority database 109 does not define any structure that does not have the reference authority to the user C. Therefore, the user C extracts all the data of the structure "ZenteiProgram" included in the output request 106c and exists in the database. And outputs it as a structured document (list document) 107a.

FIGS. 3 to 5 show examples of the structured document 100. FIG. The structured document includes a document ID 300 as a document identifier, a part document 301 having a structure "ZenteiProgram", a part document 302 having a structure "Tokuyo", a part document 303 having a structure "Caution", and a structure "Kakaku". Is composed of a component document 304.

FIG. 6 is a diagram showing an example of the document type definition (DTD) of the structured document shown in FIGS.

FIG. 7 is a diagram showing an example of the data format of data stored in the document management database 102. The stored data includes a document ID 500 that is an identifier of the input structured document, and a structure “Tok” that is a part document extracted from the input document.
ucyo ”501. When the product information shown in FIGS. 3 to 5 is registered, “010” is added to the document ID.
"0" and the content "has the following features ..." are stored in the database.

FIG. 8 is a diagram showing an example of the format of the output request 106a (when a normal document is requested). The output request is a structure “DocumentID” 600 indicating the document ID.
"Structure" indicating the name of the document structure requested to be output
uriname "601. "Structur
A plurality of “name” 601 can be specified. In this example, the structures “Tokuyo” and “ZenteiPr” are used.
ogram "," Caution "," Kakaku "
including. When a request is made in this data format, the structured document dynamic generation device has the specified document ID and the structure “Tok”.
ucyo "," ZenteiProgram "," Ca
A structured document (normal document) composed of document parts having “Ution” and “Kakuku” is generated.

FIG. 9 is a diagram showing an example of a document type definition (DTD) common to the output requests 106a (when requesting a normal document) and 106c (when requesting a list document).

FIG. 10 is a diagram showing an example of a compilation document (for a normal document) of product information (structured document) output according to the output request format of FIG. Reference numeral 800 denotes a document ID having a structure “DocumentID”;
01 is the structure for which the output was requested, "Tokucyo", "Z
enteiProgram ”,“ Caution ”,
Represents a specification for incorporating "Kakaku".

FIG. 11 is a diagram showing a part document (Tokukyo.xml) incorporated in the output format shown in FIG. This document contains the structure "Tokushio".

FIG. 12 shows a part document (ZenteiProgram) incorporated in the output format shown in FIG.
m. xml). This document contains the structure "ZenteiProgram".

FIG. 13 is a view showing a part document (Caution.xml) incorporated in the output format shown in FIG. This document contains the structure "Caution".

FIG. 14 is a diagram showing a part document (Kakaku.xml) incorporated in the output format shown in FIG. This document contains the structure "Kakaku".

FIG. 15 is a diagram showing a display example of an output structured document (normal document) generated by taking in a part document into the output format shown in FIG.

FIG. 16 is a diagram showing a format example of the output request 106c (when a list document is requested). The output request has a structure "DocumentID" 1 with empty content
400 and a structure “str” indicating the name of the document structure requested to be output
actuname "1401. When a request is made in this data format, the specified document structure "Zent
All of the data of "eiProgram" existing in the database are extracted to generate a structured document (list document).

FIG. 17 is a diagram showing an example of a product information (structured document) compilation document (for a list document) output according to the output request format of FIG. Part document “soten1” 150 stored in the database
0, including designation for capturing “soten2” 1501.

FIG. 18 is a diagram showing a part document (soten1.xml) incorporated in the document of FIG. This part document includes the structure “ZenteiProgrammer” specified in the output request in the product information of the document ID “0100”.
m ”is included.

FIG. 19 shows a part document (soten2.xml) to be included in the consolidated document shown in FIG. This part document has a document ID “0110”
"Zent" specified in the output request in the product information
eiProgram ”is included.

FIG. 20 is a diagram showing a display example of an output structured document (list document) generated by incorporating a part document into the consolidated document shown in FIG.

FIG. 21 is a diagram showing a registration process of an input structured document. In step 1900, the user inputs a structured document to the structured document registration unit 103 and instructs execution of a registration process. In step 1901, the structured document registration unit 103 extracts a part document from the structured document. In step 1902, a document ID is added to the component document extracted and stored in the structured document management database 102.

FIG. 22 is a diagram showing a structured document output process. In step 2000, the user designates the type of output request to the structured document output unit 105 and instructs execution of output processing. In step 2001, the structured document output unit 105 determines the type of the output request. If the output request type is a normal document, the process proceeds to step 2002,
If the type of the output request is a list document, the process proceeds to step 2003. In step 2002, a normal document generation process described later is executed. In step 2003, a list document generation process described later is executed. In step 2004, the generated document is output.

FIG. 23 is a diagram showing a normal document generation process in FIG. 22, and FIG. 24 is a diagram showing a base of a structured document for a normal document output of a structured document. In FIG.
Reference numeral 2300 denotes a location for storing the content defining the reference destination of the component document, 2301 denotes a storage location for the document ID, and 2302 denotes a location for storing the content referring to the component document.

In step 2100 in FIG. 23, the base of the compiled document for normal document output is created. In step 2101, the document ID included in the output request 106 is added to the portion indicated by 2301 in the normal document output format. In step 2102, the process enters the output request structure number loop, and the following processing is repeated by the number of output request structures. In step 2103, it is determined whether or not the user is permitted to refer to the requested document structure. If the reference is permitted, the process proceeds to step 2104; otherwise, the process proceeds to step 2107. In step 2104, a search is performed on the database of the requested structure name using the document ID as a key, and a corresponding part document is searched. The document obtained in step 2105 is output. In step 2106, the definition necessary for referring to the part document and the reference to the part document are collected and stored in the consolidated document. When the loop is traversed by the number of structures in step 2107, the process ends.

FIG. 25 is a diagram showing the list document generation processing in FIG. 22, and FIG. 26 is a diagram showing the base of a compiled document for outputting a structured document list document. In FIG. 26, reference numeral 2400 denotes a location for storing a definition necessary for referring to a component document, and 2401 denotes a location for storing a component document ID and contents for referring to a document component.

In step 2200 of FIG. 25, the base of the summary document for the list document is created. In step 2201, it is determined whether or not the user is permitted to refer to the requested document structure. If reference is permitted, the process proceeds to step 2202; otherwise, the process ends. In step 2102, a loop for the number of output document IDs is entered, and the following processing is repeated by the number of output document IDs. In step 2203, a search is performed on the database of the requested structure name using the document ID as a search key, and a corresponding part document is searched. Step 2
At 104, the document ID and the acquired component document are output as a new component document. In step 2205, the definition necessary for referring to the newly created part document, the part document ID, and the contents referring to the document part are collected and stored in the combined document. In step 2206, the process ends when the loop is traversed by the number of IDs. As described above, according to the present embodiment, an input structured document can be automatically registered by the structured document registration system, and an output structured document can be dynamically generated in response to a user output request. Further, it is possible to output a document corresponding to the reference authority of the user who has requested the output. Further, it is possible to generate a structured document (list document) in which all contents of a specific document structure are collected for a plurality of documents in the database.

[0034]

As described above, according to the present invention, a structured document can be dynamically generated by dynamically combining accumulated component documents.

[Brief description of the drawings]

FIG. 1 is a diagram showing a structured document dynamic generation device according to an embodiment of the present invention.

FIG. 2 is a diagram illustrating an operation of a structured document dynamic generation device.

FIG. 3 is a diagram illustrating an example of a structured document.

FIG. 4 is a diagram illustrating an example of a structured document.

FIG. 5 is a diagram illustrating an example of a structured document.

FIG. 6 is a diagram illustrating an example of definition contents of a document type of a structured document.

FIG. 7 is a diagram illustrating an example of a data format of data stored in a document management database.

FIG. 8 is a diagram showing a format example of an output request.

FIG. 9 is a diagram illustrating an example of a DTD of an output request format.

FIG. 10 is a diagram illustrating an example of a product information collection document.

FIG. 11 is a diagram showing a part document.

FIG. 12 is a diagram showing a part document.

FIG. 13 is a diagram showing a part document.

FIG. 14 is a diagram showing a part document.

FIG. 15 is a diagram illustrating a display example of an output structured document.

FIG. 16 is a diagram showing another example of the format of the output request.

FIG. 17 is a diagram illustrating an example of a product information collection document.

FIG. 18 is a diagram illustrating a part document.

FIG. 19 is a diagram showing a part document.

FIG. 20 is a diagram illustrating a display example of an output structured document.

FIG. 21 is a diagram illustrating an input process of a structured document.

FIG. 22 is a diagram illustrating a structured document output process.

FIG. 23 illustrates a normal document generation process.

FIG. 24 is a diagram illustrating a base of a compiled document for normal document output.

FIG. 25 is a diagram showing a list document generation process.

FIG. 26 is a diagram showing a base of a compiled document for outputting a list document.

[Explanation of symbols]

 REFERENCE SIGNS LIST 100 input structured document 101 structured document dynamic generation device 102 structured document management database 103 structured document registration means 104 structure reference authority management means 105 structured document output means 106 output request 107 output structured document 108 user 109 structure Reference authority management database

 ──────────────────────────────────────────────────続 き Continuing from the front page (72) Inventor Hideo Matsunaga 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Prefecture Inside the Software Division of Hitachi, Ltd. (72) Inventor Yasuki Ito 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Hitachi, Ltd. Software Division (72) Inventor Takehide Mihara 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Prefecture Co., Ltd. (72) Inventor Kiyotaka Kiho 5030 Totsukacho, Totsuka-ku, Yokohama-shi, Kanagawa Prefecture Hitachi, Ltd. Software Division (72) Inventor Emi Sawabe 6-81 Onoecho, Naka-ku, Yokohama-shi, Kanagawa Prefecture Hitachi Software Engineering Co., Ltd. In-house F-term (reference) 5B009 NA05 ND04 5B082 BA00 GA02

Claims (5)

[Claims] A structured document registration means for registering a structured document to be managed in a structured document management database; a reference authority management database for registering structured document reference authority data set for each user; The reference authority of the reference is acquired by referring to the reference authority management database, the part document having the reference authority is acquired from the structured document management database based on the acquired reference authority, and the acquired part document is dynamically structured. A structured document dynamic generation device comprising a structured document output unit for outputting. 2. The structured document moving device according to claim 1, wherein said structured document registering means divides the structured document to be managed into part documents and registers them in a structured document management database. Generating device. 3. A structured document output means according to claim 1, wherein said structured document output means dynamically structures and outputs a part document according to a document structure designated by a user. Structured document dynamic generation device. 4. A step of dividing a structured document to be managed into part documents and registering it in a structured document management database; and a step of registering a reference authority management database in which structured document reference authority data set for each user is registered. Acquiring the reference authority for each user by referring to; acquiring the part document having the reference authority from the structured document management database based on the acquired reference authority; and dynamically structuring the acquired part document. A structured document dynamic generation method characterized by comprising an output step. 5. A step of dividing a structured document to be managed into part documents and registering it in a structured document management database, and a step of registering a reference authority management database in which reference authority data of the structured document set for each user is registered. Referring to the reference authority for each user; acquiring the component document having the reference authority from the structured document management database based on the acquired reference authority according to a preset output format; A structured document dynamic generation method, comprising a step of dynamically structuring and outputting based on a preset instruction content of an integrated document.