tbl_entries:
* internal_entry_id
  title
  short_title ((for use in permalinks))
  summary
  <<categories>>
  <<contents>>
  time_posted ((yyyy-mm-dd HH:MM:SS))
  <<objects>>

tbl_categories:
* category_id
  parent_category_id
  name
  short_name

tbl_entries_to_categories:
* internal_entry_id
* category_id

tbl_object_types: ((write in a plugin style - so that to add new object types you can drop in 
                    a (tar.gz/zip?) file - the system could then install it on command))
* internal_object_type_id
  name
  short_name
  xml ((should contain all information needed to at least display the appropriate fields on a 
        "new entry" page - discuss later whether this should be binary or plain))

tbl_objects:
* internal_object_id
  name
  short_name
  object_type
  shared ((boolean - if true, this object should be made easily available to include on as 
           many entries as the user wants. Objects should still be able to be shared anyway,
           but this might make it easier to use.))
  <<fields>>

tbl_object_fields:
* internal_object_id
* internal_object_field_id
  field_contents ((probably just a plain text field - in MySQL, a LONGTEXT field.))

tbl_entries_to_objects:
* internal_entry_id
* internal_object_id
  inline ((boolean))
  order
  settings ((XML? A DTD might be needed.))
  ((objects will be able to be displayed either inline or as a separate section. If inline is 
    true, XML tags(?) of a form such as '<weblog:object shortName="picture" align="right" />' 
    will be replaced with the appropriate object. If inline is false, the object will be 
    displayed in the order given along with any other non-inline objects.))

======

tbl_shortcuts: ((used to alleviate typing. For example, '[[picture]]' might be replaced with 
                 '<weblog:object shortName="picture" align="clear" />'.))
  search_for ((can include wildcards and ways to remember values, probably parentheses))
  replace_with ((can include placeholders for the remembered values above))