JPH04177455A - Document structure generation system - Google Patents

Abstract

PURPOSE:To save the labor required for the document processing operation by acquiring the information on a logic structure which satisfies the limitation of an input common logical structure from the logical structure of an input document and generating a part or the whole of a logic structure which satisfies an output common logical structure based on the information on the former logical structure. CONSTITUTION:An automatic logical structure generation processing part 107 generates a new logical structure which satisfies a common logical structure stored in a common logical structure storage part 105 and the document parts and also generates the connection between the logical structure and the document parts based on a program of a logical structure generation program storage part 106. In other words, a generation rule is prescribed between a logical structure which satisfies the limitation of the common logical. structure that limits the logical structure of the input document and a logical structure which satisfies an limitation of the common logical. structure that limits the logical structure of an output document. Based on this generation rule, the logical structure of the output document is obtained.

Description

[Detailed Description of the Invention] [Industrial Application Field] The present invention relates to a method for generating a document structure of an electronic document processed by a word processor or a WorkStylon or the like having a document processing function, and particularly relates to a method for generating a document structure of an electronic document that is processed by a word processor or a workstation with a document processing function. From the document structure of multiple electronic documents,
The present invention relates to a document structure generation method that automatically generates the document structure of a new single or multiple electronic documents.

[Conventional technology]

Conventionally, methods for automatically generating electronic documents from electronic documents include Yamada's "Automatic Execution Method for Data Processing Between Documents,"
Proceedings of the Information Processing Society of Japan, Page 35, Golden Country Conference, P, 2571,
Asami, Yamada "User interface for inter-form data processing", Proceedings of the Information Processing Society of Japan, Page 36, Kinkoku Conference, p. 2213
There are known methods for processing forms, such as the one described in .

In a form, the entries and the form of the data entered in each entry are almost fixed, and it is easy to define the data structure of the form.

Therefore, it was easy to define the data structure of a form, prepare a program to automatically generate a form from the form, and execute the program on the input form to automatically process the form. However, for general electronic documents such as technical papers, manuals, and specifications, the structure of the data is defined, except for documents such as forms in which the entry items and the type of data entered in each entry are clear. There was no way to do this, which made automatic processing difficult.

More recently, Furuta, R.: Conc.
epts and Models for 5t
structured documents, 5t
structured documents, Ca
mbridge University Pre
ss, pp. 7-38 (1988), consider electronic documents as a collection of document parts that hold part of the content of the document, and consider the relationship between document parts from a logical perspective. It has become possible to consider adding a document structure to electronic documents, such as a logical structure that expresses relationships and an layout structure that expresses relationships between document parts from a layout perspective. It has become relatively easy to express.

A document having such a document structure is called a structured document.

In particular, ODA is an international standard that embodies the concept of a structural document.
(Office Document Arch
ISO/Is 8613
．． Information Processing -
Text and Office System -0
ffice Document Architecture
re (ODA) and Interchange
Format (1988), an electronic document has a specific logical structure that expresses the relationships between document parts from a logical perspective, and a specific logical structure that expresses the relationships between document parts from a layout perspective. It is standardized that specific assignments expressing relationships have a structure.

Further, in ODA, a common structure (common logical structure/common allocation is a structure) that restricts the possible structures of a specific logical structure/specific allocation is defined.

Documents of the same type have the same common structure, such as all patent specifications having a common structure as patent specifications and all manuals having a common structure as manuals.

ODA documents are generated using a common structure as a model.

Ishida is an example of such electronic document processing technology.

"Prototype of Murata rODA document processing system (1) -Design issues-", Proceedings of the Information Processing Society of Japan, Page 37, Golden Country Conference, p. 18
53, Suzuki, Nakatsuyama, Murata, "Prototype of ODA document processing system (2) - Human power, visualization processing -", Proceedings of Information Processing Society of Japan's 37-page Golden Country Conference.

P, 1855, Hayashi, Saito 1 Ishida, Murata, "Prototype of rODA document processing system (2) - Allocation is processing -", Proceedings of the Information Processing Society of Japan's 37-page Golden Country Conference, P.

As described in 1857, it is known that documents are edited and automatically allocated in accordance with ODA standards.

[Problem to be solved by the invention]

In many office document processing operations, (1) the logical structure of documents is explicitly or implicitly specified within the organization, and many documents completely or partially follow these rules; Is pleased.

(2) There is a relationship between documents based on their logical structure (for example, the title of one document is the same as an item in another document), and based on this relationship, It has the characteristic that part or all of it is generated many times regularly or non-regularly, or it is generated in large quantities at once.

The above-mentioned document processing is performed by human interactive editing, except for a part such as form processing.

In this case, (1) similar editing operations are performed on many documents of the same type over and over again, either regularly or irregularly;

Or do it in large quantities at − degrees. (2) There is a lot of processing work that uses existing documents as raw materials.

This feature points out the redundancy and inefficiency of performing the above document processing through human interactive editing.

In general, for tables and forms in which the document structure is fixed, the above-mentioned conventional technology is used to complete the document by assigning the contents of the document in a concrete manner to the contents of another document. Is possible.

On the other hand, for technical documents, manuals, reports, etc., only the outline of the structure of the document is prescribed, and each document is allowed a degree of freedom in determining its specific structure.

It became possible to express the logical structure of these documents for the first time through structured documents such as ODA.

However, for such a logical structure, a content assignment method that assumes that document contents are mapped based on a strictly determined structure is not effective; There was no way to manipulate it other than to create it by interactively reshaping the structure.

The purpose of the present invention is to provide an automatic document generation method for structured documents in order to solve the above problems.
The object of the present invention is to improve the labor saving of document processing for general documents other than forms.

[Means to solve the problem]

In order to achieve the above object, the present invention has a logical structure expressed by a connection of nodes indicating a structural group of document parts, and constraints on the connection state of nodes that can be taken in the logical structure of the document are set by a common logic. In a document structure generation method for electronic documents that is defined as a structure, when the logical structure of an existing electronic document is input and a part or the entire logical structure of a new electronic document is output, the logical structure of the input document is Between the input common logical structure to be constrained and the output common logical structure to constrain the logical structure of the output document, a generation rule that generates the logical structure of the document to be output from the information of the logical structure of the input document is created in advance. , is set, and information on the logical structure that satisfies the constraints of the input common logical structure is obtained from the logical structure of the input document, and based on this information, part or all of the logical structure that satisfies the constraints of the output common logical structure is obtained. It is characterized by automatically generating.

In addition, it has a logical structure expressed by a tree structure that connects nodes that indicate a structural grouping of document parts, and the constraints on the logical structure of the document are common logical structures that are templates of nodes that can appear on the tree structure. Document structure generation of an electronic document defined by a common logical structure expressed as a set of elements, in which the common logical structure element describes constraints on a sequence of child nodes of a node whose model is the common logical structure element. Method When outputting part or all of the logical structure of a new electronic document using the logical structure of an existing electronic document as input, the common logical structure elements included in the common logical structure that constrain the logical structure of the input document are used as a template. The relationship between the sequence of child nodes that can be applied to a node and the sequence of child nodes that can be applied to a node whose model is a common logical structure element included in a common logical structure that constrains the logical structure of the output document. , A logical structure element generation rule consisting of application conditions for determining the nodes to which the relationship is applied is set in advance, and a new logic is created from the logical structure of the input document based on the logical structure element generation rule. It is characterized by automatically generating part or the entire structure.

[For production]

According to the present invention, a logical structure that satisfies the common logical structure constraints that constrain the logical structure of one or more input documents, and a common logical structure constraint that constrains the logical structure of one or more output documents. A generation rule is defined between logical structures that satisfy the following, and the logical structure of an output document is generated from the logical structure of an input document according to the generation rule, thereby making it possible to automatically generate a logical structure.

In particular, by writing production rules between common logical structures in which constraints on logical structures are described, logical structures having the same common logical structure can be processed using the same production rule.

For example, if a common logical structure regarding the document structure of patent specifications exists, a generation rule for automatic document structure generation written using the common logical structure can be applied to all patent specifications. be.

The present invention is particularly effective in generating a specific logical structure of ODA.

At that time, production rules are written between common logical structures.

〔Example〕

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram showing an outline of a document logical structure generation device to which the present invention is applied.
From 01, an instruction to start the automatic logical structure generation process is input.

102 is a display unit such as a CRT display; 103
104 is an input/output control unit, and 104 is a collection of document parts of the electronic document.
The logical structure/layout is an electronic document storage unit that stores structure/document attributes, and 105 is a common logical structure storage unit that stores a common logical structure that is a common structure of logical structures to be processed in the automatic logical structure generation process. , 106 creates a new logical structure,
A logical structure generation program storage unit that stores a logical structure generation program that generates document components and connections between the logical structures and document components; 107 is a logical structure of one or more electronic documents stored in the electronic document storage unit 104; , the common logical structure storage unit 1 based on the logical structure generation program stored in the logical structure generation program storage unit 106.
This is a logical structure automatic generation processing unit that generates new logical structures, document parts, and connections between the logical structures and document parts that satisfy the constraints of the common logical structures stored in 05.

FIG. 2 is an explanatory diagram of the data structure of an electronic document stored in the electronic document storage unit, in which 201 is electronic document data, 202 is a document identifier that is an identifier of the electronic document, and 203 is a part of the electronic document data. A document component information section 204 is information regarding a certain document component; document structure information 204 is information regarding a document structure (logical structure/layout structure) that is a part of the electronic document data; and 205 is a part of the electronic document data. A document attribute information section 206 is information regarding a certain document attribute, a logical structure information section included in the document structure information section 204, and 207 is a document structure information section 204.
208 is a common logical structure identifier that is an identifier of a common logical structure that constrains the generation of the logical structure contained in the logical structure information part 206. 209 is the logic contained in the logical structure information part 206. Structure information, 210, allocation is included in the structure information section 207. Allocation, which constrains the generation of the structure, common allocation is the identifier of the structure, common allocation is the structure identifier, 211, allocation is included in the structure information section 207. The included layout is structural information.

FIG. 3 is an explanatory diagram of the data structure of the document component information section included in the electronic document data, in which 301 is the document component data, 302 is the document component identifier included in the document component data 301, and 303 is the document component information section. This is document component content information included in the component data 301, and stores information regarding part of the document content held by the document component.

Reference numeral 304 is a portion where various information related to the document component data included in the document component data 301 is stored.

FIG. 4 is an explanatory diagram of the data structure of logical structure information included in electronic document data.

In this embodiment, the logical structure is such that nodes representing logically structured groups of document parts are connected in a tree structure, and the document parts are further connected to leaf nodes of the logical structure.

That is, either a plurality of child nodes or a plurality of document parts are connected under the node.

Also, nothing is connected under the document component.

In the figure, numeral 401 denotes structural element data in which data of structural elements, which are units constituting a logical structure, are stored, and the structural elements correspond to nodes on the logical structure.

Furthermore, information about the connections between the structural elements, which holds information about the structural elements and the rows of child nodes of the structural elements (directly subordinate structures), is expressed as direct subordinate structure data.

402 is a structural element identifier included in the structural element data 401, and represents an identifier of a structural element.

A common structural element identifier 403 is an identifier of a common structural element that constrains the structural element specified by the structural element identifier 402.

A common structural element is a unit that constitutes a common logical structure,
Constrain the immediate structure of a structural element.

One common structural element constrains one or more structural elements.

404 is direct structure data that describes the structure immediately below the structure element specified by the structure element identifier 402, if the structure exists, and the direct structure data includes a list of identifiers of child nodes of the structure element, that is, the structure A list of element identifiers is maintained.

Reference numeral 405 is a leaf node in which the structural element specified by the structural element identifier 402 has no child nodes, and is document component data that is written when the structural element has a specific document component.

The document component data holds a list of document component identifiers.

Reference numeral 406 is a portion in which various information related to the structural element data included in the structural element data 401 is stored.

The layout structure information 211 included in the electronic document data 201 also has the same data structure as the logical structure information 11i 209.

FIG. 5 is an explanatory diagram of the data structure of the common logical structure data stored in the common logical structure storage unit, where 501 is the common logical structure data, 502 is the common logical structure identifier, and 503 is the common logical structure. A common structural element data section in which common structural element data is stored, 504 common structural element data stored in the common structural element data section 503, and 505 a common structural element identifier for identifying individual common structural element data. , which represents the identifier of a common structural element.

506 is constraint information that constrains the immediate structure of the structural element;
Reference numeral 507 is a portion in which various information regarding the common structural element data included in the common structural element data 504 is stored.

FIG. 6 is an explanatory diagram of the data structure of the logical structure generation program stored in the logical structure generation program storage unit, in which 601 is the logical structure generation program, 602 is the logical structure generation program identifier, and 603 is the output electronic data. 604 is an input common logical structure designation part in which the common logical structure of the logical structure of the input electronic document is designated; 605 is the logical structure generation program; This is the structure element generation rule section included in the structure element generation rule section, in which rules for generating a new logical structure from an existing logical structure are described.

Reference numeral 606 denotes a content part generation rule section included in the logical structure generation program 601, which creates document parts of a new document and connections between the logical structure and document parts based on existing document parts and the connections between the logical structures and document parts. Rules for generation are described.

607 is a structure element generation rule stored in the structure element generation rule section 605, 608 is a structure element generation rule identifier for identifying this structure element generation rule, and 609 is a structure element specified by the structure element generation rule identifier 607. The output structure element specification section 610 describes the conditions (structure element specification description) for the structure elements in the logical structure of the output document to which the production rules are applied, to which the structure element generation rules specified by the structure element generation rule identifier 607 are applied. This is an input structure element specification part that describes conditions (structure element specification description) for structure elements in the logical structure of the input document to be processed.

What is written in the output structure element specification part and the input structure element specification part becomes the application condition of the structure element generation rule.

611 is a production rule applied to the structure elements specified by the output structure element specification section 609 and the input structure specification section 610.

612 is a content generation rule stored in the content generation rule section 606, 613 is a content generation rule identifier for identifying each content generation rule, and 614 is the content specified by the content generation rule identifier 613. An output structure element specification section 615 describes the conditions (structure element specification description) for the structure elements in the logical structure of the output document to which the section generation rules are applied; This is an input structure element specification section that describes conditions (component specification description) for the structure elements in the logical structure of the input document to be applied.

What is written in the output structure element specification part and the input structure element specification part becomes the application condition of the content part generation rule.

616 is a production rule applied to the structure element specified by the output structure element specification section 614 and the input structure element specification section 615.

FIG. 7 is a content explanatory diagram of a common logical structure having a common logical structure identifier called "paper class" stored in the common logical structure storage unit, where 701 is a common logical structure identifier;
02 is a common structure element data section.

Some common structural element data 703 is stored in the common structural element data section.

In the case of the paper class, 13 pieces of common structural element data exist in the common structural element data section.

The common structural element identifier is represented by "R", "-", and numbers 704.

Descriptors such as ``$'', ``¥'', and ``ψ2'', represented by 705, followed by a list of common structural element identifiers, or a string of child nodes of the structural element are described by ``nil''. This is constraint information that constrains the immediate structure.

706 is a name added to each common structural element to aid the user's understanding, and corresponds to the other information 507 portion.

FIG. 8 is an explanatory diagram of the contents of the logical structure information part included in the electronic document having the document identifier "Paper A" stored in the electronic document storage unit 104, and 801 is a common logical structure identifier. , identifier of a common logical structure that constrains the logical structure of the electronic document of "Paper A", 80
2 is logical structure information, and 803 is structural element data.

Logical structure information 802 stores 16 structural element data.

The structural element identifier is represented by 'r'', '-'', and numbers 804.

What is described by the R",'-" numerals represented by 805 is a common structural element identifier that is an identifier of a common structural element that constrains the structure immediately below the structural element.

What is described by the list of structural element identifiers represented by 806 or "ni1" is the immediately subordinate structure data indicating the immediately subordinate structure.

What is described by a list or "niI" represented by 807 is document component data indicating a document component possessed by a structural element, and the contents of the list are document component identifiers.

One of the direct structure data and document component data is always nil.

This corresponds to the fact that one of the document parts is always connected to a child node under a node in the logical structure.

808 is a name added to each common structural element to aid the user's understanding, and corresponds to the other information 406 portion.

FIG. 9 is an explanatory diagram showing the contents of the common logical structure shown in FIG. 7 in an easy-to-understand graph, and rectangles represented by 901 indicate common structural elements.

The common structure element identifier of each common structure element is the name of the common structure element described in the other information 507 portion in the lower half of the rectangle, as shown in 902.

The common structural element data corresponding to the rectangle 901 is 707 (common structural element "R") (the iiik identifiers match).

The constraint information for the common structural element "R" is $ (R-1, R-2, R-3) (1).

“$” indicates that it has an immediate structure with the same pattern as the list.

Therefore, this notation means that the structural element constrained by the common structural element "R" is (the structural element constrained by the common structural element "R-1").

Constrained by common structural element "R-2" structural elements.

Constrained by common structural element "R-3" structural elements) This shows that it has a structure directly below the pattern.

This means that in FIG. 9, the three unmarked arrows from the rectangle 901 indicate the common structural element "R-1" and the common structural element "R-1".
2”, shown as connected to the common structural element “R-3”.

The common structural element data corresponding to the rectangle 903 is 708 (common structural element "R-1-2").

The constraint information of the common structural element “R-1-2” is ¥(R-1
-2-1) (2).

``¥3'' indicates the repetition of the pattern described in the list.

Therefore, this notation is the common structural element "R-1-2"
The structural elements constrained by the common structure requirement i″R-1-2-
It shows that it has a direct structure consisting of repeating structural elements constrained to 1''.

This means that in FIG. 9, from the rectangle 903
The arrow labeled “t” is the common structural element “R-
1-2-1'.

The common structural element data corresponding to the rectangle 904 is 703 (common structural element "R-3-1").

The constraint information of the common structural element “R-3-1” is φ(R-3
-1-1, R3-1-2) (3).

"φ" indicates that one of the items described in the list is selected.

Therefore, this notation is the common structural element "R-3-1"
(Structural element constrained by common structural element "R-3-1-1") or (Structural element constrained by common structural element "R-3-1-2") This indicates that it has a direct structure of either type.

This means that in FIG.
The arrow labeled “e” indicates the common structural element “R-3”
-1-1" and the common structural element "R-3-12".

FIG. 10 is an explanatory diagram showing the contents of the logical structure information shown in FIG. 8 in a graph.

However, connections between structural elements and document components are not illustrated.

In the figure, rectangles represented by 1001 indicate structural elements.

The structural element identifier of each structural element is shown at the top of the rectangle, such as 002.

Further, a common structural element identifier of a common structural element that constrains each structural element is shown in the middle of the rectangle, such as 1003.

The bottom row of the rectangle is the name of the structural element described in the other information 406 section.

The common structural element constrained by structural element 1001 (structural element "r") is 901 (common structural element "R") (common logical structure identifier of paper A, "common logical structure" paper shown in FIG. 9). class”, and the structural element “r”
The common structure element is specified by the common structure element identifier).

Therefore, the structure immediately below the structural element "r" is $ (R-1
, R-2, R-3) (4).

The structural element data of structural element "r" is 809.

The structure data immediately below the structure element data 809 includes (r-1
, r-2, r-3).

The structure element with the identifier "r-1" is 1004, and the constraint on the structure element "r-1" is the common structure element "R-1".
” is.

The structural element with the identifier "r-2" is 1005, and the common structural element "R-2" constrains the structural element "r-2".
” is.

The structure element with the identifier "r-3" is 1006, and the constraint on the structure element "r-3" is the common structure element "R-3".
” is.

Therefore, the structure immediately below the structural element "r" satisfies the constraint information possessed by the common structural element that constrains this structural element.

The common structural element that constrains the structural element 1007 (structural element "r-1-2") is the common structural element 903 (common structural element "R-1-2").
2″).

Therefore, the structure immediately below the structural element "r-1-2" is constrained by the description ¥(R-1-2-1) (5).

The structural element data of structural element "r-1-2" is 810. In the structure data directly below the structure data 810, (r-1-2-1) is written.

The structural element with the identifier "r-1-2-1" is 1008, and the common structural element "R-1-2-1" constrains the structural element "r-1-2-1".

Therefore, the structure immediately below the structural element "r-1-2" satisfies the constraint information possessed by the common structural element that constrains this structural element.

The common structural element that constrains structural element 1009 (structural element "r-3-1") is 904 (common structural element "R-3-1").
″).

Therefore, the structure immediately below the structural element "R-3-1" is constrained by the description φ(R-3-1-1, R-3-1-2).

The structural element data of structural element "r-3-1" is 811.

The structure data immediately below the structure element data 811 includes (r-3-
1-1).

The structural element with the identifier "r-311" is 1010, and the common structural element "R-3-1-1" constrains the structural element "r-3-1-1".

Therefore, the structure immediately below the structural element "r-3-1" satisfies the constraint information possessed by the common structural element that constrains this structural element.

The common structural element that constrains the structural element 1010 (structural element "r-3-1-1") is 905 (common structural element "R-
1-1-1'').

Constraint information of common structural element "R-3-1-1" is nil"
It is.

This indicates that the structural element constrained by the common structural element "R-3-1-1" does not have a direct subordinate structure.

Therefore, the direct structure data of the structural element "r-3-1-13" is ni1.

Instead, the document component is connected under the structural element "r-3-1-1".

As shown in FIG. 8, a document component having a document component identifier "5. Paper A" is connected to the structural element "r-3-1-1".

FIG. 11 is an explanatory diagram of the contents of a common logical structure having a common logical structure identifier called "paper abstract class" stored in the common logical structure storage section.

FIG. 12 is an explanatory diagram of the contents of the logical structure information section included in the electronic document having the document identifier "Paper Abstract A" stored in the electronic document storage section.

FIG. 13 is an explanatory diagram showing the contents of the common logical structure shown in FIG. 11 in an easy-to-understand graph.

FIG. 14 is an explanatory diagram showing the contents of the logical structure information shown in FIG. 12 in a graph.

However, connections between structural elements and document components are not illustrated.

FIG. 15 is an explanatory diagram of the contents of the logical structure generation program having the identifier "Paper Abstract Generation" stored in the logical structure generation program storage unit, and 1501 is the logical structure generation program identifier; ” is stored.

Reference numeral 1502 is an output common logical structure designation section, which specifies that the common logical structure that constrains the logical structure generated by this logical structure generation program has an identifier of "article abstract class."

1053 is an input common logical structure specification part, and the logical structure that is input to this logical structure generation program is a "paper class".
It is specified that there are two types of constraints: one is constrained by a common logical structure with the identifier ``paper abstract class,'' and the other is constrained by a common logical structure with the identifier ``paper abstract class.''

Reference numeral 1504 is a structural element generation rule section, and 1505 represents individual structure element generation rules.

1507 is a content part generation rule part, and 1508 is representative of the content part generation rule.

FIG. 16 is an explanatory diagram of an automatic logical structure generation window displayed on the display unit 102 for the user to specify a logical structure generation program, and an example of its input. A logical structure automatic generation window is displayed on the display unit 102 to allow the user to specify the logical structure generation program stored in the generation program storage unit 106, and 1601 is a logical structure automatic generation window, and 1602 is a logical structure automatic generation window when the user uses a mouse or the like. An end button 603 for instructing the end of input through the pointing device is a logic structure generation program identifier description field for the user to write the identifier of the logic structure generation program.

In addition, in the same figure (b), "paper abstract generation" is entered by the user in the logical structure generation program identifier description field 1603.
This is an example where the identifier is written.

Figure 17 shows an electronic document specification window and its window for specifying the identifier of an electronic document with a logical structure to be input and the identifier of an electronic document with a logical structure to be output after the user completes the input in the logical structure automatic generation window. FIG. 6 is an explanatory diagram of a display example, in which (a) is a logical structure automatic generation window 160;
1 is a diagram illustrating an electronic document designation window for the user to specify an identifier of an electronic document having a logical structure to be input and an identifier of an electronic document having a logical structure to be output after completing the input in step 1.

1701 is an electronic document specification window, and 1702 is an end button for the user to instruct to end input through a pointing device such as a mouse.

1703 is a logical structure generation program identifier display area in which the identifier of the logical structure generation program to be executed is displayed, and this identifier matches the logical structure generation program identifier specified by the user when inputting the logical structure automatic generation window 1601. .

1704 is a logical structure generation program identifier display section 170
This is an input common logical structure identifier display area in which an identifier of a common logical structure that constrains the logical structure that is input to the logical structure generation program displayed in 3 is displayed, and its contents are as follows:
This matches the contents of the input common logical structure designation section of the logical structure generation program displayed in 03.

1705 is a logical structure generation program identifier display section 170
This is an input electronic document identifier description field for the user to specify the identifier of an electronic document with a logical structure that will be input to the logical structure generation program displayed in 3, and the electronic document data of the electronic document specified in the field. The common logical structure identifier included in the input common logical structure identifier must match the common logical structure identifier displayed in the input common logical structure identifier display section 1704.

When there are multiple logical structures that can be input to the logical structure generation program displayed in the logical structure generation program identifier display section 1703, that is, the logical structure generation program identifier display section 170
If multiple common logical structure identifiers are described in the input common logical structure specification section of the logical structure generation program displayed in 3, the pairs of input common logical structure identifier display section and input electronic document identifier description field are also the same. There are only a few.

1706 is a logical structure generation program identifier display section 170
This is an output common logical structure identifier display section in which an identifier of a common logical structure that constrains the logical structure that is the output of the logical structure generation program displayed in 3 is displayed, and its contents are as follows:
This matches the content of the output common logical structure designation section of the logical structure generation program displayed in 03.

1707 is a logical structure generation program identifier display section 170
This is an output electronic document identifier description field for allowing the user to specify the identifier of a new electronic document having a logical structure that is the output of the logical structure generation program shown in 3.

When there are multiple logical structures that are the output of the logical structure generation program displayed in the logical structure generation program identifier display section 1703, that is, the output common logical structure of the logical structure generation program displayed on the structure generation program identifier display section 1703. When multiple common logical structure identifiers are described in the specification section, the same number of pairs of output common logical structure identifier display section and output electronic document identifier description field also exist.

Figure 17(b) shows that the logical structure automatic generation window is
6 is a display example of the electronic document designation window that is displayed when the screen is as shown in FIG. 6(b).

Further, FIG. 17(c) is an example in which each field of the electronic document designation window of FIG. 17(b) is filled in by the user.

FIG. 18 shows a new electronic document logical structure, document parts, and connection of the logical structure and document parts from the logical structure of an existing electronic document, document parts, and the connection of the logical structures and document parts by the logical structure automatic generation device. 12 is a flowchart showing the flow of processing when automatically generating .

FIG. 19 shows step 181 of the flowchart in FIG.
2 “Generation of new logical structures, document parts, and their connections”
FIG.

FIG. 20 is an explanatory diagram for explaining the process of generating a new logical structure according to the flowchart of FIG. 19, and shows the common logical structure identifier and the state of the logical structure.

FIG. 21 is a graph showing the contents of the common logical structure "paper abstract class (revised)" stored in the common logical structure storage unit 105.

FIG. 22 shows step 181 of the flowchart in FIG. 18.
2 “Generation of new logical structures, document parts, and their connections”
20 is a flowchart of an example different from that shown in FIG. 19, showing the flow of processing in the part shown in FIG.

Below, the common logical structure is the "paper class" shown in Figure 7, and the logical structure, document parts, and the logical structure and document parts of the electronic document "Paper A", which has the logical structure shown in Figure 8. The connection and common logical structure is the "Paper Abstract Class" shown in Figure 11, and the logical structure, document parts, and the logical structure of the electronic document "Paper Abstract A" with the logical structure shown in Figure 12. From the connection of the document parts and the logical structure generation program 1, the common logical structure is
A new electronic document that is a “paper abstract class” illustrated in the figure.”
The flow of the automatic logical structure generation process will be described with reference to the flowchart of FIG. 18, taking as an example the case where the logical structure of "Paper Abstract B", document parts, and connections between the logical structures and document parts are automatically generated.

Here, the common logical structures “paper class” and “paper abstract class” are stored in the common logical structure storage unit 105, and the electronic documents “paper A” and “paper abstract A” are stored in the electronic document storage unit 104. It is assumed that the logical structure generation program “Paper Abstract Generation” is stored in the logical structure generation program storage unit 106.

When the logical structure automatic generation processing unit 107 is instructed to automatically generate a logical structure, a document component, and a connection between a logical structure and a document component by a user input from the input unit 101 or by other means, a logical structure is displayed on the display unit 102. An automatic structure generation window 1601 is displayed (step 1801).

When the user inputs the identifier of the logical structure generation program in the logical structure generation program identifier field 1603 and instructs to finish the input (step 1802),
The logical structure generation program having the identifier written in the logical structure generation program identifier field 1603 is read from the logical structure generation program storage section 106 into the logical structure automatic generation processing section 107 (step 1803).

In this example, the identifier of the logical structure generation program used for the automatic logical structure generation process is "Paper Abstract Generation", so the automatic logical structure generation window is entered as shown in Figure 16(b), and the The logical structure generation program having the identifier “paper abstract generation” shown in FIG. 15 is read into the logical structure automatic generation processing unit 107.

The logical structure generation program is the logical structure automatic generation processing section 10.
7, it is checked whether the common logical structure necessary for executing the logical structure generation program is stored in the common logical structure storage unit 105 (step 1804).

If the necessary common logical structure does not exist, a message warning of this is displayed on the display unit 102 (step 1808), and the automatic logical structure generation process ends.

If a necessary common logical structure exists, the common logical structure is read from the common logical structure storage unit 105 into the logical structure automatic generation process 107 (step 1805).

In the logical structure automatic generation device of this embodiment, a common logical structure that constrains the logical structure of an input electronic document and an output electronic document is necessary to execute the logical structure generation program.

Therefore, its presence or absence can be investigated.

These common logical structure identifiers are held in an output common logical structure designation section 603 and an input common logical structure designation section 604 that are output from the logical structure generation program 610.

In the case of this process, the output common logical structure specification section of the logic structure generation program "Paper Abstract Generation" contains the "paper abstract class," and the input common logical structure specification section contains the "paper class."
- It is checked whether the identifier "paper abstract class" is written and a common logical structure having the identifier "paper class" or "paper abstract class" is stored in the common logical structure storage unit 105.

The common logical structure with the identifier “paper class” is the seventh
The common logical structure having the identifier "paper abstract class" is shown in FIG.

Since both of these are stored in the common logical structure storage unit 105, the common logical structures “paper class” and “paper abstract class” are read into the logical structure automatic generation processing unit 107.

After that, an electronic document specification window 170 is displayed on the display unit 102.
1 is displayed (step 1806).

At that time, the logical structure generation program identifier display section 1703
In step 1803, the logical structure automatic generation processing unit 107
The identifier of the logical structure generation program read in is displayed, and the input common logical structure identifier display section 1704 and the output common logical structure identifier display section 1706 each display the identifier held in the input common logical structure specification section 604 of the logical structure generation program. The contents held in the output common logical structure specifying section 603 are displayed.

In the case of this processing example, since the logical structure generation program read into the automatic logical structure generation processing unit 107 is shown in FIG. 15, the display is as shown in FIG. 17(b).

Electronic document identifier description field 17 input by user
05, the identifiers of the electronic documents to be input and output of the logical structure generation program are respectively input to the output electronic document identifier description field 1707, and when the end of input is instructed (step 1807), the input electronic document identifier description field 1705 is inputted. It is checked whether an electronic document having the written identifier is stored in the electronic document storage unit 104 (step 1809).

If it is not stored, a message warning of this is displayed on the display unit 102 (step 1814),
The logical structure automatic generation process ends.

If the electronic document is stored, the electronic document is read from the electronic document storage unit 104 into the logical structure automatic generation processing unit 107 (step 1810).

When the user makes an input as shown in FIG. 17(C), the electronic document with the identifiers “Paper A” and “Paper Abstract A” is stored in the electronic document storage unit, so the electronic document has a logical structure automatically. The data is read into the generation processing unit 107.

After the electronic document is read into the logical structure automatic generation processing unit 107, the identifier of the common logical structure that constrains the logical structure of the electronic document, that is, the common logical structure identifier in the electronic document data of the electronic document and the logical structure generation program It is checked whether the identifiers held in the input common logical structure specification section of the input common logical structure specifying section match (step 1811). If they do not match, a message warning about this is displayed on the display section 102.
is displayed (step 1815), and the logical structure automatic generation process ends.

If they match, a new logical structure, a document component, and a connection between the logical structure and the document component are automatically generated (step 1812).

When the generation of a new logical structure, document component, and connection of the logical structure and document component is completed, it is stored in the electronic document storage unit 104 as a new electronic document (step 181
3).

The identifier of the electronic document at this time is the output electronic document identifier description field 1707 of the electronic document specification window 1701.
This is what was described in .

Further, among the data of the electronic document, data that is not yet set, such as the layout and structure, is stored as unset, and is set later by means such as automatic layout processing or editing by the user.

Next, based on the same processing example, the method of "generating new logical structure 1 document parts and their connections" in step 1812 will be explained according to the flowchart of FIG. 19.

The generation of a logical structure in this embodiment is the generation of structural elements that constitute the logical structure.

As shown in FIG. 4, each structural element consists of a structural element identifier, a common structural element identifier, immediate structural data, document component data, and other information.

Among these, the structural element identifier is automatically determined according to the tree structure to be generated.

First, a structural element corresponding to the root node of the logical structure is generated (step 1901).

The identifier of the structural element corresponding to the root node is "r".

In this processing example, the structural element corresponding to the root node is constrained by the common logical structure "paper abstract class" common structural element 1101 shown in FIG.

Therefore, the common structure element identifier is the common structure element 110
1 is the identifier “R”.

Direct structure data is not set at this point, and “no-1”
nfo''.

Further, the document component data is set to "nil" at this point.

In this embodiment, the other information 406 section holds a name set to aid the user's understanding.

In the logical structure automatic generation process, this name is assumed to inherit as it is the name set in the other information part of the common structure element that constrains the structure element.

Therefore, for the structural element corresponding to the root node,
The same information as the content of the other information part of the common structure element 1101, ``name→article abstract'', is set.

At this point, the state of the common logical structure identifier and logical structure of the newly generated "paper abstract B" is as shown in FIG. 20<a).

Next, a search is made for an unset structural element in the direct structure, that is, a structure element whose direct structure data is "no-1nfo" (step 1902).

If such a structure element does not exist, the generation of the logical structure ends.

If it exists, one of such structural elements is selected (step 1903), and the immediate structure is set.

In this process, the structure element "r" (20
02), the structure immediately below it is set.

The structural element selected in step 1903 is first checked to see if there is a structure immediately below it (step 1904).

Its presence or absence is determined by whether ni1'' is held in the constraint information of the common structural element that constrains the structural element.

If it is "nil", there is no direct structure in the structural element, and its direct structure data is "ni1" (step 1905).

Next, for structural elements that do not have a direct structure, the document component data of the structural element is set when the structural element has a document component (step 1906).

Setting the document component data involves generating a document component by copying the document component of the input electronic document, and adding a list of the document component identifiers of the generated document component to the structure element that is the target of the document component data settings. This consists of setting the document part data of

Setting of document component data is performed by selecting and evaluating the logical structure generation program content generation rules shown in FIG.

The selection/evaluation method is similar to the selection/evaluation method for structural element generation rules described later, but since the details are outside the scope of the present invention, the explanation will be omitted. ), it is assumed that "?" is set as a rule.

In step 1904, if the information held in the constraint information of the common structural element that constrains the structural element is not "nil", a direct subordinate structure exists, and the direct subordinate structure is set in steps 1907 and subsequent steps.

The common structural element that constrains (2002) with the structural element "r" can be found from the common logical structure identifier "paper abstract class" in Figure 20 (a) and the structural element identifier "R" of the structural element "r". In addition, the common structural element "R" (
1101), and the common structural element "R" (1101)
has constraint information, so structure element “r” (2002) has a direct subordinate structure.

When setting the direct subordinate structure, first, it is determined whether the structural element generation rules written in the logical structure generation program need to be applied to the determination of the direct subordinate structure (step 1907).

Its necessity is determined based on information on common structural elements that constrain the determined structural elements of the immediate structure.

The constraint information is described by a descriptor of "$", "\", "ψ" followed by a list of common structural element identifiers, or "nil".

If the constraint information is "nil", it is excluded by the determination in step 1904, and step 1907 is not applied.

If the constraint information is a "$" descriptor followed by a list of common structure element identifiers, if you create a sequence of structure elements corresponding to the list of common structure element identifiers, it will become the direct structure, so the structure element There is no need to apply production rules.

If the constraint information is a "\" descriptor followed by a list of common structure element identifiers, it means that the immediate structure is a structure in which the sequence of structure elements corresponding to the list of common structure element identifiers is repeated. The number of repetitions must be determined by the structure element generation rules.

If the constraint information is a "ψ" descriptor followed by a list of common structure element identifiers, the immediate structure consists of structure elements that are constrained by one common structure element in the list of common structure element identifiers. This means that which common structural element to select must be determined by the structural element generation rule.

As a result of determining the necessity of applying structural element generation rules, if it is determined that it is not necessary, apply the structural element generation rule based on the constraint information of the common structural element that constrains the structural element whose immediate subordinate structure is to be determined. A structural element that is a child node is generated, and a list of identifiers of the structural element that is a child node is set in the immediately subordinate structure data of the structural element whose immediate subordinate structure is to be determined (step 1908), and the process returns to step 1902.

However, at this time, the direct structure data of the structure element which is the newly generated child node is "no-1nfo".

If it is determined that there is a need to apply a structural element generation rule, it is determined which structural element generation rule to apply (step 1909).

The constraint information of the common structural element “R” (1101) that constrains the structural element “r” (2002) is ¥ (R-1)
(7), it is necessary to apply the structural element generation rule.

The structure element generation rules applied to determine the immediate structure are the structure element designation notation that expresses the structure element whose immediate structure is being determined, and the output structure element specification part held in the structure element generation rule. Determined by the structural element specification description.

According to the BNF notation, the structural element designation notation has the following format.

<Structural element specification notation> Here=〈Structural element specification section〉@ <Identifier of common logical structure> : <I/O identifier>.

Structural element instruction section Here = <Structural element designator> 1. Structural element designator.

Structural element instruction section>

Structural element designator Here = <Identifier of common structural element> #<Natural number> 1 <Identifier of common structural element.

input/output identifier)::=il.

For example, “paper abstract A” which is the input electronic document for this processing example.
The structural element designation notation for the structural element "1-3-2" included in the logical structure is R1-3-112, R-1-3#1. R-1#1゜R@Paper Abstract Class: i (9).

The ``bi'' at the end is an input/output identifier and indicates that the structural element designation is related to the logical structure of the input electronic document.

If the input/output identifier is "0", the structural element designation is related to the logical structure of the electronic document to be output.

The description "paper abstract class" immediately after "@" is an identifier of a common logical structure that constrains the logical structure including the structural element expressed by the structural element designation notation.

@Dissertation abstract class: i The notation (10) indicates that the logical structure including the structural element expressed by this structural element directive notation is the logical structure of the input electronic document and is constrained by the common logical structure "Dissertation abstract class". It can be seen that the

R-1-3-1 #2. R-1-3#1. R-1#1. The R part is a structural element designation part in which structural element designators are connected by ",", and the structural element designation notation starts from the structural element which is the root node of the logical structure containing the structural element expressed by the structural element designation notation. It expresses the logical structural route to reach the expressed structural element.

The structural element designator "R" on the rightmost side of the formula (11) indicates "
It refers to something that is constrained by a common structural element with an identifier "R", that is, a structural element "r' (root node)."

The rightmost structural element designator in the structural element designation section always describes the identifier of a common structural element that constrains the root node of the logical structure that includes the structural element expressed by the structural element designation notation.

Each structural element designator other than the rightmost structural element designator in the structural element designator is a structural element included in the structure immediately below the structural element designated by the structural element designator to the right of the structural element designator. Refers to one of the following.

For example, R-1#1 in formula (11). R-1 #1” in the R(12) part is restricted by a common structural element with an identifier “R-1” among the structural elements included in the structure immediately below the structural element specified by 'R1. Among them, the first one on the list that represents the immediate structure ("#1
”).

Therefore, it refers to the structural element "r-1" included in the logical structure of "paper abstract A".

Similarly, R-1-3 #1 of formula (11). R-1#1. In the R part, the structural element "r-1-3" is specified, and the structural element designation notation (
10) Specify the structural element "r-1-3-2" for the whole.

In this way, the structural element designation notation is a path on the logical structure to reach the structural element expressed by the structural element designation notation from the structural element corresponding to the root node of the logical structure. is expressed by sequentially specifying the structural elements on the path using structural element designators.

The structural element designation notation can be specified for all structural elements on the logical structure, and only one structural element can be specified.

When the structural element 2002 is expressed using structural element designation notation, it becomes R@paper abstract class: o (14).

The structural element specification description written in the output structural element instruction part held in the structural element generation rule describes conditions for the above-mentioned structural element specification notation.

Therefore, the structure element generation rule is applied only to the setting of the structure immediately below the structure element expressed by the structure element specification notation that meets the conditions set in the structure element specification description written in the output structure specification part.

Structural element generation rule “rulel” included in the logical structure generation program “Paper Abstract Generation” shown in Figure 15
The structure element specification description of the output structure element specification section (1505) is No=R@paper abstract class: o (15).

This indicates that the structural element generation rule "rule" is applied only to the determination of the immediate structure of the structural element specified by the structural element designation notation R@paper abstract class: o (16).

Therefore, to determine the structure immediately below the structural element 2002,
The structural element production rule "rulel" is applied.

"No" is called a generation variable and indicates a structure element associated with the condition set in the description below "-" in the structure element specification description when applying the structure element generation rule.

This also applies to the generated variable "Nbi" included in the input structure specification section structure element specification description G.

The production variables are used in the production rules of the structure element production rules.

The description number of the output structure element specification part of the structure element generation rule "rule2" (1506) included in the same logical structure generation program "Paper Abstract Generation" is No.=R-1-2#1.
R-1#x, R@paper abstract class: O na X ≦ count (R@paper abstract class: 1).

This means that the structure element generation rule "rule2" is R-1-
2#1. R-1#x, R@ This indicates that it is applied to the determination of the immediate structure of the structural element specified by the structural element designation notation called Paper Abstract 20.

Here, there is a variable called x.

Such variables can be any natural number within certain conditions.

The condition is described after "and" in the same structure element specification description. In formula (17), X≦c o u n t
It is described as (R@Paper Abstract Class: 1).

The function count (a) (20) indicates the number of identifiers of structural elements included in the structure immediately below the structural element specified by “a”.

Therefore, if the value of count (R@paper abstract class: 1) is 3, then X can be any of 1, 2, and 3.

At that time, the structure element generation rule "rule2" is R-1-2 #1 when x=1. R-1#1. R @ Paper abstract class: 0 When x=2, R-1-2 #1. R-1#2. R @Paper Abstract Class: 0 When x=3, R-1-2 #1. R-1#3. R @Paper Abstract Class 20 This is applied to the determination of the immediate structure of a structural element specified by any of the structural element designation notations.

In addition, the value of X" when it is decided that such a structure element generation rule will be applied will be used later when determining the structure element pointed to by the generation variable 'Ni' in the input structure element specification section description. .

When the structural element generation rule to be applied is determined, the structure element generation rule is evaluated to determine the immediate structure (step 1910).

The evaluation of the structural element generation rule consists of (1) determination of the structural element pointed to by the generation variable "Ni" based on the structural element specification description of the input structure element specification section; and (2) evaluation of the generation rule.

First, the structural element pointed to by the generation variable "Nbi" in (2) is determined.

The structure element specification description written in the input structure element specification part of the structure element generation rule describes conditions for the structure element specification description, similar to the structure element specification description written in the output structure element specification part.

That is, the structure element realized by the structure element designation notation that matches the structure element designation description written in the input structure element designation part is what the generated variable "Nbi" points to.

In determining the structure immediately below the structure element 2002, the applied structure element generation rule "rulel" (1505
), the structure element specification description of the input structure element specification section is N1=R@paper abstract class: i (22>).

Therefore, the structural element specified by the structural element specification notation R@Paper Abstract Class:i (23) becomes the structural element pointed to by the generated variable "Ni".

Such a structural element is the structural element "r" (
1201).

Also, the structure element specification description N1=R12#1 of the input structure element specification section of the structure element generation rule "rule2" (1506) of the logical structure generation program "Paper Abstract Generation". R-
The variable "X" is sometimes used, as in 1#x,R.

At this time, the variable "X" always appears in the structure element specification description of the output structure element specification part of the structure element generation rule, and the variable "X" is determined when determining the structure element generation rule to be applied. The value of is used as is.

After the structure element pointed to by the generation variable “Ni” is determined by the input structure element specification description, the generation rule is evaluated (■),
The structure immediately below the structural element on the output side is determined.

In determining the immediate structure of the structural element 2002, the description of the production rule of the structural element production rule “rulel” that is applied is count (No)=count (Ni)+1.

This is the number of structure element identifiers included in the structure immediately below the structure element specified by the generated variable "NO".
(No)) is the number of structure element identifiers (count
t (Ni)).

The structural element specified by this generation variable “Ni” is structural element 1201, and the evaluation value of count (Ni) is 1.

therefore, count (No) becomes 2.

The structure element 2002 is constrained by the common structure element 1101, and its immediate structure is constraint information ¥(R-1)
(26), the common structural element “R-
1” (1102), so the structure element 200
2 is determined to be a list consisting of two structure elements constrained by the common structure element 1102, and after generating two structure elements constrained by the common structure element 1102, the list of their identifiers is It becomes a structure.

However, at this time, the direct structure data of the newly generated structural element is "no-1nfo".

At this point, the state of the common logical structure identifier and logical structure of the newly generated "paper abstract B" is as shown in FIG. 20(b).

In FIG. 20(b), the common structural element “R-1” (1102
) is “r-1” (2005),
Two “r-2” (2006) are created, and the list of identifiers (r-1, r-2) becomes the structure data directly under the structure element 2002.

At this time, the identifier of structure element 2005.2006 is "r-1"
",""r-2" are automatically set according to the tree structure to be generated.

As a result, the structural element 2002 becomes like 2004.

When the evaluation of the generation rule (2) is completed, the process returns to step 1902 to confirm the existence of an unset structure element in the immediate structure, that is, a structure element whose direct structure data is "no-1nfo".

Hereinafter, the process of generating the logical structure of the electronic document "paper abstract B" will be explained step by step starting from the state shown in FIG. 20(b).

Step 1902: Structural elements are “r-1” and “r-2”
Since the direct structure data of is "no-1nfo", the process advances to step 1903.

Step 1903: Select structural element "r-1".

Step 1904: The common structural element that constrains the structural element “r-1” is “R-1” of the common logical structure “paper abstract class”.
” and has constraint information.

Therefore, since the structure element "r-1" has a structure immediately below it, the process advances to step 1907.

Step 1907: The constraint information of the common structure element “R-1” of the common logical structure “paper abstract class” is $ (R-1-1
, R-1-2, R-1-3).

Therefore, there is no need to apply structural element production rules. Proceed to step 1908.

Step 1908: Structural elements “r-1-1”, “r-1-2”, and “r-13” are generated according to the constraint information of the common structural element “R-1” of the common logical structure “paper abstract class” The common logical structure identifier and the state of the logical structure of the electronic document "Paper Abstract B" are as shown in FIG. 20(c).

Return to step 1902.

Step 1902: Structural element "r-1-1", r-1-
2”, “r-1-3”, and r-2” structure data is “
no-4nfo'', step 1903
fart.

Step 1903: Select structural element "r-1-1".

Step 1904: The common structural element that constrains the structural element “r-1-1” is the common logical structure “R-
1-1'' and has no constraint information.

Therefore, the structure element "r-1-1" has no structure immediately below it, so the process advances to step 1905.

Step 1905.1906: Structural element "r-1-1"
The direct structure data of is "nil", and the document part data is "?"
”. Return to step 1902.

Step 1902: Structural elements "r-1-2", "r-1"
-3", the direct structure data of 'r-2" is no-1nfo
”, the process advances to step 1903.

Step 1903: Select structural element "r-1-2".

Step 1904: The common structural element that constrains the structural element "r-1-2" is "R" of the common logical structure "paper abstract class".
-1-2'' and has constraint information.

Therefore, since there is a structure immediately below the structural element "r-1-2", the process advances to step 1907.

Step 1907: The constraint information of the common structure element "R-1-2" of the "common logical structure 1 paper abstract class" is ¥ (R-1-2-1) (28).

Therefore, it is necessary to apply structural element generation rules. Proceed to step 1909.

Step 1909: The structural element specification description representing the structural element "r-1-2" is R-1-2#1. '#R-1#1. R @ Essay Abstract Class 20.

Among the structure element specification descriptions in the output structure specification part of the structure element generation rule "rule 2", what is specified by R@paper abstract class: i (31) of X≦count (R@paper abstract class: 1) is: This is the structural element "r" (1201) in the logical structure of the electronic document "Paper Abstract A", and count (R@
Paper abstract class: i) ±1 Therefore, ``variable 1''X''
The set of numbers in is (1).

In the case of x-1, the structural element designation notation representing the structural element "r-1-2" conforms to the structural element specification description of the output structural element specification part of the structural element production rule "ruIe2', and the structural element production rule" The application of "rule2" is decided.

In step 1910 and step 1909, the generated variable "
It has been determined that “N o ” refers to the structural element “r-1-2” (2007).

Evaluation■〉Since the variable “Xゝ” in the structure element specification description in the output structure element specification part of the structure element generation rule “rule2” is 1, the generation variable “Ni” points to the structure element specification expression R-1 -2#1.R-1#1.R @Thesis abstract class: This is a structural element specified by 1.

This is the structural element “r-1-2” (1202
), and it is determined that the generated variable "Ni" refers to this.

<Evaluation ■> count (Ni) = 2 Therefore, count (No) = 2, and the number of structural elements included in the structure immediately below structural element "r-12" (2007) is determined to be two.

Structural element "r-1-2" (2007) is constrained by common structural element "R-1-2" (1103), and its immediate structure is constrained by constraint information ¥(R-1-2-1) (34). , is determined to be a list consisting of a sequence of structural elements constrained by the common structural element "R-1-2-1" (1104), so the list immediately below the structural element "r-1-2" (2007) The structure is determined to be a list consisting of two structural elements constrained by the common structural element "R-1-2-1" (1104), and the immediate structure is set.

At this point, the state of the common logical structure identifier and logical structure of the newly generated "paper abstract B" is as shown in FIG. 20(d). Return to step 1902.

Step 1902: "Structural element "r-1-2-1","
Since the direct structure data of r-1-2-2", "r-1-3", and 'r-2' is n0-info", the process advances to step 1903.

Step 1903: Select structural element "r-1-2-1".

Step 19Q4: The common structural element that constrains the structural element "r-1-2-1" is "R-1-2-1" of the common logical structure "paper abstract class" and has constraint information.

Therefore, since the structure element "r-1-2-1" has a structure immediately below it, the process advances to step 1907.

Step 1907: The constraint information of the common common structural elements “R-1 to 2-1” of the common logical structure “paper abstract class” is $ (R-1-2-1-1, R-1-2-1- be.

Therefore, there is no need to apply structural element production rules. Go to step 1908 Step 1908: Constraint to common structural element "R-1-2-1-1" according to constraint information of common structural element "R-1-2-1" of common logical structure "paper abstract class" Structural element "r-1-2-1-1", common structural element "R-1"
-2-1-2” structural element “r-1-2-1”
2'' is generated and becomes the structure immediately below the structural element "r-1-2-1". The process returns to step 1902.

Step 1902: Structural element "r-1-2-1-1",
"r-1-2-1-2", "r-1-2=2", "r
-1-3", the direct structure data of "r-2" is "no-1"
nfo”, the process advances to step 1903.

Step 1903: Select structural element "r-1-2-1-1".

Step 1904: The common structural element that constrains the structural element “r-1-2-1-1” is “R-1-2-1-1” of the common logical structure “paper abstract class” and has constraint information. do not have.

Therefore, since there is no structure immediately below the structural element "r-1-2-1-1", the process advances to step 19o5.

Step 1905.1906: Structural element "r-1-2-
The structure data immediately below “1-1” is “nil”.

Document part data file? ”. Return to step 19o2.

Step 1902: Structural element "r-1-2-1-2"
, "r-1-2-2", "r-1-3"
, since the direct structure data of "r-2" is "no-1nfo", the process advances to step 1903.

Step 1903: Select structural element "r-1-2-1-2".

Step 1904: The common structural element that constrains the structural element 'r-1-2-1-2' is the common logical structure 'R-1-2-1-2' of the 'paper abstract class' and does not have any constraint information. .

Therefore, since there is no structure immediately below the structural element "r-1-2-1-2", the process advances to step 1905.

Steps 1905, 1906: Structural element "r-1-
The direct structure data of "2-1-2" is "nil", and the document part data is "?". Return to step 1902.

Step 1902: Structural elements "r-1-2-2", r-
1-3", "r-2" direct structure data is no-1nf
o”, proceed to step E903.

Step 1903: Select structural element "r-1-2-2".

Step 1904: The common structural element that constrains the structural element 'r-1-2-2' is R-1-2-1'' of the common logical structure "paper abstract class" and has constraint information.

Therefore, since the structure element "r-122" has a structure immediately below it, the process advances to step 1907.

Step 1907: The constraint information of the common structural element "R-1-2-1" of the common logical structure "paper abstract class" is $ (R-1-2-1-1, R-1-1-1- .

Therefore, there is no need to apply structural element production rules. Proceed to step 1908.

Stesive 1908: Structural element "r-" that is constrained to the common structural element "R-1-2-1-1" according to the constraint information of the common structural element "R-12-1" of the common logical structure "Paper Abstract Class" 1-2-2-1”, common structural element “R-1-
2-1-2'' is generated.

Return to step 1902.

Step 1902: Structural element "r-1-2-2-1",
"r-1-2-22", "r-1-3", "r 2
Since the direct structure data of "," is "no-1nfo", the process advances to step 1903.

Step 1903: Select structural element "r-1-2-2-1".

Step 1904: The common structural element that constrains the structural element “r-1-2-2-1” is “R-1-2-1-1” of the common logical structure “paper abstract class” and has constraint information. do not have.

Therefore, since there is no structure immediately below the structural element "r-1-2-2-1", the process advances to step 1905.

Step 1905. '1906: Structural element "r-1-2
-2-1", the direct structure data is nil" and the document component data is "?". Return to step 1902.

Step 1902: Structural element “r-1-2-2-2”
, "r-1-3" and "r-2" are "no-1nfo", so step 190 is executed.
Go to 3.

Step 1903: Select structural element "r-1-2-2-2".

Step 1904: The common structural elements that constrain the structural element “r-1-2-2-2” are both il! The logical structure is ``R-1-2-1-2'' of ``paper abstract class'' and does not have constraint information.

Therefore, since there is no structure immediately below the structural element "r-1-2-2-2", the process advances to step 1905.

Steps 1905, 1906: Structural element "r-1-2-"
The direct structure data of "2-2" is "nil", and the document part data is "?" ”.

At this point, the state of the common logical structure identifier and logical structure in FIG. 20(d) becomes as shown in FIG. 20(e). Return to step 1902.

Step 1902: Structural elements "r-1-3", "r-2"
Since the direct structure data of " is "no-1nfO", the process advances to step 1903.

Step 1903: Select structural element "r-1-3".

Step 1904: The common structural element that constrains the structural element “r-1-3” is “R” of the common logical structure “paper abstract class”.
-1-3'' and has constraint information.

Therefore, since the structure element "r-1-3" has a structure immediately below it, the process advances to step 1907.

Step 1907: The constraint information of the common structure element “R-1-3” of the common logical structure “Paper Abstract Class” is ¥(R-1-
3-1) (37).

Therefore, it is necessary to apply structural element generation rules. Proceed to step 1909.

Step 1909: The structural element specification description representing structural element "r-1-3" is R-1-3#1. R-1#1. R @ Paper abstract class: 0.

Among the structure element specification descriptions in the output structure element specification part of the structure element generation rule "rule 4", X≦count (R@paper abstract class: 1)
The R@paper abstract class: i (40) specifies the structural element "r" (1201) in the logical structure of the electronic document "paper abstract A", and the count (R@
Paper abstract class: i) = 1 Therefore, 'variable'X
” if the number is (1).

When x=1, the structural element designation notation representing the plate structural element "r-1-3" is combined with the structural element specification description of the output structural element specification part of the structural element generation rule "rule 4", and the structural element generation rule The application of "rule 4" is determined.

Step 1910 In step 1909, the generated variable "N"
It is determined that "o" refers to the structural element "r-1-3" (2008).

Evaluation ■> Since the variable “X” of the structure element specification description in the output structure element specification part of the structure element generation rule “rule 4” is 1, the generation variable “Ni” points to the structure element specification description R-1 -3#1. R-1#1. This is a structural element specified by R @Paper Abstract Class: 1.

This corresponds to the structural element “r-1-3” (1203
), and it is determined that the generated variable "Ni" refers to this.

Evaluation ■> count (Ni) = 2 Therefore, count (No') = 2, and the number of structural elements included in the structure immediately below structural element "r-1-3" (2008) is determined to be two.

Structural element "r-1-3" (2008) is constrained by common structural element "R-1-3" (1105), and its immediate structure is constrained by constraint information ¥ (R-1-3-1) (43). , it is determined that the list consists of a sequence of structural elements constrained by the common structural element "R-1-3-11 (1106)," so the structure directly under the structural element "r-1-3" (200B) is determined to consist of two structural elements constrained by the common structural element "R-1-3-1" (1106), and the immediate structure is set.

At this point, the state of the common logical structure identifier and logical structure in FIG. 20(e) becomes as shown in FIG. 20(f). Return to step 1902.

Step 1902: Structural element “r-1-3-1”,”
The direct structure data of “r-1-3J” and “r-2” is “n”
o-1nfo'', the process advances to step 1903.

Step 1903: Select structural element "r-1-3-1".

Step 1904: The common structural element that constrains the structural element "r-1-3-1" is "R-1-3-1" of the common logical structure "paper abstract class 2" and does not have constraint information.

Therefore, since the structure element "r-1-3-1" has no structure immediately below it, the process advances to step 1905.

Steps 1905, 1906: Structural element "r-1-3-
The direct structure data of “1” is “nil”, and the document part data is “?” ”. Return to step 1902.

Step 1902: Structural elements "r-1-3-2", "r
Since the direct structure data of ``-2'' is 3no-info'', the process advances to step 1903.

Step 1903: Select structural element "r-1-3-2".

Step 1904: The common structural element that constrains the structure element i"r-1-3-2" is "R-1-3-1" of the common logical structure "paper abstract class" and does not have constraint information.

Therefore, since there is no structure immediately below the structural element "r-1-3-2", the process goes to 1905.

Steps 1905, 1906: Structural element "r-1-3-
The direct structure data of "2" is "nil", and the document part data is "?" ”. Return to step 1902.

Step 1902: Step 19
Go to 03.

Step 1903: Select structural element "r-2".

Step 1904: The common structural element that constrains the structural element “r-2” is “R-1” of the common logical structure “paper abstract class”
and has constraint information.

Therefore, since the structure element "r-2" has a structure immediately below it, the process advances to step 1907.

Step 1907: The constraint information of the common structure element “R-1” of the common logical structure “paper abstract class” is $ (R-1-1
, R-1-2, R-1-3).

Therefore, there is no need to apply structural element production rules. Proceed to step 1908.

Step 1908: Structure elements "r-2-1", "r-2-2", "r-2-3" according to the constraint information of the common structure element "R-1" of the common logical structure "paper abstract class" is generated, and the common logical structure identifier and the state of the logical structure of the electronic document "paper abstract B1" are as shown in FIG. 20(g).

Return to step 1902.

Step 1902: Structural elements “r-2-1”, ′″r-
2-2", the direct structure data of "r-2-3" is no-1
nfo', the process advances to step 1903.

Step 1903: Select structure requirement lA"r-2-1".

Step 1904: The common structural element that constrains the structural element "r-2-1" is "R" of the common logical structure "paper abstract class".
-1-1'' and has no constraint information.

Therefore, since there is no structure immediately below the structural element "r-2-1", the process advances to step 1905.

Steps 1905, 1906: Structural element "r-2-1"
The direct structure data of is "nil", and the document part data is "?"
”. Return to step 1902.

Step 1902: Structural element "r-2-2", r-2-
Since the direct structure data of ``3'' is ``no-1nfo'', the process advances to step 1903.

Step 1903: Select structural element "r-2-2".

Step 1904: The common structural element corresponding to the structural element "r-2-2" is "R" of the common logical structure "paper abstract class".
-1-2' and has constraint information.

Therefore, since there is a structure immediately below the structural element "r-2-2", the process advances to step 1907.

Step 1907: The constraint information of the common structural element "R-1-2" of the common logical structure "paper abstract class" is ¥ (R-1-2-1> (45)).

Therefore, it is necessary to apply structural element generation rules. Proceed to step 1909.

Step 1909: The structural element specification description representing the structural element "r-2-2" is R-1-2#1. R-1#2. R @ Paper abstract class: 0.

Among the structure element specification descriptions in the output structure element specification part of the structure element generation rule "rule 3", count (R@paper abstract class: i) +1 R@paper abstract class: i (48) is the structural element w r″ (1201) in the logical structure of the electronic document “Paper Abstract A”, and count (R
@Paper abstract class: i) = 1 Therefore, 'variable'
The set of numbers in χ” is (2).

In the case of x=2, the structural element designation notation representing the structural element "r-2-2" matches the structural element specification description of the output structural element specification part of the structural element production rule "rule 3", and the structural element production rule Application of "rule 3" is determined.

Step 1910 In step 1909, the generated variable "N"
It is determined that o'' refers to the structural element "r-22" (2009).

Evaluation ■> The generated variable “Ni” refers to the structural element specification notation R-1-2 #1. R-1#1. This is a structural element specified by R @paper class: 1.

This is the structural element "r-1-2" (810) included in the logical structure of the electronic document "Paper A" shown in FIG. 8, and it is determined that the generated variable "Ni" points to this.

Evaluation ■> count (Ni) = 1 Therefore, count (No) = 1, and the number of structural elements included in the structure immediately below the structural element "r-2-2" (2009) is determined to be one.

Structural element "r-2-2" (2009) is structural element"
R-1-2'' (1103), and its immediate structure is constrained by the constraint information \(R-1-2-1) (51), the common structural element "R-1-2-1" (Eng. 104) Since it is determined that the list consists of a sequence of structural elements constrained by ), and the immediate structure is set.

At this point, the state of the common logical structure identifier and logical structure of the newly generated "paper abstract B" is as shown in FIG. 20(h). Return to step 1902.

As a result of continuing the same process, the direct structure data is no.
-1nfo" is no longer present, and the generation of the logical structure ends.

At that time, the common logical structure identifier and the state of the logical structure of "Paper Abstract B" are as shown in FIG. 20(i).

The logical structure generation program structure element generation rules in this processing example have one structure element on the input side and output side, but the structure element generation rules are designed so that they can be written between multiple structure elements. It is also possible to configure the device.

For example, the logical structure is constrained by the common logical structure "paper abstract class (revised)" shown in FIG.

From an existing electronic document and an existing electronic document whose logical structure is constrained by the common logical structure "paper class" shown in Fig. 13, a new electronic document whose logical structure is constrained by the common logical structure '''(revised)' shown in Fig. 21. Consider a logical structure generation program that generates a logical structure.

There shall be no duplication in the abstract contents contained in the two existing electronic documents, and the output electronic document shall contain all of the abstract contents contained in the two existing electronic documents. do.

In this process, the common structural element "R-2" of the common logical structure "Paper abstract class (revised)" in Figure 21 is the 1ndex of the registered paper, and the number of items in the 1ndex is the paper summary. It must be the same as the number.

At this time, the structural element generation rule indicating this is: Structural element specification description No. 1 of the output structural element specification section = R-111, R@ Paper abstract class (revised):.

No. 2 = R-211, R@ Paper abstract class (revised) 20 Structural element specification description of input structural element specification section Ni1 = R-1 #1. R @ Paper abstract class (revised): 1Ni2=R
@Paper abstract class: i (62) Production rule count (Nol) = count (Nil) + count (Ni
2) count (No2) = count (Nil) + count (Ni
2).

In this description, there are multiple structural elements involved in generation on both the input and output sides, so there are multiple structural element specification descriptions in the output structure element specification part, multiple structure element specification descriptions in the input structure element specification part, and there are also generation variables. There are multiple.

They are distinguished by adding subscripts such as "Nol" and "No2".

In order to automatically generate a logical structure using a logical structure generation program having structure element generation rules described in this way, slightly modify the flowchart in FIG.
It is necessary to create a process flow as shown in the figure.

The process flow shown in FIG. 22 will be explained below.

The process flow in FIG. 22 is the same as the process flow in FIG. 19 up to step 2203.

In step 2203, a structural element generation rule to be applied is selected, but at this time, the structural element specification notation expressing the structural element selected in step 2201 is one of the structural element specification descriptions in the output structure element specification part that exists. If any one of these is met, that structural element generation rule will be applied.

At this point, one of the generation variables described in the structure element specification description of the output structure element specification section is determined as the structure element pointed to by the generation variable.

In step 2204, for the generation variables described in the structure element specification description of the output structure element specification part, for which the structure element pointed to by the generation variable has not yet been determined, the structure element corresponding to the generation variable is specified. It is checked whether a structural element exists that satisfies the conditions of the description.

If there is even one generation variable for which there is no structure element that satisfies the conditions of the structure element specification description, the structure element generation rule cannot be used repeatedly, and the process moves to step 2206.

In step 2206, it is checked whether there is an unset structure element in the immediate structure to which it has not been determined that all the structure element generation rules in the logical structure generation program cannot be applied.

If it does not exist, an error message will be displayed and the process will end.

If it exists, one unset structural element in the immediate structure to which it has been determined that the structural element generation rule cannot be applied is selected, and the process returns to step 2202.

If the structural element generation rule is applicable in step 2204, the structural element generation rule is evaluated, and the direct structure of the structural element for which all the generated variables described in the structural element specification description of the output structural element specification section are fingers is determined. be done.

The electronic document shown in this embodiment is close to an ODA-compliant document, and the present invention is particularly effective in processing a specific logical structure and content part of an ODA-compliant document.

In addition, the specific layout of an ODA-compliant electronic document is the structure, and the common layout that restricts the structure is the same data as the logical structure in this embodiment and the common logical structure that restricts the logical structure. It is possible to take a configuration.

Therefore, this embodiment can also be configured to generate a specific logical structure of a new ODA-compliant electronic document from the specific layout structure of an existing ODA-compliant electronic document.

[Effects of the Invention] As described above in detail, the document structure generation method of the present invention makes it possible to automatically generate the logical structure of a new electronic document from the logical structure of an existing electronic document.

This makes it possible to automate not only form processing but also the processing of general electronic documents, leading to significant labor savings in document processing, especially in offices.

[Brief explanation of drawings]

FIG. 1 is a block diagram schematically showing a logical structure automatic generation device for electronic documents to which the present invention is applied; FIG. 2 is an explanatory diagram of the data structure of electronic documents stored in an electronic document storage unit; The figure is an explanatory diagram of the data structure of the document component information section included in the electronic document data. Figure 4 is an explanatory diagram of the data structure of the logical structure information included in the electronic document data. Figure 5 is a common logical structure. FIG. 6 is an explanatory diagram of the data structure of the common logical structure data stored in the storage section. FIG. 6 is an explanatory diagram of the data structure of the logical structure generation program written in the logical structure generation program storage section. FIG. 7 is the common logic FIG. 8 is a content explanatory diagram of an example of a common logical structure stored in a structure storage unit; FIG. 8 is a content explanatory diagram of a logical structure information section included in an example of an electronic document stored in an electronic document storage unit; Figure 9 is an explanatory diagram showing the contents of the common logical structure shown in Figure 7 in a graph, Figure 10 is an explanatory diagram showing the contents of the logical structure information shown in Figure 8 in a graph, and Figure 11 is a common logical structure. The common logical structure stored in the storage section shown in FIG. 7 is another example of the content explanatory diagram, and FIG. 12 is different from the one shown in FIG. 8 that is stored in the electronic document storage section. Figure 13 is an explanatory diagram showing the contents of the common logical structure shown in Figure 11 as a graph. Figure 14 is the logical structure shown in Figure 12. An explanatory diagram showing the content of information in a tree structure; FIG. 15 is an explanatory diagram of an example of a logical structure generation program stored in the logical structure generation program storage unit; FIG. 16 is an explanatory diagram for allowing the user to specify a logical structure generation program. 17 is an explanatory diagram of the logical structure automatic generation window displayed on the display unit and an example of its input. FIG. 17 is an explanatory diagram of the logical structure automatic generation window displayed on the display unit and an example of its input. FIG. An electronic document specification window for specifying the identifier of an electronic document with a logical structure, its display example, and an explanatory diagram of an input example. FIG. 19 is a flowchart showing the flow of processing when creating a logical structure. FIG. is an explanatory diagram of the process in which a new logical structure is generated according to the flowchart in FIG.
FIG. 1 is an explanatory diagram that graphically shows the contents of an example of the common logical structure stored in the common logical structure storage unit, different from those shown in FIGS. 7 and 11, and FIG. 19 is a flowchart different from that shown in FIG. 19, which shows the processing flow of the "generation of new logical structure 1 document parts and their connections" part in the flowchart of FIG. 101... Input unit 102... Display unit 103... Input/output control unit 104... Electronic document storage unit 105... Common logical structure storage unit 106... Logical structure generation program storage unit 107...
・Logical Structure Automatic Generation Processing Department Applicant: Fuji Xerox Co., Ltd. Agent Yoji Onodera (1 other person) Figure 1 Figure 2 Figure 5 Figure 3 Figure 4 Figure 6 Section 9 Figure 13 repeat Figure 16 (a) Figure 16 (b) District 17 (a) jg 1 8 (k)) Figure 20 (sa) Figure 20 (b) Figure 21 Figure 22 (b)

Claims (2)

[Claims] (1) An electronic document that has a logical structure expressed by a connection of nodes that represents a structural grouping of document parts, and in which constraints on the possible connection states of nodes in the document's logical structure are defined as a common logical structure. In the document structure generation method, when outputting part or all of the logical structure of a new electronic document using the logical structure of an existing electronic document as input, an input common logical structure that constrains the logical structure of the input document and an output A generation rule that generates the logical structure of the document to be output from information on the logical structure of the input document is set in advance between the output common logical structure that constrains the logical structure of the document to be output. A document characterized in that information on a logical structure that satisfies the constraints of an input common logical structure is obtained from the logical structure of the logical structure, and based on this information, part or all of the logical structure that satisfies the constraints of the output common logical structure is automatically generated. Structure generation method. (2) A common logic that has a logical structure expressed by a tree structure that connects nodes that represent a structural grouping of document parts, and whose constraints on the logical structure of the document are templates of nodes that can appear on the tree structure. A document structure of an electronic document that is defined by a common logical structure expressed as a set of structural elements, and in which the common logical structural element describes constraints on a sequence of child nodes of a node whose model is the common logical structural element. In the generation method, when outputting part or all of the logical structure of a new electronic document using the logical structure of an existing electronic document as input, common logic included in the input common logical structure that constrains the logical structure of the input document is A sequence of child nodes that can be applied to a node whose model is a structural element and a sequence of child nodes that can be applied to a node whose model is a common logical structure element included in the output common logical structure that constrains the logical structure of the output document. A logical structure element generation rule is set in advance, which consists of a relationship between A document structure generation method characterized by automatically generating part or the entire logical structure of a document to be output from the structure.