CN116521671A

CN116521671A - DOA architecture handle technology level list-based identified data definition method and system

Info

Publication number: CN116521671A
Application number: CN202310264645.5A
Authority: CN
Inventors: 黄伟; 黄海; 杨瑀; 于红; 李万勇
Original assignee: Beijing Xinyuan Electronic Information Technology Co ltd
Current assignee: Beijing Xinyuan Electronic Information Technology Co ltd
Priority date: 2023-03-17
Filing date: 2023-03-17
Publication date: 2023-08-01
Anticipated expiration: 2043-03-17
Also published as: CN116521671B

Abstract

The invention discloses a DOA architecture handle technology level list-based identified data definition method and system. The DOA architecture handle technology level list-based identified data definition method comprises the following steps: adopting an ontology concept mode identification definition method to perform data definition on the data object of the handle system so as to form a data object containing the associated attribute; the data object includes the following fields: index, type, identification resource byte sequence, record value survival time, rights, timestamp, reference field; the association attribute reflects the association relation between the data object and other data objects; associating a handle code for a data object containing an association attribute; constructing a basic table, and associating a handle code for the basic table; the data object of the associated handle code is stored in a base table. By adopting the method and the device, the attribute of the data object is enhanced, the data object which can be used by the handle system can be rapidly increased in the DAO/handle system, and the practicability of the handle system is enhanced.

Description

DOA architecture handle technology level list-based identified data definition method and system

Technical Field

The invention relates to the technical field of big data, in particular to a DOA architecture handle technology level list-based identified data definition method and system.

Background

The Digital Object Architecture (DOA) abstracts all things, processes, services and various data on the Internet into Data Objects (DO), so that information management and sharing are independent of host equipment and independent of an information system, and the attribute, access right, information interface and other contents of the information can be obtained through a unified rule. The handle system is a key technology system for implementing DOA. The method defines a set of mature and compatible coding rules, and has a set of stable background analysis system and an autonomous controllable global distributed management architecture.

The DOA architecture mainly comprises two protocol supports, namely a handle protocol and a DOIP protocol, wherein the handle is a core protocol of the DOA architecture, and is used for realizing digital object identification, analysis, information management, security and the like and is also a foundation for realizing the DOIP protocol.

The handle system has great innovation space and is responsible for management and popularization work by the Swiss DONA foundation. The method is a set of technical system which originates from the Internet and aims at realizing the identification registration, analysis, management and security of the information system. Under the support of the handle system, the secure interoperation among heterogeneous, remote and remote main information systems can be realized.

The handle system has a set of independent global analytic system, and has the unique advantage of solving the problems of information exchange, opening and sharing among different places, different hosts and heterogeneous systems. And secondly, the handle system has a set of coding rules which are fully compatible with the prior coding technology, and can be used for quickly and low-cost butting of information systems of enterprises at the upstream and downstream of a supply chain on the basis of not changing the prior information system. The distributed storage architecture of the handle system can effectively avoid the problems of unclear data attribution right, excessively large information system and the like caused by an uploading mode in a data set.

The handle system defines a hierarchical set of service models, with the top-level service consisting of a global service called GHR. Below which is made up of other handle services, commonly referred to as LHS. The LHS is below the GHR and is responsible for all handle services under a certain or some handle prefix. GHR is responsible for management by the international organization DONA. DONA authorizes multiple MPAs to be in charge of the operation of GHR in the global scope, and each MPA is equal, negotiated and managed together, each MPA has a handle prefix which is independently managed, and all lower-level LHSs of the prefix are allocated and analyzed.

An important feature of the handle system is that it employs a distributed architecture. The handle system as a whole is made up of many handle services. Each handle service consists of one or more service sites (sites). Each service site under the same handle service has the same function. A service site may contain one or more handle servers. Handle requests to the service site should ultimately be distributed to these handle servers. The handle system should consist of any number of handle services; the number of service sites constituting the handle service is not limited; the number of servers constituting the service site is not limited as well.

The handle system gives a unique, legal, safe and permanent identification to various objects (documents, images, multimedia and the like) on the network in a certain mode, and the functions of reading, positioning, tracking, inquiring, applying and the like of the identified objects can be realized through the identification and analysis.

The method has the characteristics of maturity (possessing a global distributed system, application in nearly 70 countries), uniqueness (ensuring that the identifier is unique in the global scope), safety (ensuring that the identifier is registered, analyzed and managed to operate safely), compatibility (being compatible with various existing identifiers), expandability (possessing enough capacity), practicability (being simple in form, easy to store, read and process, good in economical efficiency) and the like, can be organically integrated with two-dimension codes, RFID, databases, information systems and the like, realizes seamless butt joint with the original system and low-cost interoperation among different application systems at low cost, effectively and reasonably solves the phenomenon of information island, provides international standard-compliant and global unified identification service and information management service for downstream enterprises on the industrial Internet, and is an important underlying commonality technology of the industrial Internet.

The handle has an independent resolution system, is compatible and complementary with the DNS, and is independently operated without being limited by the DNS. The domain name system as an identification layer provides effective support for internet applications. To meet the higher application demands, including industrial internet, the identification layer in the internet architecture needs to be extended from "server-oriented" to "server-oriented" and information-oriented ". The identification resolution system is an important means for supporting the 'servers and information as main bodies'. At present, a plurality of identification analysis schemes at home and abroad are totally divided into two development paths. To identify whether there are two paths (improvement and reformulation paths) for the resolution hierarchy to evolve based on DNS differentiation. The improved path is still based on the internet DNS system, and the identification resolution is implemented in the existing internet DNS resolution system with appropriate improvements. The innovation path adopts a brand new identification analysis system, and is mainly a handle scheme proposed by a digital object name management agency (DONA foundation).

The conventional handle system of the DOA lacks a generating method for generating the data object DO, and the development and application effects and capabilities of the handle system are restricted by the application of a data sharing mode.

Disclosure of Invention

The embodiment of the invention provides a DOA architecture handle technology level list-based identified data definition method and system, which are used for solving the problem of poor performance of a method for generating handle system data objects of DOA in the prior art.

According to the embodiment of the invention, the DOA architecture handle technology level list-based identified data definition method comprises the following steps:

adopting an ontology concept mode identification definition method to perform data definition on the data object of the handle system so as to form a data object containing the associated attribute; the data object includes the following fields: index, type, identification resource byte sequence, record value survival time, rights, timestamp, reference field; the association attribute reflects the association relation between the data object and other data objects;

associating a handle code for the data object containing the association attribute;

constructing a basic table, and associating a handle code for the basic table;

and storing the data object of the associated handle code into the basic table.

According to some embodiments of the present invention, the defining method for identifying definition of ontology concept patterns is used to perform data definition on data objects of a handle system to form data objects containing associated attributes, and the defining method includes:

analyzing an ontology handle code corresponding to the data object, and associating the ontology handle code with the data object as an association attribute of the data object;

the body handle codes are in one-to-one correspondence with the bodies;

the ontology comprises a concept ontology and a domain ontology; the concept ontology is constructed based on concept constituent elements in the concept field and association relations among the concept constituent elements; the domain ontology is constructed based on association relations between domain concepts.

According to some embodiments of the invention, the association relationship includes an association relationship between the concept constituent elements and an association relationship between the domain concepts, and the association relationship includes inclusion, aggregation, union, equality and correlation.

According to some embodiments of the invention, the method further comprises:

and constructing an index for the handle codes associated with the data objects and the handle codes associated with the basic table for user inquiry.

According to some embodiments of the invention, the constructing an index for the handle code associated with the data object and the handle code associated with the base table includes:

and constructing a plurality of barrels, and mapping the handle codes associated with the data objects and the handle codes associated with the basic table into corresponding barrels according to a preset hash function.

According to an embodiment of the invention, a DOA architecture handle technology level list-based identified data definition system comprises:

the data definition unit is used for carrying out data definition on the data object of the handle system by adopting an ontology concept mode identification definition method so as to form a data object containing the associated attribute; the data object includes the following fields: index, type, identification resource byte sequence, record value survival time, rights, timestamp, reference field; the association attribute reflects the association relation between the data object and other data objects; associating a handle code for the data object containing the association attribute;

a table definition unit, configured to construct a basic table, and associate a handle code for the basic table;

and the storage unit is used for storing the data object of the associated handle code into the basic table.

According to some embodiments of the invention, the data definition unit is configured to:

the body handle codes are in one-to-one correspondence with the bodies;

According to some embodiments of the invention, the system further comprises:

and the index unit is used for constructing an index for the handle codes associated with the data objects and the handle codes associated with the basic table so as to be inquired by a user.

According to some embodiments of the invention, the indexing unit is configured to:

According to the embodiment of the invention, the data object is defined based on the standard requirement of the handle system on the data object, so that the attribute of the data object is enhanced, and according to the data object defined by the invention, the data object which can be used by the handle system can be rapidly increased in the DAO/handle system, so that the practicability of the handle system is enhanced.

The foregoing description is only an overview of the present invention, and is intended to be implemented in accordance with the teachings of the present invention in order that the same may be more clearly understood and to make the same and other objects, features and advantages of the present invention more readily apparent.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. In the drawings:

FIG. 1 is a flowchart of a DOA architecture handle technology level list-based identified data definition method in an embodiment of the present invention;

FIG. 2 is a conceptual diagram of an embodiment of the present invention;

FIG. 3 is a domain ontology diagram of an embodiment of the present invention;

FIG. 4 is a conceptual overview of a vehicle in accordance with an embodiment of the invention;

FIG. 5 is a basic representation of an intent in an embodiment of the present invention;

FIG. 6 is a schematic diagram of a node hierarchy in an embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present invention are shown in the drawings, it should be understood that the present invention may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. In other instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Referring to fig. 1, a method for defining data based on a handle technology level list identification of a DOA framework according to an embodiment of the present invention includes:

s1, adopting an ontology concept mode identification definition method to perform data definition on a data object of a handle system so as to form a data object containing associated attributes; the data object includes the following fields: index, type, identification resource byte sequence, record value survival time, rights, timestamp, reference field; the association attribute reflects the association relation between the data object and other data objects;

s2, associating a handle code for the data object containing the association attribute;

s3, constructing a basic table, and associating a handle code for the basic table;

and S4, storing the data object of the associated handle code into the basic table.

The traditional definition method based on the concept is an entity relation method, cannot meet the requirement of intelligent data definition, adopts an ontology concept mode and a handle technology to carry out data concept mode identification definition, improves the intelligent capability of data object concept mode definition, and facilitates the usability and interactivity of data management of the whole system.

An ontology is a formal description of a shared conceptual model. The present ontology concept contains four layers of meaning: (1) sharing: refers to the fact that knowledge embodied in an ontology is commonly accepted, reflecting the collection of terms accepted in the art; (2) conceptualization: meaning that an ontology represents a description of things as a set of concepts; (3) clarity: all terms, attributes and axioms in the ontology are clearly defined; (4) formalization: refers to an ontology capable of being processed by a computer and is computer readable.

Classifying the ontology into four categories: top layer body, field body, task body and application body. Top layer body: research on general concepts and relationships among concepts, such as space, time, events, behaviors and the like, is independent of specific applications and is completely independent of limited fields, so that sharing can be performed in a large range; domain body: research is about the relationship between concepts in a specific field; task body: defining some general tasks or related reasoning activities to express concepts and relations between concepts in specific tasks; application body: to describe some specific applications, reference may be made to specific concepts within domain ontologies, as well as to concepts that appear within task ontologies.

On the basis of the above-described embodiments, various modified embodiments are further proposed, and it is to be noted here that only the differences from the above-described embodiments are described in the various modified embodiments for the sake of brevity of description.

the body handle codes are in one-to-one correspondence with the bodies;

The reference relation between the handle code and the handle value based on the handle technology, that is to say, the binding relation between the body handle code and the body handle value, or the mapping relation, can position the handle value through the body handle code in the handle system, and acquire the handle value of the body.

The data object defined by the method meets the standard requirement of the handle system on the data object, and provides data definition references for other data definition data objects.

According to some embodiments of the invention, the method further comprises:

The DOA architecture based handle technology level list-based data definition method according to an embodiment of the present invention is described in detail below with reference to the accompanying drawings. It is to be understood that the following description is exemplary only and is not to be taken as limiting the invention in any way.

According to the DOA architecture handle technology level list-based identified data definition method, data definition is carried out on data objects, the data after the data definition become data objects with associated attributes and virtual resource pools with specific structures, and necessary virtual resource pool components such as virtual resource pool modes, tables, views, indexes and the like are defined. The data object referred to herein is a data object of the handle system. The data object is compatible with the original attribute of the data object defined by the handle technology, the data object is subjected to handle coding, so that a data resource pool is identified, the enhancement practical function can be realized in a DAO/handle system, and conditions are created for the practical implementation of the handle.

The DOA architecture handle technology level list-based identified data definition method provided by the embodiment of the invention comprises the following steps:

1. an ontology concept mode identification definition method based on doa architecture handle technology.

Classifying the ontology into four categories: top layer body, field body, task body and application body. (1) a top layer body: research on general concepts and relationships among concepts, such as space, time, events, behaviors and the like, is independent of specific applications and is completely independent of limited fields, so that sharing can be performed in a large range; (2) domain ontology: research is about the relationship between concepts in a specific field; (3) task ontology: defining some general tasks or related reasoning activities to express concepts and relations between concepts in specific tasks; (4) application ontology: to describe some specific applications, reference may be made to specific concepts within domain ontologies, as well as to concepts that appear within task ontologies.

The ontology is formalized description of a conceptual mode, and a handle value data structure of the ontology realized by a handle technology is as follows. The reference relation between the handle code and the handle value based on the handle technology, that is to say, the binding relation between the body handle code and the body handle value, or the mapping relation, can position the handle value through the body handle code in the handle system, and acquire the handle value of the body.

The ontology identification construction method is composed of concept component identifications and interrelation identifications in the concept field, and the field identifications are composed of identification level lists.

For example, the business ontology is shown in fig. 2 through various concepts and interrelationship level list composition ontology concept identification definition method in the business field, the business ontology is shown in fig. 2 by various concepts in the business field, the relation identification combination mode among various concepts is shown in fig. 2, and the concepts themselves are composed of concept identifications and data structures for identifying bound values.

Referring to Table 1, the business ontology-identified construction method can be described as { C, W, D } composition, where:

C＝{C001、C002、C003、C004、C005、C006、C007、C008、C009、C010}

W＝{W001、W002、W003、W004、W005、W006、W007、W008、W009、W010}

D＝{D001、D002、D003、D004、D005、D006、D007、D008、D009、D010}

table 1 commercial ontology handle identification description

Concept handle identification	Associating handle identifications	Domain handle identification	Concept name
				C001	W001	D001	Commercial business
C002	W002	D002	Industrial process
				C003	W003	D003	Service industry
C004	W004	D004	Mining industry
				C005	W005	D005	Construction industry
C006	W006	D006	Manufacturing industry
				C007	W007	D007	Public utility
C008	W008	D008	Consumer industry
				C009	W009	D009	Transportation industry
C010	W010	D010	Communication system

Various domain ontology concepts are composed by context, for example: various concepts are defined in terms of the context of the domain in which they reside, such as: "staff", a concept known in the catering industry as "waiters" and in the manufacturing industry as "workers". In addition, in a certain domain, the enterprise model may be subdivided into different regions, which correspond to the general domains in the enterprise model.

The domain ontology is a combination of a concept ontology and a relationship ontology, hierarchical combination relationships are arranged among the domain ontologies, and the domain ontology is represented by a handle identifier.

For example: the description method of the domain ontology is shown in fig. 3. Referring to Table 2, the domain ontology is composed of triples { C, R, H } wherein the C concept set, R association set, abstraction level set H.

Table 2 domain ontology handle identification code description format

Concept handle code	Domain handle code	Hierarchical handle code	Concept name
				C001	R001	H01	Product engineer
C002	R002	H02	Quotation sheet
				C003	R002	H03	Invoice sheet

The association method of the conceptual relations between the ontologies comprises the following steps:

the relationship between concepts and between fields is that a certain relationship exists between concept bodies through association relationship combination, and the association method is represented by an association method, and can be represented as: and (3) association: { contain, aggregate, equal, related }, expressed as handle identifier: r: { I, P, A, E, R } where R is the association set, I is the containing relationship set, P is the aggregate relationship set, A is the association and relationship set, E is the equivalence set, and R is the correlation set.

Concept pattern abstraction method:

comprising: identifying a relationship representing subclasses and superclasses;

aggregation: representing a relationship in which two or more objects may be represented by a higher-level object;

and (3) combining: a group of members is represented by a high-level set;

weak entity convergence: a strong entity is used for collecting weak entities directly connected with the strong entity to form a composite entity;

dominance: for "1: the binary relation of M 'and the entity of the' 1 'side are dominant entities, which can converge the' M 'side and the relation between the' M 'side and the M' side to become a compound entity, and the compound entity name is dominant entity name. For example as shown in table 3.

Table 3 association example

Semantic association quantization representation:

semantic association quantization is represented by a value v [0,1], SYN: both terms are synonyms that refer to the same class of objects in the real world; BT/NT: there is an inclusive relationship between the two terms; ET: there is some link between the two terms; USE: the two terms are merely the difference in terms of the word head or the word tail.

Entity similarity calculation formula:

the coupling degree calculation formula:

the method for generating the concept body identification component comprises the following steps:

1) Determining the domain of the component.

2) In the concept model, the domain must concept is regarded as a component (corresponding to the basic concept model), then the region must elements in the remaining elements are each regarded as a component (corresponding to the region component) by region, and finally, all the remaining elements are each regarded as a component (general component).

3) The coupling values (Cx, cy) between any pair of the components Cx and Cy are obtained, and these values are organized in a matrix C (we refer to as a component-dividing matrix), and the following is set:

C _xy ＝Coupling(C _x ，C _y )

C _xx ＝0

4) Selecting a threshold value capable of combining two components, comparing elements in the clustered array with the threshold value, and combining according to the following criteria: general component → general component, general component → regional component → basic conceptual schema. Then, the corresponding elements in the component dividing array are removed, and the joint values generated by comparing the new component with other components are inserted.

In order to refer to concept ontology resources registered in the doa architecture handle system, the process aims to assist a user in performing efficient work by utilizing existing resources.

The first step is to determine the domain of data definition, extract the basic concept pattern identity from the component library, then the basic concept model, reference to the component generation process, which includes:

(1) The basic mode, the integration of components and parts, and the visualization by utilizing the abstract concept level in the domain;

(2) Referencing the integrated schema using concepts not contained in the basic schema, components, parts contained in the domain in the ontology;

(3) Embodying the current concept mode by using mapping in the ontology until the concept of the domain corresponds to a certain ending domain of the ontology;

(4) In the transition domain, the model may be defined using the domain concept identification.

For example: the conceptual ontology of the vehicle may be identified as a logical relationship diagram as shown in fig. 4.

2. The base table method is defined based on the handle identifier.

A base table is defined in the DOA based on the handle identification, the base table including a determination of a table name, a determination of a field type, a determination of a field attribute, a determination of a primary key field in the table that uniquely identifies the record, and the like.

The basic table data types include text, remarks, numbers, date and time type, money, automatic number, whether type, object type, hyperlink type, and reference guide type.

The table structure consists of rows and columns. The number and order of columns is fixed, with each column having a name. The number of rows is varied (which reflects the amount of data stored at a given time). There is no provision for the order of the rows in the table. When a table is read, the rows will appear in a random order unless ordering is explicitly required. In addition, rows are not given unique identifications, so we are likely to have several identical rows in a table.

Each column specifies a data type. The data type limits the set of all possible values for a column and limits the semantics of the data in the column so that it can be used for computation. For example, a column declared as a numeric type would not accept any text strings, and the data stored in such a column could be used for mathematical calculations. In contrast, a column declared as a string type accepts almost any type of data, but they cannot be mathematically calculated (although operations like string concatenation can be done).

A method for defining a table based on handle identification, comprising the steps of:

1. based on the handle identification definition basic table, the handle identification coding prefix/suffix form coding structure definition and reference basic table are adopted.

2. The names of the base tables are defined by the base table handle code suffix level, e.g., prefix/table names.

3. Identifying a structure of the definition table based on the table name:

{ Table name, table description, reference scene, superordinate List, extranet field, pattern Format, classification, state, icon size, icon color, version number, generation rule, remark … … }.

And organizing the index attribute values into a handle node tree form, wherein the handle node leaf nodes are formed by drinking corresponding tuple pointers for the attribute values.

The formalization of creating the base table is as follows:

the createtable < table name handle identifier > (< column name handle identifier > < data type > [ column level integrity constraint ], …, …, …, [ table level integrity constraint ]). The schematic diagram of the correspondence between the base table and the identifications is shown in fig. 5.

3. The handle system identifies the method of establishing the key value mapping index.

The identification code and the identification value of the handle system are in a binding relation of key values, and an infrastructure for inquiring the identification code and the identification value is provided for the user system by establishing a node identification index.

Based on the identifications stored by the handle nodes, the infrastructure does not need sequential indexing, but rather, by hashing the identifications to construct an index for querying fields within the handle system that have certain attributes.

And (3) searching the handle node, wherein a plurality of buckets are required to be established, the index attribute is mapped into the corresponding bucket according to the hash function value, and the index attribute value and the corresponding tuple pointer are stored in the bucket.

The hash function h is used:

h(K)→B

k represents the set of all search handle codes

B represents a set of all bucket addresses, and a bucket represents a unit of storage that stores one or more records

h is a function from K to B, i.e. a hash function

A schematic of the node hierarchy is shown in fig. 6.

If a search for a certain search code value K is performed, h (K) needs to be calculated and then the search is performed for the bucket with that address.

If two code values are searched, the two code values have the same hash value.

4. Identification formalization establishment method based on handle data management data dictionary

The data dictionary is a set of system tables inside the data management system, which records all definition information and the like in the data management.

The handle code suffix is represented by brackets, for example, the data dictionary is represented by a data dictionary, and the formalization establishment method of the data dictionary of the handle system is as follows:

< data dictionary >: : =date_dictionary

< data item > {, < data item > };

< data structure > {, < data structure > };

< data stream > {, < data stream > };

< data store > {, < data store > };

< process > {, < process > };

End_of_Date_Dictionary

< data item >: : =date_item

< data item name >;

< data item type >; < length >; < value range >;

End_of_Date_Item

< data structure >: : =date_structure

< data structure name >; < data structure composition >;

End_of_Date_Structure

< data stream >: : =date_flow

< data stream name >; < data Source >; < data to >;

< data stream composition >; < average flow >; < peak flow >;

End_of_Date_Flow

< data store >: : =date_storage

< data storage name >; < storage number >; < data in flow >;

< outgoing data stream >; < data storage composition >; < data volume >; < access method >

End_of_Date_Storage

< data processing >: : =date_procedure

< process name >; < input >; < output >; < processing function >

End_of_Date_Procedure

The table is built while integrity constraints associated with the table are defined, which are stored in a data dictionary of the system, and when a user manipulates data in the table, the relational database management system automatically checks whether the manipulation violates the integrity constraints. If the condition relates to multiple attribute columns of the table, it must be defined at the table level, or it may be defined at both the column level and the table level.

Implementing a data definition operation method by referring to other data object data definitions, comprising:

step one, requesting to access the handle system by a delegated authentication method, entering a handle authentication process, and obtaining the authority for accessing the handle root node system.

And step two, creating a data object according to the need, namely distributing corresponding names in the handle node according to the data object format, giving a handle code, and carrying out association in a system for query.

And thirdly, searching in the handle system, and judging whether the data object meeting the requirement exists or not.

And step four, if the data objects with the same data type are not available, directly defining the data objects. Corresponding data are generated, a handle code is created according to the requirement, the corresponding handle code is associated, and the data object is persisted.

Step five, establishing a version level relation table in a registration node according to field content defined by data objects each time, searching data object fields in a previous definition level table when the data objects are defined next time, adopting the same definition if the required fields exist, and adopting no step four if the required fields exist

It should be noted that the above description is only a preferred embodiment of the present invention, and is not intended to limit the present invention, but various modifications and changes will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

the body handle codes are in one-to-one correspondence with the bodies;

According to some embodiments of the invention, the system further comprises:

It should be noted that what is not described in detail in the present specification belongs to the known technology of those skilled in the art.

The use of suffixes such as "module", "component" or "unit" for representing elements is only for facilitating the description of the present invention, and is not of particular significance per se. Thus, "module," "component," or "unit" may be used in combination.

The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Any reference signs placed between parentheses shall not be construed as limiting the claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The use of the words first, second, third, etc. are used to distinguish between similar objects and not to indicate any order. These words may be interpreted as names.

"and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.

Claims

1. A method for defining hierarchical list-identified data based on a DOA architecture, comprising:

constructing a basic table, and associating a Handle code for the basic table;

and storing the data object associated with the Handle code into the basic table.

2. The method of claim 1, wherein the defining data objects of the handle system to form data objects containing associated attributes using an ontology concept schema identification definition method comprises:

the body handle codes are in one-to-one correspondence with the bodies;

3. The method of claim 2, wherein the association relationship includes an association relationship between the concept components and an association relationship between the domain concepts, and the association relationship includes include, aggregate, combine, equal, and correlate.

4. The method of claim 1, wherein the method further comprises:

5. The method of claim 4, wherein the constructing an index for the Handle code associated with the data object and the Handle code associated with the base table comprises:

6. A DOA architecture handle technology level list based identified data definition system comprising:

the table definition unit is used for constructing a basic table and associating a Handle code for the basic table;

7. The system of claim 6, wherein the data definition unit is to:

the body handle codes are in one-to-one correspondence with the bodies;

8. The system of claim 7, wherein the association relationship includes an association relationship between the concept components and an association relationship between the domain concepts, the association relationship including include, aggregate, combine, equal, and correlate.

9. The system of claim 6, wherein the system further comprises:

10. The system of claim 9, wherein the indexing unit is to: