JP2002063156A - Providing information conversion system and information recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a providing information conversion system, capable of providing even information prepared based on a role rule an opposite party as information, in a format which can be fully recognizable by the opposite party. SOLUTION: This providing information conversion system is provided with a memory 20 for storing a mapping file 110, for mapping standardized meaning information to a part or the whole of plural items constituting an intermediate file 210 of distribution information 200 prepared based on an applied local rule, and an XML generator 30 for mapping the meaning information to a part or the whole part of the plural items of the intermediate file 210, based on the mapping file 110 and generating standardized distribution information 300.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a provided information conversion system and an information storage medium, in particular, information created based on a local rule can be converted into information in a form recognizable by a destination. The information provided by
The present invention relates to a provided information conversion system and an information storage medium that can generate information in accordance with a predetermined local rule.

[0002]

[Background Art] Current EDI (Electronic Data Intercha)
nge) often converts data in a message format defined by an industry or corporate organization into V
In most cases, communication is performed using a dedicated line such as an AN. Transactions are digitized by EDI, reducing input work (eliminating double input), sharing information inside and outside the company, speeding up work, reducing labor costs and other costs, improving office work quality, and reducing paperwork. Such effects can be expected. EDI such as financial EDI, logistics EDI, etc.
Has been implemented in many companies.

[0003] However, introduction costs and delays in in-house computerization,
Many companies have not implemented EDI because of the necessity.

[0004] In recent years, the business itself has changed drastically due to the rapid flow of computerization (the spread of personal computers and the Internet), and worldwide transactions have been required. Following this change, that is, realizing the e-business, has attracted much attention. Therefore, there are many problems in the current EDI. For example, there is a problem that EDI messages can be exchanged only within a limited organization (industry, business organization).

[0005]

In the current EDI, a format is determined for each industry or company, and messages are exchanged only between companies complying with the format. Therefore, it is difficult to find new business partners of different industries and companies.

[0006] Various formats and protocols have already been established for each type of business and company, and this is not open, and a closed environment has been created which limits companies that perform EDI. However, if you try to change something already systematized according to these formats,
Very difficult both technically and costly.

Hitherto, the CSV format and the like have been used as the EDI format. In this format, the order of data and the like are determined in advance, and based on information such as "what number data from the front indicates what". The process is performed. Therefore, there is a problem that a change in the data structure always involves a change in the application.

The present invention has been made in view of such a problem, and an object of the present invention is to make it possible for a partner to sufficiently recognize even information that is not based on a common format created based on a role rule. It is an object of the present invention to provide a provided information conversion system and an information storage medium that can be provided to a partner as information in a format and that can accurately grasp the contents of information received from the partner.

[0009]

Means for Solving the Problems (1) In order to achieve the above object, the present invention provides a method for providing part or all of a plurality of items constituting provided information or an intermediate file created based on a given local rule. Means for providing mapping data for mapping the standardized semantic information, and mapping the semantic information to some or all items of the provided information or its intermediate file based on the mapping data, And conversion means for generating

According to the present invention, standardized semantic information is mapped to some or all of a plurality of items constituting information or even an intermediate file created based on local rules. It can be provided as provided information.

[0011] For this reason, information that can be conventionally used only in a closed range as information in accordance with local rules can be widely used in various fields other than the above.

[0012] In particular, in today's widespread use of the Internet, information and the like created based on local rules are
Since the standard information can be widely provided to the other party by using the method of the present invention, local information, which was conventionally only available in some fields, can be effectively used in a wide field.

According to the present invention, the information processing apparatus includes means for converting provided information created based on a given local rule into an intermediate file, wherein the mapping data includes part or all of a plurality of items constituting the intermediate file. The mapping means maps the standardized semantic information, and the conversion means maps the semantic information to a part or all of the items of the intermediate file based on the mapping data to obtain standardized provision information.

As described above, the information based on the local rules is once converted into an intermediate file, and then converted into the standardized provision information using the mapping data, so that the generation and restoration of the standardization provision information can be more easily performed. It can be.

[0015] Further, the standardization providing information includes an XML file and a document type definition file defining a structure of the XML file, and the mapping data is an XML file.
As a document type definition file that defines the file structure,
The conversion means maps the provided information or the intermediate file to the XML file and the document type based on the mapping data. It is characterized in that it is converted into standardized provision information including a definition file.

An XML file is a file described in a markup language that expresses text and data using "tags" similar to HTML, and is used as distribution information on the Web and information between various systems. It can be widely used as an intermediate data format for exchange. Therefore, the standardized information is generated from the information created based on the local rules, and is optimal as a file format when the information is provided to the other party.

Further, in the present invention, it is preferable to include a means for transmitting the standardized provision information to a transmission destination via a communication line.

(2) Further, the present invention provides a method for providing a given local information from standardized provided information based on standardized semantic information mapped to a part or all of a plurality of items constituting the provided standardized provided information. Means for providing information based on a rule or data for mapping for generating an intermediate file for generating the same; information based on a given local rule or information based on a given local rule from the standardized provided information based on the data for mapping; Conversion means for generating an intermediate file for obtaining

Further, the conversion means converts the standardized provision information into an intermediate file for information generation based on local rules.

The standardized provision information includes an XML file and a document type definition file that defines the structure of the XML file so as to give semantic information to some or all of the items of the XML file. The mapping data generates information based on a given local rule or an intermediate file for obtaining the information from the XML file with reference to the document type definition file included in the provided standardized provided information. And the converting means includes:
Based on the mapping data, information based on a given local rule or an intermediate file for obtaining the information is generated from the standardized provided information.

Further, the present invention is characterized in that it includes means for receiving the standardized provision information from a partner via a communication line.

In the present invention, the intermediate file is:
It is a CSV format file.

(3) The present invention may be configured by combining the configuration of the invention described in the above (1) and the configuration of the invention described in the above (2).

(4) An information storage medium according to the present invention is an information storage medium that can be used by a computer, and stores information for realizing each of the means described in (1) to (3) above. It is characterized by doing.

The information can be formed, for example, as a program or, if necessary, a program combined with data.

The information according to the present invention may be a program usable by a computer (including a program embodied in a carrier wave), and may be formed to include a processing routine for executing the above means. Good.

[0027]

Next, a preferred embodiment of the present invention will be described.

The explosion of the Internet in recent years has been known. By launching a WWW browser and entering a URL, you can view WWW pages around the world and anyone can access information around the world. It is also possible to send information to the world. In just a few years, the Internet has become the largest and least expensive means of communication.

Attempts to use this Internet infrastructure not only for WWW and e-mail but also for EDI have attracted attention, and at the same time, networking of all transactions has been required, and the conversion of EDI to the Web is inevitable. became. First, an EDI that simply replaces the dedicated line with the Internet can be considered. As a result, the communication cost is greatly reduced, but the advantage is limited to this, and other problems (EDI with unspecified majority) are not achieved. There are some advantages for companies that have already introduced EDI and are aiming for cost reduction, rather than companies that newly introduce EDI. Another example is EDI using a web browser. This means that one has a Web server and the other company accesses the EDI system from a Web browser. It is easy to install because it requires only the same equipment as when starting the Internet, but it is not possible to automate cooperation with in-house systems, and people who constantly check and input from a Web browser are required.

The inventor paid attention to "XML / EDI", which has the advantages of EDI and allows both companies to use the data on an in-house system.

(1) XML XML (extensible Markup Language) is, for example, as shown in FIG.
Is a markup language that expresses documents and data using "tags" similar to HTML. W3C (World Wide Web Consortium) promoting WWW diffusion and standardization is 1
In February 998, "XML1.0" was recommended and its basic specifications were established. SGML as well as HTML (Hyper Text Markup Language)
(Standardized Generalized Markup Language), but because of its simplicity, its application range is very wide, and it is expected not only as a delivery document on the Web but also as an intermediate data format for data exchange with various systems. I have.

Tags indicate the structure of a document or the meaning of data.
You can freely and flexibly define and describe tags of any structure.

In XML, apart from a file describing XML,
There is a file called DTD (document type definition), which defines what tags are used, in what hierarchy and in what order. This DTD was required in SGML, but X
ML only needs to be grammatical and DTD is not required.

Unlike a document file that depends on a certain application, an XML document is a simple text file, and thus has an advantage that it does not depend on software or hardware environments. Another advantage is that Internet technologies such as links and JAVA (registered trademark) can be used.

(2) Atomic Object An atomic object is prepared to ensure the sharability (reusability) of a business object. An atomic object is a minimum unit of a semantic element constituting a business object. The atom object is
Area-independent objects that do not belong to a specific area (industry, industry).

Since the atomic object is defined in detail in "Data Model Function JDMF / MODEL 1992" of the Japan Standards Association, its outline will be described here.

In general, a business object representing a business entity uses several attributes (data items) as a set to represent its characteristics. At this time, the attribute plays a specific role (Role) in the object, and a region-independent atomic object exists to realize the role.

For example, a representative attribute of an order is “order_
Date ". The attribute “order_date” has a role of “indicating the time of order”, and therefore uses the atomic object “calendar date” as its role realizing means. Constraints defined on an atomic object are inherited by higher-level objects that incorporate it. For example, the following is defined as the constraint on the atomic object “calendar date”. [Format constraint] [Value constraint] Year = 4 digits CCYY Month = 2 digits 1 to 12 Day = 2 digits 1 to 31 This constraint is inherited by all objects using “calendar date”. In addition, it is also possible to have “a business day” as its inherent constraint.

The atomic object is conceptually as follows.

A: Independence of objects It is possible to avoid overlapping constraints, and if the constraints are changed (for example, a date constraint in the year 2000 problem),
You only need to change one atomic object. No changes need to be made across multiple systems or objects.

B: Ensuring implementation independence An atomic object has a “mountable atomic object” for its implementation. For example, "calendar date" has a "date type (DateType)" as a data type on many computer systems. By separating it from the data type for implementation, independence from the implementation environment can be secured.

C: Ensuring Exchangeability In order to share the same meaning among different people, organizations, or companies, they must have a common information element. Furthermore, when using the information element, it must not be such a matter as to discuss its definition. It must be an element that everyone accepts unconditionally and need not be defined. Only by sharing undefined elements with each other, conversation and information exchange become possible. An atomic object is a defining element for sharing an object. However, in order to actually use an atomic object, a restriction on a computer system and a definition using a physical data type are required.

Therefore, the inventor has decided to implement the following operation on this conceptual “atomic object” to make the implementable atomic object more business-oriented, that is, a logical data type. I decided to set it.

There are the following classifications as mountable atomic objects.

A: Identification: An object used to uniquely identify a thing or a management target. The way of identification is a thing or identifier that uniquely limits the management target by the identification. A thing that clarifies the internal structure of the managed object by identification,
code. There are three types of objects that give identification by numbers (however, these numbers are composed of numbers but have no size).

B: System: An object whose existence is defined by an artificial system, law, standard or the like. The things decided by the system are geographical rules, such as country, prefecture, municipal, and local. It is not a system, but includes areas handled by companies. Includes codes determined by public institutions. Postal code,
phone number

C: Description: An object description that defines a description and a name of an object is an object that describes an object defined by identification. The description object includes a description object name object. In Japan, Kana names are recognized as subtypes.

D: Quantity: Quantity objects can be classified into the following patterns. Decimal point (Integer), Real (Actual Numb)
er)) Imaginary numbers are not considered in business handling. Amount and general quantity There are basically four patterns according to the above classification. Amount-with decimal point: cost, unit price, etc. Amount-without decimal point: sales amount, purchase amount, etc. Quantity-with decimal point: factor, percentage Quantity-without decimal point: number, count

E: Time: An object handling the concept of time A time object is roughly classified into a date object and a time object.

F: Flag: A flag is an object that has essentially no business meaning. In computer processing, a flag is used when two branches of processing are performed. Therefore, its value is basically 0 or 1
(YorN is also possible), and cannot take any more values.

G: Irregular: An irregular object such as an image or a document.

(2-1) Attachable Atomic Object Before semantic analysis of EDI data, it is necessary to clarify the basic constraints of the implementable atomic object. For this purpose, the basic constraints based on the implementable atomic objects defined by the inventor and those already used as national and international standards (basic constraints) are described here.

With respect to the mountable atomic object, it is necessary to define its properties and assign the properties to attributes and columns. The results need to be recorded in the dictionary, while at the same time providing logical and physical properties.

The mountable atomic object needs to display and modify the logical properties assigned to the domain in the dictionary. You also need to specify one set of properties for the domain itself, or another set of properties for domain-based attributes.

In the data modeling tool ERwin used in the embodiment, a domain can create both logical properties and physical properties. These properties are inherited and migrated to child domains and the attributes and columns to which the domains relate. Other properties are non-inheritable properties and apply only to that domain.

(2-2) Example of Mountable Atomic Object Regarding the mountable atomic object, it is necessary to define its properties and assign the properties to attributes and columns. The results need to be recorded in the domain dictionary, while at the same time providing logical and physical properties.

The mountable atomic object needs to display and modify the logical properties assigned to the domain in the dictionary. You also need to specify one set of properties for the domain itself, or another set of properties for domain-based attributes.

(2-3) List of Mountable Atomic Objects, Physical Subscripts, and Data Types For mountable atomic objects, first, the basic explanation of the restrictions was given, and the subscripts assigned to the attributes were specified.

The physical suffix is a name added to the end of the column name when the mountable atomic object is mounted on the database.

2-3-1. Identification Constraint: An identification implementable atomic object is a domain used to uniquely identify things and managed objects. Classified into identification code number.

2-3-1.1.1 Identification (_ID) Restriction: An identifier uniquely limits a management target by identification.
It is an identifier. Attribute subscript: ID Physical subscript: id Data type: INTEGER

2-3-3-1.2 Code Constraint: A code clarifies the internal structure of a management target by identification. The use of code has several advantages. The advantages are as follows. The codes are in principle numbers or short characters, so that computer memory and disk space can be used efficiently. By using the code, the number of key inputs can be reduced and the unique value (validation) of the data value can be specified.

1) General Code Constraint: A general code is a class of an attribute or a data element, and describes it as explanatory or functional information. Codes are specified as numbers or alphanumeric characters. Attribute subscript: code Physical subscript: cd Data type: CHAR

2) Product Code Constraint: A code assigned to general products and services. Attribute subscript: Product code Physical subscript: pd cd Data type: CHAR Restriction: However, international standards and national standards are defined for this code, and if these standards are followed, these standards must be used. Must comply. International and national standards include the following, and their contents are subject to the restrictions of the standards. JAN code (Japanese Article Number) EAN code (European Article Number) ISBN code (International Standard Book Numberin
g) International standard book number

2-3-1.3 Number 1) Number Constraint: This code has an arbitrary value, but has no internal structure or unique structure. In short, it is a number composed of meaningless code numbers. The order of the numbers has no significance. Therefore, the number may be used synonymously with the confirmation code, but the number is composed of only numbers, whereas the confirmation code may be alphanumeric. Attribute subscript: number Physical subscript: nb Data type: NUMBER

2) Serial Number Restriction: In the case of using a series of consecutive numbers for issuing numbers, serial numbers are used. The serial number starts from 1 and ends with an arbitrary n. Basically, the number of n cannot be set. Attribute subscript: serial number Physical subscript: ni Data type: ROWID

3) Row Restriction: Used to indicate a repeated part when a serial number is used. Therefore, any restrictions are imposed on the computer system. The line starts at 1 and ends with any n, but the number of n can be set. Attribute subscript: line Physical subscript: dl Data type: SMALLINT

2-3-2. Flags 1) Flags Constraint: This code can basically take only two values.
Yes / No, Yes / No.

The flag gives a logical switch whether the event has been activated or not. Flags must not be NULL. You must also take the right or wrong as the default. Attribute subscript: flag Physical subscript: fl Data type: CHAR

2-3-3. Description 1) Description Constraint: A description is used to describe an abstract attribute such as an ID or a number or a code. Attribute subscript: description Physical subscript: ds Data type: CHAR

2) E-mail Address Restriction: An E-mail address is a description object representing an e-mail address. E-mail addresses are classified into descriptions after recognizing that they are atomic objects that can be identified and mounted. Attribute subscript: E-mail address Physical subscript: em Data type: CHAR

3) Comments Constraints: Comments are implementable atomic object objects that provide a brief description for identification. Attribute subscript: comment Physical subscript: cm Data type: VARCHAR2

4) Unit of measurement Restriction: The unit of measurement is "notation method for exchanging information of unit symbol".
(JIS X 0124-1993). Attribute subscript: unit of measure Physical subscript: mu Data type: CHAR

5) Address Restriction: Address described in the resident card. Includes specific locations and addresses. Attribute subscript: address Physical subscript: ad Data type: VARCHAR2 (60)

6) Detailed Description Restriction: The comment is a relatively short description, whereas the detailed description is used for more detailed description. Attribute subscript: detailed Physical subscript: ex Data type: VARCHAR2

7) Name Object Constraints: Names are used to define the names of all events, events, and abstractions. Attribute subscript: Name object Physical subscript: no Data type: VARCHAR2

8) General Name Constraints: Used for names commonly referred to as names and names. Attribute subscript: General name Physical subscript: nm no Data type: VARCHAR2

9) Last name, first name 9-1) Last name Constraint: Used when defining the last name of the person in the personal name. Attribute subscript: surname Physical subscript: ln nm Data type: VARCHAR2 9-2) First name Restriction: Used to specify the first name of the last name of the person in the name. Attribute subscript: name Physical subscript: fn nm Data type: VARCHAR2

2-3-4. Numerical values 1) Numerical values Constraint: A mountable atomic object that represents the general form of numerical values. Therefore, the case including the decimal point and the case not including the decimal point are included. Attribute subscript: Numeric value Physical subscript: ad Data type: NUMBER 2) Number of transactions Restriction: Used when counting the number of transaction events. Basically, it starts from 1 and counts the number of transactions within a certain specified time. Attribute subscript: number of transactions Physical subscript: tc Data type: INTEGER 3) Percent Restriction: Express the number of percentages. Percent is relevant
It expresses the ratio of two numbers based on 100. Attribute subscript: percent Physical subscript: pe Data type: NUMBER 4) Factor Restriction: Expresses factors and coefficients. Attribute subscript: factor Physical subscript: fa Data type: NUMBER 5) Quantity Restriction: A quantity that can be represented by an integer. Attribute subscript: quantity Physical subscript: qt Data type: NUMBER 6) Amount Restriction: General system that represents an amount. Attribute subscript: Amount Physical subscript: mo Data type: NUMBER 7) Cost Restriction: General system of cost. Express the cost of goods and services. Attribute subscript: cost Physical subscript: como Data type: NUMBER 8) Total amount Restriction: Represents the total of the amount. Although the total amount is a derived attribute, it is added to the mountable atomic object because it is frequently used. Attribute subscript: Total price Physical subscript: ammo Data type: NUMBER 9) Unit price Restriction: Express unit price such as sales unit price and purchase unit price. Attribute subscript: unit price Physical subscript: pr mo Data type: NUMBER

2-3-5. Institutional constraints: Objects whose existence is defined by artificial systems, laws, standards, etc.

What is determined by the system is the geographical rules, such as country and country.
fecture, State), City (City), Region (Region)
There is. Although it is not a system, the area (Territor
y), including Region. Includes codes determined by public institutions. Postal code (Zip Code), Phone number (Phone Number) 1) Country code Restriction: The country code uses JIS X0304 country code as standard. Attribute subscript: country code Physical subscript: cn Data type: CHAR 2) Prefecture code Restriction: The prefecture code is based on JIS X0401 prefecture code. Attribute subscript: prefecture code Physical subscript: pf Data type: CHAR 3) City code Restriction: Use JIS X0402 for city code. However, municipal codes are not unique by themselves. It becomes unique by combination with the above prefecture code. Attribute subscript: municipal code Physical subscript: ci Data type: CHAR 4) Postal code Restriction: The postal code is based on the new postal code set by the Ministry of Posts and Telecommunications. Regarding postal codes, the "purpose of the new postal code system" prepared by the Ministry of Posts and Telecommunications is a constraint. Attribute subscript: zip code Physical subscript: pc Data type: CHAR 5) Telephone number Restriction: Defines telephone and mobile telephone numbers. Attribute subscript: telephone number Physical subscript: pn Data type: CHAR

2-3-6. Date constraints: The basic constraints for dates and times are date and time notation (JIS X 0301-1992) (ISO 8601: 1988) (Representati
on of dates and times).

In this project, the accounting period is set as a mountable atomic object in order to clearly show the accounting period. 1) Date / Time Constraint: A conceptually implementable atomic object of date and time. 2) Calendar Restriction: The date described in the calendar is defined based on the Gregorian calendar. Since the above two domains are not generally used, they do not have physical subscripts or data types. 3) Calendar month Restriction: Month described in the above calendar Sexual subscript: month Physical subscript: mn Data type: DATE 4) Calendar date Restrictions: Use the date and year described in the calendar above. Attribute subscript: date Physical subscript: date Data type: DATE 4-1) Japanese calendar date Restriction: Can be specified as a subtype of calendar date, but Japanese calendar date is specified as a derived attribute to the last. I do not have it as a basic. 5) Calendar year Restriction: The calendar year described on the calendar Attribute subscript: Year Physical subscript: cy Data type: DATE 6) Calendar day Restriction: Day of the week (Sunday to Saturday) described on the calendar Attribute subscript: Day of the week Physical subscript: wd Data type: VARCHAR2 7) Accounting period Restriction: This is a conceptual domain that defines the accounting period of a company. Therefore, it has no physical attribute. 8) Period of accounting period Restriction: Defines the accounting period classification of a company. In Japan, it is specified in the first half and second half, but may be specified in the quarter. Attribute subscript: accounting period Physical subscript: tf ft Data type: CHAR 9) Accounting period month Restriction: Defines the operating month of the company in the accounting period. Therefore, it may not be the same as the month on the calendar. Attribute subscript: accounting month Physical subscript: mf ft Data type: CHAR 10) Accounting period week Restriction: In the accounting period, the first week of the period is the first week, and the number of weeks in the elapsed period is indicated. Attribute subscript: fiscal week Physical subscript: wf ft Data type: CHAR 11) Fiscal period year Restriction: Represents the concept of the fiscal year in the fiscal period. Attribute subscript: fiscal year Physical subscript: yf ft Data type: CHAR 12) Time Restriction: This is a conceptual domain that specifies time. Therefore, it has no physical attribute. 13) Time Stamp constraint: expresses details of date and time. It is a unique expression of a computer system. Attribute subscript: Time Stamp Physical subscript: ts Data type: Time Stamp 14) Period Restriction: Indicates the elapsed time of date or time. This mountable atomic object object can be derived if the start and end are specified. Attribute subscript: period Physical subscript: tt Data type: INTEGER 15) Time constraint: Represents the time in time. Attribute subscript: time Physical subscript: tm Data type: DATE 16) Minute Restriction: Represents the minute of time. Attribute subscript: minute Physical subscript: mi Data type: DATE 17) Second Restriction: Indicates the second of time. Attribute subscript: second Physical subscript: se Data type: DATE

(3) XML and DTD XML (extensible Markup Language) is a markup language that expresses documents and data using “tags” similar to HTML. W3C (World) to promote and standardize WWW
The Wide Web Consortium recommended "XML1.0" in February 1998, and its basic specifications were defined.

As with HTML (Hyper Text Markup Language), SGML (Standardized Generalized Markup Language)
It is a language derived from e), but because of its simplicity, its application range is very wide, and it is expected not only as a distributed document on the Web but also as an intermediate data format for data exchange with various systems.

For example, as shown in FIG. 7, tags represent the structure of a document and the meaning of data, and tags having any structure can be freely and flexibly defined and described.

In XML, apart from a file describing XML,
There is a file called DTD (document type definition), which defines what tags are used, in what hierarchy and in what order.

Unlike a document file that depends on a certain application, an XML document has the advantage that it is a simple text file and does not depend on software or hardware environments. Another advantage is that Internet technologies such as links and JAVA can be used.

In XML, tags can be independently introduced. However, if anyone can introduce tags as they like, it is difficult to be confused. So XM
In L, what start tag and end tag can be used and what attributes can be used can be specified by a mechanism called document type definition. Document Type Definition in English
It is called on and abbreviated as DTD.

Normally, the DTD is created separately from the XML file,
In the XML document, specify the corresponding DTD file.

As described above, XML / EDI has various advantages by using XML. However, “exchange of EDI messages between different industries” required for XML / EDI is only the advantage of XML. Cannot be realized. In order to be able to understand the meaning of a field that can only be understood by different industries, it is necessary to standardize some semantic information. The solution to this is the concept of atomic objects, and what is needed to actually execute them is the mountable atomic object.

Data elements between companies and business types are standardized by using the mountable atomic object. Thereby,
The meaning of data is clarified, and contracts held by data are shared. In other words, the mountable atomic object has a role to bridge the difference between EDI messages for which standards are defined for each type of business.

The content of the mountable atomic object is EDI
Each of the companies that do this has an implementable atomic object attached using an XML tag. This makes it possible to read whether a field in the EDI message is "money" or "date" even between different industries. This feature of XML tags is an advantage when adding implementable atomic objects. For example, CSV
The format does not make sense of such data.

XML has a drawback that when defining a document type by DTD, only a character string type can be defined as the data type. ED
Since a data type is required for I, some countermeasures are required, but by using an implementable atomic object,
This disadvantage can be compensated for.

Although the format of the DTD is defined in XML, it is defined only as a syntax, and in order to use it in a concrete EDI message, it is necessary to first standardize its structure. At that time, the most important thing is the description of the basic element. This is INT or
Although it is effective as a program for conversion to lower the level of a program such as CHARCTER, it is too abstract from the original meaning of sending data, and the contents and meaning of data items cannot be transmitted.

For this reason, EDI is generally used to standardize a data item such as “sales amount” as an industry term and use it as a basic element. However, the standardization of the data item is a standardization of a limited range, that is, a local rule. Therefore, several local rules are arranged at the same time, and exchange of EDI messages over a wide area requires adjustment for each local rule.

The mountable atomic object is an optimal means for solving such a problem of the basic element. The existence of such means dramatically simplifies the establishment of basic elements.

Although not all of the basic elements can be said to be implemented by the mountable atomic objects alone, they can be used as description items of most data items.

The conventional EDI message could not be defined unless the definition of the data item was viewed by a paper specification program. This is because the EDI message has only the data value and the data definition information is missing. By using the mountable atomic object, it is clear which basic data item each data belongs to.

Moreover, since the data items are standardized beyond the industry, the definition of the data can be transmitted widely.

It is considered that the EDI message includes not only the definition information of the data but also the restriction. Strictly speaking, the information is not described in the EDI message. However, since the mountable atomic object is the standardization of data items and the restrictions are also subject to standardization, the EDI message is not Is guaranteed to be satisfied.

[0102]

EXAMPLES The present invention will be described below in detail with reference to examples, but the scope of the present invention is not limited by the examples.

FIG. 1 is a conceptual diagram of an XML / EDI system using a mountable atomic object, which is a system to which the present invention is applied.

The system 1000-1 or 1000 of the embodiment
-2 are connected to each other via the Internet.
Each of the systems 1000-1 and 1000-2 includes a memory 10 in which legacy data 200, which is provision information created based on a predetermined local rule, is stored.
The semantic information is mapped to some or all of the plurality of items constituting the legacy data 200 based on a mapping file as mapping data, and standardized provided information (hereinafter referred to as standardized provided information) is generated and generated. The provided information is exchanged with each other.

Since both systems have basically the same configuration, for simplicity of explanation, one system 1000-1 will be described as an example.

To perform the above series of processing, the system 1000 of the embodiment uses the data conversion tool 12 to
The conversion target data included in the legacy data 200 is converted into an intermediate file of a predetermined format and stored in the memory 14.
Here, the CSV format is very simple and easy to use,
Using the conversion tool 12, the conversion target data included in the legacy data 200, which is local data, is converted into a CSV-format intermediate file 210 and stored in the memory 14.

FIG. 3 shows an example of the intermediate file 210 formed as described above.

Further, in the system of the embodiment, the mapping file 110 created based on the information of the mountable atomic object 100 is stored in the memory 20.

FIG. 4 shows this mapping file 110.
An example is shown.

This mapping file 110 is information for mapping standardized semantic information to some or all of a plurality of items constituting the legacy data 200 or its intermediate file 210 created based on local rules. Is configured as

The system of the embodiment has an XML generator 30 functioning as a conversion means. The XML generator 30 maps semantic information to some or all items of the intermediate file 210 based on the mapping file 110. Then, the standardization providing information is generated and stored in the memory 40.

The standardized provision information of the present embodiment is XML
The file 300 includes a file 300 and a document type definition file (hereinafter, referred to as a DTD file). The DTD file 310 is configured to include information that defines the structure of the XML file. Specifically, the DTD file has X, which describes what tags are used in what hierarchy and order, and so on.
Define the structure of the ML file.

As the standardized provision information, an XML file 3
00 and a DTD file, the mapping file 110 of the embodiment defines information for mapping semantic information to some or all items of the intermediate file 210 as a DTD file that defines the structure of the XML file. Including. Then, the XML generator 3 of the embodiment
0 sets the intermediate file 210 to the XML file 300 and the DTD based on the mapping file 110.
The file is configured to be converted into standardized provision information including the file.

As described above, the XML generator 30
In addition to converting the data format from the intermediate file 210 to an XML file for data exchange, information on the mountable atomic objects is added to the XML file in the form of a DTD file, and semantic information is added to each item of the XML file. Can be added.

The system 1000-1 of the embodiment
The standardized provision information stored in the memory 40, specifically, the XML file 30
0 and the DTD file to the desired system 1
000-2 via a communication line such as the Internet.

The transmission destination system 1000-2 is
It has substantially the same structure as the above-described system 1000-1 shown in FIG. 1, and transmits received information, specifically, the XML file 300 and the DTD file 310 to the system 1.
In a procedure reverse to the procedure described in 000-1, the data can be converted back to data conforming to its own local rule and used.

As described above, according to the present embodiment, in each of the systems 1000-1 and 1000-2, the data created according to the respective local rules is converted into a format that can be used universally by the other party. Each of the systems 10000-1 and 1000-2
.. Can be utilized as data that can be used in other systems because of the unique local rules created in each of the..., So that the versatility of existing data can be improved and the data use efficiency can be significantly improved. it can.

In particular, when information is transmitted and received via the Internet or the like, the system of the present embodiment is extremely effective.

Further, in the present embodiment, the standardized providing information transmitted and received via the Internet is provided as an XML file 300 and a DTD file. XM
Since the L file 300 has few restrictions on the description, the XML file
Conversion between the file 110 and the file 210 is facilitated.

In particular, the standardized provision information formed as the XML file 300 and the DTD file 310 has a data format that can be objectively read by any user, for example, as data in a format as shown in FIG.

Therefore, when this standardized provision information is transmitted, for example, from the system 1000-1 to the system 1000-2, the other system 1000-2 receives the data using a receiving means (not shown), and
Are the mapping file 110 and the DTD file 31
XML file 300 included in the received data based on 0
To an intermediate file 210 in CSV format.

As described above, the data restored as the intermediate file 220 is stored in its own database as data 200 according to its own local rules as necessary, and can be used for various processes as necessary. it can.

Hereinafter, each component of the system shown in FIG. 1 will be described in detail.

(1) Intermediate File 210 The intermediate file 210 is a file of data extracted from the database 220 using the conversion tool 12. FIG. 3A shows an example of the intermediate file 210. FIG. 3B shows the contents of the file in FIG. 3A for easy understanding.

The top line is the item name, and the line below it is the value of the item.

In the first data, the value of the item “AA20A” is “1111”, the value of the item “chmn_ni” is “1”, and the item “chm_ni”
The value of “n_jchsh_kgy_id” is “2222” or more. ・ In the second data, the value of item “AA20A” is “1111”,
The value of the item “chmn_ni” is “2” and the item “chmn_jchsh_kgy_
The value of “id” has a content such as “2222” or more.

The contents of the intermediate file are only the item name and the item value, and do not describe information about the meaning of the item.

(2) Mapping File 110 The mapping file 110 is an XML document type definition (DTD).
Is a mapping of atomic objects and items. FIG. 4 shows an example.

In the mapping file 110, the atomic object corresponding to the item is stored in the attribute “type” at the same time as the definition of the structure, and is associated with the item.

The contents described in the example of FIG. 4 are summarized as follows: a tag of the item “chmn_ni” and its attributes “name” and “typ”
e "and" value "are defined.

“Name” is “Note_Serial number” of the item Japanese name
Is stored, and a mountable atom object "Number Auto Increment" is stored in "type", and this item is mapped to the stored mountable atom object.

The tag of the item “AA20A” and the attribute “nam”
e, "type" and "value" are defined.

In the “name” field, the item Japanese name “note_departure_company_I”
"D" is stored, and "type" stores a mountable atom object "Identifier", and this item is mapped to the stored mountable atom object.

XML has a flexible structure, and therefore, it should be noted that the structure defined here is merely an example, and the structure does not have to be the same.

(3) XML file 300 Based on the mapping file 110, the XML generator 3
0 is an XML file 30 generated from the intermediate file 210
0 is, for example, as shown in FIG. 5 in this embodiment. XM
The explanation of the grammar of L is omitted, but the XML structure is DTD
It has the structure defined in the file (mapping file).

The example shown in FIG. 5 is as follows.

Item "chmn_ni" (Japanese name: Note_serial number)
Inherits the contents of the atomic object "Number AutoIncrement" and has a value of "1".

Item "AA20A" (Japanese name: note_departure_company_I
D) inherits the contents of the atomic object "Identifier" and its value is "1111".

The item “chmn_nnysk_kgy_id” (Japanese name: note_pay_company_ID) is an atomic object “Identifier”
And the value is “2222”.

The item “chmn_jchsh_kgy_id” (Japanese name: Note_Tori_Article_Reception_Company_ID) is an atomic object “Identif
ier ", and the value is" 2222 ".

The item “chmn_trhk_jkn_kyk_ni” (Japanese name: note_take_article_contract_serial_number) is the atomic object “Number
It has "Auto Increment" and the value is "1".

This file is a file to be transferred. The purpose of this file is to give meaning to items by atomic objects, and the above XML structure is merely an example.

(4) XML generator 30 XML file 3 generated by the XML generator 30
FIG. 6 shows the relationship between the 00 and DTD files 310, the intermediate file 210, and the mapping file 110, using the values described in the embodiment.

The contents of the processing performed by the XML generator 30 are mainly conversion of the format from CSV (in this example) to XML and addition of the atom object mapped to each item.

According to the present invention, it has become possible to exchange data between different industries, which has been very difficult until now. Since the format of the legacy data 200 is not limited, the former Industrial Information Technology Promotion Center (hereinafter referred to as C), which is an EDI promotion organization of the Japan Information Processing Development Association (hereinafter abbreviated as JIPDEC),
II) and the UN / EDIFACT format promoted by the United Nations. In other words, it can be said that this is a means to realize the exchange of data between endless companies that EDI should originally have.

In the present invention, each means 1
2, 20, and 30 may be configured as hardware, or may be configured as software using a program or the like.

[Brief description of the drawings]

FIG. 1 is a schematic explanatory diagram of a system to which the present invention is applied.

FIG. 2 is an explanatory diagram of processing performed mainly on an XML generator in the present embodiment.

FIG. 3 is an explanatory diagram illustrating an example of an intermediate file used in the embodiment.

FIG. 4 is an explanatory diagram illustrating an example of a mapping file used in the embodiment.

FIG. 5 is an explanatory diagram illustrating an example of an XML file generated in the embodiment.

FIG. 6 is a conceptual diagram of processing of an XML generator performed in the present embodiment.

FIG. 7 is an explanatory diagram of a data structure of an XML file defined by a DTD file.

[Description of References] 10, 14, 20, 40 Memory 12 Data Conversion Tool 30 XML Generator 100 as Conversion Means 100 Atomic Object 110 Mapping File 200 Legacy Data 210 Provided Information 210 Intermediate File 300 XML File 310 DTD File 1000-1, 1000-2 system

 ──────────────────────────────────────────────────の Continued on the front page (72) Inventor Kazuhiko Iwasaki 2--11-24 Tsukiji, Chuo-ku, Tokyo Inside JNT System Corporation (72) Inventor Shozo Yokokawa Shiba-Koen, Minato-ku, Tokyo No. 1-38 F-term (reference) in Japan Management Association Consulting Co., Ltd. 5B009 SA13 TA11 VC01

Claims (20)

[Claims] 1. Means for providing mapping data for mapping standardized semantic information to a part or all of a plurality of items constituting provided information or an intermediate file thereof provided based on a given local rule. And a converting means for mapping semantic information to some or all of the items of the provided information or its intermediate file based on the mapping data, and generating standardized provided information. . 2. The method according to claim 1, further comprising: means for converting provided information created based on a given local rule into an intermediate file, wherein the mapping data is a part of a plurality of items constituting the intermediate file. Or mapping the standardized semantic information to all of them, wherein the converting means maps the semantic information to some or all of the items of the intermediate file based on the mapping data, and obtains standardized provision information. And provided information conversion system. 3. The standardization providing information according to claim 1, wherein the standardization providing information includes: an XML file; and a document type definition file that defines a structure of the XML file. As a document type definition file for defining a structure, semantic information is mapped to some or all of the items of the provided information or the intermediate file, and the conversion unit converts the provided information or the intermediate file into the mapping data. A conversion system for converting provided information including standardized provided information including the XML file and the document type definition file based on the XML file. 4. The provided information conversion system according to claim 1, further comprising means for transmitting the standardized provided information to a destination via a communication line. 5. Based on standardized semantic information mapped to some or all of a plurality of items constituting the provided standardized provision information, information based on a given local rule from the standardization provision information or Means for providing mapping data for generating an intermediate file for generating; information based on a given local rule or an intermediate file for obtaining the information from the standardized provided information based on the mapping data; A provided information conversion system, comprising: conversion means for generating; 6. The provided information conversion system according to claim 5, wherein the conversion unit converts the standardized provided information into an intermediate file for generating information based on a local rule. 7. The XML file according to claim 5, wherein the standardization providing information defines an XML file and a structure of the XML file so as to provide semantic information to some or all of the items of the XML file. A document type definition file, and wherein the mapping data refers to a document type definition file included in the provided standardized provided information, and obtains information based on a given local rule from the XML file, or Generating an intermediate file for obtaining information based on a given local rule or an intermediate file for obtaining the information from the standardized provision information based on the mapping data. Characteristic provided information conversion system. 8. The provided information conversion system according to claim 5, further comprising means for receiving the standardized provided information from a partner via a communication line. 9. An information providing system comprising the system according to claim 4 and the system according to claim 8. 10. A means for providing mapping data for mapping standardized semantic information to a part or all of a plurality of items making up provided information or an intermediate file thereof based on a given local rule. And a conversion unit that maps semantic information to some or all of the items of the provided information or the intermediate file based on the mapping data and generates standardized provided information. Characteristic computer-readable information storage medium. 11. The mapping data according to claim 10, including information for implementing means for converting provided information created based on a given local rule into an intermediate file, wherein the mapping data comprises a plurality of files constituting the intermediate file. The conversion means maps the semantic information to some or all of the items of the intermediate file based on the mapping data, and provides the standardized provision information. An information storage medium, characterized by obtaining: 12. The standardization providing information according to claim 10, wherein the standardization providing information includes: an XML file; and a document type definition file that defines a structure of the XML file. As a document type definition file for defining a structure, semantic information is mapped to some or all of the items of the provided information or the intermediate file, and the conversion unit converts the provided information or the intermediate file into the mapping data. An information storage medium, which is converted into standardized provision information including the XML file and a document type definition file based on the XML file. 13. An information storage medium according to claim 10, wherein information for implementing means for transmitting the standardized provision information to a transmission destination via a communication line is stored. 14. Based on standardized semantic information mapped to some or all of a plurality of items constituting standardized provided information provided, information based on a given local rule from a standardized provided information storage medium or Means for providing mapping data for generating an intermediate file for generating the same; information based on a given local rule or intermediate for obtaining the information from the standardized providing information based on the mapping data; A computer-readable information storage medium storing a conversion unit for generating a file, and information for realizing: 15. The information storage medium according to claim 14, wherein the conversion unit converts the standardized providing information into an intermediate file for generating information based on a local rule. 16. The standardization providing information according to claim 14, wherein the standardization providing information defines an XML file and a structure of the XML file so as to provide semantic information to some or all of the items of the XML file. A document type definition file, and wherein the mapping data refers to a document type definition file included in the provided standardized provided information, and obtains information based on a given local rule from the XML file, or Generating an intermediate file for obtaining information based on a given local rule or an intermediate file for obtaining the information from the standardized provision information based on the mapping data. Characteristic information storage medium. 17. The information storage medium according to claim 14, wherein information for realizing means for receiving the standardized provision information from a partner via a communication line is stored. 18. Information storing the information for realizing each means according to any one of claims 10 to 13 and each means according to any one of claims 14 to 17. Storage medium. 19. The provided information conversion system according to claim 1, wherein the intermediate file is a CSV format file. 20. The information storage medium according to claim 10, wherein the intermediate file is a CSV format file.