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


During execution ProcessSteps follow one another over time. This is also true when we parallelize because within each thread work flows. In every thread during execution we advance through a sequence of pairs. Each pair has a "prev" and a "cur". In the course of execution "cur" becomes "prev" and a new "cur" comes along.

In this context the Execution Pair is the current "prev" and "cur".



Event associated with the observation


Non-empty set of dimensions functioning as a key in a Datum Structure


Unit identifier in a Datum Structure.


Identifier of the Datum Structure. It can be defined either by a Unit or a set of Dimensions.




This view includes the core set of objects required to describe a methodology. Based on the model developed at the Minneapolis sprint, detailed at:


Subscribe to DDI Moving Forward RSS