Claims
- 1. A method of representing information, said method comprising:
generating a first software object comprising a first node; generating a second software object comprising a second node; generating a third software object comprising a nexus that connects said first node and said second node; and performing at least one of the following:
generating a fourth software object as a third node, said third node comprising said first node, said second node, and said nexus; and generating a fifth software object as a fourth node, said fourth node comprising said nexus.
- 2. The method of claim 1, wherein said first node, said second node, and said third node serve as respective information containers directly addressable by a user and each has a format as a tuple:
- 3. The method of claim 2, wherein said nexus has a format as a tuple:
- 4. The method of claim 1, further comprising:
generating a sixth software object comprising a nexus to connect said fourth node to one of another node and a nexus.
- 5. A middleware module to represent and store information for a user application, said middleware module comprising:
a library having a module to generate an information-container, said module allowing for:
generating a first software object comprising a first node; generating a second software object comprising a second node; generating a third software object comprising a nexus that connects said first node and said second node, performing at least one of the following:
generating a fourth software object as a third node, said third node comprising said first node, said second node, and said nexus; and generating a fifth software object as a fourth node, said fourth node comprising said nexus; and an Application Program Interface (API) to allow a user to fill in data for said information-container generated by said module.
- 6. The middleware module of claim 5, wherein said first node, said second node, and said third node serve as respective information containers directly addressable by a user and each has a format as a tuple:
- 7. The middleware module of claim 6, wherein said nexus having a format as a tuple:
- 8. The middleware module of claim 5, said module further allowing:
generating a sixth software object comprising a nexus to connect said fourth node to another node or nexus.
- 9. A data structure comprising:
a first software object comprising a first node; a second software object comprising a second node; a third software object comprising a nexus that connects said first node and said second node; and at least one of the following:
a fourth software object generated as a third node, said third node comprising said first node, said second node, and said nexus; and a fifth software object generated as a fourth node, said fourth node comprising said nexus.
- 10. The data structure of claim 9, wherein said first node, said second node, and said third node serve as respective information containers directly addressable by a user and each has a format as a tuple:
- 11. The data structure of claim 10, said nexus having a format as a tuple:
- 12. The data structure of claim 7, further comprising:
a sixth software object comprising a nexus to connect said fourth node to another node or nexus.
- 13. An apparatus to represent and store information for a user application, said module comprising:
a storage unit containing a library having a module to generate an information-container, said module allowing for:
generating a first software object comprising a first node; generating a second software object comprising a second node; generating a third software object comprising a nexus that connects said first node and said second node, performing at least one of the following:
generating a fourth software object as a third node, said third node comprising said first node, said second node, and said nexus; and generating a fifth software object as a fourth node, said fourth node comprising said nexus; and a processor executing an Application Program Interface (API) to allow a user to fill in data for each said information-container generated by said library module.
- 14. The apparatus of claim 13, wherein said first node, said second node, and said third node serve as respective information containers directly addressable by a user and each has a format as a tuple:
- 15. The apparatus of claim 14, said nexus having a format as a tuple:
- 16. The apparatus of claim 13, said module further allowing:
generating a sixth software object comprising a nexus to connect said fourth node to another node or nexus.
- 17. A network executing a method to represent and store information for a user application, said network comprising:
at least one computer containing a middleware module having the ability to do at least one of the following:
generate an information-container using a format of representing information including:
generating a first software object comprising a first node; generating a second software object comprising a second node; generating a third software object comprising a nexus that connects said first node and said second node; and performing at least one of the following:
generating a fourth software object as a third node, said third node comprising said first node, said second node, and said nexus; and generating a fifth software object as a fourth node, said fourth node comprising said nexus; and allow a user to fill in data for each said information-container generated by said method.
- 18. The network of claim 17, wherein said first node, said second node, and said third node serve as respective information containers directly addressable by a user and each has a format as a tuple:
- 19. The network of claim 18, said nexus having a format as a tuple:
- 20. The network of claim 13, said method stored in said middleware module further comprising:
generating a sixth software object comprising a nexus to connect said fourth node to another node or nexus.
- 21. A signal-bearing medium tangibly embodying a program of machine-readable instructions executable by a digital processing apparatus to perform a method of representing information, said method comprising:
generating a first software object comprising a first node; generating a second software object comprising a second node; and generating a third software object comprising a nexus that connects said first node and said second node, wherein said method further allows at least one of the following:
a fourth software object to be generated as a third node, said third node comprising said first node, said second node, and said nexus; and said nexus to be included in a fifth software object generated to be a fourth node.
- 22. The signal-bearing medium of claim 21, wherein said first node, said second node, and said third node serve as respective information containers directly addressable by a user and each has a format as a tuple:
- 23. The signal-bearing medium of claim 22, said nexus having a format as a tuple:
- 24. The signal-bearing medium of claim 21, said method further comprising:
generating a sixth software object comprising a nexus to connect said fourth node to another node or nexus.
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] The present Application is related to U.S. patent application Ser. No. 10/______ filed on ______, to Rosario Uceda-Sosa, entitled “METHOD AND STRUCTURE FOR DOMAIN-INDEPENDENT MODULAR REASONING AND RELATION REPRESENTATION FOR ENTITY-RELATION BASED INFORMATION STRUCTURES”, having IBM Docket YOR920020217US1, and to U.S. patent application Ser. No. 10/______, filed on ______, to Rosario Uceda-Sosa, entitled “METHOD AND STRUCTURE FOR TEMPLATE-BASED DATA RETRIEVAL FOR HYPERGRAPH ENTITY-RELATION INFORMATION STRUCTURE”, having IBM Docket YOR920020218US1, both assigned to the present assignee, and both incorporated herein by reference.