Yukatan data model project defines the schema for the webmail database.
The Yukatan data model project serves as the schema definition for the Yukatan webmail database. The PostgreSQL structures outlined in this file can function as a backend store for email message applications. For proper handling of messages in different languages, it is recommended that the database be configured with Unicode encoding.
To make the field semantics more explicit, the introduction of seven new domains has been made. The related COMMENT statements further clarify the use of these domains. Refer to the SQL schema file for more detailed documentation on these domains.
All the table constraints in the database are now explicitly named and documented, leading to an improved database implementation that is more organized and well-documented. To enhance clarity and reduce repetitiveness, all the *address field names have been shortened to *addr. Additionally, the referencesfield table is now named referencefield to eliminate the plural form in the table name. The contained references* field names have likewise been renamed to reference*.
Several changes have been made to the semantics of various fields. For instance, the unnecessarily tight constraints on sequence numbers have been replaced with clear documentation. The format and encoding of most fields are now explicitly documented, and the previous dual use of the enttext and enddata fields has been prohibited.
In Version 1.0, the envelope data added in Version 0.5 of the data model has been removed. Envelope data is not considered an integral part of an email message, and the goal was to keep Version 1.0 as clear as possible. The database now exclusively stores email messages, and envelope data may be reintroduced in an incremental Version 1.x along with other extensions.
This updated release cleans up and documents the data model that has developed since Version 0.1. The renaming and redefinition of some fields and tables, and the extensive documentation of the database structure, has resulted in a more user-friendly and streamlined experience.
To make the field semantics more explicit, the introduction of seven new domains has been made. The related COMMENT statements further clarify the use of these domains. Refer to the SQL schema file for more detailed documentation on these domains.
All the table constraints in the database are now explicitly named and documented, leading to an improved database implementation that is more organized and well-documented. To enhance clarity and reduce repetitiveness, all the *address field names have been shortened to *addr. Additionally, the referencesfield table is now named referencefield to eliminate the plural form in the table name. The contained references* field names have likewise been renamed to reference*.
Several changes have been made to the semantics of various fields. For instance, the unnecessarily tight constraints on sequence numbers have been replaced with clear documentation. The format and encoding of most fields are now explicitly documented, and the previous dual use of the enttext and enddata fields has been prohibited.
In Version 1.0, the envelope data added in Version 0.5 of the data model has been removed. Envelope data is not considered an integral part of an email message, and the goal was to keep Version 1.0 as clear as possible. The database now exclusively stores email messages, and envelope data may be reintroduced in an incremental Version 1.x along with other extensions.
This updated release cleans up and documents the data model that has developed since Version 0.1. The renaming and redefinition of some fields and tables, and the extensive documentation of the database structure, has resulted in a more user-friendly and streamlined experience.
What's New
Version 1.0: N/A