Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panelwarning

WORK IN PROGRESS

Section
This page provides coverage information for the DDI 4 Q2 2016 Development Draft Review plus links to the following:
  • Status report on each review document
  • Link to the review package
  • Link to the comment form
  • Link to the DDI 4 Drupal site
  • Link back to GENERAL REVIEW information and useful documents 
Warning
titleSpecial Instructions for this review:

Read this document BEFORE reviewing

Panel
green
borderColortitlePrototype Documents - not in LION

Goals of DDI 4 (Why DDI 4) - Outline of important goals for the model-based standard

What's New in DDI 4 - (section on patterns is forthcoming) combined sections on functional views, plugging into the model, the variable cascade, and more. 

Examples (forthcoming) - XML examples for each functional view. 

List of packages, functional views, and use cases to be included in the prototype.

Image Added

Panel
borderColorred
borderWidth1
borderStylesolid
titleData Capture Issues

Jira Legacy
serverSystem JIRA
columnskey,summary,status
maximumIssues1000
jqlQueryproject = "Technical Committee" AND labels = data_capture AND labels = prototype
serverIdb62a0bb6-d990-3186-ba9e-0c3828bdee04


Panel
borderColorred
borderWidth1
borderStylesolid
titleLibrary Packages and Functional Views in Release

NEW Library Packages

Functional Views

Previous Library Packages

(Note these will have changed from 2015 Q1)

Collections Pattern

Agent Registry

Agents (revised using Collections Pattern)

Complex Process

Data Dictionary

Collections (renamed Collections Pattern)

Custom Metadata

Statistical Classification

Complex Data Types

Data Capture

Instrument

Conceptual

Format Description

Core Process

Logical Data Description

Discovery

Methodologies

Identification

Methodology Pattern

Primitives

Process Pattern

Representations

Segment Location Specifications

Utility

Signification Pattern

Workflows 
 
Packaging Issues

Jira Legacy
serverSystem JIRA
columnskey,summary,status
maximumIssues1000
jqlQueryproject = "Technical Committee" AND labels = packaging AND labels = prototype
serverIdb62a0bb6-d990-3186-ba9e-0c3828bdee04


Panel
borderColorred
borderWidth1
borderStylesolid
titlePatterns Issues

Jira Legacy
serverSystem JIRA
columnskey,summary,status
maximumIssues1000
jqlQueryproject = "Technical Committee" AND labels = patterns AND labels = prototype
serverIdb62a0bb6-d990-3186-ba9e-0c3828bdee04


Panel
borderColorred
borderWidth1
borderStylesolid
titleSpecial Modification Issues:

Modeling Team Open Issues:

·         Logical Data Description and Format Description have been placed in review as received from the Data Description working group without additional review by the Modeling Team.

·         The Methodology Pattern has been placed in review without a specific instantiated application. Methodology Pattern will be found only in the model, not in the XML Bindings as its classes are all abstract. Several instantiations of this pattern are anticipated in the upcoming special Codebook Release.

·         The interaction of Patterns (Collection, Process, Methodology, and Signification) is still under discussion. In particular, questions about combining Methodology and Process Patterns and the detail of content within classes belonging to a pattern are still being discussed. Comments and recommendations are welcome. As this is resolved the Modeling Team will provide a high level document providing a bird’s eye view of the conceptual framework of DDI, how the patterns interact, and how the patterns work together to express similar relationship patterns within different areas and applications of DDI.

·         Data Capture and Instrument View provide a design-time example of the Process pattern. We are working on a run-time example within the broader needs of a run time layer that provides actual run time binding, plus action logs, variation from design etc. This is part of the temporal perspectives talked about before (looking forward/design, execution/run, looking backward/what took place). This plays into the issue of capturing processing provenance as well as paradata during data capture operations.

·         The Service class in the Process Pattern will not talk about time. This will appear in the concrete class that realizes Service. There are three applications of time: Effective time (Availability), Historic time, and Expected Time. Look at estimatedDuration in the WorkflowService object.

·         Service does not relate correctly to Process Step. Leave as an open issue. Service needs a more complete review, but we should wait until we see how people implement it (regarding what properties they need.) There are also issues with the relationship between process step and service including the directionality of the relationship and the use of internal controlled vocabularies.

·         Should the Variable Cascade approach be replicated for forms of capture such as Questions? Is there a parallel in terms of comparison and reuse? If InstanceQuestion inherits from RepresentedQuestion it would solve the current issue of requiring the creation of both a RepresentedQuestion and an InstanceQuestion.

·         The Variable Cascade has been modified since the last development release and should be reviewed carefully.

Data Description (Logical Data Description, Format Description) Open Issues:

·         Only limited physical formats are currently described (Fixed Format and CSV). Development of other formats may include additional properties for PhysicalLayout, ValueMapping, and ValueAndConceptDescription.

·         Datum and its consequences are still being worked out. It expands the scope of DDI from the record into the actual datum (observation) and allows for support of datum specific paradata and viewpoints.  

Tip

Status Report

Warning

Link to Review Package

Package based on Build #501

HTML DOCUMENTATION

PDF DOCUMENTATION

PDF of documentation is now available! Click on the link above. – Technical Committee

Tip
titleENTER A COMMENT

Follow the link "submit comment" to the issue tracking page for this release. Click on "CREATE" in the top banner and following the instructions.

IN THE SUMMERY LINE: Please enter the name of the document you are commenting on, a page number, and section and/or object name.

PLEASE submit a separate comment for each issue.

Please note your name and email at the beginning of the description

SUBMIT COMMENT

Tip

Link to Drupal development site

NOTE: Drupal is a development site so may reflect changes made AFTER the generation of the build used for the review. Some changes will be the result of review issue resolution, others the result of continued development work.

  

Info
titleLibrary Package

In DDI 4, a group of classes within the Library related by a theme. The Class Library for DDI 4 encompasses the entire DDI 4.0 model, but without any specific schemas or vocabularies for Functional Views. Classes contain primitives and extended primitives and are the building blocks used to construct the Functional Views.

Info
titleFunctional View
 In DDI 4, a functional view identifies a set of classes that are needed to perform a specific task. It primarily consists of a set of references to specific versions of classes. Functional views are the method used to restrict the portions of the model that are used, and as such they function very much like DDI profiles in DDI 3.*.
   

Jira Legacy
serverSystem JIRA
columnskey,summary,status
maximumIssues1000
jqlQueryproject = "Technical Committee" AND labels = modification AND labels = prototype
serverIdb62a0bb6-d990-3186-ba9e-0c3828bdee04


Panel
borderColorred
borderWidth1
borderStylesolid
titleTechnical Issues

Jira Legacy
serverSystem JIRA
columnskey,summary,status
maximumIssues1000
jqlQueryproject = "Technical Committee" AND labels = technical AND labels = prototype
serverIdb62a0bb6-d990-3186-ba9e-0c3828bdee04


Panel
borderColorred
borderWidth1
borderStylesolid
titleClass Functionality Issues

Jira Legacy
serverSystem JIRA
columnskey,summary,status
maximumIssues1000
jqlQueryproject = "Technical Committee" AND labels = class_function AND labels = prototype
serverIdb62a0bb6-d990-3186-ba9e-0c3828bdee04


Panel
borderColorred
borderWidth1
borderStylesolid
titleNaming Issues

Jira Legacy
serverSystem JIRA
columnskey,summary,status
maximumIssues1000
jqlQueryproject = "Technical Committee" AND labels = naming AND labels = prototype
serverIdb62a0bb6-d990-3186-ba9e-0c3828bdee04


Panel
borderColorred
borderWidth1
borderStylesolid
titleConsistency Issues

Jira Legacy
serverSystem JIRA
columnskey,summary,status
maximumIssues1000
jqlQueryproject = "Technical Committee" AND labels = consistency
serverIdb62a0bb6-d990-3186-ba9e-0c3828bdee04






Tip

Link to Drupal development site


Panel
titleIntegrity Check Criteria:

Review Technical Committee Review Coverage items to ensure modeling rules have been adhered to.


Structural Package Content Review:

  • use of primitives and complex data types
  • use of annotation and contents
  • use of appropriate cardinalities
  • use of identifiable and annotatedIdentifiable
  • consistency in class structure: property usage, pattern structure, pattern realization, documentation within a class
  • verify that design principles are followed

Functional View Content Review:

  • content of a functional view
  • documentation of a functional view


Panel
borderColorgray
borderWidth1
borderStylesolid
titleUseful background documents:



Contact Information:

For questions regarding the review process please contact the Technical Committee list ddi-srg@icpsr.umich.edu or the Technical Committee Chair, Wendy Thomas wlt@umn.edu

...