Today's Weblog Home  Weblog Index

The following section is under Copyright/License June 16, 2001 reserved to Jim Pivonka Consulting and James F. Pivonka, and otherwise reserved and assigned under the GNU Public License.

Specification for a fully indexed, pseudo relational list/outline.

  • Goal -- fully indexed (pseudo relational) bookmarks/favorites file
  • There is nothing new in the above, all it does is preserve the functionality of existing favorite/bookmark approaches.  Below is new; at least I have not seen an instance.
  • Definitions
  • An index data base contains an individual "elemental record" for each unique key and element.  The index data base contains records of a single record format, called the "elemental record".
  • The elemental record set "elements" or data elements:
  • The elemental record set "keys"
  • The elemental record set "names"
  • Other elemental record sets
  • Additional information maintained in the index data base may be either contained in data fields within "elemental records", which enlarges record size, or in additional elemental record sets accessed through pointers contained in the elemental records, which increases the number of records.  A well designed analytical engine will be able to adaptively modify the manner in which the information is maintained "on the fly" to optimize the index data base's overall performance.
  • An analytical engine (AE) parses the elements and keys and other "elemental records" in the index data base to produce the hierarchical representation of the listing/outline which is used by the GUI to represent the indexed data to the user.
  • The analytical engine parses user modifications to the GUI representation of the indexed data to produce the unitary "elemental records" for posting to the index data base. Unique "elemental records" are established by the analytical engine based on parsing of the user modifications to the index data base information as they relate to the preexisting information.
  • Synonyms - Since the analytical engine relies on the logical access path to the indexed information rather than the user supplied name for elements, it also provides for synonym identification and display in the GUI.  (This applies also to keys, should different key names refer to identical sets of subsidiary elements and keys.)
  • Additional features:  Secure encoding of data.  Availability as plugin to browsers.  Searchable and sortable by name/synonym; User defined keyword; date range.  Automated merging of lists/outlines, with elimination of full duplicates and identification of synonyms.  Automated identification and display of multiple references to indexed information.