JPH0844718A - Document processor - Google Patents

Abstract

PURPOSE:To provide the document processor which can maintain the consistency of common information by correctly reflecting addition, deletion, or update on sharing sources which share a common constituent element when the common constituent element is added, deleted, or updated at the time of document editing, etc. CONSTITUTION:A document management part 1-13 manages a document as a group of document constituent elements and manages information on the respective document constituent elements divisionally as an information part depending upon the document like document structure and an information part which does not depend upon the document like content information to enable the latter information part to be shared. A document constituent element retrieval part retrieves a document constituent element of the document stored in a document storage part 1-131. When the document constituent element retrieved by the document constituent element retrieval part is a document constituent element to be shared, a display part 1-4 displays the shared document constituent element on the basis of sharing management information to support decision making at the time of processing as to the common information.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a document processing apparatus which enables data sharing among a plurality of document data.

[0002]

2. Description of the Related Art Conventionally, when a similar document is created or the same figure or table is created for a plurality of documents, a method of copying an entire existing document or a part of the document and utilizing a necessary part Has been adopted (for example, JP-A-60-16
3144, Japanese Patent Laid-Open No. 4-76664). By incorporating the necessary parts from the existing document, you do not have to write the same sentence, figure, table, etc. many times,
The effect that the document can be created accurately or the time for creating the document can be shortened is obtained. In addition, when you try to create sentences, diagrams, etc. with the same content in multiple documents,
By pointing to the same contents in multiple documents using a pointer, etc., the contents of the documents can be shared, and in addition to accuracy and time reduction, the storage capacity can be reduced (for example, (Kaihei 4-348468). In addition, version management, in which a new document created and edited based on one document is associated with a version to manage the document, has become popular as a document management method.

[0003]

DISCLOSURE OF THE INVENTION Problems to be Solved by the Invention The above-mentioned prior arts (for example, JP-A-60-163144 and JP-A-4-76).
In the document editing method of Japanese Patent No. 664), a duplicate is automatically created at the time of editing and the duplicate is edited. Therefore, only the duplicated document for editing is the object of editing, and the result of the change due to the editing is not reflected in the document which is the source of the duplication. Even if the editing document is written back to the storage unit as a new file, only the reference relationship is written for the document components that refer to other documents, and the contents of the document components are shared with the document of the sharing destination. Since there is no way to write to the component of the above, when reading a new file later, the contents of the shared part can only refer to the contents before the editing, and cannot refer to the result of the change by the editing. Further, in the conventional technique described in Japanese Patent Laid-Open No. 4-34846, since the relationship of the logical structure of a document is managed in a table for each document, for example, a new section is added to a chapter shared by a plurality of documents. When you edit something like
There is a problem that the added section cannot be shared from other documents.

In general, when the same document constituent element is shared by a plurality of documents, the document constituent element includes information shared between documents and information different between documents. For example, consider document format information such as the type and size of character fonts used, color, and paragraph format. This appearance information may be different in multiple documents. Further, in addition to the appearance information of the entire document, there is appearance information attached to each paragraph, appearance information attached to characters, and the like. In a document system that supports these functions, when document components are shared among multiple documents as described above, control is performed including how to display the shared content for each document. If you do not
There is a problem that unified display as individual documents cannot be performed. Also, when considering the logical structure of a document other than the appearance information, when the same document constituent element is shared among a plurality of documents, it becomes a chapter in one document and a section in another document. There is a case.

Further, as a document management method, it has become common to manage document versions. Therefore, when document components are shared between a plurality of documents, document version management is required. There must be. However, in the above-mentioned conventional technique, since the version is not dealt with, there is a problem that it cannot be applied to a document system in which version management is performed. For example, if there is a sharing relationship between document components and the shared document is deleted suddenly, the shared document side will lose the shared document components and maintain the consistency of shared information. There is a problem that you cannot do it.

Further, in the prior art, when reusing documents such as sharing, it becomes a problem whether a part of the target document has a sharing relationship with other parts. Up to now, the above-mentioned JP-A-4-76664 has been proposed.
As in the technique described in Japanese Patent Publication, a method of displaying a reference portion or a shared portion so that the reference portion and the shared portion can be identified on the editor screen when the document is edited has been adopted. However, when using these methods, in order to search for a component of a document and determine whether or not to share the search result, it is necessary to display that part once and then make the determination. In the prior art, it is not possible to extract or store only the document component from the document storage unit, and it is necessary to extract or store the file of the document including the document component as a unit. There is a problem that it takes a very long time to make a decision and the work efficiency is low.
Further, when the copied or shared document is read back later, it is difficult to determine which part of the document is a duplicate or shared part of another document. Further, when a change occurs in the shared portion, it may be necessary to know the range of the effect of the change, but it has not been possible to know that in the past.

The present invention is intended to solve the problems of the prior art as described above. That is, the present invention relates to a document processing device that shares document components,
The purpose is to enable more efficient document creation. Further, the present invention, when editing a document,
To provide a document processing apparatus capable of accurately reflecting the edited result in a document of a sharing source and maintaining consistency of shared information when, for example, a shared document component is added, deleted, or updated. The purpose is. It is another object of the present invention to provide a document processing device capable of managing appearance information used when displaying shared document constituent elements. It is another object of the present invention to maintain the consistency of shared information even when document version management is performed. Another object of the present invention is to provide a means for efficiently supporting the determination of reuse of document components.

[0008]

A document processing apparatus according to the first invention comprises a document management unit (1-13) for managing a document composed of document components and a document component managed by the document management unit. Document storage means (1-
131) and. Then, the document management means manages the information of each document constituent element in the document composed of the document constituent elements separately into a document-dependent information portion and a document-independent information portion, and manages the same document contents between documents. In order to share, it has a means for sharing an information part that does not depend on the document in the document component to be shared.

Further, the document processing apparatus of the second invention is a document management means (1-1 for managing a document composed of document constituent elements.
3) and a document storage means (1-131) for storing a document composed of document constituent elements managed by the document management means. Then, the document management means manages the information of each document constituent element in the document composed of the document constituent elements by dividing into a document-dependent information portion and a document-independent information portion, and a plurality of documents have the same document content. A first means for sharing an individual document-independent information part of the document component which is the top of the subtree formed by the document components to be shared in order to share the document component below Multiple versions of each document are managed in a tree structure, each node is a version, and each document is a sequential tree with a version of the node sequence obtained by tracing the eldest son from a node with a root or elder brother. Of the document component of the document under version management by using the second means for managing the derivation relationship of the version by the version management information of the document and the shared management information including the version information of the shared document component. Relationship management And a third means for performing.

The document processing apparatus according to the third aspect of the invention manages the document consisting of the document constituent elements, and manages the sharing relationship by using the sharing management information provided corresponding to each document. (1-1), a document storage means (20-2) for storing a document composed of document constituent elements managed by the document management means, and a document constituent element of the document stored in the document storage means. Search means (20-
3), and means for displaying the shared document component based on the shared management information when the document component specified by the search means is a shared document component (2)
0-5 to 20-7) are provided.

[0011]

The information expressing the constituent elements of a document can be divided into document-dependent information and document-independent information. Information that depends on a document is information that should be set for each document, such as information indicating the relationship between document constituent elements for expressing the document structure and appearance information (text style) indicating the overall appearance of the document. The information that does not depend on the document is information that can be commonly used for other documents, such as information that represents the content of the document and appearance information (specific style) that is particularly designated for paragraphs and characters. Here, the format information is information that specifies in what form the document contents are displayed. In the first invention, the document management means manages the document constituent elements of the document composed of the document constituent elements stored in the document storage means by dividing them into an information part that depends on the document and an information part that does not depend on the document. In order to share the same document contents with each other, sharing of the document-independent information part in the document component of the sharing target is managed, so that the document-independent information part is the same and shared from all documents. However, no problem occurs, and the document-dependent information part can be set for each individual document, and the shared document components can be easily imported in a form compatible with the original document. it can. Therefore, according to the present invention, it is possible to eliminate the contradiction caused by sharing a plurality of documents of the related art. Document components created as one document as part of another document,
When there is a change in a document component that is captured and shared at the document component level, the change can be made from any shared document and the result of the change can be shared. Further, in the present invention, the format information can also be managed by being divided into an information part (text style) that depends on the document and an information part (specific style) that does not depend on the document.
It also shares the appearance information of a specific style that is attached to the document components that are the target of sharing, such as the appearance information that underlines a part of the sentence to emphasize it or displays gothic characters. be able to. By providing a means for selecting whether or not to use the format information, if the format information given to the shared document component is inappropriate in the document on the sharing side,
It is also possible to display using the format information on the shared document side.

According to a second aspect of the invention, the document management means manages the sharing of the document composed of the document constituent elements stored in the document storage means, and uses the tree-structured version management information generated for each document. Manage version. In the shared management information, information indicating the correspondence between the shared document constituent element and the document-dependent information part of the constituent element of the document sharing the shared document is used in addition to the shared management information. Since the information about the transition of the version for coexisting version management is also included, the management using this information can maintain the shared state when the version is updated or deleted. In addition, in order to manage sharing of document components from multiple documents, sharing of document components in a shared document is specified outside the version control to specify sharing of document components of the shared document. It is possible to avoid an increase in the number of versions of the shared document each time it is done.

In the third invention, the document management means manages the document composed of the document constituent elements, and manages the sharing relationship by using the sharing management information provided corresponding to each document. The search means searches for the document constituent elements of the document stored in the document storage means. The means for displaying the document constituent element displays the shared document constituent element based on the shared management information when the document constituent element searched out by the search means is the shared document constituent element. This allows the sharing management information to support the judgment when processing the sharing information in a certain document component.

[0014]

【Example】

[First Embodiment] FIG. 1 is a diagram showing the configuration of a first embodiment of the present invention. As shown in FIG. 1, this apparatus includes an input unit 1-1, a document designation unit 1-2, a document sharing designation unit 1-3, a display unit 1-4, a document editing unit 1-5, and a printing unit 1-6. , Memory 1-7, document storage control unit 1-8, document reading unit 1-
9, a temporary document storage unit 1-10, a document registration unit 1-11, a document operation unit 1-12, a document management unit 1-13, and the like. When the document designation unit 1-2 designates the name of the document and the version, the document operation unit 1-12 identifies the target data using the version management unit, and the operation (process) designated by the input unit 1-1. Do. The specified operation is the document management unit 1.
-13, such as fetching a document in the document storage unit 1-131 managed by the document storage unit 1-131 to the document temporary storage unit 1-10, deleting a document, and deleting a document version.

The document reading unit 1-9 reads the document data from the document temporary storage unit 1-10 into the memory 1-7. The display of the document by the display unit 1-4 and the editing by the document editing unit 1-5 are performed on the document data read in the memory 1-7. The temporary editing result is stored in the document temporary storage unit 1-10 by the document storage control unit 1-8. When the document editing work is completed, the document registration section 1-1
Reference numeral 1 denotes a temporary document storage unit 1-10 to a document management unit 1-13.
Then, the updated document is registered and the version is updated.
The document management unit 1-13 manages the structured document stored in the document storage unit 1-131, and also manages document sharing and document version management. The version management is performed by the version management unit 1-132, and the version management information is stored in the version structure storage unit 1-133.

The version management unit 1-132 includes a document storage unit 1-1.
The version of the document stored in 31 is managed in a tree structure, and the version of a certain document is specified from the name of the document and the version. The management data of the version tree structure is stored in the version structure storage unit 1-133. The document sharing designation unit 1-3 designates a document component to be shared stored in the document storage unit 1-131 and a position where the shared document is placed (document component of parent and sibling). The document management section 1 accordingly
Reference numeral -13 designates the document constituent element designated as the sharing target from the parent and sibling document constituent elements of the shared document, generates management information for sharing under the subtree, and manages the sharing.

FIG. 2 shows an example of a structured document handled in this embodiment. The document described in this embodiment is a structured document composed of elements divided into logical structures such as chapters, sections, paragraphs, and frames, and is represented by a tree structure. The document constituent element in the present invention means a unit of a logical structure such as a chapter, a section, a paragraph, and a frame. In the document management section 1-1, the document shown in FIG.
It is stored in the document storage unit 1-131 in a format as shown in FIG. An object Doc3-1 that is management information for managing a document includes a docstyle that manages the style of the document as an attribute, a root that indicates a document constituent element at the top of the document structure, and a pstabl that indicates a table of shared information.
e, manages other information. The document component shown in FIG. 3 is a priv representing the unique attribute shown in FIG.
ate_attribute4-3 and shared_attribute4 representing the shared attribute shown in FIG.
-1. Attribute shared_attribute
The element owner's of te is private_attribute4-of the document in which the document component is created.
Refers to 3. The attribute cont_attr4-2 is the content part c
Indicates the paragraph style p_style specified for the ontent and its content part. The relationship between the document components is
Expressed in a tree structure, the relationship between parent and child siblings is private
_Attribute's oya, ani, ototo,
It manages as shown in FIG. 5 with kodomo. That is, each document constituent element is private_attribute and s
It is composed of a pair of information of “hared_attribute”, and in FIG.
The information pairs of 1, S2-1, P3, and S3 are shown, and a part of the relationship between them, that is, the relationship between the parent, the brother, the younger brother, and the child is illustrated by an arrow. Particularly, P2 and S2 are shown in detail.

The style management information 3-2 includes a body style and a specific style, as shown in FIG. The specific style is specified for each paragraph or character, and the specified style has priority for the specified content part. If nothing is specified, the body style will be applied. The style information is managed according to the relationship shown in FIG. The style information belonging to the document is managed by docstyle3-2. Individual paragraph style and character style are doc
It is an element of the list pointed to by the paragraph style list and character style list in style3-2. If a paragraph style is used from a paragraph in the document, the shared_attribute of the element representing that paragraph
Cont_attr of p_style. The character style is referenced from within the content.

The document sharing designation section 1-3 shares documents as follows. To specify sharing of document components of a document,
Private_att of the vertex of the subtree to be shared
private_attrib corresponding to the ribute
It is realized by creating an ute in a document on the sharing side and setting a parent-child sibling relationship. The shared vertex has the private_attributes corresponding to the shared_attributes. Shared_at being shared
private_att shared with tribute
The relationship of the ribbets is managed by the shared information management table sptable of the shared document.

FIG. 8 shows the structure of the shared information management table sptable. This shared information management table 8-2 is
shared_attribute and its shared
Private_ sharing _attribute
Holds an attribute relationship. Si is the shared_attribute of the vertex shared by other documents in the document constituent element of this document. The set of Prefs with Si as a key includes a list of private_attributes pointing to Si from another document. This private_attribute is
It is a document constituent element of a document sharing a subtree under shared_attribute. For example, the shared information management table Table of the document A in FIG. 7 is as shown in FIG.
The shared_attribute SA2 of the document component shared by the document B and the private_attributeP of the document B referenced from the shared_attribute SA2 as shown in FIG.
It includes information indicating the relationship with the information Pref (PB2,1) indicating B2.

Regarding the content section and the specific style information, s
By sharing the shared_attribute, the shared document is referenced. Regarding the specific style, shared_attribute when reading the document
Set when reading e. A specific procedure for designating sharing of document constituent elements will be described with reference to FIGS. 6 and 7. A specific method of designating sharing of the document constituent elements will be described by taking as an example the case where sharing is performed as the chapter 2 of the document B in which the shaded portion of the entire chapter 2 of the document A is PA2. First, take the root node of the subtree representing the second chapter of document A. This is document_shared_a
This is done by accessing the tribute SA2. The position where the document B is shared is designated. It is located by specifying the parent sibling of the document component to share. If it is brought to the beginning of a certain level, for example, chapter 1, the parent and younger brother are designated, and conversely, if it is brought to the last chapter, the parent and brother are designated. If there are no elements at the same level, only the parent is specified. In the case of this example, it is designated to share SA2 as a younger brother of SB1. Private_att corresponding to PA2 of document A
A ribbon is generated as PB2 in document B, and individual attributes of PB2 are set as shown in FIG. Change the younger brother of PB1 to SA2 and the older brother of PB3 to SA2. SA2-1
The following points to SA2 as a child of PB2,
Other than that, nothing is done about SA2-1 and below. In document A, in order to manage that SA2 is pointed to by PB2 of document B, Pref (PB2,1) having PB2 and ref_count as a pair is spta of document A.
Register SA2 as a key in ble. If SA2 is already registered, Pr is set as the element of the set with SA2 as the key.
Register ef (PB2,1). Details of the Table of FIG. 7 are shown in FIG. The processing procedure described above is shown in FIG.
Shown in The information in the shared information management table is used when reading the document B. With the above, the setting of sharing the contents of the second chapter of the document A as the second chapter of the document B is completed. If the sharing target includes a specific paragraph style or character style, this style is loaded when the document is loaded.

The document reading unit 1-9 loads the document from the document temporary storage unit 1-10 to the memory 1-7. That is, the document reading unit 1-9 reads the document designated by the document designation unit 1-2 in the procedure shown in FIG. Step (10-1) The document reading unit 1-9 reads the document management information Doc from the document temporary storage unit 1-10. Step (10-2) Style management information Docsty
Read le. Step (10-3) Read the document component. This document component can be read by sharing_attri
priv corresponding to the document after reading the butte
Read ate_attribute. private
The parent-child sibling relationship can be traced by reading e_attribute. The search of the tree structure in the reading is performed by the vertical search from the root root of the document. In this vertical search, the eldest son, younger brother, parent's younger brother, parent's younger brother ,. ． ． Is repeated, and this is repeated until there is no document component to be traced. Step (10-4) Allocation processing is performed based on the information read by the above. The setting of the structure in the memory is
Perform in order of the eldest son.

Sha in step (10-3)
p corresponding to the document from red_attribute
FIG. 11 shows a procedure for determining the private_attribute. Step (11-1) Document curr to be processed
Set ent_doc. Step (11-2) current_d in variable si
Set the shared_attribute of the oc root. Step (11-3) s set in the variable si
private_attribute pointed to by owner's of shared_attribute
Owner_doc (si), which is the doc value of
It is determined whether or not it is current_doc. Step (11-4) As a result of the determination, owner_
If doc (si) is current_doc, shared_at set in variable si
Read the privateattribute pointed to by the owner's of the tribute. Step (11-5) As a result of the determination in the step (11-3), owner_doc (si) is curren.
If it is not t_doc, owner_doc
(Si) p from shared information management table sptable
Determine private_attribute. The determination method will be described later with reference to FIG. Step (11-6) By the above step (11-4) or step (11-5), private at
After reading the tribute, ne is set to the variable si.
Set the value of xt (pi). next (pi) is searched next in the order of eldest son, younger brother, parent's younger brother, parent's younger brother, ...
returns i. After tracing all the elements, NIL is returned. Step (11-7) It is determined whether or not the value of the variable si is NIL. If it is not NIL, the search is continued, and if it is NIL, the process is ended.

FIG. 12 shows the shared information management table spta.
It is a flowchart which shows the detail of the process of the said step (11-5) which determines private_attribute from ble. Step (12-1) Obtain a set of Prefs that share si as a vertex from sitable with si as a key. For example, in the case of FIG. 7, as shown in FIG.
When i = SA2, a set of Prefs {Pref (PB2,
1), ...} is obtained. Step (12-2) For each element of Pref, an element whose doc value is the same as current_doc is obtained. For example, in the case of FIG. 7, the element Pref (PB2,
1) is obtained. Step (12-3) It is determined whether or not there is one element obtained in step (12-2). Step (12-4) When it is determined that the number of elements is one by the determination, pr is determined by the Pref.
Determine the ivate_attribute. Pref
Is a private referenced from S as shown in FIG.
It includes information p indicating an attribute and information ref_count that counts the versions of a shared document when the document system has version management, and the private P can be determined by this information P. Step (12-5) When it is determined in the step (12-3) that there are a plurality of elements, the values of the parent and the elder brother of the private_attribute of each element are the private_attributes currently pointing to si.
private_attr compared to e's parent and itself
Determine ibute.

Here, the reading of the paragraph style and the character style will be described. shared_attrib
When ute is read, cont_attr is read. When sharing is not performed, all style information used in the document is pointed to by the paragraph style list or the character style list of docstyle. In the case of the first reading of a document in which sharing of document components is designated, paragraph styles and character styles may not be loaded yet. shared_att
The cont_attr when reading the libute
Check whether the specific (character, paragraph in this embodiment) style pointed to by is in the specific list of docstyle of the document being read, and if not, con
The specific style pointed to by t_attr is read and added to the shared paragraph style list or shared character style list of d_style shown in FIG.

The document display section 1-4 generally displays a document with the priority of the character style, the paragraph style, and the body style. The same applies to character styles and paragraph styles assigned to shared document components. When the style information is edited by the document editing unit 1-5, the edited result of the style information is also shared. If the paragraph style assigned to the shared document component does not match the display of the shared document, specify that the body style of the shared document has priority over the shared paragraph style, and Can be displayed in style. For example, when a document component for which the font is specified in the paragraph style is specified in the place where the font is specified in the OHP document, in order to make the display of the shared document consistent, , The display style of the shared document is maintained by giving priority to the body style over the paragraph style assigned to this document component.

The document reading unit 1-9 allows the document storage unit 1
-131 when the document of -131 is read into the memory 1-7 via the temporary document storage unit 1-10
13 and 14 show an example of the relationship between the above document and the document in the memory 1-7. In the example of FIG. 13, the document storage unit 1
The document B in −131 is read into the memory 1-7. First, the document B is stored in the current_doc.
Is set, and sha of the document component that becomes that root
SB0 of red_attribute is read, and then its own's private attr
PB0 of ibut is read. Next, SB1 and PB1 of the document components pointed to as children by PB0 are read. As a younger brother, PB1 is the document component S of document A.
Since it points to A2, its SA2 is read,
Since the owner's is not current_doc, the shared information management table sptable is referred to and S
The PB2 corresponding to A2 is obtained and read into the memory 1-7. Since PB2 points to SB3 as a younger brother, the SB3 and the PB3 of its owner's are read. FIG. 14 shows an example of reading format information. When the information of the document style d_style is read as a part of the document management information of the shared document B, and the document constituent element of the shared destination has a specific style, that is, a paragraph style or a character style, the shared paragraph style list or the shared character. Read as a style list. Then, when the shared document component is displayed, the read paragraph style or character style is used.

Next, version management will be described. If version management is not required, this part can be omitted. The document version management unit 1-132 is shown in FIG.
As shown in FIG. 5, multiple versions of the document are managed by a tree structure. That is, the version management unit 1-132 is the document storage unit 1
The version derivation relationship is managed by a sequential tree for each document stored in −132. The version data is managed by using a data structure in which each node of the ordered tree is a version, and a sequence of nodes obtained by tracing the eldest son from a node having a root or an elder brother is a version branch. Bod (Branch of of) is used as document version management data to specify the version of the document.
Document) is used. Document version management data B
The od exists for each branch of the version and is used for managing the version in the branch. The cb_name of the document version management data Bod is
The name of the latest version of the branch, b_name is the name of the version that became the branch point of the branch, and v_list is a list of the names of the versions that belong to the branch. One document version management data Bod is generated and added to the bodylist of the document management data Doc when a branch is created. The relationship between the Bod, the document, and the version is shown in FIGS.

In FIG. 15, the structure of the version of document A is main.
1, named main2 and main3, respectively
There are two editions, indicating that they belong to one branch, Bod_1. The version main3 is set as the latest version cb_name of the data of the branch Bod_1, and main1, main is set as the list of versions belonging to the branch
2, main3 is set. FIG. 16 shows a state in which the version eda_1, which is a branch of the version main2 and is derived, is added to the document A of FIG. Edition eda_
Since 1 is a node with an elder brother in the tree structure, it belongs to a new branch. Branch data B as data for managing the branch
od_2 has been created, and the branch Bod_2 has version eda_1 set as the latest version cb_name, and the version b_name that is the branch point of the branch is main.
2 is set, and eda is used as the list of versions belonging to that branch.
_1 is set.

The object of version management is a value other than the bodylist and the stable of the document management data Doc. The data that is the object of version management is managed by the document version management unit 1-13, and by specifying a specific version, the value of that version can be obtained from the version management unit 1-132. The editions in the document are managed by name,
A desired version is specified by specifying the name of the document and version, and the document data of that version is accessed.

Sharing of document components under version control will be described. The share of the document management data Doc is used to manage the transition of the versions of the shared document components.
Use dlist. Document management data docsha
redlist is a pointer to a Bod representing a branch of a document version that is the owner of the document component shared by the document in order to identify the version of the document component shared by the document. A list of elements. When sharing of a document component is designated, a pointer to the Bod that manages the branch of the document version that is the owner of the shared document component is added to the sharedlist. Shared document sha
The redlist Bod is used to specify the version of the shared document component when the document is read.
Therefore, when the version of the shared document is updated, the document on the sharing side can use the content of the document constituent element updated in the shared document by checking the value of the Bod of sharedlist. In other respects, it is the same as when version management is not performed. Since a shared table that manages from which document the shared component is shared is placed outside the version management, the shared document may have its version updated every time sharing is specified. Absent. Regarding the function of sharedlist when the document B shown in FIG. 7 shares the constituent elements of the document A under version control.
This will be described using 5. First, the version of main1 of document A is designated as shared by document B. Document B when sharing is specified
A pointer to Bod_A1 is added as an element to the shared list. The Bod_A1 is a Bod for managing the branch of the version of the document A. When the document A is updated, the version of main2 is created and the value of Bod_A1 is also updated. From document B, as information of shared component,
By using the value of Bod_A1 from sharedlist, it is possible to follow the transition of the version of the document A. Since there are usually a plurality of sharedlist elements, the bodylist of the owner document of the shared component is
The element is selected by comparing it with the element of t.

Next, the relationship between version update and sharing of a document in a state where the document components are shared will be further described. Figure 8 shows the sharing count including version management between documents.
Ref_cou of Pref of the shared information management information shown in
nt. Even if the version of the shared document is updated, ref_count is not changed. When the version of the shared document is updated, ref_count is incremented. When the version of the shared document A is updated, the sharing target from the document B points to the latest version as shown in FIG. 17A, so V1, V2,
It will be updated to V3. When the document B is displayed in this state, the contents of V3 of the document A are displayed as the shared contents.

When the document B is updated, FIG.
As shown in (b), updating the version increases the number of shares. This means that if document B has multiple editions, document B
Even if one version is deleted, another version may still share the document component of document A.

Cancellation of sharing will be described. When a shared document component is released from a certain version of the shared document, ref_count of the corresponding element of the shared table's sptable is decremented. ref_co
If unt is 1, the element is deleted from the sptable, and the Bod of the document having no shared relationship is removed from the shared list of the shared document.

The document deletion will be described. If there is a sharing relationship between the constituent elements of the document, if the shared document is suddenly deleted, the contents of the shared document will be lost. Therefore, when a document is deleted, the processing shown in FIG. 18 and described below is performed to maintain the consistency of the sharing relationship among a plurality of documents. Step (18-1) Before deleting the document, it is determined whether or not the document has a shared document constituent element by checking the sptable. Step (18-2) If there is a shared document constituent as a result of the judgment, the shared document constituent and the document are displayed. Step (18-3) If there is no shared document component as a result of the determination, it is determined whether or not there is a document component shared by the document. Step (18-4) If there is a shared document component as a result of the determination, the pri of the document is shared from the shared table of the shared document having the document component.
Delete the element containing vate_attribute.
As a result, the sharing relationship between the shared document and the document is canceled. Step (18-5) If there is no document component shared in step (18-3) and if the process in step (18-4) is completed, the entire document is deleted.

When deleting a version, the same problem as that of deleting a document occurs. When deleting a version, by performing the processing shown in FIG. 19, it is possible to maintain the consistency of the sharing relationship among a plurality of documents. Step (19-1) It is determined whether the version of the document to be deleted is the latest version. Step (19-2) If the result of the determination is that the version is not the latest version, the shared document constituent element and document are displayed. Step (19-3) In the case of the latest version, it is determined by checking sptable whether or not the document of the version has a document component shared. Step (19-4) If there is a shared document component, the shared document component and the document are displayed. Step (19-5) If there is no shared document component as a result of the determination, it is determined whether or not the document of the version has a shared document component. Step (19-6) If the result of determination in step (19-5) is that there is a shared document constituent element, from the shared table's sptable, the p
ref of the element containing private_attribute
Decrement _count by 1. If ref_count is 0, it is deleted from sptable. Step (19-7) As a result of the determination in the step (19-5), if there is no shared document constituent element, it is determined whether or not there is a version of the document in addition to the version. Step (19-8) If there is another version as a result of the determination, the version is deleted and the value of the version management information Bod is updated. Step (19-9) If there is no other edition, the edition document is deleted.

In the present embodiment, the information of the document constituent elements of the document is divided into the private attribute information which is information dependent on the document and the shared attribute information which does not depend on the document. By setting the information that is the same from any document and is dependent on the document, it is possible to eliminate the contradiction caused by sharing the document constituent elements among a plurality of documents. If a document component created as one document is included as part of another document at the document component level and changes are made to the shared document component, then from any shared document You can make changes and the results are shared. In the present embodiment, since the appearance information is also managed, it is possible to share the appearance information given to the document constituent element to be shared. However, in the document on the sharing side, when the format information given to the shared document component is inappropriate, the format information on the shared document side can be displayed. Further, it is possible to share document constituent elements even for a document whose version is managed, and maintain consistency of shared information even when a version is updated or deleted. Moreover, by adopting the document deletion method in which the sharing state is checked, the consistency of shared information is not lost due to the deletion of the document.

[Second Embodiment] The second embodiment is the same as the first embodiment except that the document information is searched for and the shared information of the document information obtained by the search is displayed. Is an embodiment in which a configuration for supporting judgment in processing is added. The second embodiment also has the schematic structure of FIG. 1 similarly to the first embodiment, but the additional portion is shown in FIG.
Included in the configuration. The relationship between the configuration of FIG. 20 and the configuration of FIG. 1 is as follows. The search condition input unit 20-1 corresponds to the input unit 1-1. The document storage unit 20-2 corresponds to the document storage unit 1-13. The operation result instruction unit 20-7 corresponds to the display unit 1-4. The document component search unit 20-3, the search result storage unit 20-4, the search result selection unit 20-5, and the shared information acquisition unit 20-6 are newly added.
The second embodiment will be described focusing on this additional portion.
In FIG. 20, a search condition input unit 20-1 is for inputting a condition for searching a document constituent element using an input device such as a keyboard. The document storage unit 20-2 stores a plurality of pieces of document data expressed as a set of document constituent elements, and is the same as the document storage unit 1-131 in FIG. The component search unit 20-3 is a search condition input unit 20.
The document components that satisfy the search condition acquired in -1 are searched. The search result storage unit 20-4 is a unit for temporarily storing the result of the search by the component search unit 20-3. The search result selection unit 20-5 is the search result storage unit 20.
-4 is a portion for selecting a document constituent element for which shared information is acquired from the search result stored in -4. Shared information acquisition unit 20
Reference numeral -6 is a portion for acquiring the shared information from the document storage unit 20-2 regarding the document constituent element selected by the search result selection unit 20-5. The operation result display unit 20-7 is the search result and shared information acquisition unit 20 stored in the search result storage unit 20-4.
The shared information acquired in -6 is displayed on a display unit such as a display.

Here, as an example of the document constituent elements, chapters, sections,
I will handle the charts. The document is stored in the document storage unit 20-2.
In FIG. 21, it is stored in a tree structure as shown in FIG.
Further, as shown in FIG. 22A, index information indicating the correspondence between the document name and the pointer (storage position) to the root in the tree structure of the document is created, and the index information is used to create the document. An index for searching a root at high speed, and as shown in FIG. 22 (b), showing a correspondence relationship between a heading character string of a document constituent element and a pointer (storage position) to the document constituent element Information is created in advance, and by using this, the search for the document component is speeded up. The first is the method of realizing sharing of document components, the data structure of document components, the structure of the shared information management table, etc.
This is the same as that described in the embodiment.

An example of sharing a document constituent element among a plurality of documents in this embodiment will be described. The document constituent elements are, as shown in FIGS.
_Attribute and private section private
_Attribute, and the shared portion stores information about the document in which the document constituent element was first created, and if the content portion has a content portion such as a character string, the content thereof is stored. A pointer to the document doc belonging to the private part, the type of the document component type, and a parent oy for constructing the tree structure
A pointer to a document constituent element such as a, an older brother ani, a younger brother ototo, and a child kodomo, a pointer to a shared portion, and the like are stored. When sharing an existing document component belonging to a certain document with another document, a new private part of the document component is created in the sharing document, and the shared part of the existing document component is created from the private part. With a pointer. Further, in the newly created private part, attribute information (parent, child, etc.) for forming the tree structure of the document to which the private part belongs is stored. Further, the shared document for obtaining the information of the document component sharing the document component and the document to which it belongs from the shared portion of the document component is shared information for managing shared information as shown in FIG. It holds the management table 8-2.

The process steps of the document processing apparatus of the present embodiment thus constructed will be described in detail with reference to the flowchart of FIG. Step (24-1) First, the document condition search condition is input by the search condition input unit 20-1 which is an input means such as a keyboard. The search condition here is, for example,
The conditions include paragraphs that include the character string “structured document” in the content, tables that include the “data structure” in the heading character string, and the figures included in Chapter 1. Step (24-2) Document component search unit 20-3
Performs a search according to the search condition acquired in step (24-1). As the search method, there are a method of performing a search using a headline character string and the like using the set for search described in FIG. 22, and a method of determining each document constituent element by tracing a structure tree. The former method is used to search at high speed. As a search result, a pointer to a document constituent element (shared portion) that satisfies the search condition and a character string representing the document constituent element, for example, a chapter or section heading character string or a figure caption is paired to form a list. To output. Step (24-3) It is determined whether or not one or more search results have been obtained. If no search result has been obtained, the process ends, and if one or more search results have been obtained, the process proceeds to step 24-4. Step (24-4) The search result acquired in step (24-2) is temporarily stored in the search result storage unit 20-4. Step (24-5) Operation result display unit 20-which is a display means such as a display for displaying character strings corresponding to the document constituent elements of the result list stored in step (24-4).
Display on 7. Step (24-6) The character string of the document constituent element for which the shared information is desired to be referenced is selected. Here, it is possible to select all or a plurality of candidate document constituent elements. Step (24-7) The pointer to the private part of the document component corresponding to the character string selected in step (24-6) is retrieved using the list stored in step (24-4), and the pointer is traced. Access the shared part of the document component. Step (24-8) The shared information management table of the document to which the shared part of the document constituent element extracted in step (24-7) belongs is accessed, and the shared information corresponding to the shared part is extracted. Step (24-9) The operation result display unit 20-7 displays the document component shared information extracted in step (24-8).
To be displayed. According to this embodiment, the reference information and the shared information in the document data can be easily retrieved and referred to when necessary, so that the reuse of the constituent elements of the document can be promoted. Also, operations such as management of document component shared information and display of shared documents can be easily performed.

[0042]

According to the first aspect of the present invention, the information of the constituent elements of the document is divided into the information that depends on the document and the information that does not depend on the document. Therefore, the shared information can be seen from any document. Information that is the same and that is dependent on a document can be set for each individual document, and it is possible to eliminate the contradiction caused by sharing a document constituent element among a plurality of documents. If a document component created as one document is included as part of another document at the document component level and changes are made to the shared document component, then from any shared document You can make changes and the results are shared. Since the appearance information can also be managed, it is possible to share the appearance information given to the document constituent element that is the object of sharing. However, in the document on the sharing side, when the format information given to the shared document component is inappropriate, it is possible to display the format information on the shared document side. According to the second invention, the first
In addition to the above effect of the invention, the document constituent elements can be shared even for the document whose version is managed, and the consistency of the shared information can be maintained even when the version is updated or deleted. Can be maintained. Further, according to the third invention, by displaying the shared information of one or more document constituent elements retrieved by the searching means from the document storing means by the searching means, a certain document structure is displayed. It is possible to provide judgment support when processing shared information in an element.

[Brief description of drawings]

FIG. 1 is a diagram showing a configuration of a first embodiment of the present invention.

FIG. 2 is a diagram showing an example of a structured document handled in this embodiment.

FIG. 3 is a diagram for explaining a structured document according to the present embodiment.

FIG. 4 is a diagram showing a data structure of attribute information of document constituent elements, (a) showing a shared attribute and (b) showing a private attribute.

FIG. 5 is a diagram for explaining a relationship between document components.

FIG. 6 is a diagram for explaining designation of sharing of document components.

FIG. 7 is a diagram for explaining designation of sharing of document components.

FIG. 8A is a diagram for explaining a sharing designation example;
(B) is a figure for demonstrating a shared information management table.

FIG. 9 is a diagram showing a flow of processing for setting sharing.

FIG. 10 is a diagram showing a schematic processing flow of reading a document.

FIG. 11: sh in step (10-3) of FIG.
The figure which shows the flow of the process which determines private_attribute corresponding to the document from ared_attribute.

FIG. 12 is a diagram for determining private_attribute from the shared information management table sptable.
Flow chart showing details of the processing in step (11-5)

FIG. 13 is a document in a document storage unit 1-131 and a memory 1-7.
The figure which shows one example of the relationship of the document inside

FIG. 14 is a document in a document storage unit 1-131 and a memory 1-7.
The figure which shows one example of the relationship of the document inside

FIG. 15 is a diagram for explaining document version management.

FIG. 16 is a diagram for explaining document version management.

17A is a diagram showing a sharing relationship when the version of the shared document A is updated, and FIG. 17B is a diagram showing a sharing relationship when the version of the shared document B is updated.

FIG. 18 is a diagram showing a flow of processing for deleting a shared document.

FIG. 19 is a diagram showing a flow of processing for deleting a document version.

FIG. 20 is a diagram showing a configuration of a second exemplary embodiment of the present invention.

FIG. 21 is a diagram for explaining a document storage mode.

FIG. 22 (a) is a form of a document root search set,
FIG. 3B is a diagram for explaining the form of a set for document component search

FIG. 23 is a diagram showing an example of a tree structure of document data when sharing occurs.

FIG. 24 is a diagram showing a flow of processing of the second embodiment.

FIG. 25 (a) (b) (c) is a shared list.
The figure for explaining the function of.

[Explanation of symbols]

1-1 ... Input unit, 1-2 ... Document designation unit, 1-3 ... Document sharing designation unit, 1-4 ... Display unit, 1-5 ... Document editing unit, 1-
6 ... Printing unit, 1-7 ... Memory, 1-8 ... Document storage control unit, 1-9 ... Document reading unit, 1-10 ... Temporary document storage unit, 1-11 ... Document registration unit, 1-12 ... Document Operation part, 1
-13 ... Document management unit, 1-131 ... Document storage unit, 1-1
32 ... Plate management unit, 1-133 ... Plate structure storage unit.

Front page continuation (72) Inventor Nobuhiro Yamazaki 3-2-1, Sakado, Takatsu-ku, Kawasaki-shi, Kanagawa KSP R & D Business Park Building Fuji Xerox Co., Ltd.

Claims (3)

[Claims] 1. Information of each document constituent element in a document composed of document constituent elements is managed by dividing it into a document-dependent information portion and a document-independent information portion, and sharing the same document contents between documents. For this purpose, the document management means has means for sharing an information part that does not depend on the document in the document constituent elements to be shared, and the document storage means for storing the document composed of the document constituent elements managed by the document management means. A document processing device characterized by the above. 2. Information of each document constituent element in a document composed of document constituent elements is managed by dividing it into a document-dependent information portion and a document-independent information portion, and a plurality of documents share the same document content. Therefore, the first means for sharing an information part that does not depend on each individual document of the document constituent elements that are the vertices of the subtree formed by the document constituent elements that are to be shared, and the following document constituent elements Version management information for each document based on a sequential tree that manages multiple versions in a tree structure, each node as one version, and the sequence of nodes obtained by tracing the eldest son from a node with a root or elder brother as a branch of the version By using the second means for managing the derivation relationship of the version by and the shared management information including the version information of the shared document constituent element, the management of the sharing relationship of the document constituent element of the version managed document is performed. Third hand to do A document processing apparatus comprising: a document management unit having a step; and a document storage unit for storing a document composed of document constituent elements managed by the document management unit. 3. A document management unit that manages a document composed of document constituent elements, and also manages a sharing relationship using sharing management information provided corresponding to each document, and is managed by the document management unit. Document storage means for storing a document composed of document constituent elements, search means for searching the document constituent elements of the document stored in the document storage means, and document composition in which the document constituent elements specified by the search means are shared A document processing apparatus comprising: means for displaying the shared document constituent element based on the shared management information when the element is an element.