Apparatus method and system for registration effecting information access

• US 20040163020A1
• Filed: 02/11/2004
• Published: 08/19/2004
• Est. Priority Date: 01/25/2002
• Status: Abandoned Application

• Current Assignee: Content Directions, Inc. (Linkstorm Corp.)
• Original Assignee: Content Directions, Inc. (Linkstorm Corp.)
• Inventors: Sidman, David
• Application Number:
  US10/470,257
• Publication Number:
  US 20040163020A1
• Time in Patent Office: Days
• US Class Current: 714/100
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/2282 Tablespace storage structures; Management thereof
• CPC Class Codes: H04L 2101/604 Address structures or formats
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 61/3015 Name registration, generation or assignment
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping

Abstract

An apparatus, method and system to register and provide a persistent indentifier of information that may be located in multiple locations, formats, and accesible in variable fashions based on the context of use. The present disclosure further provides the ability to automatically make information available and associated with its identifier. The disclosure also details the ability to create identifier. The disclosure also details the ability to create identifiers from content authoring tools within and for documents and/or other information. The invention teaches how to associate a single identifier while making information available, and accessible under varying conditions, from varying locations, in varying formats, based on various contexts of access. The present disclosure further teaches an enhanced digital object identifier, an enhanced Handle system, and enhanced directory registry that facilitate the access, association, and instantiation of information over a communications network.

Claims

1. A method of using a computer to access information, comprising:

generating a unique, persistent, and universal name identifier associated for specified information;

receiving an address for a location for the information;

receiving metadata for the unique, persistent, and universal name identifier, wherein the metadata provides descriptive data regarding the unique, persistent, and universal name identifier;

associating the unique, persistent, and universal name identifier with the metadata so that the unique, persistent, and universal name identifier and metadata can be identified by each other;

registering the metadata in a metadata database before effecting the registration of the unique, persistent, and universal name identifier in a first phase of a two-phase registration commitment;

generating an error signal if the metadata fails to register in the metadata database;

effecting the registration of the unique, persistent, and universal name identifier with the address associated to the location of the information in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the unique, persistent, and universal name identifier is unique in the database, wherein the registration of the unique, persistent, and universal name identifier is a second phase of a two-phase registration commitment and occurs after effecting the registration of the metadata in a first phase of a two-phase registration commitment; and

generating an error signal if the unique, persistent, and universal name identifier fails to register in the database; and

denying registration of a unique, persistent, and universal name identifier if either phase of a two-phase commitment generate an error.

2. The method of claim 1, wherein the registration of the unique, persistent, and universal name identifier resolves to entity information representing an entity.

3. The method of claim 2, wherein the entity is a person.

4. The method of claim 1, further comprising:

determining a prefix component of a unique, persistent, and universal name identifier automatically;

effecting the registration of the prefix component of a unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the prefix component is unique in the database, and wherein the prefix component may be used as a basis for registering subsequent unique, persistent, and universal name identifier s with unique suffixes.

5. The method of claim 1, wherein metadata is denied registration in a metadata database by user request for the unique, persistent, and universal name identifier be unpublished.

6. The method of claim 1, wherein the generated errors are tagged in XML format.

7. A method of using a computer to access information, comprising:

allocating space in a storage facility for information;

making the location of the allocated space addressable and accessible over a communications network;

storing the information to the allocated space;

generating a unique, persistent, and universal name identifier associated with the information;

effecting the registration of the unique, persistent, and universal name identifier with an address associated to a location where the information is stored in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the unique, persistent, and universal name identifier is unique in the database.

8. The method of claim 7, further comprising:

determining a prefix component of a unique, persistent, and universal name identifier automatically;

effecting the registration of the prefix component of a unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the prefix component is unique in the database, and wherein the prefix component may be used as a basis for registering subsequent unique, persistent, and universal name identifier s with unique suffixes.

9. The method of claim 7, further comprising:

receiving metadata for the unique, persistent, and universal name identifier, wherein the metadata provides descriptive data regarding the unique, persistent, and universal name identifier; and

associating the unique, persistent, and universal name identifier with the metadata so that the unique, persistent, and universal name identifier and metadata can be identified by each other.

10. The method of claim 9, wherein metadata is denied registration in a metadata database by user request for the unique, persistent, and universal name identifier to be unpublished.

11. The method of claim 7, further comprising:

registering the metadata in a metadata database before effecting the registration of the unique, persistent, and universal name identifier in a first phase of a two-phase registration commitment; and

generating an error if the metadata fails to register in the metadata database;

registering the unique, persistent, and universal name identifier in the database in a second phase of a two-phase registration commitment after effecting the registration of the metadata in a first phase of a two-phase registration commitment; and

generating an error if the unique, persistent, and universal name identifier fails to register in the database; and

failing to register a unique, persistent, and universal name identifier if either phase of a two-phase commitment generate an error.

12. The method of claim 11, wherein the generated errors are tagged in XML format.

13. The method of claim 7, further comprising:

indexing the information stored in the storage facility; and

associating the indexed information with the unique, persistent, and universal name identifier so that the unique, persistent, and universal name identifier and indexed information can be identified by each other.

14. A method of using a computer to access information, comprising:

determining a prefix component of a unique, persistent, and universal name identifier automatically;

effecting the registration of the prefix component of a unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the prefix component is unique in the database, and wherein the prefix component may be used as a basis for registering subsequent unique, persistent, and universal name identifier s with unique suffixes.

15. The method of claim 14, further comprising:

receiving metadata for said prefix component of a unique, persistent, and universal name identifier, wherein the metadata provides descriptive data regarding the prefix; and

associating the prefix with the metadata so that the prefix and metadata can be identified by each other.

16. The method of claim 14, wherein metadata is denied registration in a metadata database by user request for the unique, persistent, and universal name identifier to be unpublished.

17. A method of using a computer, comprising:

generating, automatically, an instruction signal for a prefix component for a unique, persistent, and universal name identifier.

18. The method of claim 17, further comprising:

generating, automatically, an instruction signal for a suffix component for a unique, persistent, and universal name identifier.

19. The method of claim 17, further comprising:

generating, automatically, an instruction signal to allocate space for information for which the unique, persistent, and universal name identifier is being registered and making the location of the allocated space addressable and accessible over a communications network.

20. The method of claim 19, further comprising:

generating, automatically, an instruction signal to allocate space for information that is auctioned to a plurality of storage facilities for offers.

21. The method of claim 19, further comprising:

generating, automatically, an instruction signal to allocate space for information that is auctioned to a plurality of content distributors for offers.

22. The method of claim 19, further comprising:

generating, automatically, an instruction signal to allocate space for information solicits offers from a plurality of storage facilities.

23. The method of claim 19, further comprising:

generating, automatically, an instruction signal to allocate space for information solicits offers from a plurality of content distributors.

24. The method of claim 17, further comprising:

generating, automatically, an instruction signal to register the prefix component of a unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the prefix component is unique in the database, and wherein the prefix component may be used as a basis for registering subsequent unique, persistent, and universal name identifier s with unique suffixes.

25. The method of claim 17, further comprising:

generating, automatically, an instruction signal to register the unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the unique, persistent, and universal name identifier is unique in the database.

26. A method of using a computer, comprising:

generating, automatically, an instruction signal to register a unique, persistent, and universal name identifier; and

generating, automatically, an instruction signal to allocate space for information for which the unique, persistent, and universal name identifier is being registered and making the location of the allocated space addressable and accessible over a communications network.

27. The method of claim 26, further comprising:

generating, automatically, an instruction signal with encoded information for which the unique, persistent, and universal name identifier is being registered.

28. The method of claim 26, further comprising:

generating, automatically, an instruction signal with an encoded location for the information for which the unique, persistent, and universal name identifier is being registered.

29. The method of claim 26, further comprising:

generating, automatically, an instruction signal for a prefix component for a unique, persistent, and universal name identifier.

30. A method of using a computer to establish an association of desired information and a unique, persistent, and universal name identifier, comprising:

specifying desired information;

specifying a prefix for a unique, persistent, and universal name identifier;

specifying a suffix for a unique, persistent, and universal name identifier;

specifying a location for the desired information;

effecting the submission of any specified desired information, prefix, suffix, and location to a unique, persistent, and universal name identifier database for registration.

31. The method of claim 30, wherein the specification of desired information is through a selection tool of a content authoring application providing access to information in the content authoring application through an application programming interface disposed in communication with an interaction interface.

32. The method of claim 30, wherein the specification of desired information is through a file selection tool.

33. The method of claim 30, wherein the specification of a prefix invokes a publisher registration tool.

34. The method of claim 33, wherein a publisher registration tool provides fields for contact and billing information to be entered by a user.

35. The method of claim 34, wherein the publisher provided fields for contact and billing information to be entered by a user are storable.

36. The method of claim 30, wherein the specification of a prefix obtains stored publisher contact and billing information.

37. The method of claim 36, wherein the stored publisher contact and billing information is to be stored in a cookie.

38. The method of claim 36, wherein the stored publisher contact and billing information is to be stored in a preference file.

39. The method of claim 36, wherein the stored publisher contact and billing information is to be stored in a database.

40. The method of claim 30, further comprising:

specifying metadata.

41. The method of claim 40, wherein the specification to effect submission is further configured to submit metadata to a metadata database to be associated with respective data submitted to the unique, persistent, and universal name identifier database.

42. The method of claim 30, wherein the specification of a prefix sets a flag for automatically generating a prefix.

43. The method of claim 30, wherein the specification of a suffix sets a flag for automatically generating a suffix.

44. The method of claim 30, wherein the specification of a location is through a file selection tool.

45. The method of claim 30, wherein the specification of a location is through a URL text field.

46. The method of claim 30, wherein the specification to effect submission of data is through a button.

47. The method of claim 30, wherein the specification to effect submission of data effects the registration of a unique, persistent, and universal name identifier for a document.

48. The method of claim 30, wherein the specification to effect submission of data effects the registration of a unique, persistent, and universal name identifier for a selection of information.

49. The method of claim 30, wherein the effectuation of the registration of a unique, persistent, and universal name identifier for a selection of information is automatic without further user interaction.

50. The method of claim 30, wherein the specification to effect submission of data is through a menu.

51. The method of claim 30, wherein the specification to effect submission of data imbeds identifying tags within the context of a selection of information.

52. The method of claim 30, wherein the specification to effect submission of data imbeds identifying tags within a document.

53. The method of claim 30, wherein the specification to effect submission of data stores a provisional unique, persistent, and universal name identifier.

54. The method of claim 53, wherein the provisional unique, persistent, and universal name identifier is stored in a file.

55. The method of claim 53, wherein the provisional unique, persistent, and universal name identifier is stored in a batch file.

56. The method of claim 53, wherein the provisional unique, persistent, and universal name identifier is stored in a database.

57. The method of claim 30, wherein the mechanism to effect submission of data stores a metadata for a provisional unique, persistent, and universal name identifier.

58. The method of claim 57, wherein the stored metadata includes document information.

59. The method of claim 58, wherein the document information includes the author of the document.

60. The method of claim 58, wherein the document information includes the creation date of the document.

61. The method of claim 58, wherein the document information includes the modification date of the document.

62. The method of claim 58, wherein the document information includes corporation owning the document.

63. The method of claim 58, wherein the document information includes automatic document generated values.

64. The method of claim 63, wherein the automatic document generated values is include index information.

65. The method of claim 63, wherein the automatic document generated values is table of contents information.

66. The method of claim 63, wherein the automatic document generated values is glossary information.

67. A system for information access, comprising:

means to generate a unique, persistent, and universal name identifier associated for specified information;

means to receive an address for a location for the information;

means to receive metadata for the unique, persistent, and universal name identifier, wherein the metadata provides descriptive data regarding the unique, persistent, and universal name identifier;

means to associate the unique, persistent, and universal name identifier with the metadata so that the unique, persistent, and universal name identifier and metadata can be identified by each other;

means to register the metadata in a metadata database before effecting the registration of the unique, persistent, and universal name identifier in a first phase of a two-phase registration commitment;

means to generate an error signal if the metadata fails to register in the metadata database;

means to effect the registration of the unique, persistent, and universal name identifier with the address associated to the location of the information in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the unique, persistent, and universal name identifier is unique in the database, wherein the registration of the unique, persistent, and universal name identifier is a second phase of a two-phase registration commitment and occurs after effecting the registration of the metadata in a first phase of a two-phase registration commitment; and

means to generate an error signal if the unique, persistent, and universal name identifier fails to register in the database; and

means to deny registration of a unique, persistent, and universal name identifier if either phase of a two-phase commitment generate an error.

68. The system of claim 67, wherein the registration of the unique, persistent, and universal name identifier resolves to entity information representing an entity.

69. The system of claim 68, wherein the entity is a person.

70. The system of claim 67, further comprising:

means to determine a prefix component of a unique, persistent, and universal name identifier automatically;

means to effect the registration of the prefix component of a unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the prefix component is unique in the database, and wherein the prefix component may be used as a basis for registering subsequent unique, persistent, and universal name identifier s with unique suffixes.

71. The system of claim 67, wherein metadata is denied registration in a metadata database by user request for the unique, persistent, and universal name identifier be unpublished.

72. The system of claim 67, wherein the generated errors are tagged in XML format.

73. A system for information access, comprising:

means to allocate space in a storage facility for information;

means to make the location of the allocated space addressable and accessible over a communications network;

means to store the information to the allocated space;

means to generate a unique, persistent, and universal name identifier associated with the information;

means to effect the registration of the unique, persistent, and universal name identifier with an address associated to a location where the information is stored in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the unique, persistent, and universal name identifier is unique in the database.

74. The system of claim 73, further comprising:

means to determine a prefix component of a unique, persistent, and universal name identifier automatically;

means to effect the registration of the prefix component of a unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the prefix component is unique in the database, and wherein the prefix component may be used as a basis for registering subsequent unique, persistent, and universal name identifier s with unique suffixes.

75. The system of claim 73, further comprising:

means to receive metadata for the unique, persistent, and universal name identifier, wherein the metadata provides descriptive data regarding the unique, persistent, and universal name identifier; and

means to associate the unique, persistent, and universal name identifier with the metadata so that the unique, persistent, and universal name identifier and metadata can be identified by each other.

76. The system of claim 75, wherein metadata is denied registration in a metadata database by user request for the unique, persistent, and universal name identifier to be unpublished.

77. The system of claim 73, further comprising:

means to register the metadata in a metadata database before effecting the registration of the unique, persistent, and universal name identifier in a first phase of a two-phase registration commitment; and

means to generate an error if the metadata fails to register in the metadata database;

means to register the unique, persistent, and universal name identifier in the database in a second phase of a two-phase registration commitment after effecting the registration of the metadata in a first phase of a two-phase registration commitment; and

means to generate an error if the unique, persistent, and universal name identifier fails to register in the database; and

means to fail to register a unique, persistent, and universal name identifier if either phase of a two-phase commitment generate an error.

78. The system of claim 77, wherein the generated errors are tagged in XML format.

79. The system of claim 73, further comprising:

means to index the information stored in the storage facility; and

means to associate the indexed information with the unique, persistent, and universal name identifier so that the unique, persistent, and universal name identifier and indexed information can be identified by each other.

80. A system for information access, comprising:

means to determine a prefix component of a unique, persistent, and universal name identifier automatically;

means to effect the registration of the prefix component of a unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the prefix component is unique in the database, and wherein the prefix component may be used as a basis for registering subsequent unique, persistent, and universal name identifier s with unique suffixes.

81. The system of claim 80, further comprising:

means to receive metadata for said prefix component of a unique, persistent, and universal name identifier, wherein the metadata provides descriptive data regarding the prefix; and

means to associate the prefix with the metadata so that the prefix and metadata can be identified by each other.

82. The system of claim 80, wherein metadata is denied registration in a metadata database by user request for the unique, persistent, and universal name identifier to be unpublished.

83. A system for using a computer, comprising:

means to generate, automatically, an instruction signal for a prefix component for a unique, persistent, and universal name identifier.

84. The system of claim 83, further comprising:

means to generate, automatically, an instruction signal for a suffix component for a unique, persistent, and universal name identifier.

85. The system of claim 83, further comprising:

means to generate, automatically, an instruction signal to allocate space for information for which the unique, persistent, and universal name identifier is being registered and making the location of the allocated space addressable and accessible over a communications network.

86. The system of claim 85, further comprising:

means to generate, automatically, an instruction signal to allocate space for information that is auctioned to a plurality of storage facilities for offers.

87. The system of claim 85, further comprising:

means to generate, automatically, an instruction signal to allocate space for information that is auctioned to a plurality of content distributors for offers.

88. The system of claim 85, further comprising:

means to generate, automatically, an instruction signal to allocate space for information solicits offers from a plurality of storage facilities.

89. The system of claim 85, further comprising:

means to generate, automatically, an instruction signal to allocate space for information solicits offers from a plurality of content distributors.

90. The system of claim 83, further comprising:

means to generate, automatically, an instruction signal to register the prefix component of a unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the prefix component is unique in the database, and wherein the prefix component may be used as a basis for registering subsequent unique, persistent, and universal name identifier s with unique suffixes.

91. The system of claim 83, further comprising:

means to generate, automatically, an instruction signal to register the unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the unique, persistent, and universal name identifier is unique in the database.

92. A system for using a computer, comprising:

means to generate, automatically, an instruction signal to register a unique, persistent, and universal name identifier; and

generate, automatically, an instruction signal to allocate space for information for which the unique, persistent, and universal name identifier is being registered and making the location of the allocated space addressable and accessible over a communications network.

93. The system of claim 92, further comprising:

generate, automatically, an instruction signal with encoded information for which the unique, persistent, and universal name identifier is being registered.

94. The system of claim 92, further comprising:

generate, automatically, an instruction signal with an encoded location for the information for which the unique, persistent, and universal name identifier is being registered.

95. The system of claim 92, further comprising:

generate, automatically, an instruction signal for a prefix component for a unique, persistent, and universal name identifier.

96. A system to establish an association of desired information and a unique, persistent, and universal name identifier, comprising:

means to specify desired information;

means to specify a prefix for a unique, persistent, and universal name identifier;

means to specify a suffix for a unique, persistent, and universal name identifier means to specify a location for the desired information;

means to effect the submission of any specified desired information, prefix, suffix, and location to a unique, persistent, and universal name identifier database for registration.

97. The system of claim 96, wherein the specification of desired information is through a selection tool of a content authoring application providing access to information in the content authoring application through an application programming interface disposed in communication with an interaction interface.

98. The system of claim 96, wherein the specification of desired information is through a file selection tool.

99. The system of claim 96, wherein the specification of a prefix invokes a publisher registration tool.

100. The system of claim 99, wherein a publisher registration tool provides fields for contact and billing information to be entered by a user.

101. The system of claim 100, wherein the publisher provided fields for contact and billing information to be entered by a user are storable.

102. The system of claim 96, wherein the specification of a prefix obtains stored publisher contact and billing information.

103. The system of claim 102, wherein the stored publisher contact and billing information is to be stored in a cookie.

104. The system of claim 102, wherein the stored publisher contact and billing information is to be stored in a preference file.

105. The system of claim 102, wherein the stored publisher contact and billing information is to be stored in a database.

106. The system of claim 96, further comprising:

means to specify metadata.

107. The system of claim 106, wherein the specification to effect submission is further configured to submit metadata to a metadata database to be associated with respective data submitted to the unique, persistent, and universal name identifier database.

108. The system of claim 96, wherein the specification of a prefix sets a flag for automatically generating a prefix.

109. The system of claim 96, wherein the specification of a suffix sets a flag for automatically generating a suffix.

110. The system of claim 96, wherein the specification of a location is through a file selection tool.

111. The system of claim 96, wherein the specification of a location is through a URL text field.

112. The system of claim 96, wherein the specification to effect submission of data is through a button.

113. The system of claim 96, wherein the specification to effect submission of data effects the registration of a unique, persistent, and universal name identifier for a document.

114. The system of claim 96, wherein the specification to effect submission of data effects the registration of a unique, persistent, and universal name identifier for a selection of information.

115. The system of claim 96, wherein the effectuation of the registration of a unique, persistent, and universal name identifier for a selection of information is automatic without further user interaction.

116. The system of claim 96, wherein the specification to effect submission of data is through a menu.

117. The system of claim 96, wherein the specification to effect submission of data imbeds identifying tags within the context of a selection of information.

118. The system of claim 96, wherein the specification to effect submission of data imbeds identifying tags within a document.

119. The system of claim 96, wherein the specification to effect submission of data stores a provisional unique, persistent, and universal name identifier.

120. The system of claim 119, wherein the provisional unique, persistent, and universal name identifier is stored in a file.

121. The system of claim 119, wherein the provisional unique, persistent, and universal name identifier is stored in a batch file.

122. The system of claim 119, wherein the provisional unique, persistent, and universal name identifier is stored in a database.

123. The system of claim 96, wherein the mechanism to effect submission of data stores a metadata for a provisional unique, persistent, and universal name identifier.

124. The system of claim 123, wherein the stored metadata includes document information.

125. The system of claim 124, wherein the document information includes the author of the document.

126. The system of claim 124, wherein the document information includes the creation date of the document.

127. The system of claim 124, wherein the document information includes the modification date of the document.

128. The system of claim 124, wherein the document information includes corporation owning the document.

129. The system of claim 124, wherein the document information includes automatic document generated values.

130. The system of claim 129, wherein the automatic document generated values is include index information.

131. The system of claim 129, wherein the automatic document generated values is table of contents information.

132. The system of claim 129, wherein the automatic document generated values is glossary information.

133. A program stored on a medium readable by a processor, the program for information access, comprising:

a module to generate a unique, persistent, and universal name identifier associated for specified information;

a module to receive an address for a location for the information;

a module to receive metadata for the unique, persistent, and universal name identifier, wherein the metadata provides descriptive data regarding the unique, persistent, and universal name identifier;

a module to associate the unique, persistent, and universal name identifier with the metadata so that the unique, persistent, and universal name identifier and metadata can be identified by each other;

a module to register the metadata in a metadata database before effecting the registration of the unique, persistent, and universal name identifier in a first phase of a two-phase registration commitment;

a module to generate an error signal if the metadata fails to register in the metadata database;

a module to effect the registration of the unique, persistent, and universal name identifier with the address associated to the location of the information in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the unique, persistent, and universal name identifier is unique in the database, wherein the registration of the unique, persistent, and universal name identifier is a second phase of a two-phase registration commitment and occurs after effecting the registration of the metadata in a first phase of a two-phase registration commitment; and

a module to generate an error signal if the unique, persistent, and universal name identifier fails to register in the database; and

a module to deny registration of a unique, persistent, and universal name identifier if either phase of a two-phase commitment generate an error.

134. The medium of claim 133, wherein the registration of the unique, persistent, and universal name identifier resolves to entity information representing an entity.

135. The medium of claim 134, wherein the entity is a person.

136. The medium of claim 133, further comprising:

a module to determine a prefix component of a unique, persistent, and universal name identifier automatically;

a module to effect the registration of the prefix component of a unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the prefix component is unique in the database, and wherein the prefix component may be used as a basis for registering subsequent unique, persistent, and universal name identifier s with unique suffixes.

137. The medium of claim 133, wherein metadata is denied registration in a metadata database by user request for the unique, persistent, and universal name identifier be unpublished.

138. The medium of claim 133, wherein the generated errors are tagged in XML format.

139. A program stored on a medium readable by a processor, the program for information access, comprising:

a module to allocate space in a storage facility for information;

a module to make the location of the allocated space addressable and accessible over a communications network;

a module to store the information to the allocated space;

a module to generate a unique, persistent, and universal name identifier associated with the information;

a module to effect the registration of the unique, persistent, and universal name identifier with an address associated to a location where the information is stored in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the unique, persistent, and universal name identifier is unique in the database.

140. The medium of claim 139, further comprising:

a module to determine a prefix component of a unique, persistent, and universal name identifier automatically;

a module to effect the registration of the prefix component of a unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the prefix component is unique in the database, and wherein the prefix component may be used as a basis for registering subsequent unique, persistent, and universal name identifier s with unique suffixes.

141. The medium of claim 139, further comprising:

a module to receive metadata for the unique, persistent, and universal name identifier, wherein the metadata provides descriptive data regarding the unique, persistent, and universal name identifier; and

a module to associate the unique, persistent, and universal name identifier with the metadata so that the unique, persistent, and universal name identifier and metadata can be identified by each other.

142. The medium of claim 141, wherein metadata is denied registration in a metadata database by user request for the unique, persistent, and universal name identifier to be unpublished.

143. The medium of claim 139, further comprising:

a module to register the metadata in a metadata database before effecting the registration of the unique, persistent, and universal name identifier in a first phase of a two-phase registration commitment; and

a module to generate an error if the metadata fails to register in the metadata database;

a module to register the unique, persistent, and universal name identifier in the database in a second phase of a two-phase registration commitment after effecting the registration of the metadata in a first phase of a two-phase registration commitment; and

a module to generate an error if the unique, persistent, and universal name identifier fails to register in the database; and

a module to fail to register a unique, persistent, and universal name identifier if either phase of a two-phase commitment generate an error.

144. The medium of claim 143, wherein the generated errors are tagged in XML format.

145. The medium of claim 139, further comprising:

a module to index the information stored in the storage facility; and

a module to associate the indexed information with the unique, persistent, and universal name identifier so that the unique, persistent, and universal name identifier and indexed information can be identified by each other.

146. A program stored on a medium readable by a processor, the program for information access, comprising:

a module to determine a prefix component of a unique, persistent, and universal name identifier automatically;

a module to effect the registration of the prefix component of a unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the prefix component is unique in the database, and wherein the prefix component may be used as a basis for registering subsequent unique, persistent, and universal name identifier s with unique suffixes.

147. The medium of claim 146, further comprising:

a module to receive metadata for said prefix component of a unique, persistent, and universal name identifier, wherein the metadata provides descriptive data regarding the prefix; and

a module to associate the prefix with the metadata so that the prefix and metadata can be identified by each other.

148. The medium of claim 146, wherein metadata is denied registration in a metadata database by user request for the unique, persistent, and universal name identifier to be unpublished.

149. A computer readable medium, comprising:

an instruction signal to automatically generate a prefix component for a unique, persistent, and universal name identifier.

150. The medium of claim 149, further comprising an instruction signal to automatically generate a suffix component for a unique, persistent, and universal name identifier.

151. The medium of claim 149, further comprising an instruction signal to automatically allocate space for information for which the unique, persistent, and universal name identifier is being registered and making the location of the allocated space addressable and accessible over a communications network.

152. The medium of claim 151, further comprising an instruction signal to automatically allocate space for information is auctioned to a plurality of storage facilities for offers.

153. The medium of claim 151, further comprising an instruction signal to automatically allocate space for information is auctioned to a plurality of content distributors for offers.

154. The medium of claim 151, further comprising an instruction signal to automatically allocate space for information solicits offers from a plurality of storage facilities.

155. The medium of claim 151, further comprising an instruction signal to automatically allocate space for information solicits offers from a plurality of content distributors.

156. The medium of claim 149, further comprising an instruction signal to automatically register the prefix component of a unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the prefix component is unique in the database, and wherein the prefix component may be used as a basis for registering subsequent unique, persistent, and universal name identifier s with unique suffixes.

157. The medium of claim 149, further comprising an instruction signal to automatically register the unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the unique, persistent, and universal name identifier is unique in the database.

158. A computer readable medium, comprising:

an instruction signal to automatically register a unique, persistent, and universal name identifier; and

an instruction signal to automatically allocate space for information for which the unique, persistent, and universal name identifier is being registered and making the location of the allocated space addressable and accessible over a communications network.

159. The medium of claim 158, further comprising an instruction signal with encoded information for which the unique, persistent, and universal name identifier is being registered.

160. The medium of claim 158, further comprising an instruction signal with an encoded location for the information for which the unique, persistent, and universal name identifier is being registered.

161. The medium of claim 158, further comprising an instruction signal to automatically generate a prefix component for a unique, persistent, and universal name identifier.

162. A program stored on a medium readable by a processor, the program to establish an association of desired information and a unique, persistent, and universal name identifier, comprising:

a module to specify desired information;

a module to specify a prefix for a unique, persistent, and universal name identifier;

a module to specify a suffix for a unique, persistent, and universal name identifier;

a module to specify a location for the desired information;

a module to effect the submission of any specified desired information, prefix, suffix, and location to a unique, persistent, and universal name identifier database for registration.

163. The medium of claim 162, wherein the specification of desired information is through a selection tool of a content authoring application providing access to information in the content authoring application through an application programming interface disposed in communication with an interaction interface.

164. The medium of claim 162, wherein the specification of desired information is through a file selection tool.

165. The medium of claim 162, wherein the specification of a prefix invokes a publisher registration tool.

166. The medium of claim 165, wherein a publisher registration tool provides fields for contact and billing information to be entered by a user.

167. The medium of claim 166, wherein the publisher provided fields for contact and billing information to be entered by a user are storable.

168. The medium of claim 162, wherein the specification of a prefix obtains stored publisher contact and billing information.

169. The medium of claim 168, wherein the stored publisher contact and billing information is to be stored in a cookie.

170. The medium of claim 168, wherein the stored publisher contact and billing information is to be stored in a preference file.

171. The medium of claim 168, wherein the stored publisher contact and billing information is to be stored in a database.

172. The medium of claim 162, further comprising:

a module to specify metadata.

173. The medium of claim 172, wherein the specification to effect submission is further configured to submit metadata to a metadata database to be associated with respective data submitted to the unique, persistent, and universal name identifier database.

174. The medium of claim 162, wherein the specification of a prefix sets a flag for automatically generating a prefix.

175. The medium of claim 162, wherein the specification of a suffix sets a flag for automatically generating a suffix.

176. The medium of claim 162, wherein the specification of a location is through a file selection tool.

177. The medium of claim 162, wherein the specification of a location is through a URL text field.

178. The medium of claim 162, wherein the specification to effect submission of data is through a button.

179. The medium of claim 162, wherein the specification to effect submission of data effects the registration of a unique, persistent, and universal name identifier for a document.

180. The medium of claim 162, wherein the specification to effect submission of data effects the registration of a unique, persistent, and universal name identifier for a selection of information.

181. The medium of claim 162, wherein the effectuation of the registration of a unique, persistent, and universal name identifier for a selection of information is automatic without further user interaction.

182. The medium of claim 162, wherein the specification to effect submission of data is through a menu.

183. The medium of claim 162, wherein the specification to effect submission of data imbeds identifying tags within the context of a selection of information.

184. The medium of claim 162, wherein the specification to effect submission of data imbeds identifying tags within a document.

185. The medium of claim 162, wherein the specification to effect submission of data stores a provisional unique, persistent, and universal name identifier.

186. The medium of claim 185, wherein the provisional unique, persistent, and universal name identifier is stored in a file.

187. The medium of claim 185, wherein the provisional unique, persistent, and universal name identifier is stored in a batch file.

188. The medium of claim 185, wherein the provisional unique, persistent, and universal name identifier is stored in a database.

189. The medium of claim 162, wherein the mechanism to effect submission of data stores a metadata for a provisional unique, persistent, and universal name identifier.

190. The medium of claim 189, wherein the stored metadata includes document information.

191. The medium of claim 190, wherein the document information includes the author of the document.

192. The medium of claim 190, wherein the document information includes the creation date of the document.

193. The medium of claim 190, wherein the document information includes the modification date of the document.

194. The medium of claim 190, wherein the document information includes corporation owning the document.

195. The medium of claim 190, wherein the document information includes automatic document generated values.

196. The medium of claim 195, wherein the automatic document generated values is include index information.

197. The medium of claim 195, wherein the automatic document generated values is table of contents information.

198. The medium of claim 195, wherein the automatic document generated values is glossary information.

199. An apparatus, comprising:

a processor;

a memory, communicatively connected to the processor;

a program, stored in the memory, including,

a module to generate a unique, persistent, and universal name identifier associated for specified information;

a module to receive an address for a location for the information;

a module to receive metadata for the unique, persistent, and universal name identifier, wherein the metadata provides descriptive data regarding the unique, persistent, and universal name identifier;

a module to associate the unique, persistent, and universal name identifier with the metadata so that the unique, persistent, and universal name identifier and metadata can be identified by each other;

a module to register the metadata in a metadata database before effecting the registration of the unique, persistent, and universal name identifier in a first phase of a two-phase registration commitment;

a module to generate an error signal if the metadata fails to register in the metadata database;

a module to effect the registration of the unique, persistent, and universal name identifier with the address associated to the location of the information in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the unique, persistent, and universal name identifier is unique in the database, wherein the registration of the unique, persistent, and universal name identifier is a second phase of a two-phase registration commitment and occurs after effecting the registration of the metadata in a first phase of a two-phase registration commitment; and

a module to generate an error signal if the unique, persistent, and universal name identifier fails to register in the database; and

a module to deny registration of a unique, persistent, and universal name identifier if either phase of a two-phase commitment generate an error.

200. The apparatus of claim 199, wherein the registration of the unique, persistent, and universal name identifier resolves to entity information representing an entity.

201. The apparatus of claim 200, wherein the entity is a person.

202. The apparatus of claim 199, further comprising:

a module to determine a prefix component of a unique, persistent, and universal name identifier automatically;

a module to effect the registration of the prefix component of a unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the prefix component is unique in the database, and wherein the prefix component may be used as a basis for registering subsequent unique, persistent, and universal name identifier s with unique suffixes.

203. The apparatus of claim 199, wherein metadata is denied registration in a metadata database by user request for the unique, persistent, and universal name identifier be unpublished.

204. The apparatus of claim 199, wherein the generated errors are tagged in XML format.

205. An apparatus, comprising:

a processor;

a memory, communicatively connected to the processor;

a program, stored in the memory, including,

a module to allocate space in a storage facility for information;

a module to make the location of the allocated space addressable and accessible over a communications network;

a module to store the information to the allocated space;

a module to generate a unique, persistent, and universal name identifier associated with the information;

a module to effect the registration of the unique, persistent, and universal name identifier with an address associated to a location where the information is stored in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the unique, persistent, and universal name identifier is unique in the database.

206. The apparatus of claim 205, further comprising:

a module to determine a prefix component of a unique, persistent, and universal name identifier automatically;

a module to effect the registration of the prefix component of a unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the prefix component is unique in the database, and wherein the prefix component may be used as a basis for registering subsequent unique, persistent, and universal name identifier s with unique suffixes.

207. The apparatus of claim 205, further comprising:

a module to receive metadata for the unique, persistent, and universal name identifier, wherein the metadata provides descriptive data regarding the unique, persistent, and universal name identifier; and

a module to associate the unique, persistent, and universal name identifier with the metadata so that the unique, persistent, and universal name identifier and metadata can be identified by each other.

208. The apparatus of claim 207, wherein metadata is denied registration in a metadata database by user request for the unique, persistent, and universal name identifier to be unpublished.

209. The apparatus of claim 205, further comprising:

a module to register the metadata in a metadata database before effecting the registration of the unique, persistent, and universal name identifier in a first phase of a two-phase registration commitment; and

a module to generate an error if the metadata fails to register in the metadata database;

a module to register the unique, persistent, and universal name identifier in the database in a second phase of a two-phase registration commitment after effecting the registration of the metadata in a first phase of a two-phase registration commitment; and

a module to generate an error if the unique, persistent, and universal name identifier fails to register in the database; and

a module to fail to register a unique, persistent, and universal name identifier if either phase of a two-phase commitment generate an error.

210. The apparatus of claim 209, wherein the generated errors are tagged in XML format.

211. The apparatus of claim 205, further comprising:

a module to index the information stored in the storage facility; and

a module to associate the indexed information with the unique, persistent, and universal name identifier so that the unique, persistent, and universal name identifier and indexed information can be identified by each other.

212. An apparatus, comprising:

a processor;

a memory, communicatively connected to the processor;

a program, stored in the memory, including,

a module to determine a prefix component of a unique, persistent, and universal name identifier automatically;

a module to effect the registration of the prefix component of a unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the prefix component is unique in the database, and wherein the prefix component may be used as a basis for registering subsequent unique, persistent, and universal name identifier s with unique suffixes.

213. The apparatus of claim 212, further comprising:

a module to receive metadata for said prefix component of a unique, persistent, and universal name identifier, wherein the metadata provides descriptive data regarding the prefix; and

a module to associate the prefix with the metadata so that the prefix and metadata can be identified by each other.

214. The apparatus of claim 212, wherein metadata is denied registration in a metadata database by user request for the unique, persistent, and universal name identifier to be unpublished.

215. An apparatus, comprising:

a processor;

a memory, communicatively connected to the processor;

a program, stored in the memory, including,

a module to generate, automatically, an instruction signal for a prefix component for a unique, persistent, and universal name identifier.

216. The apparatus of claim 215, further comprising:

a module to generate, automatically, an instruction signal for a suffix component for a unique, persistent, and universal name identifier.

217. The apparatus of claim 215, further comprising:

a module to generate, automatically, an instruction signal to allocate space for information for which the unique, persistent, and universal name identifier is being registered and making the location of the allocated space addressable and accessible over a communications network.

218. The apparatus of claim 217, further comprising:

a module to generate, automatically, an instruction signal to allocate space for information that is auctioned to a plurality of storage facilities for offers.

219. The apparatus of claim 217, further comprising:

a module to generate, automatically, an instruction signal to allocate space for information that is auctioned to a plurality of content distributors for offers.

220. The apparatus of claim 217, further comprising:

a module to generate, automatically, an instruction signal to allocate space for information solicits offers from a plurality of storage facilities.

221. The apparatus of claim 217, further comprising:

a module to generate, automatically, an instruction signal to allocate space for information solicits offers from a plurality of content distributors.

222. The apparatus of claim 215, further comprising:

a module to generate, automatically, an instruction signal to register the prefix component of a unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the prefix component is unique in the database, and wherein the prefix component may be used as a basis for registering subsequent unique, persistent, and universal name identifier s with unique suffixes.

223. The apparatus of claim 215, further comprising:

a module to generate, automatically, an instruction signal to register the unique, persistent, and universal name identifier in a database for resolving unique, persistent, and universal name identifier s and locations of associated information, wherein the unique, persistent, and universal name identifier is unique in the database.

224. An apparatus, comprising:

a processor;

a memory, communicatively connected to the processor;

a program, stored in the memory, including,

a module to generate, automatically, an instruction signal to register a unique, persistent, and universal name identifier; and

generate, automatically, an instruction signal to allocate space for information for which the unique, persistent, and universal name identifier is being registered and making the location of the allocated space addressable and accessible over a communications network.

225. The apparatus of claim 224, further comprising:

generate, automatically, an instruction signal with encoded information for which the unique, persistent, and universal name identifier is being registered.

226. The apparatus of claim 224, further comprising:

generate, automatically, an instruction signal with an encoded location for the information for which the unique, persistent, and universal name identifier is being registered.

227. The apparatus of claim 224, further comprising:

generate, automatically, an instruction signal for a prefix component for a unique, persistent, and universal name identifier.

228. An apparatus, comprising:

a processor;

a memory, communicatively connected to the processor;

a program, stored in the memory, including,

a module to specify desired information;

a module to specify a prefix for a unique, persistent, and universal name identifier;

a module to specify a suffix for a unique, persistent, and universal name identifier;

a module to specify a location for the desired information;

a module to effect the submission of any specified desired information, prefix, suffix, and location to a unique, persistent, and universal name identifier database for registration.

229. The apparatus of claim 228, wherein the specification of desired information is through a selection tool of a content authoring application providing access to information in the content authoring application through an application programming interface disposed in communication with an interaction interface.

230. The apparatus of claim 228, wherein the specification of desired information is through a file selection tool.

231. The apparatus of claim 228, wherein the specification of a prefix invokes a publisher registration tool.

232. The apparatus of claim 231, wherein a publisher registration tool provides fields for contact and billing information to be entered by a user.

233. The apparatus of claim 232, wherein the publisher provided fields for contact and billing information to be entered by a user are storable.

234. The apparatus of claim 228, wherein the specification of a prefix obtains stored publisher contact and billing information.

235. The apparatus of claim 234, wherein the stored publisher contact and billing information is to be stored in a cookie.

236. The apparatus of claim 234, wherein the stored publisher contact and billing information is to be stored in a preference file.

237. The apparatus of claim 234, wherein the stored publisher contact and billing information is to be stored in a database.

238. The apparatus of claim 228, further comprising:

a module to specify metadata.

239. The apparatus of claim 238, wherein the specification to effect submission is further configured to submit metadata to a metadata database to be associated with respective data submitted to the unique, persistent, and universal name identifier database.

240. The apparatus of claim 228, wherein the specification of a prefix sets a flag for automatically generating a prefix.

241. The apparatus of claim 228, wherein the specification of a suffix sets a flag for automatically generating a suffix.

242. The apparatus of claim 228, wherein the specification of a location is through a file selection tool.

243. The apparatus of claim 228, wherein the specification of a location is through a URL text field.

244. The apparatus of claim 228, wherein the specification to effect submission of data is through a button.

245. The apparatus of claim 228, wherein the specification to effect submission of data effects the registration of a unique, persistent, and universal name identifier for a document.

246. The apparatus of claim 228, wherein the specification to effect submission of data effects the registration of a unique, persistent, and universal name identifier for a selection of information.

247. The apparatus of claim 228, wherein the effectuation of the registration of a unique, persistent, and universal name identifier for a selection of information is automatic without further user interaction.

248. The apparatus of claim 228, wherein the specification to effect submission of data is through a menu.

249. The apparatus of claim 228, wherein the specification to effect submission of data imbeds identifying tags within the context of a selection of information.

250. The apparatus of claim 228, wherein the specification to effect submission of data imbeds identifying tags within a document.

251. The apparatus of claim 228, wherein the specification to effect submission of data stores a provisional unique, persistent, and universal name identifier.

252. The apparatus of claim 251, wherein the provisional unique, persistent, and universal name identifier is stored in a file.

253. The apparatus of claim 251, wherein the provisional unique, persistent, and universal name identifier is stored in a batch file.

255. The apparatus of claim 228, wherein the mechanism to effect submission of data stores a metadata for a provisional unique, persistent, and universal name identifier.

256. The apparatus of claim 255, wherein the stored metadata includes document information.

257. The apparatus of claim 256, wherein the document information includes the author of the document.

258. The apparatus of claim 256, wherein the document information includes the creation date of the document.

259. The apparatus of claim 256, wherein the document information includes the modification date of the document.

260. The apparatus of claim 256, wherein the document information includes corporation owning the document.

261. The apparatus of claim 256, wherein the document information includes automatic document generated values.

262. The apparatus of claim 261, wherein the automatic document generated values is include index information.

263. The apparatus of claim 261, wherein the automatic document generated values is table of contents information.

264. The apparatus of claim 261, wherein the automatic document generated values is glossary information.

254. The apparatus of claim 125185, wherein the provisional unique, persistent, and universal name identifier is stored in a database.

265. In memory, an interaction interface invocable by an application program responsive to user selections to invoke application module commands, comprising:

a selection interface mechanism to specify desired information;

an interaction interface mechanism to specify a prefix for a unique, persistent, and universal name identifier;

an interaction interface mechanism to specify a suffix for a unique, persistent, and universal name identifier;

an interaction interface mechanism to specify a location for the desired information;

an interaction interface mechanism to effect the submission of any specified desired information, prefix, suffix, and location to a unique, persistent, and universal name identifier database for registration; and

a display area to display any of the mechanisms.

266. The interface of claim 265, wherein the selection mechanism to specify desired information is a selection tool of a content authoring application providing access to information in the content authoring application through an application programming interface disposed in communication with the interaction interface.

267. The interface of claim 265, wherein the selection mechanism to specify desired information is a file selection tool.

268. The interface of claim 265, wherein the mechanism to specify a prefix invokes a publisher registration tool.

269. The interface of claim 268, wherein the publisher registration tool provides fields for contact and billing information to be entered by a user.

270. The interface of claim 269, wherein the publisher provided fields for contact and billing information to be entered by a user are storable.

271. The interface of claim 265, wherein the mechanism to specify a prefix obtains stored publisher contact and billing information.

272. The interface of claim 271, wherein the stored publisher contact and billing information is to be stored in a cookie.

273. The interface of claim 271, wherein the stored publisher contact and billing information is to be stored in a preference file.

274. The interface of claim 271, wherein the stored publisher contact and billing information is to be stored in a database.

275. The interface of claim 265, further comprising an interaction interface mechanism to specify metadata.

276. The interface of claim 275, wherein the interaction interface mechanism to effect submission is further configured to submit metadata to a metadata database to be associated with respective data submitted to the unique, persistent, and universal name identifier database.

277. The interface of claim 265, wherein the mechanism to specify a prefix sets a flag for automatically generating a prefix.

278. The interface of claim 265, wherein the mechanism to specify a suffix sets a flag for automatically generating a suffix.

279. The interface of claim 265, wherein the selection mechanism to specify a location is a file selection tool.

280. The interface of claim 265, wherein the selection mechanism to specify a location is a URL text field.

281. The interface of claim 265, wherein the mechanism to effect submission of data is a button.

282. The interface of claim 265, wherein the mechanism to effect submission of data effects the registration of a unique, persistent, and universal name identifier for a document.

283. The interface of claim 265, wherein the mechanism to effect submission of data effects the registration of a unique, persistent, and universal name identifier for a selection of information.

284. The interface of claim 265, wherein the affectation of the registration of a unique, persistent, and universal name identifier for a selection of information is automatic without further user interaction.

285. The interface of claim 265, wherein the mechanism to effect submission of data is a menu.

286. The interface of claim 265, wherein the mechanism to effect submission of data imbeds identifying tags within the context of a selection of information.

287. The interface of claim 265, wherein the mechanism to effect submission of data imbeds identifying tags within a document.

288. The interface of claim 265, wherein the mechanism to effect submission of data stores a provisional unique, persistent, and universal name identifier.

289. The interface of claim 288, wherein the provisional unique, persistent, and universal name identifier is stored in a file.

290. The interface of claim 288, wherein the provisional unique, persistent, and universal name identifier is stored in a batch file.

291. The interface of claim 288, wherein the provisional unique, persistent, and universal name identifier is stored in a database.

292. The interface of claim 265, wherein the mechanism to effect submission of data stores a metadata for a provisional unique, persistent, and universal name identifier.

293. The interface of claim 292, wherein the stored metadata includes document information.

294. The interface of claim 293, wherein the document information includes the author of the document.

295. The interface of claim 293, wherein the document information includes the creation date of the document.

296. The interface of claim 293, wherein the document information includes the modification date of the document.

297. The interface of claim 293, wherein the document information includes corporation owning the document.

298. The interface of claim 293, wherein the document information includes automatic document generated values.

299. The interface of claim 298, wherein the automatic document generated values is include index information.

300. The interface of claim 298, wherein the automatic document generated values is table of contents information.

301. The interface of claim 298, wherein the automatic document generated values is glossary information.