CA2242904C - Document processing method and system, and computer-readable recording medium having document processing program recorded therein - Google Patents

Document processing method and system, and computer-readable recording medium having document processing program recorded therein Download PDF

Info

Publication number
CA2242904C
CA2242904C CA002242904A CA2242904A CA2242904C CA 2242904 C CA2242904 C CA 2242904C CA 002242904 A CA002242904 A CA 002242904A CA 2242904 A CA2242904 A CA 2242904A CA 2242904 C CA2242904 C CA 2242904C
Authority
CA
Canada
Prior art keywords
shared information
structured document
information
version
document
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
CA002242904A
Other languages
French (fr)
Other versions
CA2242904A1 (en
Inventor
Yuki Aoyama
Yukie Takita
Toru Takahashi
Yukio Hoshi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Ltd
Original Assignee
Hitachi Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hitachi Ltd filed Critical Hitachi Ltd
Publication of CA2242904A1 publication Critical patent/CA2242904A1/en
Application granted granted Critical
Publication of CA2242904C publication Critical patent/CA2242904C/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/93Document management systems
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99942Manipulating data structure, e.g. compression, compaction, compilation
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99944Object-oriented database structure
    • Y10S707/99945Object-oriented database structure processing
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99951File or database maintenance
    • Y10S707/99952Coherency, e.g. same view to multiple users
    • Y10S707/99953Recoverability

Abstract

A computer-implemented method and system for processing a document such as a structured document in which information such as a term, name and belonging department is used as shared information and word consistency or modification can be automatically and easily reflected on all documents. In the document processing method, a shared information editing program edits shared information shared information frequently described in a plurality of documents, a shared information storage program stores the edited shared information in a secondary memory, a shared information list-up program lists up the shared information for each information type, a structured document editing program edits a structured document to describe a link to the shared information selected from the edited shared information listed up, a structured document storage program stores the structured document in the secondary memory, and a structured document output program reads out the shared information and structured document from the secondary memory and embeds the contents of the shared information in the structured document for its display or printout.

Description

DOCUMENT PROCESSING METHOD AND SYSTEM, AND COMPUTER-READABLE RECORDING MEDIUM HAVING DOCUMENT PROCESSING
PROGRAM RECORDED THEREIN
BACKGROUND OF THE INVENTION
The present invention relates to techniques for creating and processing a document with use of a word processor or personal computer for its display and print and more particularly, to a technique for proces-sing a document which uses information that frequently appears in the document as shared information.
For the purpose of efficiently sharing and re-using document information, a recent active move is to use such a document language as a standard generalized markup language (SGML) or XML to obtain and utilize a document. ' Since a document prepared in a structured document language can be prepared by dividing the document into its structural elements as document parts for editing and describing links to the respective parts, it is easy fcr the document parts to be shared with another document or to re-use another document on every part basis.
When it is desired to display or print the link-described document having such links to the parts described therein, the document is converted to a document having the contents of the document parts of the other link-destination document embedded in the locations, and then displayed or printed.
To this end, a conventional editor for editing such a document provides a means for designating a document part as a part of the other document to describe a link to the document in the editing document.
When such a document editor is used, it can facilitate such an operation that a figure, which has been prepared in a functional specification as another document, can be re-used, for example, during editing of a design document.
Further, when a re-used part has been edited, its edited result can be reflected throughout the entire document having the shared part. As a result, consistency management can be facilitated.
JP-A-8-44718 (Fuji Xerox Ltd.) discloses a method that, when a figure or table is shared among a plurality of documents, its shared relationships are managed so that, even the shared constituent element is edited in the sharing original document, its edited result can be correctly reflected even on the other shared documents (figure or table), thus maintaining a consistency of the shared information.
In addition, even in a document system for performing version management, the above method can keep the shared information consistency. Thus, when it is desired to reduce the number of versions, it becomes possible to judge whether a constituent element or elements are shared among a plurality of versions, thus realizing such a management as to prevent an inconsistency in the shared relationships.
Constituent elements of documents which are effective when the elements are shared inc~~ude, in addition to such a figure or table as mentioned in connection with JP-A-8-44718, a character string which are used in many documents.
For example, at the time of preparing a document, it is very often for a document writer to consistently use the same character string as in a plurality of documents or in one document. More specifically, when it is desired to prepare specifica-tions in a product development project, it is required to use common module names, unique abbreviations and coinages which constitute the project.
In reality, however, it is often required to modify such words tc more appropriate ones as the project goes on. In such a case, it has been conven-tionally inevitably required to manually modify all the documents at the modified time point.
When such documents are written as shared by a plurality of writers, it becomes further difficult to obtain a word consistency throughout the documents and thus it inevitably involves an enormous amount of labor of finally proof-reading the documents.
Further, person's names or belonging depart-ments are frequently appear in a plurality of documents regardless of the document types. For this reason, when a belonging department was modified, it is also required _4_ to modify many associated documents.
Furthermore, when a document is prepared, it is often not tc prepare the document newly but to copy the same type of document as a template and to edit the contents thereof. Thus, even when it is required to change the old department to the new one, it is often to erroneously leave some of the old departments as they are without being modified to the new ones.
When such modification information is treated as a document part to be shared among a plurality of documents, the information consistency can be auto-matically realized. And even when the information is corrected, its corrected contents can be reflected on all the documents. As a result, highly efficient document preparation and editing can be carried out.
However, when such shared information is edited in the conventional system for its sharing, this involves problems which follow.
Fig. 5 shows an example of a plurality of documents which contain a document part or parts as a part or parts of the other documents with use of a known document editor.
For example, when a figure 504 (which is called share originator information), which forms one of constituent elements of a document A 501, is designated to describe its link to a document B 502, this causes appearance of contents of the document part (figure 504) of a link destination in the document B 502 (as a figure 505) .
Next, when it is desired to share the same figure 504 even in a document D 506, a document contain-ing the share originator information, that is, the document A 501 is searched to perform similar share designation to the above.
When information is shared in such a large unit as the figure and the number of sharing units as document parts is not so large as in the example of Fig. 5, the conventional system may be applicable.
However, when such document parts such as terms, names and belonging departments appear frequently, this share designating operation becomes highly troublesome.
That is, when many pieces of information are to be shared in such a small unit, it becomes difficult in the share designation to search the other documents containing the share originator information. Meanwhile, it is often that an identical type of shared information is simultaneously modified as when many terms are modified or a plurality of persons changes their belonging departments at a time in a project. In this case, the prior art system is required to search and modify the other documents containing the share originator information, which makes the modifying operation complex.
Meanwhile, information on person's name or belonging department is associated with each other, and thus when a person is determined, its name, belonging department, extension telephone number ought to be automatically determined. However, when the prior art system is employed to edit the document to share information associated with the person, its name, belonging department and extension telephone number are shared respectively independently. For this reason, modification of, e.g., name cannot follow av~tomatic modification of the belonging department and extension telephone number associated with the name and require individual editing of the shared information. As a result, its editing operation becomes highly complicated.
For the purpose of controlling such related information, a database management system is employed.
This system however has a problem that, since schema design for determining a data structure is difficult in database, the system cannot be easily applied to document preparation. Another problem is that, once the data structure is determined, it becomes hard to modify the structure.
Further, when the shared information has been modified, there are considered two cases one of which is desired to reflect the modification on all documents having the shared part and the other, it is desired not to reflect the modification on past documents already edited.
For example, in the case of a term used in a project, it is necessary to reflect the term modifi-cation even on the documents already edited, but with respect to reporter's name and belonging department described in a report submitted in the past, the information at the time of the submission must remain.
The prior art system has a problem that the management of consistency between the above two cases cannot be realized since the part modification is inevitably reflected on all the documents having the shared part.
The prior art system also has another problem that, when it is desired to modify shared information and to reflect the information modification on documents having the shared information, the correlation between the document and shared information link varies depending on the modification contents of the shared information, resulting in a wrong reflection thereof.
SUMMARY OF THE INVENTION
In accordance with one aspect of the present invention there is~provided a structured document processing method in an information processing system comprising a processor, a memory and a terminal, said _ g method comprising: generating a block of shared information as a set of shared information appearing in a plurality of structured documents; editing said shared information; managing a change history of said shared information, providing edited shared information with version information as a new version for said shared information and storing the version-provided shared information in said memory; editing a structured document and describing a link to said shared information in said structured document; managing a change history of said structured document, providing the edited structured document with version information as a new version for said structured document and storing the version-provided structured document in said memory; reading from said memory said shared information and said structured document, embedding the shared information in the structured document according to the link described in the structured document and outputting the structured document into which said the shared information is embedded; wherein, when embedding said shared information into said structured document, said outputting step comprises, embedding one of the latest version of said shared information and the latest version of said shared information among versions generated prior to generation of said structured document according to said version information for said shared information.
In accordance with another aspect of the present invention there is provided a structured document processing system in an information processing system comprising a processor, a memory and a terminal, said structured document processing system comprising:
means for generating a block of shared information as a set of shared information appearing in a plurality of structured documents; means for editing said shared information; means for managing a change history of said shared information, providing edited shared information with version information as a new version for the said shared information and storing the version-provided shared information in said memory; means for editing a structured document and describing a link to said shared information in said structured document; means for managing a change history of said structured document, providing the edited structured document with version information as a new version for said structured document and storing the version-provided structured document in said memory; means for reading from said memory said shared information and said structured document, embedding the shared information in the structured document according to the link described in the structured document and outputting the structured document into which said the shared information is embedded; wherein said means for reading, embedding and outputting comprises means for embedding one of the latest version of said shared information and the latest version of said shared information among versions generated prior to generation of said structured document according to said version information for shared information when embedding said shared information into said structured document according to the link information in said structured document.
In accordance with yet another aspect of the present invention there is provided a computer readable medium having stored thereon computer-executable instructions for structured document processing in an information processing system comprising a processor, a memory and a terminal, said instructions comprising:
generating a block of shared information as a set of shared information appearing in a plurality of structured documents; editing said shared information;
managing a change history of said shared information, providing edited shared information with version information as a new version for said shared information and storing the version-provided shared information in said memory; editing a structured document and describing a link to said shared information in said structured document; managing a change history of said structured document, providing the edited structured document with version information as a new version for said structured document and storing the version-provided structured document in said memory; reading from said memory said shared information and said structured document, embedding the shared information in the structured document according to the link described in the structured document and outputting the structured document into which said the shared information is embedded; wherein, when embedding said shared information into said structured document, said outputting step comprises, embedding one of the latest version of said shared information and the latest version of said shared information among versions generated prior to generation of said structured document according to said version information for said shared information.
Other objects, features and advantages of the present invention will become apparent when reading the following detailed description of the embodiments of the invention taken in conjunction with the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 shows an arrangement of a first embodiment of the present invention;
Fig. 2 is a processing flowchart for editing shared information in the first embodiment of the present inventio_~.;
Fig. 3 is a processing flowchart for editing a structured document in the first embodiment of the present invention;
Fig. 4 is a processing flowchart for displaying or printing the structured document in the first embodiment of the present invention;
Fig. 5 shows an example for explaining a prior art sharing method of document parts in documents;
Fig. 6 shows a first example of shared information when represented by graphical user interface (GUI) function of a shared information editing program;
Fig. 7 shows an example when a first example of the shared information is output as a structured document;
Fig. 8 shows diagrams for explaining how the first example of the structured document is edited and how the shared information is inserted to explain the first embodiment;
Fig. 9 is an example when a first example of the structured document is output as a structured document;
Fig. 10 is an example when the first example of the structured document having the shared information embedded therein is displayed in the form of a layout;
Fig. 11 is a second example of the shared information when displayed by the GUI function of the shared information editing program;
Fig. 12 is an example when a second example of the shared information is output as a structured document;
Fig. 13 is an example when a second example of the structured document is output as a structured document;
Fig. 14 is an example when the second example of the structured document having the shared information embedded therein is displayed in the form of a layout;
Fig. 15 shows an arrangement of a second embodiment of the present invention;
Fig. 16 is a processing flowchart for editing shared information in the second embodiment of the present invention;
Fig. 17 is a processing flowchart for editing a structured document in the second embodiment of the present invention;
Fig. 18 is a processing flowchart for displaying or printing the structured document in the second embodiment of the present invention;

Fig. 19 shows examples of V1.0 and V2.0 after and before a second example of the shared information is edited;
Fig. 20 shows examples of version informa~ion about edited structured document;
Fig. 21 shows an example of V2.0 after a second example of the structured document was edited;
Fig. 22 shows examples of version information about the edited structured document;
Fig. 23 shows an arrangement of a third embodiment of the present invention;
Fig. 24 is a processing flowchart for displaying or printing a structured document in the third embodiment of the present invention;
Fig. 25 is a processing flowchart for performing consistency processing operations over shared information in the third embodiment of the present invention;
Fig. 26 shows examples of V1.0 and V2.0 after and before a third example of the shared information is edited;
Fig. 27 is an example when a third example of the structured document is output as a structured document;
Fig. 28 is an example when the third example of the structured document having the shared information embedded therein is displayed in the form of a layout;
Fig. 29 is an example when the third example of the s~ructured document having the shared information embedded therein. is displayed in the form of a layout in the second embodiment;
Fig. 30 is an example when a third example of the shared information is differentially extracted;
Fig. 31 shows an example of the shared information already subjected to the consistency processing opera~ion; and Fig. 32 is an example when the third example of the structured document having the shared information already subjected to the consistency processing operation is displayed in the form of a layout.
DESCRIPTION OF THE PREFERRED EMBODIMENTS
The present invention will be explained in connection with embodiments of the present invention.
Although explanation will be made in the present embodiments in connection with a structured document having a document structure prepared using SGML by way of example, it should be noted that the present invention may be applied to general documents as well.
<Embodiment 1>
Fig. 1 shows an arrangement of a first embodiment of the invention. As illustrated, the present embodiment includes a CPU 101, a terminal unit 102 including input/output devices, a secondary memory 103 for storing documents therein, a memory medium 104 for storing programs therein, and a primary memory 1 for -li-storing a procedure program for processing various structured documents.
The structured document processing program further includes a shared information editing program 105 for editing shared information 103a frequently described in a plurality of structured documents, a shared information storage program 106 for storing the shared information 103a in the secondary memory 103, a shared information list up program 107 for listing up the stored shared information 103a for each of the types of the information, a structured document editing program 108 for editing a structured document 103b to describe a link of the shared information 103a in the edited structured document, a structured document storage program 109 for storing the structured document 103b in the secondary memory 103, and a structured document output program 110 for embedding the contents of the shared ir~Tormation 103a in the structured document 103b according to link information described in the document structured document 103b to generate information indicative of a structured document as an editing objective and to output the information in the form of a display or printout. An output of the structured document output program 110, that is, the shared-information embedded document information can be provided to various types of user application devices.
For example, the information can be provided not only to the aforementioned display or printout device but also -18_ to a file means, network terminal or server. As an alternative to the hardware configuration in the above arrangement, a plurality of terminal units 102 may be connected to the CPU 101, primary memories 1, 103a and 103b, secondary memory 103, shared information. 103a and structured document 103b through a bus or a communica-tion network communication network 120.
In the present embodiment, an SGML document is used as the structured document as an example. SGML is a document description language which is prescribed as a marked-up structured document based on 8879 of the International Organization for Unification (ISO).
However, the present embodiment is not limited to SGML.
For example, the present invention can be applied to a structured document language such as XML and non-structured documant languages with modifications. The shared information 103a and structured document 103b are stored in a memory such as a hard disk drive.
Explanation will next be made as to specific processing procedures of the present embodiment by referring to flowcharts such as shown in Figs. 2, 3 and 4, followed by description of processing examples according to the processing procedures.
As shown i.n Fig. 2, editing operation of shared information is carried out according to a procedure which follows.
Step 201:
The shared information editing program 105 _1G_ receives manv pieces of shared information alone frequently appearing in a plurality of structured documents, edits the received shared information, and stores it in the secondary memory 103 as the shared information 103x.
At this time, information such as assumed to be later shared among a plurality of documents are selected as the shared information, described and modified according t.o the type of the information.
Step 202:
The edited shared information 103a is stored in the secondary memory 103 by execution of the shared information storage program 106.
Shown in the present embodiment is an example such that shared information are stored as structured documents depending on the types of term information such as abbreviation or coinage and of person informa-tion such as person's name or belonging department.
However, when it is unnecessary to store the shared information as the structured document, the shared information may be stored by using a database management system or may be stored in an ordinary file system as data files.
As shown in Fig. 3, next, a structured document is edited independently of the steps 201 and 202 in accordance with a procedure which follows.
Step 301:
The structured document editing program 108 performs structured documen~ editing operation.
Step 302:
When iL is desired to insert shared informa-tion in a structured document being edited, the shared information list-up program 107 lists up the shared information stored in the secondary memory 103.
At this time, an operator or user specifies the type such as term or person of the shared information to be inserted, which causes the program 107 to produce a list of the information for each of the types.
Sep 303:
A link of the shared information to be inserted is described to a target structured document by execution of the structured document editing program 108.
The link description may be performed by means of the user who directly writes a link representation from an input device using the structured document program 108, or also may be realized by means of the user who gives the link representation through such user's operation as a drag and drop of a selected term in an insertion location of the objective structured document using the shared information list-up program 107.
Step 304:
Completion of the editing operation of the structured document causes the structured document storage program 109 to store the document already edited in the secondary memory 103.
The structured document stored in the step 304 is displayed or printed in accordance with a procedure which follows, as shown in Fig. 4.
Step 401:
When it is desired to display or print the structured document, the structured document to be displayed or printed as well as the shared information about a link destination described in the structured document are read into the structured document output program 110 from the secondary memory 103.
Step 402:
The contents of the shared information is embedded in the structured document, displayed or printed by execution of the structured document output program 110.
Processing Example 1:
The embodiment will be detailed in connection with specific processing examples of Figs. 6 to 10 by referring to flowcharts of Figs. 2, 3 and 4.
Step 201:
The shared information editing program 105 receives many pieces of shared information alone frequently appearing in a plurality of structured documents and edits the received shared information.
In the processing example, the shared information is assumed to be terms of character strings of such company name or product name as to be commonly used throughout all the documents, or of such as module name which may be modified on the way in a project.
In the example, terms which are estimated to be later shared in a plurality of documents as shared information, are selected and the shared information is described and modified depending on the types of sets of the terms.
For example, the shared information editing program 105 has a graphical user interface (GUI) as shown in Fig. 6. In the present example, items of key and term are defined in term definition.
Of character strings to be described in documents, the user defines as sets of keys and terms such character strings or terms that are desired to keep their expression consistencies or such terms that are desired to be used commonly throughout all the documents even when the terms are modified on the way. The key item is used when a link to the associated term is described in a structured document, and is defined uniquely in all the terms.
Prepared in the GUI of Fig. 6 is a term definition which includes items of key and term and in which the user can define such a term such as a company name or product name to be unified in all the documents or a module name of a project which may be modified on the way.
The GUI defines shared information of the input terms. The shared informa~ion editing program 105 edits the shared information according to the definition to create a structured document as shown in Fig. 7.
The term shared information is described as followed by a structure of <term definition> and as structured so as to have structures of <term> corre-sponding in number to the defined terms. Item key for each term describes the attribute of identification (ID) with respect to the construction <term>, and the actual character string is expressed so as to indicate the contents of the structure.
Step 202:
The edited shared information is stored in the secondary memory 103 by execution of the shared information storage program 106.
Upon storing the shared information, the term shared information is stored, for example, as such a structured document 701 as shown in Fig. 7.
A processing example of editing a structured document is shown in the following.
Step 301:
The structured documer_t editing program 108 edits a structured document.
For example, the structured document editing program 108 has a GUI as shown in Fig. 8. In the drawing, a reference numeral 801 denotes a window for displaying therein a logical structure of a document, and a numeral 802 denotes a window for displaying therein character strings in the logical structure.
Step 302:
When the shared information be inserted in the structured document now being edited, the shared information list-up program 107 junctions to display a list of the shared :information ef the terms stored in the secondary memory 103.
For example, the shared information list-up program 107 has a GUI similar to that of the shared information editing program shared information editing program 105 shown in Fig. 6, and lists up terms defined as term shared information.
Step 303:
The structured document editing program lOB
describes a link of a term to be inserted to the shared information.
In the example of Fig. 8, the user selects one of terms displayed by the shared information list-up program 107, drags and drops the selected term into an insertion location to insert the term shared information in the structured document. This causes the structured document editing program 108 to describe its link. In this connection, a reference numeral 803 denotes a representation to be linked.
Further, the user can directly describe the link to the shared information from an input device by execution of the structured document editing program 108.

Fig. 9 shows an example of a struc~ured document having links described therein. Such user's operation as shown in Fig. 8 causes generation of a structured document as shown in Fig. 9.
In the structured document of Fig. 9, the links are described in hypermedia/time-based structuring language (HyTime) (ISO/IEC 10744).
In the SGML, for the purpose of expressing mutual reference between structures, an ID attribute is given to one of the structures to be referenced while an identification (ID) of the referencing structure is given to the value of the IDREF attribute.
In Fig. 9, a construction 902 cf <TERM> is inserted as a link to a term and the term as a link destination is specified in the IDREF attribute of the TERM. However, since direct IDREF reference to the ID
described in another document cannot be made in the SGML, the HyTime language is used to reference the ID of the shared information in another document in this example.
As shown in Fig. 9, first, in an item 901, ENTITY reference to the structured document 701 of Fig.
7 having the shared information described therein is described in HyTime notation. The ENTITY reference is a notation for referencing another document, following which, another structured document 701 of "term_dic.sgm"
can be referenced under the ENTITY name of "term dic".
Descriptions by reference numerals 903 and 904 are such that a structure having the ID at~ribute can be referenced from inside of the document in "term-dic.sgm". More specifically, the description 903 enables a "product name" 905 as an ID in the "term_dic.sgm" to be referenced with an ID of "product_name_ref" 906, while the description 904 enables a "SGML parser" 907 to be referenced with an ID
of "SGML parser-ref" 908.
Since the "product name ref" 906 and "SGML parser-ref" 908 can make IDREF reference, these are defined as attribute values of <TERM>, respectively.
Step 304:
Completion of editing operation of the structured document causes the structured document storage program 109 to store the edited document in the secondary memory 103.
This means that such a structured document shown in Fig. 9 is stored.
Explanation will next be made as to a processing example of displaying or printing the structured document of Fig. 9 stored in the step 34.
Step 401:
The structured document to be printed as well as the shared information 701 of the link destination term described in the structured document are read out from the secondary memory 103.
Step 402:
The contents of the shared term information structured document 701 is embedded in the structured document, and then displayed or printed by execution of the structured document output program 110.
Fig. 10 shows an example of displaying the structured document of Fig. 9. In the Figure, the contents of the shared term information described as links are embedded in the structured document and displayed in the form of a layout.
Through the above steps, links of terms frequently appearing in the structured documents to the shared information can be easily described in the structured documents.
As a resu'yt, the consistency of a term to be desirably used as the same term in different documents can be easily kept and thus efficient document editing can be realized. This is valid, in particular, when it is desired for a plurality of persons to edit term-consistent documents.
Further, even when a term is madified, only modification of its shared information causes automatic reflection of the modification on all the documents, thus realizing efficient document modification.
Processing Example 2:
Explanation will then be made of the second processing example of the first embodiment in accordance with flowcharts of Figs. 2, 3 and 4 with use of examples of Figs. 11 to 14.
Step 201:

The shared information editing program 105 edits shared information frequently appearing in a plurality of structured documents.
In this processing example 2, it is assumed that the shared information is person information which includes person's name, belonging department and extension telephone number as a combination of terms of such character strings. It goes without saying that information other than the person information may be employed as the combination terms.
In this example, information which is estimated as will be later shared in the plurality of documents is selected as the shared information, and described and modified for each of the types of sets of the terms.
For example, the shared information editing program shared information editing program 105 has a GUI
as shown in Fig. 11. In this Figure, person information include items of key, name, belonging department and extension telephone number.
The user defines person information to be described in the documents as a set of person's key, name, belonging department and extension telephone number. Item key is to be used when a link to the person information is described in the structured document, and is defined uniquely throughout all person information.
Prepared in the GUI of Fig. 11 is a term definition which includes of name, belonging department and extension telephone number of person information.
Using the term definition, the user can define the person information to be unified throughout all the documents.
The GUI defines shared information of input person information. This causes the shared information editing program 105 to edit the shared information according to the definition to thereby create a structured document shown in Fig. 12 as an example of person dictionary file.
The shared information. of the present example is described as structured in such a manner that a construction of <person information> is followed by constructions of <person> corresponding -~n number to defined persons. Further, a key for each person is described as an ID attribute of a structure <person>.
Each person information has such a structure as to have a structure of <person> followed by structures of the person's <name>, <belonging department> and <extension telephone number>, which are described as the contents of their structures.
Step 202:
Shared information 1101 of the edited person information is stored in the secondary memory 103 by execution of the shared information storage program 106.
Upon storing the shared information, the shared information is stored in the memory 103b, for example, as a structured document 1201 as shown in Fig.
12.
The following is an processing example of editing a structured document.
Step 301:
The structured document editing program 108 edits a structured document. The structured document editing program 108 has a GUI similar to that of Fig. 8.
Step 302:
When the shared information of the person information is inserted in the structured document being edited, the shared person information stored in the secondary memory 103 is listed up by execution of the shared information list-up program 107.
For example, the shared information list-up program 107 has a GUI similar to that of the shared information editing program 105 shown in Fig. 11, and lists up the defined person information.
Step 303:
A link to the shared information to be inserted is described by execution of the structured document editing program 108. The link description is carried out in the same manner as in the processing example 1.
Shown in Fig. 13 is an example of a structured document having links already described therein. In the Figure, similarly to Fig. 9, the HyTime language is used to describe the links to the shared information.

As shown in Fig. 13, first cf ali, ENTITY
reference to the structured document 1201 of Fig. 12 having the shared information described therein is described in a representation 1301 in the HyTime notation. Due to such description, another structured document 1201 referred to herein as "person_dic.sgm" can be referenced by the ENTITY name of "person dic".
In a description 1304, a structure of "taro"
1202 as an ID in the "person-dic.sgm" can be referenced with use of an ID of "person ref" 1309.
In a description 1305, an ID of "person-name-ref" 1310 is described in the 'treeloc' notation of the HyTime language to indicate the first child structure of its own as viewed from the structure of "person ref".
More in detail, the description 1305 has a construction <name> having contents of "Heisei Taro".
The first "1" as the contents of <marklist> given below <treeloc> means its own and the next "1" means the first child.
In a description 1306, an ID of "person belong_ref" 1311 indicates a structure of the second child as viewed from a structure of "person ref"
In a description 1307, an ID of "person tel ref" 1312 indicates a construction of the third child as viewed from the construction of "person ref".
The respective ID's, since the ID's can receive the IDREF reference from inside of the document, are defined as attribute values of <TERM>, respectively.
Further, when the "tarc" 1308 is changed to "jiro", its name, belonging department and extension telephone number indicate a child of a construction having an ID "jiro". Thus, a "jiro" report can be created without any need for modifying the <TERM>
description 1302 in Fig. 13 and "treeloc" descriptions 1305, 1306 and 1307.
Step 304:
Completion of the editing of the structured document causes the structured document storage program 109 to store the edited document in the secondary memory 103.
That is, such a structured document as shown in Fig. 13 is stored in the memory 103.
Next shown is a processing example of displaying or printing the structured document of Fig.
13 stored in the step 304.
Step 401:
A structured document to be displayed or printed as well as shared document 1201 of the link destination described in the structured document are read out from the secondary memory 103 into the memory 110.
Step 402:
By execution of the structured document output program 110, the contents of the shared person information 1201 is embedded in the structured document, -3 ~-and then output in the form of a display or printout.
Fig. 14 shows an example of displaying the structured document of Fig. 13. In the Figure, the contents of the shared person information described as links, that is, having its name "Heisei Taro", belonging department "development depart. 12 group" and extension telephone number "1111" are embedded in the structured document and displayed in the form of a layout.
Through the above steps, similarly to the processing example 1, links to the shared information of a combination of terms frequently used in the documents can be easily described in the structured documents.
Thus, even when person's belonging department or extension telephone number is modified, only modifi-cation of the shared information of the combination terms causes automatic reflection of the modification contents on all the documents, thereby enabling automatic and efficient modification of the documents.
Further, when the HyTime notation is used, a link can be described as a relative position from its KEY. Hence, once one document is previously prepared as a template, only modification of KEY ID enables automatic modification of all the associated informa-tion, thus increasing the document preparation efficiency.
Furthermore, when the shared information of combination terms are previously saved as a structured document, modification of a structure of the shared combination. term information can be facilitated. For example, upon adding persons's addresses to the person information, the structure of the structured document of this Figure is converted by an SGML converting tocl so that it is only required to insert a structure <address>
below the structure <person>. Therefore, this manage-ment of the structure modification of the shared combination term information can be made easier than the schema modification when a database is used.
<Embodiment 2>
An arrangement of a second embodiment is shown in Fig. 15.
As illustrated, the present embodiment includes, in addition of the arrangement (see Fig. 1) of the first embodiment, a version management program 1501 which, the shared information 103a and structured document 103b are to be stored, stores them as a new version without overwriting them to manage a modifica-tion history of document creation date, time, etc. When a structured document is to be displayed or printed by execution of the structured document output program 110, the version management program 1501 extracts the shared information of latest one of versions of documents prepared prior to the creation date and time by the program structured document output program 110, embeds the shared information in the structured document, and then displays or prints the information-embedded document.

In other words, in accordance with the present embodiment, even when the shared information is modified, the modification is not reflected on past documents already edited, and the past shared informa-tion at the editing time is embedded for display or printout.
For example, when a report already submitted in the past is later displayed or printed, it becomes necessary to output the report without changing the reporter's name and belonging department described at the time of the report submission.
In the case of such a term used in a project, on the contrary, it becomes necessary to reflect the latest revision information even on the documents already edited.
In order to manage the consistency between the above two cases, whether to employ either one of the two cases is previously determined for each of the types of the document and shared information, and is previously stored as document attribute information.
The processing operation at the time of displaying or printing a document is changed by referring to the attribute information, so that the above two-way consistency management can be realized.
When the shared information modification is to be reflected on the shared documents to display or print the structured documents having the shared information embedded therein, this can be realized by embedding the latest version of shared information in the documents.
The operation of the present embodiment will be explained in connection with the case where the shared information modification is not to be reflected on the shared documents.
A specific processing procedure of the present embodiment will be explained with reference to flowcharts of Figs. 16 to 18, and then processing examples will be explained according to the processing procedure.
In Fig. 16 showing a procedure of editing shared information, a step 201 is the same as that in the processing procedure of the first embodiment.
Step 1601:
When the shared information storage program 106 is executed to store the shared information 103a edited in the step 201 in the secondary memory 103, control is passed to the version management program 1501, and the shared information is stored as a new version one without overwriting by execution of the program version management program 1501.
The version management program 1501 is executed to store in the secondary memory 103 version information 103c including version numbers and creation date and time of all version shared information already edited, associate the version information 103c with all the already-edited version shared information, and then store the edited version shared information in the secondary memory 103.
As a result, by specifying any version number, shared information on the specified vers;~on number can be later extracted.
Next, editing operation of a structured document is carried out according to the following procedure independently of the steps 201 and 1601.
In Fig. 17 showing a processing procedure, steps 301 to 303 are the same as those in the processing procedure of the first embodiment.
Step 1701:
When the structured document 103b edited in the step 303 is stored in the secondary memory 103 by execution of the structured document storage program 109, the document 103 is stored without overwriting it as a new version document by execution of the version management program 1501.
The version management program 1501 stores in the secondary memory 103 the version information 103c including version numbers and creation date and time of all versions of edited documents, associates the version information 103c with all the versions of edited documents, and then stores the edited version document in the secondary memory 103.
As a result, by specifying a desired version number, a structured document of the desired version can be later extracted.
Further, when it is desired to display or print the structured document 103b, a procedure is carried out according to the flowchart of Fig. 18.
In the operations of this Figure, the contents of latest one of versions of the shared information prepared prior to the creation date and time of the structured document to be displayed or printed is embedded in the structured document, and then the embedded document is displayed or printed.
Step 1801:
The creation date and time of the structured document to be displayed or printed is acquired by execution of the version management program 1501, and is set as TIME 1.
Step 1802:
The version information 103c of the shared information to be embedded in the structured document is acquired by execution of the version management program 1501.
Step 1803:
The creation date and time of the latest version of the shared information is acquired by execution of the version management program 1501. This creation date and time is set as TIME 2.
Step 1804:
When TIME 2 is earlier than TIME 1, the processing proceeds to a step 1805. When TIME 2 is not earlier than TIME1, the shared information is of the version created after the time point of having described the links in the structured document, the creation date and time of a one-previous version is acquired. This creation date and time is replaced by TIME 2 and the processing returns to the step 1804.
Step 1805:
When TIME 2 is earlier than TIME l, the shared information is information at the time at which the links have been described in the structured document, and thus the version of shared information is acquired.
Step 1806:
By execution of the structured document output program 110, the content of the shared information of the version acquired in the step 1805 is embedded in the structured document, and the embedded document is displayed or printed.
(Processing Example 3):
A specific processing example of the present embodiment will be explained with use of the document of Figs. 19 to 22 with reference to the flowcharts of Figs.
17 and 18.
Step 1601:
When the shared information edited in the step 201 is stored in the secondary memory 103 by execution of the shared information storage program 106, the edited shared information is stored as a new version by execution of the version management program 1501.
It is assumed that, for example, since the belonging department of a person "Heisei Taro" has been changed, the shared information 1101 as the person.
information of Fig. 11 has been edited as shown in Fig.
19. In this case, the shared information 1101 of the person information shown in Fig. 11 is set as version V1.0, while shared information shared information 1901 of the person information after edited is set as version V2Ø By execution of the version management program 1501, version information 2001 of creation date and time as shown in Fig. 20 is stored.
The following is a processing example of editing a structured document.
Step 1701:
When the structured document edited in the step 303 is stored in the secondary memory 103 by execution of the structured document storage program 109, the edited structured document is stored as a new version by execution of the version management program 1501.
For example, it is assumed that the structured document 1401 of Fig. 14 has been edited as another report as shown in Fig. 21 and that the structured documents of the old and new versions as well as version information 2201 of creation date and time, etc. as shown in Fig. 22 have been stored.
As shown in Fig. 22, the structured document 1401 of V1.0 is created on "1996.5.15,9:00", and the shared information inserted at that time is of V1Ø
The shared information is edited on "1996.8.21,15:30" as shown in Fig. 20 and stored as a new version V2Ø
Accordingly, since the structured document 2101 of V2.0 is created on "1996.11.20,16:30", the shared infcrmation inserted at that time is of V2Ø
Further, explanation will be then made of an example of displaying or printing the structured documents of Figs. 14 and 21, by referring to the flowchart of Fig. 18.
Step 1801:
The creation date and time of the structured document to be displayed or printed is acquired by execution of the version management program 1501. The creation date/time is set as TIME 1.
In the case of the structured document 1401 of Fig. 14, "1996.5.15,9:00" is substituted for TIME 1.
In the case of the structured document 2101 of Fig. 21, "1996.5.11,16:30" is substituted for TIME 1.
Step 1802:
The version information of the shared information to be embedded in the structured document is acquired by execution of the version management program 1501.
The version information 2001 of the shared information of Fig. 20 is acquired.
Step 1803:
The creation date and time of the latest version of the shared information is acquired by execution of the version management program 1501. The creation date and time is set as TIME 2. Here, "1996.8.21, 15:30" is substituted for TIME 2.
Step 1804:
When TIME 2 is not earlier than TIME 1, this means that the shared information is edited after the time point at which the link has been described in the structured document. Thus, the creation date and time of the one-previous version is acquired. The acquired creation date and time is substituted for TIME 2, and then, the processing returns to the step 1804.
In the case of the structured document 1401 of Fig. 14, since TIME 2 is later than TIME l, the creation date and time "1996.4.1,10:00" of the one-previous version V1.0 is substituted for TIME 2. At this time point, TIME 2 is earlier than TIME 1.
In the case of the structured document 2101 of Fig. 21, TIME 2 is earlier than TIME 1.
Step 1805:
When TIME 2 is earlier than TIME 1, the shared information is the information at the time point at which the link has been described in the structured document, so that the shared information of that version is acquired.
In the case of the structured document 1401 of Fig. 14, the version V1.0 is acquired.
In the case of the structured document 2101 of Fig. 21, the version V2.0 is acquired.
Step 1806:

The content of the shared information acquired in the step 1805 is embedded in the structured document and displayed or printed by execution of the structured document output program 110.
In the case of the structured document 1401 of Fig. 14, the content of the shared information of Vi.O
is embedded therein, so that its belonging department column has "development department 12 group" corre-sponding to the content at the time of creating the structured document.
In the case of the structured document 2101 of Fig. 21, the content of the shared information of V2.0 is embedded therein, so that its belonging department column has "development department 16 group" corre-sponding to the content at the time of creating the structured document.
Through the above steps, when a structured document created in the past is displayed or printed, the shared information at the time point of having created the structured document can be embedded therein.
It will be easily appreciated that, when a structured document is copied and edited to create another document, it is unnecessary to change the description of the link to the shared information and the shared information at that time point is auto-matically embedded, thus facilitating document re-use.
When shared information to be embedded in a structured document mixedly contains such shared information as person information rea_uiring the aforementioned version selection and shared information such as term information for which the latest version is always selected; a flag is provided at each link location in the structured document. In the case of the person information, the flag is set; while, in the case of the term information, the flag is not set. When the flag is set in the display or print mode, operations as shown by the flowchart in Fig. 18 are carried out to select a version and to embed the shared information.
When the flag is not set, the latest version is selected to embed the shared information.
In addition to combination terms such as person information indicative of a combination of term, person's name and belonging department as shown in Embodiments 1 and 2, there are various types of shared information which are valid when the shared information are stored according to their types, listed up and shared between structured documents.
When HyTime is used, a link to image or audio data can also be described. Thus, when personal photographic information (image data) or brief self introduction by her or his speech (audio data) as an example is previously stored in association with a person, the present invention can be applied to various types of documents including writer introduction of papers or web pages in world wide web (WWW).
In accordance with the present invention, such photographic information is previously stored as upgraded at suitable intervals, so that, when a past document such as a paper is displayed or printed, the information at the time point of having created the document can be used, and when an active document such as web pages is displayed or printed, the latest information can be used, thus realizing more flexible information re-use.
<Embodiment 3>
In Embodiment 2, the structured document has been correctly displayed or printed, when the shared information is edited but it is desired not to reflect the modification on past documents already edited and having links to the shared information, by embedding the shared information at the time of having created the structured document.
Embodiment 3 is intended, when shared information is edited but it is desired to reflect the modification on past documents already edited and having links to the shared information, to correctly display or print a structured document even when the link correlation varies due to the influence of the modification of the shared information.
Explanation will first be made of a problem that the link correlation varies.
It is now assumed that shared information 2601 of V1.0 has been edited to create a shared information 2602 of V2.0 as shown in Fig. 26, for instance.

Fig. 26 shows shared information of persons.
The shared information of V2.0 contains, in addition to the information of V1.0, structures 2603 and 260 of <name number>. In addition, the belonging department of "Heisei Taro" and extension telephone number as a character string are changed.
Assume that, prior to the editing of the shared information of Fig. 26 to V2.0, a structured document 2700 having a link to the shared information 2601 described therein as shown in Fig. 27 has already existed.
In the structured document 2700, similarly to the structured document of Fig. 13 shown by the processing example 2 of Embodiment 1, the link is described based on HyTime notation as a relative position with respect to KEY.
In a description 2701, first of all, ENTITY
reference to the shared information 2601 of Fig. 26 stored under a file name of "person dic.sgm" is described. Due to this description, the document shared information 2601 of "person dic.sgm" can be referenced with the ENTITY name of "person dic".
In a description 2704, a structure "taro" as an ID in "person-dic.sgm" can be referenced with use of an ID of "person ref" 2709.
In a description 2705, an ID of "person name ref" 2710 indicates the first child of its own as viewed from a structure "person ref". That is, it indicates a structure <name> having the contents of "Heisei Taro". The first "1" in the contents of <marklist> given below <treeloc> means its own, and the next "1" means the first child.
In a description 2706, similarly, an ID of "person belong ref" 2711 indicates a structure of the second child as viewed from a structure "person tel ref"
2712 indicates a structure of the third child as viewed from a structure of "person ref".
The respective IDs, which can be subjected to the IDREF reference from inside the document, are defined as attribute values of <TERM>, respectively.
When the structured document described in such a manner as mentioned above is displayed by execution of the structured document output program 110 in accordance with the steps 401 and 402; the contents of the shared information described as the links, i.e., the name "Heisei Taro", belonging department "development depart-ment 12 group" and extension telephone number "1111" are embedded in the structured document, and the embedded structured document is displayed in the form of a layout as shown in Fig. 28.
When the structured document 2700 is displayed or printed after the shared information 2601 is edited into V2.0 information, the system shown in Embodiment 1 involves a problem described below.
That is, the structured document 2700 is a document for describing self introduction therein, so that when it is desired to display or print the document, the latest information should be always displayed or printed. To this end, when the latest shared information 2602 is displayed as embedded in the structured document, it is undesirably displayed as shown in Fig. 29, because the link is described as a relative position with respect to KEY.
This means that, though the belonging department is defined in the structured document 2700 as the second child from the viewpoint of having an ID
"taro", insertion of a new structure in the shared information of V2.0 results in the belonging department not being the second child, thus changing its link correlation.
In Fig. 29, the contents of <name number> as the second child of a structure having an ID "taro" is displayed as the contents of the belonging department in the latest shared information 2602. Similarly, repre-sentation of its extension telephone number is also shifted and is not correct.
It is desirable that a link destination originally refers to the same structure as that at the time of creating it and contents thereof be the latest ones.
The above problem can be avoided by describing the link in the form of not the relative position but an absolute position using a structure ID. However, this system also eliminates such a merit as exemplified in Embodiments 1 and 2, that is, only KEY modification enables automatic modification of all rela~ed information.
In order to embed the contents of the latest shared information in the structured document having the links to the shared information described therein and to prevent a structure discrepancy, the present embodiment provides such an arrangement as shown in Fig. 23.
As illustrated, the present embodiment is arranged, in addition to the arrangement (see Fig. 15) of Embodiment 2, so that, when shared information is edited after creation of a structured document to thereby change a character string or structure of the shared information, a consistency processing program 2301 performs its consistency processing operation on the shared information to create new shared information already subjected to the consistency processing operation, whereby the consistency-processed shared information can be displayed or printed as embedded in the structured document by execution of the structured document output program 110.
The consistency-processed shared information generated by the consistency processing program 2301 refers to such information that, with respect to shared information after a character string or structure has been changed, the contents of the character string are the same as those after the change, the structure change causes the structured document to be returned to its creation time state, so that, by embedding it in the structured document, the change in the contents of the character string are reflected and the original link correlation can be correctly maintained.
A specific processing procedure of the present embodiment will be explained with use of the flowcharts of Figs. 24 and 25.
After that, a processing example will be explained in accordance with the processing procedure.
The editing procedure of shared information and the editing procedure of a structured document are the same as the operations of the steps 201 and 202 and steps 301 to 304 indicated in Embodiment 1. The structured document is displayed in accordance with a processing procedure, as shown in Fig. 24, described below.
Step 2401:
A structured document to be displayed or printed is acquired from the secondary memory 103 by execution of the version management program 1501.
Step 2402:
When the structured document with the latest version shared information embedded therein is displayed or printed, consistency operation is carried out to the latest shared information by execution of consistency processing program 2301 to generate shared information subjected to the consistency operation. The details will be later explained in steps 2501 to 2504. When the latest versicn shared information is not embedded, a step 2404 is performed.
Step 2403:
The contents of the consistency-processed shared information generated in the step 2402 are embedded in locations described as links in the structured document to obtain an embedded structured document, and then the embedded structured document is displayed or printed Step 2404:
When the latest version shared information is not to be embedded in the structured document for its display or printout, the shared information at the time of creating the structured document is acquired by execution of the version management program 1501 in accordance with a procedure similar to that of the steps 1801 to 1805 in Embodiment 2.
Step 2405:
The contents of the shared information acquired in the step 2404 are embedded at locations described as links in the structured document, and then the structured document is displayed or printed by execution of the structured document output program 110.
Detailed explanation will be made of a processing procedure of subjecting the latest shared information to the consistency operation to generate consistency-processed shared information by execution of the consistency processing program consistency processing program 2301, indicated in the step 2402 by referring to the flowchart of Fig. 25.
Step 2501:
The latest shared information is acquired by execution of the version management program 1501.
Step 2502:
Shared information at the time of creating the structured document is acquired by execution of the version management program 1501 in accordance with a procedure similar to that of the steps 1$01 to 1805 shown in Embodiment 2.
Step 2503:
The latest shared information acquired in the step 2501 is compared with the shared information at the time of creating the structured document acquired in the step 2502 to extract a structure-changed location.
Step 2504:
When the structure-changed location is extracted in the step 2503, this means that there may be a discrepancy in the link to the shared information. In this case, the structure change is returned to its state at the time of creating the structured document for its modification to thereby generate consistency-processed shared information.
First, in order to return the structure change to the state at the document creation time, if a new structure is added to the shared information at the document creation time, then the new additional structure is deleted from the latest shared information.
On the contrary, if a structure in the shared information at the document creation time is deleted from the new shared information, then the creation-time structure is added to the latest shared information.
The structure exchange is regarded as structure deletion and insertion, which is carried out in the same manner as the above.
Such modified latest shared information is called shared information which has been modified so as to keep the consistency.
(Processing Example 4) A specific processing example of the embodi-ment will be explained in connection with, as an example, the shared information of Fig. 26 and the structured document of Fig. 27 with reference to the flowcharts of Figs. 24 and 25.
Step 2401:
A structured document to be displayed or printed is acquired from the secondary memory 103 by execution of the version management program 1501. In this case, the structured document of Fig. 27 is acquired.
Step 2402:
When the structured document with the latest version shared information embedded therein is to be displayed or printed, the latest shared information is consistency-processed to generate consistency-processed shared information.
A processing example of the step 2402 will be detailed with use of the flowchart of Fiq. 25.
Step 2501:
The latest shared information is acquired by execution of the version management program 1501. The shared information 2602 of the latest V2.0 is acquired in Fig. 26.
Step 2502:
The shared information at the time of creating the structured document is acquired by execution of the version management program 1501 according to a procedure similar to that of the steps 1801 to 1805 shown in Embodiment 2.
Since the structured document 2700 of Fig. 27 has been already created before the editing of the shared information V2.0, the shared information 2601 of V1.0 is acquired.
Step 2503:
The latest shared information acquired in the step 2501 is compared with the shared information at the document creation time acquired in the step 2502 to extract a structure changed location.
There are considered several methods of extracting a structure changed location. Employed in the present processing example, however, is, aS an example, a difference extracting method by execution of a program which compares the old and new structured documents.
Fig. 30 shows a difference extracting result between the shared information of V1.0 and V2.0 acquired in the steps 2501 and 2052.
Fig. 30 shows that extraction is made such that character string changes are made at locations 3003 and 3004 shown by underlines in Fig. 30, and structure changes are made at locations 3005 and 3006 shown by areas shaded by slanted lines.
Step 2504:
When a structure changed location is extracted in the step 2503, there may be a discrepancy in the link to the shared information. To avoid this, the structure change in the latest shared information is returned and modified to the state at the time of having created the structured document to thereby generate consistency-processed shared information.
It will be seen from Fig. 30 that the structures 3005 and 3006 are newly added in the latest shared information. In order to return the shared information to the state at the document creation time, these structures are deleted from the latest shared information. In this connection, as a difference extraction technique, there can be employed a technique disclosed in U.S. Patent No. 5,956,726, issued on September 21, 1999.

Fig. 30 shows the consistency-processed shared information modified in this way. In Fig. 31, the newly-added structures <name number> are deleted, but the character string changed locations remain as they are as the latest contents 3102.
Step 2403:
The contents of the consistency-processed shared information generated in the step 2402, i.e., steps 2501 to 2504 are embedded at locations described as links in the structured document, and the embedded structured document is displayed or printed by execution of the structured document output program 110.
Fig. 32 shows an example of the consistency-processed shared information of Fig. 31 when the structured document of Fig. 27 is embedded and displayed. As shown in Fig. 32, no discrepancy takes place in the structures described as link destinations at the document creation time while the contents of the shared information are displayed as the latest information in the form of a layout.
When the latest shared information is not to be embedded, the operations of the steps 2404 and 2405 are carried out, which are the same as those in Embodiment 2 and thus explanation thereof is omitted.
Through the above steps, the shared information is edited. When the modification change be reflected on structured documents commonly having the shared information, the latest contents can be reflected on the documents while preventing any shift of the link correlation between the documents and shared information.
The functional programs of the memories shown in Embodiments of Figs. 1, 15 and 23 can be stored in a memory medium; such as CD-FOM, DVD-ROM or floppy disk to be installed from the medium to an implementation device. Alternatively, these programs may also be installed from a server into the primary memory 1.
These programs may be installed in various aspects, as will be appreciated easily.

Claims (18)

1. A structured document processing method in an information processing system comprising a processor, a memory and a terminal, said method comprising:
generating a block of shared information as a set of shared information appearing in a plurality of structured documents;
editing said shared information;
managing a change history of said shared information, providing edited shared information with version information as a new version for said shared information and storing the version-provided shared information in said memory;
editing a structured document and describing a link to said shared information in said structured document;
managing a change history of said structured document, providing the edited structured document with version information as a new version for said structured document and storing the version-provided structured document in said memory;
reading from said memory said shared information and said structured document, embedding the shared information in the structured document according to the link described in the structured document and outputting the structured document into which said the shared information is embedded;

wherein, when embedding said shared information into said structured document, said outputting step comprises, embedding one of the latest version of said shared information or the latest version of said shared information among versions generated prior to generation of said structured document according to said version information for said shared information.
2. The structured document processing method according to claim 1, wherein the step of embedding the shared information is performed according to a type for the structured document, a type for the shared information or a combination of the type for the structured document and the type for the shared information.
3. The structured document processing method according to claim 1, wherein the step of embedding the shared information is performed according to a value of a flag set in the link of said structured document.
4. The structured document processing method according to one of claims 1, 2 and 3, further comprising:
subjecting the shared information to a consistency processing operation to generate consistency-processed shared information, wherein when said shared information is generated and a character string or structure is changed after editing said document, said consistency processing step comprises generating consistency-processed shared information sufficient to maintain contents of said character string in its state after the change and return the structure to its state at the time of creating the document, and said embedding step embeds said consistency-satisfied shared information in the structured document in place of said latest version of the shared information.
5. The structured document processing method according to claim 4, wherein said consistency processing step acquires the latest version of said shared information and a version of the shared information at the time of creating the structured document, compares the acquired shared information to extract a structure changed location, and, when the structure change is extracted, returns the changed structure to its state at the time of creating the structured document in the latest shared information to generate consistency-satisfied shared information.
6. The structured document processing method according to claim 5, wherein, when the structure is changed in said consistency processing step, the structure is deleted from the latest shared information when contents of the change corresponds to insertion of the structure in the shared information at the structured document creation time, when the contents of the change corresponds to deletion of the structure from the shared information at the structured document creation time, the structure is inserted in the latest shared information, and when the contents of the change corresponds to exchange of the structure of the shared information at the structured document creation time, the structure after the exchange is deleted from the latest shared information and the structure before the exchange is inserted to thereby generate said consistency-satisfied shared information.
7. A structured document processing system in an information processing system comprising a processor, a memory and a terminal, said structured document processing system comprising:
means for generating a block of shared information as a set of shared information appearing in a plurality of structured documents;
means for editing said shared information;
means for managing a change history of said shared information, providing edited shared information with version information as a new version for the said shared information and storing the version-provided shared information in said memory;
means for editing a structured document and describing a link to said shared information in said structured document;
means for managing a change history of said structured document, providing the edited structured document with version information as a new version for said structured document and storing the version-provided structured document in said memory;

means for reading from said memory said shared information and said structured document, embedding the shared information in the structured document according to the link described in the structured document and outputting the structured document into which said the shared information is embedded;
wherein said means for reading, embedding and outputting comprises means for embedding one of the latest version of said shared information or the latest version of said shared information among versions generated prior to generation of said structured document according to said version information for shared information when embedding said shared information into said structured document according to the link information in said structured document.
8. The structured document processing system according to claim 7, wherein said means for embedding the shared information operates according to a type for the structured document, a type for the shared information or a combination of the type for the structured document and the type for the shared information.
9. The structured document processing system according to claim 7, wherein said means for embedding the shared information operates according to a value of a flag set in the link of said structured document.
10. The structured document processing system according to one of claims 7, 8 and 9, further comprising:
means for subjecting the shared information to a consistency processing operation to generate consistency-processed shared information subjected to the consistency processing operation, wherein when said shared information is generated and a character string or structure is changed after editing of said document, said means for subjecting comprises means for generating consistency-processed shared information sufficient to maintain contents of said character string in its state after the change and return the structure to its state at the time of creating the document, and said means for embedding comprises means for embedding said consistency-satisfied shared information in the structured document in place of said latest version of the shared information.
11. The structured document processing system according to claim 10, wherein said means for subjecting comprises means for acquiring the latest version of said shared information and a version of the shared information at the time of creating the structured document, comparing the acquired shared information to extract a structure changed location, and, when the structure change is extracted, returning the changed structure to its state at the time of creating the structured document in the -latest shared information to generate consistency-satisfied shared information.
12. The structured document processing system according to claim 11, wherein, when the structure is changed by said means for subjecting, the structure is deleted from the latest shared information when contents of the change corresponds to insertion of the structure in the shared information at the structured document creation time, when the contents of the change corresponds to deletion of the structure from the shared information at the structured document creation time, the structure is inserted in the latest shared information, when the contents of the change corresponds to exchange of the structure of the shared information at the structured document creation time, the structure after the exchange is deleted from the latest shared information and the structure before the exchange is inserted to thereby generate said consistency-satisfied shared information.
13. A computer readable medium having stored thereon computer-executable instructions for structured document processing in an information processing system comprising a processor, a memory and a terminal, said instructions comprising:
generating a block of shared information as a set of shared information appearing in a plurality of structured documents;
editing said shared information;

managing a change history of said shared information, providing edited shared information with version information as a new version for said shared information and storing the version-provided shared information in said memory;
editing a structured document and describing a link to said shared information in said structured document;
managing a change history of said structured document, providing the edited structured document with version information as a new version for said structured document and storing the version-provided structured document in said memory;
reading from said memory said shared information and said structured document, embedding the shared information in the structured document according to the link described in the structured document and outputting the structured document into which said the shared information is embedded;
wherein, when embedding said shared information into said structured document, said outputting step comprises, embedding one of the latest version of said shared information or the latest version of said shared information among versions generated prior to generation of said structured document according to said version information for said shared information.
14. The computer-executable instructions according to claim 13, wherein the step of embedding the shared information is performed according to a type for the structured document, a type for the shared information or a combination of the type for the structured document and the type for the shared information.
15. The computer-executable instructions according to claim 13, wherein the step of embedding the shared information is performed according to a value of a flag set in the link of said structured document.
16. The computer-executable instructions according to one of claims 13, 14 and 15, further comprising:
subjecting the shared information to a consistency processing operation to generate consistency-processed shared information, wherein when said shared information is generated and a character string or structure is changed after editing said document, said consistency processing step comprises generating consistency-processed shared information sufficient to maintain contents of said character string in its state after the change and return the structure to its state at the time of creating the document, and said embedding step embeds said consistency-satisfied shared information in the structured document in place of said latest version of the shared information.
17. The computer-executable instructions according to claim 16, wherein said consistency processing step acquires the latest version of said shared information and a version of the shared information at the time of creating the structured document, compares the acquired shared information to extract a structure changed location, and, when the structure change is extracted, returns the changed structure to its state at the time of creating the structured document in the latest shared information to generate consistency-satisfied shared information.
18. The computer-executable instructions according to claim 17, wherein, when the structure is changed in said consistency processing step, the structure is deleted from the latest shared information when contents of the change corresponds to insertion of the structure in the shared information at the structured document creation time, when the contents of the change corresponds to deletion of the structure from the shared information at the structured document creation time, the structure is inserted in the latest shared information, and when the contents of the change corresponds to exchange of the structure of the shared information at the structured document creation time, the structure after the exchange is deleted from the latest shared information and the structure before the exchange is inserted to thereby generate said consistency-satisfied shared information.
CA002242904A 1997-07-08 1998-07-06 Document processing method and system, and computer-readable recording medium having document processing program recorded therein Expired - Fee Related CA2242904C (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
JP19790797 1997-07-08
JP09-197907 1997-07-08
JP10117803A JPH1185750A (en) 1997-07-08 1998-04-13 Structured document rpocessing method, structured document rpocessor and computer-readable recording medium recorded with structured document processing program
JP10-117803 1998-04-13

Publications (2)

Publication Number Publication Date
CA2242904A1 CA2242904A1 (en) 1999-01-08
CA2242904C true CA2242904C (en) 2006-02-28

Family

ID=26455855

Family Applications (1)

Application Number Title Priority Date Filing Date
CA002242904A Expired - Fee Related CA2242904C (en) 1997-07-08 1998-07-06 Document processing method and system, and computer-readable recording medium having document processing program recorded therein

Country Status (5)

Country Link
US (3) US6349302B1 (en)
JP (1) JPH1185750A (en)
KR (1) KR100305459B1 (en)
CN (1) CN1097795C (en)
CA (1) CA2242904C (en)

Families Citing this family (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH1185750A (en) * 1997-07-08 1999-03-30 Hitachi Ltd Structured document rpocessing method, structured document rpocessor and computer-readable recording medium recorded with structured document processing program
US6584459B1 (en) * 1998-10-08 2003-06-24 International Business Machines Corporation Database extender for storing, querying, and retrieving structured documents
JP2000287110A (en) * 1999-03-31 2000-10-13 Ricoh Co Ltd Control system for digital camera
US6763496B1 (en) 1999-03-31 2004-07-13 Microsoft Corporation Method for promoting contextual information to display pages containing hyperlinks
US6578078B1 (en) 1999-04-02 2003-06-10 Microsoft Corporation Method for preserving referential integrity within web sites
GB2351165B (en) * 1999-06-18 2003-11-05 Univ London Method and apparatus for monitoring and maintaining the consistency of distributed documents
JP4827275B2 (en) * 1999-08-10 2011-11-30 シャープ株式会社 Electronic book display device and recording medium recording computer program
US6631519B1 (en) * 2000-03-30 2003-10-07 Microsoft Corporation Automated schema and interface generation
US20060074727A1 (en) * 2000-09-07 2006-04-06 Briere Daniel D Method and apparatus for collection and dissemination of information over a computer network
KR100436702B1 (en) * 2000-10-11 2004-07-03 맹성현 System and method for providing virtual document
FR2818409B1 (en) * 2000-12-18 2003-03-14 Expaway METHOD FOR DIVIDING STRUCTURED DOCUMENTS INTO MULTIPLE PARTS
US7302634B2 (en) * 2001-03-14 2007-11-27 Microsoft Corporation Schema-based services for identity-based data access
US7284271B2 (en) 2001-03-14 2007-10-16 Microsoft Corporation Authorizing a requesting entity to operate upon data structures
US7024662B2 (en) * 2001-03-14 2006-04-04 Microsoft Corporation Executing dynamically assigned functions while providing services
US7136859B2 (en) 2001-03-14 2006-11-14 Microsoft Corporation Accessing heterogeneous data in a standardized manner
US7539747B2 (en) * 2001-03-14 2009-05-26 Microsoft Corporation Schema-based context service
US20020133535A1 (en) * 2001-03-14 2002-09-19 Microsoft Corporation Identity-centric data access
US20030014512A1 (en) * 2001-07-10 2003-01-16 Murata Kikai Kabushiki Kaisha Communication apparatus and structured document management apparatus
US20030197060A1 (en) * 2001-12-06 2003-10-23 Vince Coyner Consumer-focused gallon-based prepaid gasoline card, system and method for a car drivers
US9886309B2 (en) 2002-06-28 2018-02-06 Microsoft Technology Licensing, Llc Identity-based distributed computing for device resources
US7546541B2 (en) * 2002-12-10 2009-06-09 International Business Machines Corporation Method and apparatus for iterative refinement of generated user-interface markup
US20040135805A1 (en) * 2003-01-10 2004-07-15 Gottsacker Neal F. Document composition system and method
US7454744B2 (en) * 2003-07-03 2008-11-18 International Business Machines Corporation Private source code commenting
US7437668B2 (en) * 2005-03-24 2008-10-14 Xerox Corporation System and method for autonomous correction of defective documents
US7720829B2 (en) * 2005-07-14 2010-05-18 International Business Machines Corporation Middleware sign-on
US20070130509A1 (en) * 2005-12-05 2007-06-07 Xerox Corporation Custom publication rendering method and system
JP4693669B2 (en) * 2006-03-23 2011-06-01 キヤノン株式会社 Image forming apparatus, image processing apparatus, image forming method, image processing method, program, storage medium
JP2009099073A (en) * 2007-10-19 2009-05-07 Fuji Xerox Co Ltd Document processing history management system, document processing history management device and program
CN102165410A (en) * 2008-01-31 2011-08-24 惠普开发有限公司 Printing structured documents
JPWO2010067675A1 (en) * 2008-12-12 2012-05-17 コニカミノルタホールディングス株式会社 Information processing system, information processing apparatus, and information processing method
US8327278B2 (en) * 2009-02-17 2012-12-04 Microsoft Corporation Synchronizing metadata describes user content updates and an indication of user gestures being performed within the document, and across client systems using different communication channels
KR20110031087A (en) * 2009-09-18 2011-03-24 인터내셔널 비지네스 머신즈 코포레이션 Link clouds and user/community-driven dynamic interlinking of resources
JP2011150424A (en) * 2010-01-19 2011-08-04 Nec Corp Document preparation support system, document preparation support method and program
US8830513B2 (en) * 2012-10-12 2014-09-09 Esko Software Bvba Method and apparatus for optimizing a destination variable document from a source variable document having recurring and variable content
US9134931B2 (en) * 2013-04-30 2015-09-15 Hewlett-Packard Development Company, L.P. Printing content over a network
KR20160039746A (en) * 2014-10-01 2016-04-12 삼성전자주식회사 Information sharing method and electronic device thereof
US20170139891A1 (en) * 2015-11-13 2017-05-18 Sap Se Shared elements for business information documents
CN107239437B (en) * 2017-06-06 2018-10-19 智为天下(北京)科技有限公司 A kind of document edit method, device, readable storage medium storing program for executing and terminal device
CN112685553A (en) * 2019-10-18 2021-04-20 小船出海教育科技(北京)有限公司 Method, device, equipment and medium for searching and replacing online document

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH04260263A (en) * 1991-02-14 1992-09-16 Canon Inc Document processor
US5649200A (en) * 1993-01-08 1997-07-15 Atria Software, Inc. Dynamic rule-based version control system
US5778398A (en) * 1993-07-20 1998-07-07 Canon Kabushiki Kaisha Document processing to permit sharing of content by plural documents
JP3053153B2 (en) * 1993-09-20 2000-06-19 株式会社日立製作所 How to start application of document management system
US5835911A (en) * 1994-02-08 1998-11-10 Fujitsu Limited Software distribution and maintenance system and method
JP3484775B2 (en) * 1994-07-29 2004-01-06 富士ゼロックス株式会社 Document processing apparatus and method
JPH08106464A (en) * 1994-10-04 1996-04-23 Fuji Xerox Co Ltd Document generating device
US5671427A (en) * 1994-10-12 1997-09-23 Kabushiki Kaisha Toshiba Document editing apparatus using a table to link document portions
JP3028738B2 (en) * 1994-11-10 2000-04-04 富士ゼロックス株式会社 Document common logical information editing device
JP3279201B2 (en) * 1996-05-17 2002-04-30 富士ゼロックス株式会社 Information processing device
US5802523A (en) * 1996-06-21 1998-09-01 Oracle Corporation Method and apparatus for reducing the memory required to store bind variable descriptors in a database
JP3790602B2 (en) * 1997-04-25 2006-06-28 富士ゼロックス株式会社 Information sharing device
JPH1185750A (en) * 1997-07-08 1999-03-30 Hitachi Ltd Structured document rpocessing method, structured document rpocessor and computer-readable recording medium recorded with structured document processing program
US6584466B1 (en) * 1999-04-07 2003-06-24 Critical Path, Inc. Internet document management system and methods

Also Published As

Publication number Publication date
CA2242904A1 (en) 1999-01-08
CN1205481A (en) 1999-01-20
JPH1185750A (en) 1999-03-30
US20040049626A1 (en) 2004-03-11
KR19990013654A (en) 1999-02-25
US20020073093A1 (en) 2002-06-13
US7113952B2 (en) 2006-09-26
US6651069B2 (en) 2003-11-18
KR100305459B1 (en) 2001-10-29
US6349302B1 (en) 2002-02-19
CN1097795C (en) 2003-01-01

Similar Documents

Publication Publication Date Title
CA2242904C (en) Document processing method and system, and computer-readable recording medium having document processing program recorded therein
US9639517B2 (en) Web page authoring
US6061698A (en) Merging tagged documents and scripts having dynamic content
US5553216A (en) Structured database system together with structure definition frame storing document body data
US6931590B2 (en) Method and system for managing documents
US7127472B1 (en) Data processing method and data processing device
US5806078A (en) Version management system
US6668354B1 (en) Automatic display script and style sheet generation
US7546533B2 (en) Storage and utilization of slide presentation slides
EP0430505B1 (en) A support method and apparatus for making a formated document
US20020087602A1 (en) Information processing apparatus, method therefor, and computer-readable memory
US7398214B2 (en) Method for translating slide presentations into different languages
US20060123337A1 (en) Web page authoring apparatus, method, and program
US6571248B1 (en) Data processing method and apparatus
US20060294468A1 (en) Storage and utilization of slide presentation slides
JP5252933B2 (en) Document processing apparatus, document processing method, and program
JPH0830620A (en) Structure retrieving device
JPH04229364A (en) Method and system for changing emphasizing characteristic
US20190147022A1 (en) Method, program, recording medium, and device for assisting in creating homepage
JP3444948B2 (en) Document editing apparatus and document editing method
GB2307571A (en) Automatically generating a document type definition
JP3765123B2 (en) Document display method and document management method
US6498964B1 (en) Job processing system using job designation sheet
JP4149940B2 (en) Document processing apparatus, document processing method, and document processing program
JPH11259458A (en) Document processor

Legal Events

Date Code Title Description
EEER Examination request
MKLA Lapsed