DDI Lifecycle: Moving Forward
Outcome of the Recent Workshop in Dagstuhl
Joachim Wackerow
• Will be model-based
– Easier to understand
– Better interaction with other disciplines and
standards
– Easier to develop and maintain in a consistent way
– Will enable more efficient software development
Why Now?
• After the experience of developing and using
the initial DDI-L structure
– We find continued improvement of the
development line is limited by the lack of a data
model
– Further, we are experiencing pressure for changes
from several directions at once
• new content from substantive working groups, which
requires new approaches to the design of the
specification.
NonDDI
Utility
DDI
Utility
Functional
DDI
Codebook
DDI
Document
Utility
DDI
Simple Data
Description
Core
Foundational
Non-DDI
DDI
Foundational
Metadata
DDI
Core
Non-DDI
Functions
DDI
Simple
Questionnaire
Modularized DDI Model
Deliverables
1. Completed model templates for the 4 identified functional
areas – In progress
2. First draft of common model documentation based on the
completed templates – In progress
3. Draft design and specification of production process – Done
4. Draft design principles for DDI work products In progress
5. Documentation of DDI Alliance workflows In progress
6. Draft XML syntax binding specification In progress
7. Draft RDF syntax binding specification Mostly done
8. Draft business rules specification for model transformations
In progress
9. Documentation of modeling style (includes UML profile)
In progress
Representations
• XML Schema / XML for exchange and
preservation
• OWL/RDF for exposure to Semantic Web /
Linked Data
• Frameworks
– Java/C#, … for processing
– DBMS for storage
• Data as a Service, Service Oriented
Architecture (SOA), Web services, REST
Timeline
•
•
•
•
•
•
•
•
Dagstuhl October 2012, 5 days
Dagstuhl October 2013, 5 days
EDDI – December 2013, 2 days
NADDI – April 2014, 5 days
IASSIST – June 2014, 5 days
Dagstuhl – October 2014, 5 days
Plus virtual meetings in between
Goal: First version of model March 31, 2015
DDI Versions
Version
Usage
Codebook 2.1/2.5
future versions only for maintenance
If Codebook features and available tools
cover requirements.
Lifecycle 3.1/3.2
future versions only for maintenance
If requirements are met by Lifecycle 3.*,
i.e. data lifecycle coverage is important.
RDF Discovery
future versions only for maintenance
If existing Codebook or Lifecycle 3.*
instances should be exposed to the
Semantic Web.
Lifecycle 4.0
additional features added to this version
If new software development is started
and stable specification packages are
available.
First packages expected in 2015.
Dagstuhl Workshop Participants
2012
2013
More Information
http://www.ddialliance.org/ddi-movingforward-process