JP2003216626A - Structured document processing apparatus, method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To simplify a program in the development of a structured document processing function. <P>SOLUTION: The structured document processing apparatus includes a database 3 for storing the relationship between data; a database operation processing part 4 for executing such operation as retrieving data from the database 3; a database/structured document converting process part 6 for converting the data from the database 3 into an intermediate structured document 6; a document rule file 1 for specifying limitations on the relationship between element contents in an input structured document or documents; and a limitation canceling process part 7 which, upon the input of the input structured document 2 and the intermediate structured document 6, verifies whether or not the input structured document 2 satisfies the relationship limitations specified in the document rule file 1. <P>COPYRIGHT: (C)2003,JPO

Description

Detailed Description of the Invention

[0001]

TECHNICAL FIELD The present invention relates to electronic commerce (E
C: Electronic Commerce) and CA
LS (Commerce At Light Speed)
In d), XML (eXtensible Mar)
kup Language) and SGML (Standard)
rd Generalized Markup Lan
The present invention relates to a structured document processing device, a structured document processing method, and a structured document processing program required for smoothly distributing a structured document such as a document) between companies or organizations within a company.

[0002]

2. Description of the Related Art With the progress of EC and CALS, there is an increasing demand for exchanging document data that can be processed by information systems among companies. As a structured document standard format to meet this demand, ISO (Internati)
onal Standard Organizatio
n) Standard 8879 SGML and W3C (World W)
X established by the idea Web Consortium)
ML (http://www.w3.org/TR/2
000 / REC-xml-20001006).

In the field of electronic commerce between companies, the consistency between the contents of the structured document expressing the purchase order and the quotation reply and the contents of the database (DB) of the accounting system and the inventory management system is verified. There is a need to develop a document processing function that spans multiple structured documents and databases in. As a related technology to meet this demand, there is a data exchange processing method between a structured document and a database. This is a method of registering the contents of a structured document in a database and outputting the contents of the database to a structured document.

FIG. 17 shows, for example, Japanese Patent Laid-Open No. 2001-92695.
FIG. 1 is a block diagram showing a configuration of a conventional structured document processing device disclosed in “a structured document / database data exchange processing method and a medium in which a program thereof is recorded” of the publication. In the figure, 101 is a database that receives data from the structured document 104 and provides data to the structured document 104, 102 is an application program that uses the data mapping support function program component 103, and 103 is a data exchange processing method. A data mapping support function program component, 104 is a structured document that is an object for data extraction and embedding, and 105 is a data mapping support file that defines a data exchange method.

In FIG. 17, reference numeral 106 is template data in which the contents of the data mapping support file 105 are read into the data mapping support function program component 103 according to an instruction from the application program 102, and 107 is selected from the template data 106. A command character string for accessing the created database 101, and 108 is search result data obtained by accessing the database 101.

Next, the operation will be described. The data mapping support function program component 103 refers to the template data 106 to generate a command character string 107 for searching the database 101, and
The search result data 108 is executed by executing the search process for 01.
To get Next, the data mapping support function program component 103 embeds the search result data 108 in the structured document 104 with reference to the data mapping support file 105 that describes the method of importing data into the structured document 104.

According to the above method, the data mapping support file 105 is set as an external file so that J
Development using a programming language such as ava (R) is not required, and programming in program system development is simplified to streamline the development and maintenance of the function of outputting the contents of the database 101 to the structured document 104. You can

However, in order to realize the application function across a plurality of structured documents and databases as described below, J
It is necessary to develop a separate program depending on the application function using a programming language such as ava (R). (1) Consistency verification function between a plurality of structured documents and a database For example, whether all the component numbers applied for in the ordering specifications, which are structured documents, are registered in the database, It is a function to verify whether all the registered part numbers are included in the order specifications. (2) Structured document generation function that refers to the contents of a plurality of structured documents and database For example, when the telephone number of the ordering company is changed,
This is a function for automatically correcting the telephone number of the ordering company in the ordering specification, which is a structured document, by referring to the contents of the database using the company name of the ordering party as a key. (3) Database registration function that integrates a plurality of structured documents and database contents For example, when ordering to an overseas country, refer to the structured document that describes the exchange rate and calculate the yen-denominated cost of the foreign currency amount. This is a function of registering the contents of the ordering specification, which is another structured document obtained as a result of the substitution, in the database.

[0009]

Since the conventional structured document processing apparatus is configured as described above, programming in developing a structured document generation function from the contents of the database can be simplified. Structured document processing functions such as a consistency verification function across a plurality of structured documents and databases, a structured document generation function, and a database registration function require separate development in a programming language such as Java (R). There was a problem that the efficiency of development and maintenance was not improved.

The present invention has been made in order to solve the above-mentioned problems, and by implementing a document rule that defines the specifications of structured document processing as an external file, it spans a plurality of structured documents and databases. A structured document processing device, a structured document processing method, and a structured document processing program, which do not require a separate development in a programming language such as Java (R) in the development of the structured document processing function and can simplify programming. Aim to get.

[0011]

A structured document processing device according to the present invention includes a database for storing data such as numerical values, texts, and binary data and a relationship between the data, and a data search for the database. A database operation processing unit that executes operations such as registration, update, and deletion, and requests the database operation processing unit to operate the database, and the data obtained from the database by the database operation processing unit is converted into an intermediate structured document. A database / structured document conversion processing unit for conversion, a document rule file that defines a relational constraint between element contents in one or more input structured documents or the intermediate structured document, the input structured document, and the intermediate Input the structured document, the input structured document or the intermediate structured document, and It is verified whether the document or the intermediate structured document satisfies the relationship constraint defined in the document rule file, or the input structured document or the intermediate structured document is satisfied so as to satisfy the relationship constraint. And a constraint resolution processing unit for converting

In the structured document processing device according to the present invention, a query language description that prescribes commands for data retrieval, registration, update, deletion, etc. to the database is included in the relational constraints prescribed in the document rule file. Prepared, the constraint resolution processing unit,
The question language description provided in the document rule file is used to execute the operation by the database / structured document conversion processing unit.

In the structured document processing device according to the present invention, the table name, the tuple name, the column name in the query language description for the database and the input structured document or the intermediate structure are included in the relation constraint defined in the document rule file. The database / structured document conversion processing unit is provided with a database / document relation constraint description that defines the correspondence relationship between the element name and the attribute name of the structured document. With reference, the data obtained from the database is converted into an intermediate structured document.

In the structured document processing device according to the present invention, in the input constraint document or the intermediate structured document, the element or attribute targeted by the relational constraint is included in the relational constraint defined in the document rule file. The document in the input structured document or the intermediate structured document is referred to by the constraint resolution processing unit by referring to the document context description provided in the document rule file. It verifies whether or not the relationship constraint between contents is satisfied, or transforms the input structured document or the intermediate structured document so as to satisfy the relationship constraint.

In the structured document processing device according to the present invention, the relational constraint for each of a plurality of elements repeatedly appearing in the input structured document or the intermediate structured document in the relational constraint defined in the document rule file. A universal quantification description for describing the above, and the constraint resolution processing section refers to the universal quantification description provided in the document rule file to refer to the element contents in the input structured document or the intermediate structured document. Whether to verify whether the relationship constraint between
Alternatively, the input structured document or the intermediate structured document is converted so as to satisfy the relationship constraint.

In the structured document processing device according to the present invention, the constraint resolution processing section verifies whether or not the relational constraint defined in the document rule file is satisfied and outputs it as verification information.

In the structured document processing device according to the present invention, the constraint resolution processing section outputs the output structured document obtained as a result of substituting the contents of the database into the input structured document.

The structured document processing device according to the present invention includes a query language description that defines commands for searching, registering, updating, deleting, etc., of data in the database in the relational constraint defined in the document rule file. , A table / tuple name / column name in this question language description, and a database / document relation constraint description that defines the correspondence relation between the element name and the attribute name of the input structured document. The contents of the input structured document are registered in the database based on the question language description and the database / document relation constraint description provided in the document rule file.

According to the structured document processing method of the present invention, data retrieval is performed with respect to a database that stores data such as numerical values, texts, and binary data and the relationship between these data.
A database operation step for executing operations such as registration, update, deletion, etc., a database / structured document conversion step for converting data obtained from the database into an intermediate structured document, and one or more input structured documents and The intermediate structured document, or the input structured document or the intermediate structured document is input, and the input structured document or the intermediate structured document is defined in the document rule file. A constraint resolution step of verifying whether or not a relational constraint between element contents in the structured document is satisfied, or converting the input structured document or the intermediate structured document so as to satisfy the relational constraint. It is a thing.

A structured document processing program according to the present invention executes operations such as data search, registration, update, and deletion with respect to a database that stores data such as numerical values, texts, and binary data and the relationship between these data. Database operation procedure, database / structured document conversion procedure for converting data obtained from the database into an intermediate structured document, one or more input structured documents and the intermediate structured document, or the input structure The structured document or the intermediate structured document is input, and the input structured document or the intermediate structured document is specified in the document rule file. The input structured document or the relational constraint between the element contents in the intermediate structured document. Whether the input structured document or the above input structured document is satisfied so that the relational constraint is satisfied. A constraint releasing procedure to convert between structured document is intended to be executed by a computer.

[0021]

BEST MODE FOR CARRYING OUT THE INVENTION An embodiment of the present invention will be described below. The structured document processing device according to the present invention comprises a computer system that operates according to a structured document processing program. Embodiment 1. 1 is a block diagram showing the structure of a structured document processing device according to a first embodiment of the present invention. In the first embodiment, whether or not all the numbers of the parts applied in the order specification which is the input structured document are registered in the database, and the part numbers registered in the database are all the order specifications. It shows an implementation example of the function of verifying whether the document is included.

In FIG. 1, solid arrows show the flow of data, and dotted arrows show the flow of control. Reference numeral 1 is a document rule file that stores a document rule that defines relational constraints between element contents in one or a plurality of input structured documents or intermediate structured documents. The document rule in the document rule file 1 is the known technique disclosed in “Structured Document Processing Apparatus and Structured Document Processing Method” of Japanese Patent Laid-Open No. 2001-75958, The query language description 11, the database / document relation constraint description 12, the document context description 13, and the universal quantum description 14 are expanded and added.

Further, in FIG. 1, reference numeral 2 denotes an input structured document which is a structured document which is an input to the constraint resolution processing section 7, and there may be a plurality of input structured documents 2. 3 is a numerical value,
It is a database that stores data such as text and binary and the relationship between these data, and is realized by existing technologies such as a relational format database, an object-oriented database, and an XML document database. 4 is data search, registration,
It is a database operation processing unit that executes operations such as updating and deleting, and is realized by existing technology, like the database 3.

Further, in FIG. 1, reference numeral 5 requests the database operation processing section 4 to operate the database 3 by using a query language for the database 3 and converts the data obtained by the operation into an intermediate structured document. Then, 6 is a database / structured document conversion processing unit 5 for generating the converted intermediate structured document on the memory of the computer or outputting it as an external file. This is an intermediate structured document to be output.

The intermediate structured document 6 generated or output by the database / structured document conversion processing unit 5 is the W3C.
The W3C standard Xpath (XML Path Lan), which is a language for indicating not only a structured document that satisfies the standard XML 1.0 but also a part in the XML document
Guage: http: // www. w3. org / T
R / 1999 / REC-xpath-1999111
A node set, a Boolean value, a numerical value, and a character string, which are objects obtained as a result of evaluating 6), may be used.

Further, in FIG. 1, 7 is an API (Application Program) from an external program.
The input structured document 2 and the intermediate structured document 6, or the input structured document 2 or the intermediate structured document 6 is read, and the content or the intermediate structure of the input structured document 2 is read. Whether the contents of the structured document 6 satisfy the relational constraint defined in the document rule file 1 or convert the input structured document or the intermediate structured document 6 so as to satisfy the relational constraint. It is a constraint resolution processing unit that outputs as a result. Reference numeral 8 is an output structured document output by the constraint resolution processing unit 7, and reference numeral 9 is verification information indicating the verification result output by the constraint resolution processing unit 7.

Further, referring to FIG. 1, the question language description 11
Is a description that prescribes commands such as search, registration, deletion, and update to the database 3, and the database / document relation constraint description 12 is a table name and tuple name (1 in the table) in the query language description 11 to the database 3. (Line portion) and column names, and the element names and attribute names of the input structured document 2 or the intermediate structured document 6 are defined, and the document context description 13 is an element or attribute targeted by the relationship constraint. Is a description that specifies which input structured document 2 or intermediate structured document 6 is included. A plurality of universal quantized quantum descriptions 14 are repeated in the input structured document 2 or the intermediate structured document 6. It is a description of relational constraints for each of the appearing elements.

FIG. 2 is a diagram showing an example of commands for activating the constraint resolution processing unit 7. These commands are A
It is called from the PI or command interface. Figure 2
The command shown in (a) is a command used in the first embodiment, and the "document rule file" order specification rule rule a.d.
“Rdl”, execute constraint elimination processing with the check option so as to satisfy the relational constraint that constitutes the document convention ”. The commands shown in FIGS. 2B and 2C will be described in Embodiments 2 and 3 described later, respectively.

FIG. 3 is a diagram showing an example of the document rule described in the document rule file 1. The order specification document rule a. Referred to in the command of FIG. An example of drdl is shown. This document convention is composed of constraint expressions that express relational constraints between element contents in one or a plurality of structured documents 2.

The meaning of the document convention shown in FIG. 3 is that, when the constraint resolution processing unit 7 is activated with the check option,
"Contents of the element" part number "of the structured document" order specification.xml "and the database 3 on the 5th to 7th lines
Check whether the contents obtained as a search result by the question language description 11 are equal to each other. If they are not equal, output "the database and order specification.xml are inconsistent." As the verification result. "

Question language description 1 on lines 5 to 7 in FIG.
1 means SQL (Structured Query La), which is the standard of the query language of relational format databases.
nguage). However, “#PathContext (specification ID)” on the 7th line is an example of the document context description 13, and is used in the question language description 11 of the database 3 to refer to the element content in the XML document. "#PathContext (Specification I
“D)” indicates the content of the element “specification ID” in the structured document “order specification.xml”.

FIG. 4 is a diagram showing an example of the input structured document 2 referred to by the file name "order specification.xml". Therefore, in the case where the “order specification.xml” is the input structured document shown in FIG. 4, “#PathContext”
"(Specification ID)" indicates "S0001".

FIG. 5 is a diagram showing an example of a table stored in the database 3 having a structure corresponding to the input structured document 2 of FIG. Fig. 5 (a) is an order specification table,
5B is a diagram showing an order parts table, FIG. 5C is a parts management table, and FIG. 5D is a view showing an ordering company management table. By the normalization procedure which is a known technique of the relational format database, the part corresponding to the “specification ID” in the input structured document 2 in FIG. 4 corresponds to the “FIG. 5 (a) order specification table”. In addition, the input structured document 2 of FIG.
The part corresponding to the element "ordered parts" that appears repeatedly in the table corresponds to "FIG. 5 (b) ordered parts table". Furthermore, “FIG. 5 (c) parts management table” and “FIG. 5 (d)
The “ordered company management table” is configured as a separate table from the “FIG. 5 (b) ordered parts table” in order to simplify the data correction process when the management information is changed.

FIG. 6 is a diagram showing an example of a query language in which an operation command for the database operation processing unit 4 is described. This question language is created based on the question language description 11 stored in the document rule file 1. FIG. 6A shows the question language quoted in the explanation of the operation of the first embodiment.
Read the ordered parts table in (b), and extract the value of the part number from the tuple whose order specification ID is S0001. "
It means that.

6 (b), (c), and (d) show the question language quoted in the explanation of the operation of the second embodiment, and FIG. 6 (b) shows "the order of FIG. 5 (d). In order to read the value of the telephone number from the tuple whose company name is Company A by reading the destination company management table, FIG. 6C reads “the ordering company management table of FIG. 5D, The value of the telephone number is extracted from the tuple whose company name is Company D. "
Further, FIG. 6 (d) means "read the ordering company management table of FIG. 5 (d) and retrieve the company name / telephone number pair from the tuples of company A and company D". .

Further, FIGS. 6 (e), 6 (f) and 6 (g) are as follows.
The question language quoted in the explanation of the operation of the third embodiment is shown.
FIG. 6 (e) shows "S in the order specification table of FIG. 5 (a),
0001, product name 1, 2001-08-01 should be registered as a tuple. "
In the ordering parts table of (b), S0001, P1, 1
6 (g) in the ordering part table of FIG. 5 (b), S0001, P2, 20, D company, 200 in the sense of "register 0, A company, 2001-10-01 as a tuple".
"1-10-02 should be registered as a tuple".

FIG. 7 is a diagram showing an example of the intermediate structured document 6 generated or output by the database / structured document conversion processing unit 5. FIG. 7A is a search result in the query language of FIG. 6A, and is an intermediate structured document 6 in which the column “d_part number” of the ordered parts table of FIG. 5B is collected. X
The type of the object of the path evaluation result corresponds to a node set made of text.

FIG. 7B shows the search result in the question language of FIG. 6B, and FIG. 7C shows the search result in the question language of FIG. 6C. It is the intermediate structured document 6 in which the column “d_phone number” of the destination company management table is taken out. The object type of the Xpath evaluation result corresponds to text.

FIG. 7D is a search result in the query language of FIG. 6D, and the column “d_company name” and the column “d_phone number” in the orderee company management table of FIG. 5D are displayed. It is an intermediate structured document 6 in which a pair is taken out.

FIG. 8 is a diagram showing an example of the verification information 9 output by the constraint resolution processing section 7. The constraint elimination processing unit 7 verifies whether or not the relational constraint defined in the document regulation file 1 is satisfied, and outputs it as a verification result.

Next, the operation will be described. FIG. 9 is a flowchart showing the overall operation of the constraint resolution processing unit 7.
In step ST11, the call command of the constraint resolution processing unit 7 shown in FIG. 2A is read from the API or command interface. In step ST12, the document rule file “order specification document rule a.drdl” described in the command of FIG. here,
The "order specification document a. Drdl" is the document document file 1 shown in FIG.

In step ST13, the path-contex in the "order specification document a. Drdl" in FIG.
“Order specification.xml”, which is the value of the t-file attribute, is read as the input structured document 2. Here, "order specification.xml" is the input structured document 2 shown in FIG.
Further, the input structured document 2 to be read is the constraint resolution processing unit 7
It may be specified directly from the call command of. In this case, it is specified as an argument of the call command of the constraint resolution processing unit 7, that is, “a.drdl” shown in FIG.
Argument after ", and pa using the variable in the document convention
It may be passed as the value of the th-context-file attribute.

In step ST14, the read input structured document 2 is evaluated based on the document rule in the document rule file "order specification document rule a.drdl" in FIG. The evaluation operation based on the document rules shall follow the procedure defined for each relational constraint expression that constitutes the document rules.

P is a relational constraint expression forming the document convention of FIG.
It is called an ath constraint formula. FIG. 10 shows step ST14 of FIG.
5 is a flowchart showing a processing procedure for evaluating a Path constraint expression in FIG. In step ST21, the option of the call command of the constraint resolution processing unit 7 is "chec".
k ”is determined. Since the command option shown in FIG. 2 is "check", the process proceeds to step ST22.

In step ST22, it is verified whether or not the node set obtained as a result of evaluating the Xpath expression in the Path attribute and the node set obtained as a result of evaluating the expression (Value expression) in the Value element are not equal. Sometimes, the character string of the f-msg attribute is output as the verification information 9. Xpath that is the value of the Path attribute
The result of evaluating the expression “part number” is the set “{P1, P of the values of the element“ part number ”in the input structured document 2 in FIG.
2} ”, and is an expression (Value expression) in the Value element.
The node set obtained as a result of evaluating is the set {shown in the intermediate structured document 6 in FIG. 7A obtained from the part number whose ordering specification ID is "S0001" in the ordering part table in FIG. 5B. P1, P2, P3}. Since the two are not the same, the Pat of the "order specification document a. Drdl" in FIG.
Character string of f-msg attribute of h constraint expression "The contents of the database and order specifications.xml are not consistent."
Is output as the verification information 9 shown in FIG.

Here, the evaluation of the Value expression will be described. Fig. 11 shows "order specification document a. Drd" in Fig. 3.
11 is a flowchart showing a processing procedure for evaluating a Value expression shown from the 3rd line name to the 9th line of "l", which is an expression (Value in the Value element in step ST22 of FIG.
The processing procedure of evaluation of (expression) is shown. Since the fourth to the eighth lines in FIG. 3 are the question language description 11, the Value expression is an SQL statement, not an Xpath expression, and step ST31
To step ST33, and then step ST34
Proceed to. However, the question language description 11 from the fourth line name to the eighth line in FIG. 3 is described in SQL which is the standard question language of the relational database. Below, the operation command to the database 3 described in SQL is called an SQL sentence.

In step ST34, the SQL sentence obtained by replacing the document context description (the portion surrounded by #PathContext) 13 in the SQL sentence with the evaluation result is executed. Here, the document context description 13 “#PathContext (specification I
Since the evaluation result of “D)” is “S0001”, the SQL sentence obtained by replacing the evaluation result with the evaluation result becomes the question language shown in FIG. By searching the ordered parts table of FIG. 5B using the SQL statement of FIG. 6A, the set {P1, P2, shown in the intermediate structured document 6 of FIG.
P3} is obtained.

Although not processed in the first embodiment, the value expression is Xp in step ST31 of FIG.
If it is the ath type, in step ST32,
Evaluate the Xpath expression.

In the first embodiment, the input structured document 2
Although there was one, it is possible to describe the relation between elements of multiple documents by introducing logical operators such as logical sum, logical product, negation, and implication in the relational constraint expressions that compose the document conventions. Therefore, even when there are a plurality of input structured documents 2, similar processing can be realized.

Further, in the first embodiment, the constraint elimination processing section 7 reads the input structured document 2 and the intermediate structured document 6, and the contents of the input structured document 2 are the document rule file 1
It is verified whether or not the relational constraint defined in 1. is read, but the input structured document 2 or the intermediate structured document 6 is read, and the contents of the input structured document 2 or the intermediate structured document 6 are read.
It may be possible to verify whether or not the contents of (1) satisfy the relational constraint defined in the document regulation file 1.

As described above, according to the first embodiment, the document rule file 1 which defines the relational constraint between the element contents in the input structured document 2 or the intermediate structured document 6 is used as an external file, and the input structured The document 2 and the intermediate structured document 6, or the input structured document 2 or the intermediate structured document 6 are input, and the input structured document 2 or the intermediate structured document 6 satisfies the relation constraint defined in the document rule file 1. Since the constraint resolution processing unit 7 for verifying whether or not to perform is provided,
This has the effect of simplifying programming in the development of the consistency verification function between the input structured document 2 and the database 3.

Further, according to the first embodiment, the document rule file 1 is provided with the question language description 11 for the database 3, and the consistency is established on the basis of the relational constraint constituting the document rule realized as an external file. By verifying,
The effect that the process of comparing the contents of the input structured document 2 and the contents of the database 3 can be realized is obtained.

Furthermore, according to the first embodiment, since the document rule file 1 includes the document context description 13, the question language description 11 including the contents of the elements and attributes of the input structured document 2 can be generated. As a result, the effect of being able to improve the description of the relational constraint across the input structured document 2 and the database 3 can be obtained.

According to the first embodiment, as a result of the above, the effect that the development and maintenance of the document processing function across the plurality of input structured documents 2 and the database 3 in the EC and CALS fields can be made efficient can be obtained. To be

Embodiment 2. The block diagram showing the configuration of the structured document processing device according to the second embodiment of the present invention is equivalent to the configuration shown in FIG. 1 of the first embodiment. In the second embodiment, when the telephone number of the ordering company is changed, the contents of the database 3 are referred to by using the company name of the ordering party as a key, and the ordering specification document which is the input structured document 2 This is an example of realizing the function of automatically correcting the telephone number of the ordering company to the changed one.

FIG. 2B is a diagram showing an example of a command for activating the constraint resolution processing section 7. This command
In order to satisfy the relational constraints forming the document rules in the “document rule file“ order specification document rule b. Drdl ”,
Execute the constraint resolution process with the status option ”
It means that.

FIG. 12 is a diagram showing an example of the document rule described in the document rule file 1, and shows an example of the "order specification document rule b.drdl" referred to in the command of FIG. 2 (b). ing. The document convention is composed of constraint expressions expressing relational constraints between element contents in one or a plurality of input structured documents 2.

The document convention shown in FIG. 12A is an example of the All-Path constraint equation which is a relation constraint equation including the universal quantized quantum description 14. The meaning of this document convention is that when the constraint resolution processing unit 7 is started with the substate option, the order of the ordering telephone number in FIG. 5D is added to the "ordering party telephone number" of the "structured document" ordering specification. The value of the column "d_phone number" in which the value of the column "d_company name" of the destination company management table is equal to the content of the element "order destination company name" that is a sibling of the element "order destination phone number" Substitute ”
Is.

From the first line to the 11th line of the document convention shown in FIG. 12B, create-view-xmlfi
This is a le constraint expression. create-view-xmlf
In the ile constraint expression, the database / structured document conversion processing unit 5 refers to the database / document relation constraint description 12 to generate the search result converted into the intermediate structured document 6 in the memory of the computer, or It defines the process to output as an external file.

Further, the second to fifth lines of the document rule shown in FIG. 12B are examples of the database / document relation constraint description 12, and "the element" for the table of the result of the database search " Company name-phone number list "corresponds,
The element "company name-phone number" corresponds to the tuple of the table, the element "v_company name" corresponds to the data column "d_company name", and the data column "d_phone". The element "v_telephone number" corresponds to "number".

The meaning of the create-view-xmlfile constraint expression from the 1st line to the 11th line in FIG. 12B is "the database 3 is searched using the question language description 11 from the 7th line to the 9th line. From the resulting data, the second / fifth line database / document relation constraint description 1
The intermediate structured document 6 configured according to
1. xml ".""Orderspecification.xml"
Is the input structured document 2 shown in FIG. 4 and the ordering company management table is as shown in FIG. 5D, “view1.
xml ”becomes the intermediate structured document 6 shown in FIG.

FIG. 13 is a diagram showing an example of the output structured document 8. In the ordering specification which is the input structured document 2 in FIG. 4, the output structured document 8 is obtained as a result of automatically correcting the telephone number of the ordering company, and the difference from the input structured document 2 in FIG. The point is that the contents of the orderee telephone numbers on lines 19 and 19 have been corrected.

Next, the operation will be described. A flowchart showing the overall operation of the constraint resolution processing unit 7 is similar to that of FIG. 9 of the first embodiment. In step ST11 of FIG. 9, the call command of the constraint resolution processing section 7 shown in FIG. 2B is read. In step ST12, FIG.
The document rule file "order specification document rule b. Drdl" described in the command (b) is read. Below,
The operation will be described with reference to two examples of “order specification document rule b. Drdl” in FIG. 12A and FIG. 12B.

First, "order specification document rule b. Drdl"
However, the case of FIG. 12A will be described. Step S
At T13, “order specification.xml”, which is the value of the path-context-file attribute in “order specification document b. Drdl”, is read as the input structured document 2. Here, "order specification.xml" is the input structured document 2 shown in FIG. In step ST14,
The input structured document 2 is evaluated based on the document rule in the document rule file "order specification document rule b. Drdl". The evaluation based on the document rules shall follow the procedure defined for each relational constraint formula that constitutes the document rules.

The relational constraint equation forming the document convention of FIG. 12A is an All-Path constraint equation. FIG. 14 shows FIG.
5 is a flowchart showing a processing procedure for evaluation of an All-Path constraint expression in the evaluation based on the document regulation (control expression) in step ST14. In step ST41,
The All-Path expression in FIG. 12A is rdb-stor.
Since it has no e element, the process proceeds to step ST43, and FIG.
Since the All-Path expression of 2 (a) has a Value element, it proceeds to step ST44.

In step ST44, the result of evaluating the Value element is substituted for each element corresponding to the node in the node set obtained as a result of evaluating the Xpath expression in the Path attribute. Specifically, the result obtained by executing the SQL statement in the 4th to 6th lines in FIG. 12A is substituted into the element "ordered telephone number" of the input structured document 2 in FIG. Processing is done.

That is, for the element "ordered telephone number" on the 11th line in FIG. 4, the result obtained by executing the SQL statement in FIG. 6 (b) is "03-" in FIG. 7 (b). 1111-22
22 ”is substituted for the content of the element“ ordered party telephone number ”on the 11th line in FIG. Further, for the element "ordered telephone number" on the 19th line in FIG. 4, the result obtained by executing the SQL statement in FIG. 6C is "078-8888-00" in FIG. 7C.
"00" is substituted for the content of the element "ordered party telephone number" on the 19th line in FIG. Based on the above result, the output structured document 8 shown in FIG. 13 is output.

Next, the "order specification document b. Drdl"
The case of FIG. 12B will be described. In the document convention of FIG. 12B, the first to 11th lines are create-
This is a view-xmlfile constraint expression, and the 13th to 15th lines are All. It is a path constraint equation. To remove restrictions on document rules, create-view-xmlfi
le constraint and All. The path constraint expression is evaluated in this order.

FIG. 15 shows create-vi in the evaluation based on the document convention (control expression) in step ST14 of FIG.
It is a flow chart which shows the processing procedure of evaluation of an ew-xmlfile constraint expression. In step ST51, SQ
Document context description 13 (#PathContext in L sentence)
The SQL statement obtained by replacing (the part surrounded by) with the evaluation result is executed. Specifically, by the same operation as the evaluation of the document context description 13 described in the first embodiment, from the SQL statement on the 7th line to the 9th line of FIG. 12B to the SQL statement of FIG. Question language) and generate S
Execute a QL statement.

At step ST52, the element rdb-
xml-rel (database / document relation constraint description 1
The "correspondence relationship between the column name in the table of the database 3 and the element name in the XML document" described in 2) is read. Then, the tuple of the search result data obtained in step ST51 is given the element name of the tupleTagName attribute, and col is set for each column of the search result data.
The intermediate structured document 6 is generated by adding the element name of the umnTagName attribute. Specifically, FIG.
The intermediate structured document 6 shown in FIG. 7D is generated using the correspondence relationship described in (b).

Next, the operation of evaluating the All-Path constraint equation of FIG. 12B will be described with reference to FIG. First, the All-Path constraint equation of FIG. 12B is rdb-
Since it does not have a store element and has a Value attribute, steps ST41 to ST43 in FIG.
After that, the process proceeds to step ST44. In step ST44, Va is calculated for each element corresponding to the node in the node set obtained as a result of evaluating the Xpath expression in the Path attribute.
The result of evaluating the lue element is substituted.

Specifically, 1 of the input structured document 2 in FIG.
For the element "telephone number of the ordering party" in the first line, the Xpath expression "v_telephone number [... Data obtained as a result of evaluation "03-1111
Substitute "-2222". However, the document context description 13
"#PathContext (... / Ordering company name)"
The evaluation result of “Company A” is used. Also,
Similarly, for the element "ordered telephone number" on the 19th line of the input structured document 2 in FIG. 4, "078-8888-00"
00 "is substituted, and as a result," order specification document rules b.d. "
As in the case of FIG. 12A, the output structured document 8 shown in FIG. 13 is output.

In the second embodiment, the constraint elimination processing unit 7
Reads the input structured document 2 and the intermediate structured document 6 and converts the contents of the input structured document 2 so as to satisfy the relational constraint defined in the document contract file 1. 2 or the intermediate structured document 6 is read, and the contents of the input structured document 2 or the contents of the intermediate structured document 6 are converted so as to satisfy the relationship constraint defined in the document convention file 1. good.

As described above, according to the second embodiment, the document rule file 1 which defines the relational constraint between the element contents in the input structured document 2 or the intermediate structured document 6 is used as the external file, and the input structured The document 2 and the intermediate structured document 6, or the input structured document 2 or the intermediate structured document 6 are input, and the input structured document 2 or the intermediate structured document 6 satisfies the relation constraint defined in the document rule file 1. By providing the constraint resolution processing unit 7 for performing the conversion as described above, it is possible to simplify programming in the development of the structured document generation function that refers to the contents of the input structured document 2 and the database 3. .

Further, according to the second embodiment, by providing the universal quantized quantum description 14 in the document rule file 1, it is possible to realize the document processing for each of the elements that appear repeatedly in the input structured document 2. As a result, the effect of being able to improve the description capability of the relational constraint that spans the input structured document 2 and the database 3 is obtained.

Further, according to the second embodiment, the database / document relation constraint description 12 is added to the document rule file 1.
With the above, it becomes possible to express the relation constraint between the contents of the input structured document 2 and the contents of the database 3 by using the relation constraint expression between the element contents of the input structured document 2. With this, it is possible to obtain an effect that the description ability of the relational constraint across the database 3 can be improved.

According to the second embodiment, as a result of the above, the effect that the development and maintenance of the document processing function across the plurality of input structured documents 2 and the database 3 in the EC and CALS fields can be made efficient can be obtained. To be

Embodiment 3. The block diagram showing the configuration of the structured document processing device according to the second embodiment of the present invention is equivalent to the configuration shown in FIG. 1 of the first embodiment. In this embodiment, an implementation example of the function of registering the input structured document 2 of FIG. 4 in the database 3 having the table structure of FIG. 5 is shown.

FIG. 2C is a diagram showing an example of a command for activating the constraint resolution processing section 7. This command
In order to satisfy the relational constraints that compose the document rules in the “document rule file“ order specification document rule c. Drdl ”,
Execute the constraint resolution process with the status option ”
It means that.

16 is a diagram showing an example of the document rule described in the document rule file 1, showing an example of the "order specification document rule c.drdl" referred to in the command of FIG. 2 (c). ing. The document convention is composed of constraint expressions expressing relational constraints between element contents in one or a plurality of input structured documents 2. The document convention shown in FIG. 16 is 1
It is composed of an All-Path constraint equation on the 12th to 12th rows and an All-Path equation on the 14th to 27th rows, and these two All-Path constraint equations may be evaluated in this order.

Next, the operation will be described. A flowchart showing the overall operation of the constraint resolution processing unit 7 is similar to that of FIG. 9 of the first embodiment, and steps ST11 to ST of FIG.
The processes up to 14 are similarly performed.

Then, in the evaluation of the input structured document 2 based on the document convention (constraint expression) in step ST14,
The evaluation of the All-Path constraint expression on the first to twelfth lines in FIG. 16 is performed according to the flowchart shown in FIG. In step ST41 of FIG. 14, since the All-Path constraint expression has the rdb-store element, step S41 is performed.
Proceed to T42.

In step 42, xml-rdb-
The "correspondence between column name in table of database 3 and element name in XML document" described in the rel element (database / document relation constraint description 12) is read. Then, the column name in the SQL statement in the SQL element is
The SQL statement obtained by replacing the Xpath attribute with the evaluated value is executed. Specifically, based on the SQL sentence (question language description 11) on the ninth line in FIG. 16, the elements “specification ID” and “target” from the second line to the fourth line of the input structured document 2 in FIG. "Product name" and "Order date" are specified in "S"
"0001", "Product name 1", "2001-08-01"
The SQL sentence (question language) shown in FIG.

Similarly, the evaluation of the All-Path constraint expression on the 14th to 27th lines in FIG. 16 is performed according to the flowchart shown in FIG. All-P from 1st to 12th lines
Similar to the operation of evaluating the ath constraint expression, the process proceeds to step ST42 in FIG. In step ST42, for the element "ordered part" from the 6th line to the 13th line of the input structured document 2 of FIG. 4, based on the SQL sentence (question language description 11) of the 24th line of FIG. , "Order specification ID", "Part number", "Quantity", "Ordering company name", "Delivery date",
"S0001", "P1", "10", and "A" respectively
6 (f) replaced with "Company" and "2001-10-01"
The SQL sentence (question language) shown in is executed. Further, for the element "ordered part" from the 14th line to the 21st line of FIG. 4, the SQL sentence (question language) shown in FIG.

The point of this operation is All-Pat
h In the attribute "Xpath" of the element "rel" in the constraint expression, a relative element position in the XML document such as "./part number" can be specified for each element "ordered part".
The point is that the contents of elements that repeatedly appear in the ML document can be registered in the database 3. By this device, the contents of the input structured document 2 shown in FIG. 4 can be registered in the database 3 composed of a plurality of tables as shown in FIG.

In the document rule file 1, All-
Since the Path constraint expression can be nested, the process of registering the content of the input structured document 2 including the repeating element in the repeating element in the database 3 can be realized by the same operation.

In this way, the two All-
By evaluating the Path expression, the contents of the input structured document 2 of FIG. 4 are tuples in the second line of the order specification table of FIG. 5A and the second line of the order parts table of FIG. 5B. And the tuple on the third line can be registered.

In the third embodiment, the case has been described in which the input structured document 2 of FIG. 4 is registered in the database 3 having the table structure of FIG. 5, but the contents of the plurality of input structured documents 2 and the database 3 are described. In order to realize the integrated database registration function, the "generation function of the output structured document 8 referring to the contents of the plurality of input structured documents 2 and the database 3" is executed as in the second embodiment. , "Function of registering generated output structured document 8 in database 3" may be executed.

Further, in the third embodiment, the intermediate structured document 6 is read, the contents of the intermediate structured document 6 are converted so as to satisfy the relational constraint defined in the document rule file 1, It may be registered in the database 3.

As described above, according to the third embodiment, the document rule file 1 for defining the relational constraint between the element contents in the input structured document 2 or the intermediate structured document 6 is used as the external file, and the input structured The document 2 and the intermediate structured document 6, or the input structured document 2 or the intermediate structured document 6 are input, and the input structured document 2 or the intermediate structured document 6 satisfies the relation constraint defined in the document rule file 1. By including the constraint resolution processing unit 7 that converts the information to be registered in the database 3 as described above, programming in the development of the database registration function that integrates the contents of the input structured document 2 and the database 3 can be simplified. The effect is obtained.

Further, according to the third embodiment, since the document rule file 1 is provided with the universal quantized quantum description 14 and the database / document relation constraint description 12, the input structured document 2
The contents of each of a plurality of elements that appear repeatedly can be registered in the database 3, and the effect of being able to improve the description ability of the relational constraint that spans the input structured document 2 and the database 3 can be obtained.

As a result of the above, according to the third embodiment, the effect that the development and maintenance of the document processing function across the plurality of input structured documents 2 and the database 3 in the EC and CALS fields can be made efficient can be obtained. To be

[0093]

As described above, according to the present invention, the database, the database operation processing unit, the database / structured document conversion processing unit, the document rule file, and the constraint resolution processing unit are provided. , It is possible to simplify the programming in the development of the consistency verification function between the input structured document and the database, and the structured document generation function that refers to the contents of the input structured document and the database. There is an effect that the development and maintenance of the spanning document processing function can be made efficient.

According to the present invention, the document rule file is provided with the question language description, and the constraint resolution processing section uses the question language description to execute the operation by the database / structured document conversion processing section, thereby the input structure There is an effect that it is possible to realize a process of comparing the content of the computerized document with the content of the database.

According to the present invention, the document / convention file is provided with the database / document relation constraint description,
The structured document conversion processing unit refers to the database / document relation constraint description and converts the data obtained from the database into an intermediate structured document, thereby limiting the relation between the contents of the input structured document and the contents of the database. Can be expressed, and it is possible to improve the ability to describe relational constraints that span the input structured document and the database.

According to the present invention, the document rule file is provided with the document context description, and the constraint resolution processing section refers to the document context description to apply the relation constraint between the element contents in the input structured document or the intermediate structured document. Generate a question language description that includes the contents of the elements and attributes of the input structured document by verifying whether they are satisfied or by converting the input structured document or the intermediate structured document so as to satisfy the relationship constraint. Therefore, there is an effect that it is possible to improve the description ability of the relational constraint that spans the input structured document and the database.

According to the present invention, the document rule file is provided with the universal quantized quantum description, and the constraint resolution processing section refers to the universal quantized quantum description to refer to the relationship between the element contents in the input structured document or the intermediate structured document. By verifying whether or not the constraint is satisfied, or by converting the input structured document or the intermediate structured document so as to satisfy the relational constraint, each of the elements repeatedly appearing in the input structured document Document processing can be realized, and there is an effect that the ability to describe relational constraints that span an input structured document and a database can be improved.

According to the present invention, the document rule file is provided with the question language description and the database / document relation constraint description, and the constraint resolution processing section based on the question language description and the database / document relation constraint description, the input structured document. By registering the contents of the above in the database, it is possible to simplify the programming in the development of the database registration function that integrates the input structured document and the contents of the database.

According to the present invention, since the database operation step, the database / structured document conversion step, and the constraint resolution step are provided, the function of verifying the consistency between the input structured document and the database and the input structured Can simplify programming in the development of structured document generation function that refers to the contents of documents and databases,
This has the effect of streamlining the development and maintenance of the document processing function that spans the input structured document and the database.

According to the present invention, a structured document processing program that causes a computer to execute a database operation procedure, a database / structured document conversion procedure, and a constraint resolution procedure is used. It can simplify programming in the development of the integrity verification function and the structured document generation function that refers to the contents of the input structured document and the database, and the development and maintenance of the document processing function that spans the input structured document and the database. This has the effect of improving efficiency.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of a structured document processing device according to first to third embodiments of the present invention.

FIG. 2 is a diagram showing an example of a command for activating a constraint resolution processing unit of the structured document processing device according to the first to third embodiments of the present invention.

FIG. 3 is a diagram showing an example of document rules written in a document rule file according to the first embodiment of the present invention.

FIG. 4 is a diagram showing an example of an input structured document according to the first to third embodiments of the present invention.

FIG. 5 is a diagram showing an example of a table stored in a database having a structure corresponding to the input structured document of FIG. 4 in the first to third embodiments of the present invention.

FIG. 6 is a diagram showing an example of a question language description in which an operation command for a database operation processing unit of the structured document processing device according to the first to third embodiments of the present invention is described.

FIG. 7 is a diagram showing an example of an intermediate structured document generated or output by the database / structured document conversion processing unit of the structured document processing device according to the first and second embodiments of the present invention.

FIG. 8 is a diagram showing an example of verification information output by a constraint resolution processing unit of the structured document processing device according to the first embodiment of the present invention.

FIG. 9 is a flowchart showing the overall operation of the constraint resolution processing unit of the structured document processing device according to the first to third embodiments of the present invention.

FIG. 10 is a Path according to the first embodiment of the present invention.
It is a flowchart which shows the process sequence of evaluation of a constraint expression.

FIG. 11 is a Valu according to the first embodiment of the present invention.
It is a flow chart which shows the processing procedure of e type evaluation.

FIG. 12 is a diagram showing an example of document rules written in a document rule file according to the second embodiment of the present invention.

FIG. 13 is a diagram showing an example of an output structured document output by the constraint resolution processing unit 7 of the structured document processing device according to the second embodiment of the present invention.

FIG. 14 is a flowchart showing a processing procedure for evaluation of an All-Path constraint expression in the second and third embodiments of the present invention.

FIG. 15 is a screen diagram according to the second embodiment of the present invention.
It is a flow chart which shows a processing procedure of evaluation of a te-view-xmlfile constraint expression.

FIG. 16 is a diagram showing an example of a document rule described in a document rule file according to the third embodiment of the present invention.

FIG. 17 is a block diagram showing a configuration of a conventional structured document processing device.

[Explanation of symbols]

1 document rule file, 2 input structured document, 3 database, 4 database operation processing unit, 5 database / structured document conversion processing unit, 6 intermediate structured document, 7
Constraint resolution processing unit, 8 output structured document, 9 verification information, 11 question language description, 12 database / document relation constraint description, 13 document context description, 14 universal quantification description.

─────────────────────────────────────────────────── ─── Continuation of front page (51) Int.Cl. ⁷ Identification code FI theme code (reference) G06F 12/00 G06F 12/00 547Z 17/21 501 17/21 501T 570 570L (72) Inventor Osamu Moriguchi Tokyo 2-3, Marunouchi, Chiyoda-ku, Sanritsu Electric Co., Ltd. F-term (reference) 5B009 NA05 SA13 VA09 5B075 ND03 ND34 NR05 QP10 UU05 5B082 GA02 GA06

Claims (10)

[Claims] 1. A database for storing data such as numerical values, texts, binary data, etc. and a relationship between the data, and searching, registration, updating of data for the database.
A database operation processing unit that executes an operation such as deletion, and a database that requests the database operation processing unit to operate the database and converts the data obtained from the database by the database operation processing unit into an intermediate structured document. A structured document conversion processing unit, a document rule file defining one or a plurality of input structured documents or relational restrictions between element contents in the intermediate structured document, the input structured document and the intermediate structured document, Or input the above input structured document or the above intermediate structured document,
It is verified whether or not the input structured document or the intermediate structured document satisfies the relational constraint defined in the document rule file, or the input structured document or the above is satisfied so as to satisfy the relational constraint. A structured document processing device, comprising: a constraint resolution processing unit for converting an intermediate structured document. 2. The data search, registration, and data registration to the database during the relational constraints defined in the document rule file.
Equipped with a question language description that defines commands such as update and delete, the constraint resolution processing unit uses the question language description provided in the document rule file to execute the operation by the database / structured document conversion processing unit. The structured document processing device according to claim 1, wherein 3. A table name, a tuple name, a column name in a query language description for a database, and an element name or an attribute name of an input structured document or an intermediate structured document in a relational constraint defined in a document rule file. The database / structured document conversion processing unit refers to the database / document relation constraint description provided in the document rule file, and obtains from the database. The converted data is converted into an intermediate structured document.
The structured document processing device described. 4. A document that specifies in the input structured document or the intermediate structured document the element or attribute targeted by this relational constraint is included in the relational constraint specified in the document rule file. Whether the constraint resolution processing unit has a context description and refers to the document context description provided in the document rule file to satisfy the relation constraint between element contents in the input structured document or the intermediate structured document. 2. The structured document processing device according to claim 1, wherein the input structured document or the intermediate structured document is converted so as to verify whether or not the relational constraint is satisfied. 5. A universal quantification description for describing a relational constraint for each of a plurality of elements appearing repeatedly in an input structured document or an intermediate structured document in a relational constraint defined in a document rule file. Whether the constraint resolution processing unit satisfies the relational constraint between the element contents in the input structured document or the intermediate structured document by referring to the universal quantized quantum description provided in the document rule file. 2. The structured document processing device according to claim 1, wherein the input structured document or the intermediate structured document is converted so as to verify whether or not the relational constraint is satisfied. 6. The structured document processing according to claim 1, wherein the constraint resolution processing unit verifies whether the relational constraint defined in the document rule file is satisfied and outputs it as verification information. apparatus. 7. The structured document processing device according to claim 1, wherein the constraint resolution processing section outputs an output structured document obtained as a result of substituting the contents of the database into the input structured document. 8. The data retrieval, registration, and data registration to the database during the relational constraint defined in the document rule file.
A query language description that defines commands such as update and delete, and a database / document relationship that defines the correspondence between the table name, tuple name, and column name in this query language description and the element name and attribute name of the input structured document. The constraint resolution processing unit registers the content of the input structured document in the database based on the question language description and the database / document relation constraint description provided in the document rule file. The structured document processing device according to claim 1. 9. A database operation step for executing operations such as data search, registration, update, and deletion with respect to a database that stores data such as numerical values, texts, and binary data and the relationship between the data, and from the database. A database / structured document conversion step of converting the obtained data into an intermediate structured document, and one or more input structured documents and the intermediate structured document, or the input structured document or the intermediate structured document. Input and verify whether the input structured document or the intermediate structured document satisfies the relational constraint between the element contents in the input structured document or the intermediate structured document specified in the document rule file. Or, the constraint is solved by converting the input structured document or the intermediate structured document so as to satisfy the relational constraint. Structured document processing method characterized by comprising the steps. 10. A database operation procedure for executing operations such as data search, registration, update, and deletion with respect to a database that stores data such as numerical values, text, and binary, and the relationship between the data, and from the database A database / structured document conversion procedure for converting the obtained data into an intermediate structured document, and one or more input structured documents and the intermediate structured document, or the input structured document or the intermediate structured document. Input and verify whether the input structured document or the intermediate structured document satisfies the relation constraint between the element contents in the input structured document or the intermediate structured document specified in the document rule file. Or a constraint resolution procedure for converting the input structured document or the intermediate structured document so as to satisfy the relationship constraint. Structured document processing program executed by a computer.