Hierarchical storage

• US 20040205581A1
• Filed: 07/15/2002
• Published: 10/14/2004
• Est. Priority Date: 07/15/2002
• Status: Abandoned Application

• Current Assignee: Toshiba Tec Corporation (Toshiba Corporation)
• Original Assignee: Toshiba Tec Corporation (Toshiba Corporation)
• Inventors: Gava, Fabio M.
• Application Number:
  US10/156,345
• Publication Number:
  US 20040205581A1
• Time in Patent Office: Days
• US Class Current: 715/513
• CPC Class Codes: G06F 40/117 Tagging; Marking up details of markup languages G06F40/143; Designating a block; Setting of attributes style sheets, e.g. eXtensible Stylesheet Language Transformation [XSLT], G06F40/154
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]

Abstract

A system and method is provided for implementing hierarchical storage of information. The system comprises a hierarchical repository having at least two levels. The first level comprises a folder and a markup language based file within the folder for storing information. Also stored within the folder is a second level folder which also has a markup language based file stored within the folder. In order to access the repository, a user interface is provided.

Claims

1. A hierarchical information storage system comprising:

a repository comprising;

at least one first level folder for storing at least first and second data sets,

at least one first level markup based file stored within the at least one first level folder, the first level markup based file comprising information relative to at least a portion of the first data set,

at least one second level folder stored within the at least one first level folder for storing information relative to the second data set, and

at least one second level markup based file stored within the at least one second level folder, the second level markup based file comprising information relative to at least a portion of the second data set; and

an interface communicatively coupled to the repository for handling communications with the repository, the interface comprising computer readable code on a computer readable medium.

2. The system of claim 1 wherein the interface comprises computer readable code for providing a functionality selected from the group consisting of:

querying the repository, changing the repository structure, adding to the repository, deleting from the repository, and combinations thereof.

3. The system of claim 1 wherein the interface comprises computer readable code for providing a functionality selected from the group consisting of:

querying the markup based files, changing the markup based files, adding to the markup based files, deleting from the markup based files, and combinations thereof.

4. The system of claim 1 wherein the interface further comprises computer readable code for ensuring data integrity.

5. The system of claim 1 further comprising at least one software component for performing a function on an element of the repository.

6. The system of claim 5 wherein the function performed by the software component is selected from the group consisting of:

querying, creating, modifying, deleting, and combinations thereof.

7. The system of claim 1 wherein the markup based files are selected from the group consisting of:

SGML, XML, HTML, and combinations thereof.

8. The system of claim 1 wherein the markup based files comprise information stored in a form selected from the group consisting of:

unsigned integers, text, binary data, and combinations thereof.

9. The system of claim 1 wherein the markup based files comprise at least one key and at least one name and value pair.

10. The system of claim 9 further comprising at least one software component for performing a function on name and value pairs.

11. The system of claim 10 wherein the function performed by the software component is selected from the group consisting of:

querying, creating, modifying, deleting, and combinations thereof.

12. The system of claim 1 comprising a plurality of repositories.

13. A hierarchical information storage system in a network environment comprising:

a client communicatively coupled to a server;

at least one repository stored on the server comprising;

at least one first level folder for storing at least first and second data sets,

at least one first level markup based file stored within the at least one first level folder, the first level markup based file comprising information relative to at least a portion of the first data set,

at least one second level folder stored within the at least one first level folder for storing information relative to the second data set, and

at least one second level markup based file stored within the at least one second level folder, the second level markup based file comprising information relative to at least a portion of the second data set; and

an interface communicatively coupled to the at least one repository for handling communications with the repository, the interface comprising computer readable code on a computer readable medium.

14. The system of claim 13 wherein the interface is located on the server.

15. The system of claim 13 wherein the interface is located on the client.

16. The system of claim 13 wherein the interface comprises computer readable code for providing a functionality selected from the group consisting of:

querying the repository, changing the repository structure, adding to the repository, deleting from the repository, and combinations thereof.

17. The system of claim 13 wherein the interface comprises computer readable code for providing a functionality selected from the group consisting of:

querying the markup based files, changing the markup based files, adding to the markup based files, deleting from the markup based files, and combinations thereof.

18. The system of claim 13 wherein the interface further comprises computer readable code for ensuring data integrity.

19. The hierarchical information storage system of claim 13 further comprising at least one software component for performing a function on an element of the repository.

20. The system of claim 19 wherein the at least one software component is located on the server.

21. The system of claim 19 wherein the at least one software component is located on the client.

22. The hierarchical information storage system of claim 19 wherein the function A=?performed by the software component is selected from the group consisting of:

querying, creating, modifying, deleting, and combinations thereof.

23. The system of claim 13 wherein the markup based files are selected from the group consisting of:

SGML, XML, HTML, and combinations thereof.

24. The system of claim 13 wherein the markup based files comprise information stored in a form selected from the group consisting of:

unsigned integers, text, binary data, and combinations thereof.

25. The system of claim 13 wherein the markup based files comprise at least one key and at least one name and value pair.

26. The system of claim 13 comprising a plurality of repositories.

27. A method for accessing a repository, the repository, the steps comprising:

receiving a command via an interface communicatively coupled to the repository specifying a value path;

searching for a file in the repository based on the value path, wherein the repository comprises at least one first level folder, at least one first level markup based file stored within the at least one first level folder, at least one second level folder stored within the at least one first level folder, and at least one second level markup based file stored within the at least one second level folder, the second level markup based file comprising information relative to at least a portion of the second data set, the searching beginning at the first level folder and continuing through additional level folders as necessary until a markup based file is found;

locking the file for exclusive use.

loading the markup file; and

finding a key within the markup file.

28. The method of claim 27 further comprising:

setting the value of the key within the markup file;

writing the change to the markup file to the repository; and

unlocking the file.

29. A computer-readable medium of instructions, comprising:

means adapted for receiving a command via an interface communicatively coupled to the repository specifying a value path;

means adapted for searching for a file in the repository based on the value path, wherein the repository comprises at least one first level folder, at least one first level markup based file stored within the at least one first level folder, at least one second level folder stored within the at least one first level folder, and at least one second level markup based file stored within the at least one second level folder, the second level markup based file comprising information relative to at least a portion of the second data set, the searching beginning at the first level folder and continuing through additional level folders as necessary until a markup based file is found;

means adapted for locking the file for exclusive use.

means adapted for loading the markup file; and

means adapted for finding a key within the markup file.

30. The computer-readable instructions of claim 29 further comprising:

means adapted for setting the value of the key within the markup file;

means adapted for writing the change to the markup file to the repository; and

means adapted for unlocking the file.