Database arranged as a semantic network

• US 5,870,751 A
• Filed: 06/14/1996
• Issued: 02/09/1999
• Est. Priority Date: 06/19/1995
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Trotter, Martin John
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): Coby, Frantz
• Application Number:
  US08/665,140
• Time in Patent Office: 970 Days
• Field of Search: 707/102, 707/103, 707/5, 707/104
• US Class Current: 1/1
• CPC Class Codes: G06F 16/288 Entity relationship models
• CPC Class Codes: Y10S 707/99935 Query augmenting and refining, e.g. inexact access
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A semantic network is described in which data is stored in data storage areas at nodes of the network, there being a root node from which all other nodes depend, in a branched structure, and in which data stored at each node includes relationship information about related nodes other than nodes linked by a branch from said node. The relationship information includes a token identifying the type of relationship. The other node in a relationship may be a virtual node, which does not actually exist, but whose data content is stored within the relationship information.

Claims

1. A database arranged as a semantic network in which:

data is stored in data storage areas at nodes of the network, there being a root node from which all other nodes depend in a branched structure;

data stored in data storage areas at a first node includes;

a value of a subject of the first node; and

relationship information about one or more relationships from the first node to one or more second related nodes, said relationship information including a token identify a relationship type and second nodes, not being linked in the branched structure to said first node wherein the token is a shortened representation of a corresponding relationship name; and

the database comprising information relating the tokens to the corresponding relationship names.

2. A database as claimed in claim 1 in which said relationship information includes a flag indicating a type of a related subject corresponding to said related node.

3. A database as claimed in claim 2 in which said relationship information includes a flag indicating that the relationship points in a direction towards this node from a related node.

4. A database as claimed in claim 1 in which said relationship information relates to a virtual node and said relationship information itself includes the data which would have been in the virtual node.

5. A database as claimed in claim 4 in which said relationship information includes a flag indicating a type of a related subject corresponding to said related node.

6. A database as claimed in claim 5 in which the data for said virtual node is stored at a location pointed to by the relationship information, the location not being part of the branched structure.

7. A database as claimed in claim 5 in which said relationship information includes a flag indicating that the relationship points in a direction towards this node from a related node.

8. A database as claimed in claim 7 in which branches in said branched structure comprise a relationship, whose flag indicates that the relationship is part of the branched structure.

9. A database as claimed in claim 8 in which said relationship information includes a flag indicating that the relationship points in a direction towards this node from a related node.

10. A computer system comprising a memory, a display device, an input device and a database arranged as a semantic networks, in which:

data is stored in data storage areas at nodes of the network, there being a root node from which all other nodes depend in a branched structure;

data stored in data storage areas at a first node includes;

a value of a subiect of the first node; and

relationship information about one or more relationships from the first node to one or more second related nodes, said relationship information including a token identify a relationship type and second nodes not being linked in the branched structure to said first node, wherein the token is a shortened representation of a corresponding relationship name; and

the database comprising information relating the tokens to the corresponding relationship names.

11. A computer system as claimed in claim 10 in which said relationship information includes a flag indicating a type of a related subject corresponding to said related node.

12. A computer system as claimed in claim 11 in which said relationship information includes a flag indicating that the relationship points in a direction towards this node from a related node.

13. A computer system as claimed in claim 10 in which said relationship information relates to a virtual node and said relationship information itself includes the data which would have been in the virtual node.

14. A computer system as claimed in claim 13 in which said relationship information includes a flag indicating a type of a related subject corresponding to said related node.

15. A computer system as claimed in claim 14 in which the data for said virtual node is stored at a location pointed to by the relationship information, the location not being part of the branched structure.

16. A computer system as claimed in claim 14 in which said relationship information includes a flag indicating that the relationship points in a direction towards this node from a related node.

17. A computer system as claimed in claim 16 in which branches in said branched structure comprise a relationship, whose flag indicates that the relationship is part of the branched structure.

18. A computer system as claimed in claim 17 in which said relationship information includes a flag indicating that the relationship points in a direction towards this node from a related node.