Issues

Relationship question - mode of data collection needed

Relationship Question to (sub)-universe needed

Cardinality in ResponseDomain intendedRepresentation is currently 0..1 source and 0..n target

Mapping concepts between variables and Capture

Language of the Instrument for a Study is missing

How to attach a note to a question that is used in different studies

Unclear usage of ExternalAid and ExternalMaterial for ShowCard

Mode of Instrument should be explicit defined

Complete modeling of Response Domains

Identify missing content needed to support priority use cases in Prototype 2018-06

Why does CodelistResponseDomain have a separate Codelist?

connecting Capture to ConceptualVariable

How can a compound question be modeled?

In Boolean response domain – what does the category do?

Mode of Collection

Update the Instrument View contents after any revisions have been made to model

Is separation of instrument and internal processing assumed to be separate?

The term "Capture" can be misinterpreted

Sentinal domains in Represented Questions

Need the ability to link from a specific represented variable through response domain to a specific represented question

What is the purpose of Workflows?

Recent edit to Process included only a general "hasParameter"

Instrument View - various

Instrument view - relationship between question and concept (design level)

Revisit QuestionGrid and QuestionBlock discussion as it relates to the newly created Response Domains

RankingResponseDomain needs to be modeled.

RankingDomain - recommend creating a ranking group that ranking domains will link to.

ScaleResponseDomain needs to be modeled.

Wolfgang's question about attaching category to booleanResponseDomain.

How do we manage missing representation?

Should we add intendedRepresentation to ResponseDomain

What to do about multiple selection on code list response domain

How do we create enumerations in Drupal? i.e. classificationLevel 'nominal', 'ordinal', 'interval', etc. Do we even need these?

NumberRange does not need to be annotated or identifiable.

Need to add OutParameters to the response domain when it's complete

Do we need classificationLevel as a property in the NumericResponseDomain?

Where to put intendedRepresentation

We need a touch point between data capture and analysis (exists as a GenerationInstruction in DDI 3.2) to capture derived and other transformations.

WorkflowSequence should have a clear beginning and end point

Binding should be updated.

Binding - Target Objects - InputParameter and OutputParameter should be 0..1

Command definition needs to be updated

structuredCommand is very XML centric in its description and the way it is used.

CommandCode definition needs to be updated

IfThenElse - the final elseContains should be 0..1 - only one else available

ControlConstruct should not contain a WorkflowStep

Elseif cardinality should be 0..n not 1..1.

ElseIf should not be identified or annotated and should not derive from ConditionalControlConstruct

workflowSteps should have bindings