Guidelines provide the methodological background for developing applications based on KPMs or UBMs from e-delos.com.

Conforming with this methodology entitles you to submit applications or plug-ins for integration in the e-delos repository. Be sure to also check the Specifications.

Guidelines go into three categories: 

This section provides a large number of rules that makes the e-delos modules virtually independant from the following components of the system : 

• Middleware
• SQL server
• HTTP Server
• XMLParser
• XSL interpreter
• any low level API

Delos-compliant data models heavily rely on thirteen normal forms, including five from Codd and eight from e-delos.com.

In a tutorial fashion, this section guides you through these forms, going all the way from a monolithic database structure to a pure Delos data model.

It does not only teach you the How, but also the Why.

XML rules help design robust, scalable, evolutive XML documents. 

XML Normal Forms inherits from Delos Normal Forms.

This section lists the XML state of the art development rules.

A complete e-delos server can feature numerous web-based applications. To reduce web server operations and maintenance, and to allow multiple e-delos servers to be run one machine, the e-delos team devised a specific directory structure.

This section details this structure very thoroughly.

Sometimes you wish experts were watching above you shoulder. In this section, they at least provide some of their know-how about issues you often run into when working with Delos data models.

Get information about proper use of identifiers, table inheritance and specialization, keys and constraints, views, field types, and more!

This section provides rules of thumb when deciding on names for data tables, join tables and fields. More generally, any entities in the data model.

Due to the profoundly rationalized structure of e-delos data models, it is important that you understand how such entities are to be named.

This section describes major universal information operator to describe data driven processes.

Universal operators are preventing programmers to invent their own way of processing information.