Added automatic builds
Each day a ZIP-file is created via cron.
The builds consist of XMI, XSD, DocBook, PDF and graphs in dot, svg and png.
Added basic validation for names
installed module for validation, some rules for object and package names have been defined.
Added help for creating and managing the model
Guidelines for naming and propeties.
Added stage-tagging for objects
Re-arranged "Status" and added field for Stage, filter added on objects page.
Changes for Datatype
Datatype taxonomy is replaced by a datatype content type, to create a new one go to /node/add/datatype. You can specify basic documentation of the datatype and specify enumerated values. A datatype must be placed in a package.

Welcome to the development platform for the next generation of DDI

The DDI Alliance is building a new model-based specification, for more information on the background to this see, the process and what we hope to achieve see the DDI Alliance website at

A site to hold discussions and further ongoing discussion is at


The number of characters by which a DataPoint is represented in a physical layout.


The pair of Datapoints in a record which are being placed in a sequence.


A realization of OrderRelation that is used to describe the sequence of Datapoints in a record.


The current version of DDI 4 used in the binding. Set value.


The CubeLayout supports the description of the structure of aggregate data, and how it may be linked to the microdata of which it is a cross-tabulation.


RectangularLayout supports the description of unit-record ("wide") data sets, where each row in the data set provides a group of values for variables all relating to a single unit. The columns will contain data relating to the values for a single variable.


The EventLayout exists to permit the description of data stored in a "tall" dataset format. For event data typically each row in the dataset will contain a single data point's value, a unit identifier, a reference to a variable, a start time, and end time, and a datatype (that of the referenced variable).


The RecordRelation object is used to indicate relationships among record types within and between datasets. For InstanceVariables existing in a data set with multiple record layouts, pairs of InstanceVariables may function as paired keys to permit the expression of hierarchical links between records of different types. These links between keys in different record types could also be used to link records in a relational structure.


The PhysicalLayout is an abstract class used as an extension point in the description of the different layout styles of data structure description. Examples include rectangular layouts, event data layouts, and cube layouts (e.g. summary data).


Subscribe to DDI Moving Forward RSS