DRAFT -- September 20, 1988 9:53:03 am PDT -- DRAFT
Internal Memo

XEROX
To    From
Distribution    Bob Hagmann
    PARC/CSL





Subject    Date
Yggdrasil Documentation Structure    September 20, 1988


Yggdrasil Glossary
Filed as YggdrasilGlossary.tioga
Overall system plan
Filed as YggdrasilOverallSystemPlan.tioga
Implementation plan
Implementation staging
Future options
Implementation Phase 1 Plan
Filed as YggdrasilPhase1Plan.tioga
Development and Execution Environments
Filed as YggdrasilEnvironments.tioga
Language
Hardware
Operating System and Programming Environment
Communications and protocols
Hardware, OS, and Programming Environment Options
Data Model
Filed as YggdrasilDataModel.tioga
[Is this covered enough in the Yggdrasi Data Model memo?  Is all we need is an implementation scheme to implement what the memo 
calls for?]
Objects
Links
Containers and children
Naming
Versions and Alternatives
Attributes and Keywords
Indices
Primitive Types
Surrogates
Storage
Filed as YggdrasilStorageDesign.tioga
Introduction
Requirements
General description
Object manager buffering policy
Object representations
Interoperation of optical disk subsystem with full system
Magnetic disk page allocator and clustering
Naming
Garbage collection
Versions and alternatives
Index data structures
Data compression
Scavenger
Replication
Frontend backup
DID map
Document Update
Filed as YggdrasilDocumentUpdate.tioga
Introduction
The big picture
Concurrency Control and Crash Recovery
Filed as YggdrasilCCandCR.tioga
Requirements
Transactions, services and clusters
Locking
Alerters
Logging
Checkpoint
Fast restart
Interrelationship with archive
Snapshot backup
Incremental backup
Faking mirrored disks - parity disks
Multi-server and foreign server support
Access Control
Access Control
f  Access control lists?  How are they done for unnamed objects?
f  Is protection done on the objects or on the access paths (e. g., links)?
Authentication
f  There has to be a secure environment in which the server operates.  Thus, there must be security on the communications.
System Features
Performance
hints
caching
buffering
storage hierarchy
Robust
Availability and replication
Queries
Query language
Query optimizer
Administration
Debugging
Backup
Historical logging
Monitoring
Issues (general)
f  Legal requirements for documents (write once in proper time order)
f  Standards (character set, naming, ...)
f  Private changes to public data (e.g., private annotation or link)