Building a Hybrid Database Application for Structured Documents

 

  1. SGML & HyTime introduction
  2. Database-internal representation as the cornerstone of Böhm
  3. Extending database functionality through added identification scheme, indexing documents, document management, and conformance checking
  4. HyTime architecture and operations
  5. What were they thinking????

 

SGML and HyTime Introduction

 

  1. Standard Generalized MarkUp Language
  2. What is a DTD?
  3. Why is there a marriage between SGML and O-O design?
  4. How are documents managed?
  5. HyTime as an SGML application for defining document intra and inter-relations.

 

Database-internal representation as the cornerstone of Böhm

 

  1. Flat vs. Non-Flat element types
  2. Database object-identifier extended
  3. Transparent physical representation of document and type elements
  4. Supporting transparency and OID functionality

 

Extending Database Functionality

 

  1. Indexing documents
  2. Document management
  3. Conformance checking
  1. HyTime architecture and operations

 

What were they thinking????

 

  1. Building excess structure on top of structure
  2. Incomplete parser/application integration
  3. Hiding structure from the user-

    4. "On another level, to reduce checking on the instance level, it seems advantageous to derive recommendations to the DTD-designer that correspond directly to such restrictions in the standard."

  4. There is no "generic" document

 

Discussion Questions

 

  1. How are SGML, HyTime, and O-O Design linked?
  2. What is the purpose of Böhm’s database-internal representation? What does it assume about the user?
  3. How does the extension of the VODAK system go beyond "normal" OODBMS?
  4. Why does Böhm continually invest himself in the "non-flat" data representaion?